Jump to content

wimb

Developer
  • Posts

    951
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by wimb

  1. Download USB_MultiBoot_8.zip - Unpack USB_MultiBoot_8.zip to your Harddisk in a simple Path without SPACES. - Run USB_MultiBoot_8.cmd Simple to Use - Help Instructions are given in the Program - See ScreenShots 1, 2, 5 and 15 Read: How to Install XP from USB - and - ScreenShots More Help: See Help_Info Folder
  2. I tried to use SETUPLDRBIN and SETUPLDR.BIN instead of NTLDR in NTFS BootSector File using the same byte sequence for terminating the bootloader name, but booting did not occur. So it seems to me that we have to live with the 5-letter limit of bootloader name in NTFS BootSector File. Actually renaming SETUPLDR.BIN as XPSTP is OK and is used now for all FileSystems by USB_MultiBoot_8.cmd in order to avoid confusion. wimb
  3. I tried to use SETUPLDRBIN and SETUPLDR.BIN instead of NTLDR in NTFS BootSector File using the same byte sequence for terminating the bootloader name, but booting did not occur. So it seems to me that we have to live with the 5-letter limit of bootloader name in NTFS BootSector File. Actually renaming SETUPLDR.BIN as XPSTP is OK and is used now for all FileSystems by USB_MultiBoot_8.cmd in order to avoid confusion. wimb
  4. The code consists of 4 lines (not 5) which you see when you copy the lines to notepad Actually Using Option -o is easier like, copy /y U:\minint\setupldr.bin U:\PELDR makebt\gsar -sBT:x00:x00:x00\:x00:x00:x00txtsetup -rBT:x00:x00:x00\:x00:x00:x00notsetup U:\PELDR -b -o where U: refers to your USB-Drive wimb
  5. copy /y %usbdrive%\minint\setupldr.bin %usbdrive%\PELDR makebt\gsar -sBT:x00:x00:x00\:x00:x00:x00txtsetup -rBT:x00:x00:x00\:x00:x00:x00notsetup %usbdrive%\PELDR %usbdrive%\peldr.new -b -f if exist %usbdrive%\peldr.new copy /y %usbdrive%\peldr.new %usbdrive%\PELDR if exist %usbdrive%\peldr.new del %usbdrive%\peldr.new As being used in USB_MultiBoot_8.cmd wimb
  6. Your solutions for Install of Vista from USB were already described here http://www.msfn.org/board/vista-t114092.html&st=6 http://www.msfn.org/board/vista-t114092.html&st=7 http://www.msfn.org/board/Install-Vista-US...6.html&st=2 and GRUB4DOS menu.lst of USB_MultiBoot_8.zip provides already entries for Install of Vista from USB using chainload of BOOTMGR
  7. Most likely your BIOS / motherboard does NOT Support Booting From USB. See Help_Info\Help_USB_MultiBoot.txt Section A. 3
  8. You might try to use it as a BootFloppy Image, which you place in folder images.Use Existing BootFloppy Image or Use WinImage http://www.winimage.com/ to Save a DOS Boot Floppy Image. In GRUB4DOS menu.lst you can make similar entry as: title 3 - Floppy Image - MS-DOS - UBCD Bart's Modboot map (hd0,0)/images/msubcd.img (fd0) map --hook chainloader (fd0)+1 rootnoverify (fd0) Boot USB-stick from boot.ini Menu and Select GRUB4DOS and Select your BootFloppy Image.
  9. New Release USB_MultiBoot_8.zip available, see previous post #7 wimb
  10. Oops, that change for x64 in your file was not discovered by me Fixed in the New Release USB_MultiBoot_8.zip wimb
  11. Thx guys, Multiple XP Install from USB SOLVED for me by ilko_t with TinyHexer ScreenShot and andy_le2k and cdob Install of XP from USB was now OK My problem was that in TinyHexer I used wrong setting for search of $WIN_NT$.~LS string. Now I know that I have to use Unicode (little endian) and Ignore case. But it is much better to use GSAR for the search and replace, then there is no problem. @andy_le2k Your GSAR Instruction is OK, no need to change wimb
  12. Unicode made the difference, Thanks Will try again now.
  13. Hi ilko, In my setupdd.sys there is no $WIN_NT.~LS string, but in yours I can see there is one. My Source is XP SP2 NLD file 03-08-2004 Mystery SOLVED, I changed Search Settings to Yours and Now I found the String. Search with: Unicode (little endian) and Ignore case Thanks a lot
  14. Did you mean here XPS01 instead of SETUPLDR1 Same for index 2 In setupdd.sys there is no $WIN_NT.~LS string Did you mean :x00B:x00T instead of :x00L:x00S Your detailed description of post #1 corresponds to what ilko_t and cdob have given, but unfortunately I was not able in all cases (3 attempts) to reach the GUI Mode of Setup. TXT Mode Setup was running well, but TXT mode could not continue after the first question. Setup cannot Find Install Files - Setup Cannot Continue - Message Occurs. So NOT SOLVED for me @ilko_t Would it bepossible that a modified NTDETECT.COM bring the solution? What kind of USB-Drive and Format did you use ? I have tried USB-Harddisk with NTFS and FAT Format, and USB-stick with NTFS Format wimb
  15. Oops, that change for x64 in your file was not discovered by me, so it is not yet implemented in USB_MultiBoot7.cmd I hope there are no more hidden changes. I focussed on all lines with AMD64 in it. I will change it in the next version. Thanks for letting me know. wimb
  16. Congratulations cdob and ilko_t with Multiple XP Install from USB All Information has been added to New Release of USB_MultiBoot7.zip
  17. Interesting ideas String $WIN_NT$.~BT occurs twice in SETUPLDR.BIN but $WIN_NT$.~LS is not found there. TXTSETUP.SIF does NOT contain string $WIN_NT$.~LS and SetupSourcePath = "\" It seems that hexediting will not bring the desired solution .... May be a second stick with other XP version is more convenient
  18. Install of Vista from Folder on NTFS USB-stick was realised as described here http://www.msfn.org/board/vista-t114092.html&st=6 It will be possible to combine XP , Vista x86 and Vista x64 for Install from USB. Different versions of XP cannot be combined on one stick, but it is very convenient to use different sticks for this purpose.
  19. Will you please give as Attachment your WinXP x64 DOSNET.INF File from AMD64 Folder. It can help me in designing and testing the USB_MultiBoot program. Thanks, wimb
  20. I am using method 2 for BTS DriverPacks with only BTS MassStorage DriverPack Integrated (Preferred). Does the 38 min also include Install of Apps ? What BTS DriverPacks are included ? I have the idea that my 16 minutes Install time is not limited anymore by USB read speed. For making the USB-stick a higher write speed will certainly help. For my normal Corsair Flash Voyager 4 GB I get with ATTO Bench for 64 kb - 8 MB range 7.7 Write and 12.8 MB / sec Read Speed, so quite comparable to your values.
  21. A new link to Install XP from USB was introduced in version 6, instead of the link to the Guide in the initial Help Screen. Thanks to thasan who made me aware of the effect of &st=6 in this link The st is then not recognized as a command and gives a message, but it will give no problem It will be corrected in the next version ....
  22. Integrate in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled, which makes anyway the XPSOURCE much more usefull. In that case the GUI Mode of XP Setup starts with presetup.cmd which executes: REM +==========================================================================+ REM | Disable Driver Signing Policy and keep it disabled. | REM |--------------------------------------------------------------------------| START %SystemDrive%\DSPdsblr.exe This might solve your problem. We use a customised version of presetup.cmd which you find in folder makebt More Info on BTS DriverPacks:
  23. The Vista Setup Files can also be located in a Separate Folder on your USB-stick e.g. Copy 32-bits Vista Setup Files to Folder Vista_32 on NTFS USB-stick prepared with USB_MultiBoot6.cmd Copy to the Root of your USB-stick the contents of the Windows PE 2.0 x86 ISO Folder. Boot in this case via boot.ini Menu > GRUB4DOS Menu > Select Windows PE 2.0 Then the Windows Boot Manager Menu Appears and one can launch Windows PE 2.0 In Win PE 2.0 Command Window > Select USB-Drive and Folder with Vista Setup > Run Vista Setup This idea was tested with success for the 32-bits version of Vista. Booting with Windows PE 2.0 does not take extra time, since it is otherwise part of Vista Setup. Similarly one might Install the 64-bits version of Vista from a Vista_64 Folder, but I am not able to test it. Booting with Windows PE 2.0 x86 and x64 will be different, but this problem can be overcome. It is possible to edit the BCD Store on the USB-stick such that the Windows Boot Manager Menu allows to Select either boot32.wim or boot64.wim from the Windows PE 2.0 sources Folder. For this purpose we use in XP OS the Vista file bcdedit.exe to edit file boot\bcd on the USB-stick. 1. Copy Vista file bcdedit.exe to your XP C:\WINDOWS\system32 folder 2. Open in XP Command Window with path C:\WINDOWS\system32 bcdedit.exe /? and bcdedit.exe /? /set give a lot of help info for using bcdedit.exe 3. The present BCD store entries for Windows PE 2.0 on USB-Drive P: are obtained by running the command C:\WINDOWS\system32>bcdedit /store P:\boot\bcd /enum Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes 4. Now as a test we are going to Edit the BCD Store to change boot.wim in boot32.wim by using C:\WINDOWS\system32>bcdedit /store P:\boot\bcd /set {default} DEVICE ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} C:\WINDOWS\system32>bcdedit /store P:\boot\bcd /set {default} OSDEVICE ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} 5. Ater Edit of the BCD Store we check the result with C:\WINDOWS\system32>bcdedit /store P:\boot\bcd /enum Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes It turns out that booting with the Windows PE 2.0 Renamed as boot32.wim enables also to Install 32-bits version of Vista by using Win PE 2.0 Command Window > Select USB-Drive and Folder with Vista Setup > Run Vista Setup So the idea of using Separate Folders for 32-bits and 64-bits Vista Setup Files is usefull It will be possible to add to the WinPE x86 BCD Store a new entry for launching Windows PE 2.0 x64 by C:\WINDOWS\system32>bcdedit /store P:\boot\bcd /copy {default} /d "Windows PE 2.0 x64" and use then the entries found in the WinPE x64 BCD Store to make in the WinPE x86 BCD Store with a similar edit as given above the correct entries which are suitable for boot64.wim More Interesting Info on bcdedit and Vista: http://www.multibooters.co.uk/cloning.html http://www.multibooters.co.uk/ I have tried also to edit the BCD store of Root folder boot\bcd such that Vista_32\SOURCES\BOOT.WIM was launched directly from the Windows Boot Manager Menu. Booting was OK, but when arriving at the point of Install Now there were complaints about missing drivers and Install.wim could not continue. So this approach was not successfull.
  24. The Vista BootSector is not needed since GRUB4DOS is able to chainload directly the Bootloader bootmgr for Vista Setup. So Vista and XP Setup can coexist on a single partition USB-stick having NTLDR (XP) Bootsector and boot.ini menu. If you want to combine it with Vista x64 on the same USB-stick, then you may need a second partition for Vista x64, but again a Vista BootSector is not needed. GRUB4DOS allows you to chainload bootmgr directly on any partition of any harddisk Very convenient without the need to have a VISTA bootsector. By the way I just copied 2.8 GB Vista Setup files using XP as OS in 16 minutes to a normal 8 GB Corsair Flash Voyager USB-stick earlier prepared with USB_MultiBoot6.cmd and using the MULTI_CONTENT Folder and the Multi_boot.ini After booting from the stick with boot.ini Menu, I selected Option 12 of GRUB4DOS Menu to launch Vista Setup from the stick. Vista Setup took 24 minutes in total, but therefore it is needed to unplug the USB-Drive just at the First Restart of Vista Install. Earlier unplugging gives Install Error (cannot be solved). Without unplugging it took 47 minutes, where in the extra 23 minutes it seemed that nothing was occurring at the computer harddisk. In this period the USB-light was flashing all the time, but on later inspection at first sight there seemed to be no changes there. Strange long wait ....
×
×
  • Create New...