![]() ![]() |
Jun 26 2008, 02:28 PM
Post
#1
|
|
|
Advanced Member ![]() ![]() ![]() Group: Members Posts: 402 Joined: 6-December 06 Member No.: 117812
|
Some news- Windows can be installed from a HD-like media, not using ~LS as source folder.
This was close: http://www.msfn.org/board/How-to-boot-inst...730#entry684730 QUOTE (ilko_t) I have tried to change TXTSETUP.SIF to : CODE [SetupData] SetupSourcePath = "\" SetupSourceDevice = \device\harddisk0\partition1 MajorVersion = 5 MinorVersion = 1 Well, make it QUOTE SetupSourcePath = "\xppro\" SetupSourceDevice = \device\harddisk1\partition1 Setupdd.sys finds source files in \xppro\, that's in root of a USB disk. QUOTE MsDosInitiated="1" are not used needed.floppyless="1" If MsDosInitiated="1" is used, then SetupSourcePath and SetupSourceDevice are ignored, it defaults to $WIN_NT$.~LS. Continue Text mode- source files are found and copied. No files are deleted. Migrate.inf is NOT used. For now I used a partition on the USB disk as install target. BOOT.INI on USB disk gets: CODE default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS Different parts of Text mode see USB disk once as first disk, then as second. Having more disks or USB card readers can easily break the whole game. However, that proves how source location can be different than ~LS and MsDosInitiated="1" not used. Another game- build a small ISO, and load it in RAM, start Setup from there. Create folder \ISO. Copy bootsect.bin there. Create folder I386 inside, copy contents of ~BT there. Replace ramdisk.sy_ with the one from 2003 sp1. Get the modified with SourcePath txtsetup.sif and put it in \ISO\I386. CODE mkisofs.exe -iso-level 4 -volid ""XP"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -b BOOTSECT.BIN -hide BOOTSECT.BIN -o j:\xp.iso J:\ISO Setupldr.bin from 2003 sp1 and ntdetect.com are in root of the USB disk. Winnt.sif in root: CODE [SetupData] BootDevice = "ramdisk(0)" BootPath = "\i386\" OsLoadOptions = "/noguiboot /fastdetect /rdexportascd /rdpath=xp.iso" Text mode goes fine source files are found in \xppro\, install to the same USB disk, second partition, boot.ini gets again CODE default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS I didn't go much further, in QEMU if a second disk is used and boot.ini fixed, at start of GUI part it complains about corrupted DATA section. That must be QUOTE [SetupData] in out winnt.sif in root.BootDevice = "ramdisk(0)" ..... Winnt.sif inside the ISO is NOT read. Hex edit setupldr.bin in root to use winn1.sif, leave our regular winnt.sif in USB disk root- it's not being read. There is a possible solution- use presetup.cmd and remove from \windows\system32\$winnt$.inf the odd lines, not tested. However, there is no much gain using RAM boot. Still a lot to be tested, but the line "SetupSourceDevice = \device\harddisk1\partition1 makes huge restriction. This post has been edited by ilko_t: Jun 26 2008, 02:41 PM |
|
|
|
Jun 26 2008, 04:06 PM
Post
#2
|
|
|
Newbie Group: Members Posts: 25 Joined: 3-January 04 Member No.: 11860 |
Thanks ilko_t!
This will give me something to do for the whole day! VMware doesn't like booting from my USB hard drive, can you do this from qemu? This post has been edited by andy_le2k: Jun 26 2008, 04:18 PM |
|
|
|
Jun 26 2008, 04:58 PM
Post
#3
|
|
|
Advanced Member ![]() ![]() ![]() Group: Members Posts: 402 Joined: 6-December 06 Member No.: 117812
|
CODE qemu-system-x86_64.exe -L . -boot c -m 300 -hda //./PhysicalDrive3 This is for QEMU 0.9.1. You have to change 300 whatever RAM you can afford and PhysicalDrive3 to the USB drive number. Numeration starts from 0, your first internal disk is PhysicalDrive0. USB drive is used as QEMU IDE disk 0, all partitions are visible. However, it's not advisable to test in QEMU, you should only test read-only operations there. VMware has a similar option to use external disk, which could be your USB one. Tests on real hardware are preferred. |
|
|
|
Jun 28 2008, 02:44 AM
Post
#4
|
|
|
Member Group: Software Developers Posts: 236 Joined: 21-March 07 Member No.: 132150
|
Well, make it QUOTE SetupSourcePath = "\xppro\" SetupSourceDevice = \device\harddisk1\partition1 Hi ilko, Interesting new experimental results. There is always more to find out .... At the moment I am adding to USB_MultiBoot.cmd the option to boot with boot.ini Menu from USB with IMG or ISO Boot Image Files loaded into RAMDISK. It is possible now to add Multiple PE Boot Images in a similar way as described by diddy in his great Guide, Step 9a - Add another BartPE, for booting with Syslinux Menu. http://www.911cd.net/forums//index.php?showtopic=18846 In this way Multiple PE from USB-stick is possible without making Multiple partitions. Instead of the SDI files I follow the handy aproach with IMG files used by the BootLand community. The BootSDI.img files made with WinBuilder can be used with the next version of USB_MultiBoot.cmd LiveXP is running quite well from USB using booting from RAMDISK with these BootSDI.img files. http://www.boot-land.net/forums/?showtopic=4111 This might be interesting in view of your experiments with Starting XP Setup from RAM. The number of Downloads at CD Forum for USB_MultiBoot_10.zip is rapidly increasing, now 30.500 since the release on June, 6th .... This post has been edited by wimb: Jun 28 2008, 05:43 AM |
|
|
|
Jun 29 2008, 01:05 AM
Post
#5
|
|
|
Member Group: Software Developers Posts: 236 Joined: 21-March 07 Member No.: 132150
|
LiveXP is running quite well from USB using booting from RAMDISK with these BootSDI.img files. http://www.boot-land.net/forums/?showtopic=4111 I used http://amalux.winbuilder.net/lx41208pg.exe to make BootSDI.img file used for booting from USB-stick via RAMDISK. The BootSDI.img file is located in the root of the USB-stick, prepared with the next version USB_MultiBoot_11.cmd and using NO Copy of XP Install folders (BT and LS). In root of stick we have additionally:
In the case of 1 Boot Image file you might keep winnt.sif as filename and don't need to patch with gsar CODE makebt\gsar -b -o -s:x46:xda:x74:x03 -r:x46:xda:xEB:x1A %usbdrive%\RMLD1 makebt\gsar -b -o -swinnt.sif -rramx1.sif %usbdrive%\RMLD1 where %usbdrive% is changed for your USB-stick e.g. Q: ramx1.sif CODE [SetupData] BootDevice="ramdisk(0)" BootPath="\i386\System32\" OsLoadOptions="/noguiboot /fastdetect /minint /rdexportashd /rdpath=BootSDI.img" For ISO files we have to use /rdexportascd instead of hd In the PE environment you can first format your C: drive with NTFS format. This LiveXP has a build in XP Setup script to specify XP Setup parameters and to launch XP Setup with XPSetupLauncher.exe Launching XP Setup from LiveXP PE environment is quite interesting. The XPSOURCE folder can be located on USB-stick bootdrive or on any partition of any HardDisk, or you can even use your XP Setup CD as XPSOURCE. This means an Alternative location of Setup files is possible in various ways and seems to be unlimited. After launching XPSetup from LiveXP, the $WIN_NT$.~BT was made on the USB-stick bootdrive, but the $WIN_NT$.~LS folder was made on C-drive used for Install of WINDOWS. So the BT and LS folders are made on different drives Now on Reboot from USB-stick, XP Setup is auto-launched from the modified boot.ini file. Filecopy to WINDOWS Install folder occurs. Then on Reboot from USB-stick I selected to boot from HD1 to start GUI mode and again to Start XP. The XPSOURCE remains on stick OK, $WIN_NT$.~BT folder on stick is removed. Next XP Install from USB via LiveXP PE, the temporary folder is made again. This works The procedure needs some small modifications, prior to first reboot from USB-stick Default in boot.ini on stick can be set to boot from HD1 MkMigrateInf2.cmd can be used to make USB-stick bootdrive U: instead of now E: (the third HD) binifix4.cmd will be needed to repair boot.ini on harddisk (put binifix4.cmd in XPSOURCE\I386 folder) txtsetup.sif in root of stick Add: CODE [SourceDisksFiles] binifix4.cmd = 100,,,,,,_x,2,0,0 winnt.sif in $WIN_NT$.~BT folder on stick Add: CODE [GuiRunOnce] "binifix4.cmd c:" To let USB-stick be preferred Boot drive U: use: copy migrate.inf from USB_MultiBoot_10\makebt folder to $WIN_NT$.~BT folder on stick and make changes with makebt\MkMigrateInf2.cmd using CODE MkMigrateInf2.cmd %usbdrive% %usbdrive%\$WIN_NT$.~BT\migrate.inf Change line with Default=C:\$WIN_NT$.~BT\BOOTSECT.DAT in boot.ini on stick as: CODE [Boot Loader] Timeout=5 Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS [Operating Systems] multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="2. and 3. Continue with GUI Mode Setup Windows XP + Start XP from HD 1" /FASTDETECT multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 2, use if installing on HD2" /FASTDETECT c:\grldr="4. Start GRUB4DOS Menu - DOS FPY IMAGES + Linux + XP Rec Cons + Vista" C:\btsec\RMLD1.bs="PE 1 - BootSDI.img from RAMDISK" C:\$WIN_NT$.~BT\BOOTSECT.DAT="Microsoft Windows XP Professional Setup" This can all simply be automated with a batch command This post has been edited by wimb: Jun 30 2008, 06:34 AM |
|
|
|
Jun 30 2008, 01:57 PM
Post
#6
|
|
|
Advanced Member ![]() ![]() ![]() Group: Members Posts: 402 Joined: 6-December 06 Member No.: 117812
|
Install from PE environment, running winnt32.exe or equivalent tool, which will run the same with some adjustments has always been an option.
The downsides are, that you cannot distribute this PE build. Now we have 2 options: 1) One builds it himself, this sends unexperienced users to something new, they want simply to install Windows from USB. I assume if one knows how to make PE, he should know how to install Windows from that environment. 2) We make this PE from the Windows source, which goes way beyond the scope of this project. There is third option 3)Make small XP with drivers pack included off the windows source: http://www.boot-land.net/forums/?showtopic=3717 Do not use winnt32.exe, but rather build ~BT and ~LS folders on the target disk from a batch script. Target has to be properly formatted, or include some simple partition tool in the small XP. That's a lot of work and experiments, is it worth? This post has been edited by ilko_t: Jun 30 2008, 01:58 PM |
|
|
|
Jul 1 2008, 04:01 AM
Post
#7
|
|
|
Member Group: Software Developers Posts: 236 Joined: 21-March 07 Member No.: 132150
|
Do not use winnt32.exe, but rather build ~BT and ~LS folders on the target disk from a batch script. Target has to be properly formatted, or include some simple partition tool in the small XP. That's a lot of work and experiments, is it worth? That can be interesting for a fourth option which is not too much work I think 4) - Make 2 scripts for WinBuilder, Use WinBuilder to make USB-stick and Boot from USB-stick with LiveXP
May be the script developers of the BootLand community can make the scripts for option 4 Or use the fifth option which is even more simple: 5) - INSTALL XP after Booting with PE from USB, using XP_SETUP.cmd on USB-stick. XP Setup Batch Program was made which is copied to USB-stick by USB_MultiBoot.cmd Program and can be used after booting from USB-stick from any PE such as LiveXP, BartPE or UBCD4WIN. Manually Quick Format C-Install-Drive with NTFS using Drive Explorer from PE Environment. XP Setup Batch Program will Create on C-drive the $WIN_NT$.~BT and $WIN_NT$.~LS plus $OEM$ folders and OEM folder for DriverPacks and will Copy Root BootFiles to C-drive. Unattended Setup is supported using Current_winnt.sif and $OEM$ folder for giving XP Setup parameters. This fifth option is most nearby and I have made such a Batch Program XP_SETUP.cmd, which provides at Boot time more freedom in the location (USB-stick, HD or CD/DVD) and the type of XPSOURCE (Home, Prof, MCE, Tablet) used for Install of XP. Instead of using XPSetupLauncher, I did already a manual try of the idea presented above:
CODE E:\XPSOURCE\i386\winnt32.exe /noreboot /makelocalsource /syspart:C: /tempdrive:C: /unattend:E:\XPSOURCE\i386\winnt.sif
Now both $WIN_NT$.~BT and $WIN_NT$.~LS folders are created on C-drive as determined by parameters /syspart:C: (for Bootdrive with folder ~BT) and /tempdrive:C: (for Install Drive with folder ~LS) The XPSOURCE type used for Install is Selectable after Booting with PE from USB and can be located anywhere: on USB-stick , HDD or CD/DVD It is interesting to add this fifth option for those who are familiar already with Booting with PE from USB using LiveXP, BartPE or UBCD4WIN. This post has been edited by wimb: Jul 4 2008, 08:44 AM |
|
|
|
Jul 27 2008, 04:32 PM
Post
#8
|
|
|
Group: Members Posts: 4 Joined: 13-May 08 Member No.: 191760 OS: none
|
5) - INSTALL XP after Booting with PE from USB, using XP_SETUP.cmd on USB-stick. XP Setup Batch Program was made which is copied to USB-stick by USB_MultiBoot.cmd Program and can be used after booting from USB-stick from any PE such as LiveXP, BartPE or UBCD4WIN. Manually Quick Format C-Install-Drive with NTFS using Drive Explorer from PE Environment. XP Setup Batch Program will Create on C-drive the $WIN_NT$.~BT and $WIN_NT$.~LS plus $OEM$ folders and OEM folder for DriverPacks and will Copy Root BootFiles to C-drive. Unattended Setup is supported using Current_winnt.sif and $OEM$ folder for giving XP Setup parameters. This fifth option is most nearby and I have made such a Batch Program XP_SETUP.cmd, which provides at Boot time more freedom in the location (USB-stick, HD or CD/DVD) and the type of XPSOURCE (Home, Prof, MCE, Tablet) used for Install of XP. Instead of using XPSetupLauncher, I did already a manual try of the idea presented above:
CODE E:\XPSOURCE\i386\winnt32.exe /noreboot /makelocalsource /syspart:C: /tempdrive:C: /unattend:E:\XPSOURCE\i386\winnt.sif
Now both $WIN_NT$.~BT and $WIN_NT$.~LS folders are created on C-drive as determined by parameters /syspart:C: (for Bootdrive with folder ~BT) and /tempdrive:C: (for Install Drive with folder ~LS) The XPSOURCE type used for Install is Selectable after Booting with PE from USB and can be located anywhere: on USB-stick , HDD or CD/DVD It is interesting to add this fifth option for those who are familiar already with Booting with PE from USB using LiveXP, BartPE or UBCD4WIN. I like the 5th option much better because it's very simple and standard. That means, after I prepare my Windows XP source with nLite and DriverPack, I simply use your USB_Multiboot to format the USB drive and then select the XP source to copy to the USB without any modification. Boot PE from USB and run the a setupxp.cmd to start Windows XP Setup. Do you have a beta version out yet to test the option 5? Kenneth |
|
|
|
Jul 29 2008, 08:23 AM
Post
#9
|
|
|
Member Group: Software Developers Posts: 236 Joined: 21-March 07 Member No.: 132150
|
================================================================================
*** Install XP from USB AFTER Booting with PE from HDD or USB *** Tutorial at Boot Land Forum http://www.boot-land.net/forums/?showtopic=5306 The package USB_XP_Setup contains 3 Batch Programs:
Direct Download - USB_XP_Setup Before you Start:
The XP Setup Procedure:
The advantage of the present technique is that there are no changes needed in the BIOS Setting. Booting for XP Setup occurs all the time as normal from the C-Install Drive. Thus the USB-stick does not need to be bootable and it is not needed that the motherboard supports booting from USB. XP Setup Source Folder can be on USB-stick or on partition 1 of USB-HDD or second HDD-Drive. This post has been edited by wimb: Aug 3 2008, 12:27 AM |
|
|
|
![]() ![]() |
| Lo-Fi Version | Time is now: 8th January 2009 - 03:17 AM |