cdob Posted April 12, 2010 Author Share Posted April 12, 2010 OEM (Dell)Help, a Dell USB BIOS.i see my USB-HDD isn't assigned with any drive letter ...why ?It's a Dell?Which hardware do you use?Open txtsetup.oem and activate fixBoot.USB, delete a comment:;set USB drivers start=0 - nonsense?dll = setup, fixBoot.USBThis reminds me the same issues as in here:http://www.msfn.org/board/install-2000xp2003-loaded-small-t139737-page-20.htmlTime for similar workaroundsService start=0 is included, but not activated by default.adjusted txtsetup.sif and/or use of mnt.exe?Unforutnately I can't test partiticular behaviour. Or you have something new in your magic sleeves?A old one: early USB PNP, Post #837 http://www.msfn.org/board/install-winsetupfromusb-t120444-pid-906043.html/page__view__findpost__p__906043 Link to comment Share on other sites More sharing options...
iosha789 Posted April 13, 2010 Share Posted April 13, 2010 (edited) Thanks in best cdob and ilko_t i have success to install Windows XP from ISO-in my USB-HDD ! Thanks so much !!!Open txtsetup.oem and activate fixBoot.USB, delete a comment:;set USB drivers start=0 - nonsense?dll = setup, fixBoot.USBYes........it successfully to install Windows XP without any error ! Edited April 13, 2010 by iosha789 Link to comment Share on other sites More sharing options...
cdob Posted April 13, 2010 Author Share Posted April 13, 2010 i have success to install Windows XP from ISO-in my USB-HDDCongratulations.Which hardware do you use? Which BIOS require the USB boot fix?Can you try a updated setup.cmd?Remove fixBoot.USB at txtsetup.oem.Setup.cmd should add fix boot autmatic.setup.7z Link to comment Share on other sites More sharing options...
iosha789 Posted April 14, 2010 Share Posted April 14, 2010 i have success to install Windows XP from ISO-in my USB-HDDCongratulations.Which hardware do you use? Which BIOS require the USB boot fix?Can you try a updated setup.cmd?Remove fixBoot.USB at txtsetup.oem.Setup.cmd should add fix boot autmatic.Thanks for support !I used a normal Hardware with:Main: ASUS P5KPL-CMBIOS: AMI v.0606 - Build date: 03/11/09RAM: 2.5GB SAMSUNG(2GB)+KINGMAX(512MB)HDD: Seagate 80GBUSB-HDD: Seagate 250GB with Transcend box 2.5"Yes ! I'll try and give a result as soon as possible !Thanks cdob. Have nice day ! Link to comment Share on other sites More sharing options...
iosha789 Posted May 8, 2010 Share Posted May 8, 2010 i have success to install Windows XP from ISO-in my USB-HDDCongratulations.Which hardware do you use? Which BIOS require the USB boot fix?Can you try a updated setup.cmd?Remove fixBoot.USB at txtsetup.oem.Setup.cmd should add fix boot autmatic.Thanks for support !I used a normal Hardware with:Main: ASUS P5KPL-CMBIOS: AMI v.0606 - Build date: 03/11/09RAM: 2.5GB SAMSUNG(2GB)+KINGMAX(512MB)HDD: Seagate 80GBUSB-HDD: Seagate 250GB with Transcend box 2.5"Yes ! I'll try and give a result as soon as possible !Thanks cdob. Have nice day !Hi again ! I have a problem with install Windows 2003. It give a error [b]Warning ! Invalid first FAT entry (=0x0)!chainloader (0x0ff)/I386/SETUPLDR.BINError 15: File not foundpress any key to continue...[/b]But with the same method i installed successfully Windows XP...Can somebody give me some advice please !Thanks in advanced....sorry because my English is so bad ! Link to comment Share on other sites More sharing options...
ilko_t Posted May 8, 2010 Share Posted May 8, 2010 0x0ff should be 0xff.In addition- I don't think firadisk driver will work on 2003 setup, at least last versions I've tested did not. Most likely you will get BSOD 0x7B. But please, test and report back, including firadisk driver version. Link to comment Share on other sites More sharing options...
iosha789 Posted May 12, 2010 Share Posted May 12, 2010 0x0ff should be 0xff.In addition- I don't think firadisk driver will work on 2003 setup, at least last versions I've tested did not. Most likely you will get BSOD 0x7B. But please, test and report back, including firadisk driver version.Sorry because my English so bad !!!!Thanks ilko_t for fast replay ! I'm so sorry for late !It's my mistake in config of grub4dos....today i fixed and the process load ISO image is success....but then Windows will dump....I used firadisk v0.0.1.12 Link to comment Share on other sites More sharing options...
jaclaz Posted May 12, 2010 Share Posted May 12, 2010 I used firadisk v0.0.1.12Try LATEST:http://www.boot-land.net/forums/index.php?showtopic=8804&st=0&start=00.0.1.18 right now.@ilkoSince you have some machines that do work with firadisk and some that won't, have you had a chance to test WinVblock?http://www.boot-land.net/forums/index.php?showtopic=8168Maybe it works with 2K3 on the "pesky" ones? jaclaz Link to comment Share on other sites More sharing options...
ilko_t Posted May 12, 2010 Share Posted May 12, 2010 @ilkoSince you have some machines that do work with firadisk and some that won't, have you had a chance to test WinVblock?http://www.boot-land.net/forums/index.php?showtopic=8168Maybe it works with 2K3 on the "pesky" ones? jaclazHaven't tested WinVBLock, at that time it was in early development stage. Don't have any spare time lately for hobby Link to comment Share on other sites More sharing options...
iosha789 Posted May 13, 2010 Share Posted May 13, 2010 Try LATEST:http://www.boot-land...04&st=0&start=00.0.1.18 right now.Today i tested with firadisk 0.0.1.18 but the same result !Any advice please !Thanks so much ! Link to comment Share on other sites More sharing options...
cdob Posted May 16, 2010 Author Share Posted May 16, 2010 Today i tested with firadisk 0.0.1.18 but the same result !Which result do you get? "Windows will dump" is not a clear error report.Firadisk 0.0.1.18 does work fine at 2003 SP2 32 bit files.If I recall correctly v0.0.1.12 did work too.Which 2003 files do you use?Integrate a 2003 setup.exe to floppy image.Do not use a XP setup.exe for 2003. Link to comment Share on other sites More sharing options...
iosha789 Posted May 25, 2010 Share Posted May 25, 2010 Do not use a XP setup.exe for 2003.Thanks ! Yes this is a mistake....now it successfully....thanks so much ! Link to comment Share on other sites More sharing options...
Tefole Posted May 27, 2010 Share Posted May 27, 2010 (edited) @cdob,with @kDN dd methode, i am recently using several winnt.sif's on the firadisk.image.If I wanna work with two setupORG.exe files (win-original and the driverpack.one) on one firadisk.image, how could i handle this per menu.lst? i mean, one entry in grub with and one without driverpack (each one with specific winnt.sif of course). Edited May 27, 2010 by Tefole Link to comment Share on other sites More sharing options...
cdob Posted May 27, 2010 Author Share Posted May 27, 2010 If I wanna work with two setupORG.exe files (win-original and the driverpack.one) on one firadisk.image, how could i handle this per menu.lst? i mean, one entry in grub with and one without driverpack (each one with specific winnt.sif of course).Well, setup.cmd does support driverpack method 2 already. There is no need to include driverpack fake setup.exe to floppy image.Quite contrary you may get strange results: read it's not supported.In addition Driverpack masstorage add textmode files to txtsetup.sif too.Anyway if you need to incldue a second setupORG.exe to floppy image.Adjust txtsetup.oem inside floppy image[Disks]setup32 = "setup files x86", \txtsetup.oem, \setup\I386\se03_32 = "2003 setup files x86", \txtsetup.oem, \setup\I386_03\Copy 2003 setup.exe to \setup\I386_03\setupORG.exe.Use a hexeditor, open txtsetup.oem, remember offset todll = setup32, setuporg.exeExample: 0x596Use the previous offset at menu.lstwrite --offset=0x596 (fd0)/txtsetup.oem se03_32 Link to comment Share on other sites More sharing options...
Tefole Posted May 30, 2010 Share Posted May 30, 2010 (edited) thank u cdob.another issue:Edit: Solved Edit2: Final & Working Configurationthx to cdob, tinybit, chenall, jaclaz, kDn, was_jaclaz, ... for their contributions and for their effort.title WinXP Pro SP3 Commonls /Images/XP_ALL.iso || find --set-root /Images/XP_ALL.isomap --mem /Images/FiraFloppy.IMA.gz (fd0)map --mem /Images/FiraFloppy.IMA.gz (fd1)map --mem /Images/XP_ALL.iso (0xFF)checkrange 0x80 read 0x8280 && map (hd0) (hd1)checkrange 0x80 read 0x8280 && map (hd1) (hd0)# if start from HDD-device, than remaping hd0<->hd1map --hookwrite --offset=0 (fd0)/setup/ISOimage.ini \\Images\\XP_ALL.iso\n;\n;\n;write --offset=0 (fd1)/setup/ISOimage.ini \\Images\\XP_ALL.iso\n;\n;\n;write --offset=1782 (fd0)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;write --offset=1782 (fd1)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;# Begin HexEditing (Map SetupLDR.bin to Ramdrive)map --mem (0xFF)/XPST/setupldr.BIN (rd)cat --locate=i386 --replace=XPST (rd)+1rootnoverify (0xff)chainloader (rd)+1title WinXP Pro SP3 Up2Date (Sereby) / nlited unattendedls /Images/XP_ALL.iso || find --set-root /Images/XP_ALL.isomap --mem /Images/FiraFloppy.IMA.gz (fd0)map --mem /Images/FiraFloppy.IMA.gz (fd1)map --mem /Images/XP_ALL.iso (0xFF)checkrange 0x80 read 0x8280 && map (hd0) (hd1)checkrange 0x80 read 0x8280 && map (hd1) (hd0)# if start from HDD-device, than remaping hd0<->hd1map --hookwrite --offset=0 (fd0)/setup/ISOimage.ini \\Images\\XP_ALL.iso\n;\n;\n;write --offset=0 (fd1)/setup/ISOimage.ini \\Images\\XP_ALL.iso\n;\n;\n;write --offset=1782 (fd0)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;write --offset=1782 (fd1)/TXTSETUP.OEM dll = setup, fixBoot.USB\r\n;# Enable Winnt.sif / for the automatic installtiondd if=(0xFF)/OS/XPLU/I386/WINNT.SIF of=(fd0)/WINNT.SIFdd if=(0xFF)/OS/XPLU/I386/WINNT.SIF of=(fd1)/WINNT.SIF# Begin HexEditing (Map SetupLDR.bin to Ramdrive)map --mem (0xFF)/XPST/setupldr.BIN (rd)cat --locate=i386 --replace=XPLU (rd)+1rootnoverify (0xff)chainloader (rd)+1title Main Menuconfigfile /boot/grub/menu.lst I think that there is logical problem somewhere on the setupldr patching part. I ll took the cat part from another thread from a posting from u.Immediately after mapping and patching, i'll get the loading screen from the setup and a few mSeconds later - a reset on the VM. Either on a physically PC is neiter working.Grub4Dos is the latest one from chenall. Without the setupldr-patching everything is fine.Edit: I think, i found it but still some problems with the mapping from setupldr.bin into the ramdrive. probably i timing issue. I ll test it soon, and will write a feedback btw: some suggestions for beautification? thats only just one entry in submenu, but its getting longer and longer... Edited May 31, 2010 by Tefole 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