mbouchard Posted May 10, 2005 Share Posted May 10, 2005 I finally received a copy of 2005 and am in the process of testing the ram drive boot option. Following the instructions in the help file I:1) Created and tested my initial WinPE iso2) Created the folder structure as specified (c:\ramdisk)3) Copied bootfix.bin, ntdetect.com, and setupldr.bin to the c:\ramdisk\i386 folder. 4) Created the Winnt.sif file and placed it in the c:\ramdisk. 5) Created the iso When I attempt to boot to it but get this error:inf File txtsetup.sif is corrupt or missing, status 14Setup cannot continue. Press any key to exit.Am I missing a step? Link to comment Share on other sites More sharing options...
getwired Posted May 10, 2005 Share Posted May 10, 2005 I didn't see the step there where you build the ISO that goes inside - the one that becomes the RAMDisk? Did you do that? Does your winnt.sif point to it? Link to comment Share on other sites More sharing options...
mbouchard Posted May 10, 2005 Author Share Posted May 10, 2005 I didn't see the step there where you build the ISO that goes inside - the one that becomes the RAMDisk? Did you do that? Does your winnt.sif point to it?<{POST_SNAPBACK}>Did this in step 1.1) Created and tested my initial WinPE isoHere is my Winnt.sif, basically copied what was in the chm.[setupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe2005.iso"The winPE2005.iso is in the root of the ramdisk folder Link to comment Share on other sites More sharing options...
getwired Posted May 10, 2005 Share Posted May 10, 2005 Duh. My bad. The ISO is at the root of the CD, and is called winpe2005.iso? Have you done any file removal, and was Server 2003 SP1 your source?So at the root of your ISO, you should have an I386 directory with the three boot files, and then winnt.sif and winpe2005.iso. Is that what you have?One other thing - in the example I have working, there is also one more line under [setupData] - Architecture = "I386"Do you have that as well? Link to comment Share on other sites More sharing options...
mbouchard Posted May 11, 2005 Author Share Posted May 11, 2005 Yes, at the root I have the ISO, i386 directory with the 3 files, and the winnt.sif.I had the line Architecture="i386" in there when I first created it, but removed it when I attempted to recreate the iso.Taken from the chm:The Architecture entry must be present for x64 computers. For i386 computers, you can omit this entry or ensure that the value of the Architecture entry equals i386. I created the ISO on a 2003 std server with SP1 installed. Link to comment Share on other sites More sharing options...
mats Posted May 12, 2005 Share Posted May 12, 2005 Either we are two that can't read the chm or they got a problem. If you copy winnt.sif to txtsetup.sif it finds the sif but then it can't access the ramdrive Link to comment Share on other sites More sharing options...
getwired Posted May 12, 2005 Share Posted May 12, 2005 Weird - it works perfectly for me... :-/ Link to comment Share on other sites More sharing options...
mats Posted May 12, 2005 Share Posted May 12, 2005 Oki kan you post a dir of your build directory for the iso and the content of winnt.sif? I think that should be the easiest way to nail any differences Link to comment Share on other sites More sharing options...
mbouchard Posted May 16, 2005 Author Share Posted May 16, 2005 Folder structure is such:C:\RamDrive Winnt.Sif WinPE2005.isoC:\RamDrive\i386 Bootfix.bin Ntdetect.com Setupldr.binIn the Sif [setupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe2005.iso"At the suggestion of someone else, I moved all the files in the i386 to the root folder. I didn't get the error anymore but nothing happened on the VirtualPC that I tested the iso on, black screen only. Havn't burned a CD yet but plan to do so today. Link to comment Share on other sites More sharing options...
mats Posted May 16, 2005 Share Posted May 16, 2005 Oki I had placed my sif in the i386 folder and that's why it failed for meCurrent structure c:\work winnt.sif test1.isoc:\work\i386 bootfix.bin ntdetect.com setupldr.binand the content of the sif is:[setupData]BootDevice = "ramdisk(0)"BootPath = "\i386\System32\"OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=test1.iso"Architecture = "i386" Link to comment Share on other sites More sharing options...
Radimus Posted June 30, 2005 Share Posted June 30, 2005 and how are you assembling the final ISO?Have you tried this on a DVD? Link to comment Share on other sites More sharing options...
JuMz Posted June 30, 2005 Share Posted June 30, 2005 What are the advantages / disadvantages of using this method, VS using regular WinPE boot and launching winnt32 from there (unattended of course)? Just wondering. Link to comment Share on other sites More sharing options...
Br4tt3 Posted July 1, 2005 Share Posted July 1, 2005 I would say that i allows u to change the removable media if that is the source of installation, nice feature if u only have a CD and not a DVD unite....and RAM is somewhat faster when performing file copy sequences then performed from a CD for example.. then again, takes longer to load the .iso into RAM also.Otherwise, it is just show off... Link to comment Share on other sites More sharing options...
mats Posted July 1, 2005 Share Posted July 1, 2005 There is a killer function in this too.Try PXE on a 10 Mbit network. Some nics will need up to 30 min. to boot, with ramdisk, they do it in 5. Link to comment Share on other sites More sharing options...
Perdu Posted May 18, 2006 Share Posted May 18, 2006 Just one small question...did you start from a FAT16 partition, FAT32 or NTFSCause in my case it doesn't work;Or i receive "Non system Disk"or I/O read errorHow did you format the disk...Cause i've followed all said heere and no way while it works if i boot pe from a CD, format it in NTFS and copy all the files...Thanks for helping Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now