VistaPE CD Will Not Boot
#1
Posted 03 May 2007 - 09:32 PM
Windows failed to start...
File: \windows\system32\boot\winload.exe
Status: 0xc0000001
Info: The selected entry could not be loaded because the application is missing or corrupt.
I have built the ISO 3 times - once using a Vista Business upgrade DVD as the source and twice using the WAIK as the source. I also changed the Preconfig Script to ImageX on the last build. Am I missing something? Any ideas?
#2
Posted 04 May 2007 - 03:01 AM
WIMFSF.SYS
Page_Fault_In_Nonpaged_Area
Stop 0x00000050
I tried booting the CD in multiple systems with the same error.
#3
Posted 04 May 2007 - 08:43 AM
Try using a base path like c:\vistape
What is the difference between "Vista Business upgrade DVD" and a regular install DVD?
Can it also be used to install Vista from scratch?
Good luck!
#4
Posted 04 May 2007 - 08:43 AM
Log please ...
Do you use boot.wim? "Finalizing" -> "Pack boot.wim"
#5
Posted 04 May 2007 - 03:16 PM
My base path has been either D:\VistaPE or D:\WinBuilder (I tried both). I will try it on C: and see what I get.
Also, I do use the "pack boot.wim" option. I'll post the results from using C:\VistaPE as my base folder soon...
Thanks guys.
Attached Files
#6
Posted 04 May 2007 - 03:25 PM
Just to ensure that it's not a program interfering with your tests, haven't noticed any detail out of the usual, but then again I'm not very experienced with VistaPE, hope others can also help you debugging this matter.
#7
Posted 04 May 2007 - 04:11 PM
1. I moved my base folder to C:\VistaPE.
2. Source was originally in %baseDir%\Source - now it is in a completely separate base folder.
So, it works but I don't know which of these 2 changes made a difference. I did not remove any applications or make any other changes.
Thanks for the help and let me know if you need any more info from me for testing...
#8
Posted 04 May 2007 - 04:15 PM
Are you working in a FAT32 partition? If so, your problem may be solved by moving the files to an NTFS partition.When I try to boot up I get the following:
Windows failed to start...
File: \windows\system32\boot\winload.exe
Status: 0xc0000001
Info: The selected entry could not be loaded because the application is missing or corrupt.
I have had this myself, and this cured it.
#9
Posted 04 May 2007 - 04:15 PM
It would be very usefull if you could continue testing to see which step gives the erroneous results and maybe this way help others - or even fix-up the needed scripts.
Have you also disabled the programs or built with all of them included?
#10
Posted 04 May 2007 - 05:06 PM
#11
Posted 04 May 2007 - 05:40 PM
Thanks again for the help...
#12
Posted 05 May 2007 - 04:10 PM
Yes, but what is the difference between your C: and D: drives? Is one formatted as FAT and the other as NTFS?Finally finished my last build. I have narrowed the problem down to having the base directory on D: instead of C:
#13
Posted 05 May 2007 - 10:38 PM
Dell Latitude D820
- 100GB SATA Drive
- 2 Partitions
- C: and D: are both NTFS
- Running Vista Business
Dell Optiplex GX270
- 80GB IDE - C: and D: - C: is NTFS, D: is FAT32
- 40GB IDE - E: - storage for ISO file
- Running XP SP2
I do have another system that is a home built Pentium D with multiple drives. I may have time this weekend to try to build an ISO on that one. If so, I will post the results.
Is there any other info that you need?
#14
Posted 06 May 2007 - 12:39 AM
#15
Posted 06 May 2007 - 01:15 PM
The best explanation that I can give for your winload.exe problem is that the imagex /capture command does not appear to work on a FAT32 drive, although it does on an NTFS drive. VistaPE calls this command in the [PackBoot] section of Standard-6-Finalizing.script.
So, when your %baseDir% was on a FAT32 drive, you had the problem, but when you moved to an NTFS drive, it went away.
The moral is: always use NTFS when building VistaPE!
#16
Posted 06 May 2007 - 07:58 PM
You can mount a .wim file with read/write permissions only on an NTFS file system. This avoids the 2-gigabyte (GB) barrier imposed by FAT file systems and prevents data loss that is possible with FAT or other non-NTFS file systems.
Note:
Although ImageX can mount a .wim file with read/write permissions only from an NTFS file system, you can mount your image as read-only from NTFS, FAT, ISO, and UDF file systems. You cannot save changes to the image file while it is mounted as read-only.
#17
Posted 06 May 2007 - 09:18 PM
#18
Posted 10 June 2007 - 06:28 AM
#19
Posted 17 June 2008 - 09:07 PM
From the WIndows AIK docs:
You can mount a .wim file with read/write permissions only on an NTFS file system. This avoids the 2-gigabyte (GB) barrier imposed by FAT file systems and prevents data loss that is possible with FAT or other non-NTFS file systems.
Note:
Although ImageX can mount a .wim file with read/write permissions only from an NTFS file system, you can mount your image as read-only from NTFS, FAT, ISO, and UDF file systems. You cannot save changes to the image file while it is mounted as read-only.
I am able to mount a .wim file for editing on a fat32 file system..
I use the following command...
imagex /mountrw c:\winpe\*.wim 1 c:\winpe\mount
where *.wim = the wim being edited and c:\winpe\mount is the mountpoint
make sure when doing changes to do the following
imagex /unmount /commit c:\winpe\mount
where c:\winpe\mount is the mountpoint..
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users