wimb

Using XP Setup Boot CD for Install of XP on second harddisk gives in fact the same problem. XP bootfiles are made on first harddisk and Bootsector is changed into NTLDR-type. Only the arcpath in boot.ini made on first harddisk is now correct referring to booting Windows from rdisk(1). Using USB_XP_Setup.exe to make $WIN_NT$.~BT folder and XP bootfiles on second partition of second harddisk (HD 1), ensures that TXT-mode is NOT making bootfiles on first harddisk (HD 0) and that BOOTMGR-type BootSector of Windows 7 is kept unchanged. The XP Setup Source is in folder XP3_911 on USB-stick being HD 2 Interesting in this case is the $winnt$.inf file in which floppylessbootpath has defined setting as: [Data] floppylessbootpath=\Device\HardDisk1\partition2 sourcepath=\device\harddisk2\partition1\XP3_911\ unattendedinstall=yes floppyless=0 AutoPartition=0 InstallDir=\WINDOWS MsDosInitiated=0 dospath=U:\XP3_911\ In that case the second partition of second harddisk has also the correct drive letter C: in the drive listing, whereas for Install from CD and the small ISO USB-boot were giving drive letter C: to the first partition of first harddisk, allthough in all cases the BIOS Boot priority was such that second harddisk was set as first HDD boot device. But the question remains: How to trigger that TXT-mode is behaving for Install from CD and the small ISO USB-boot correct as to make the XP bootfiles on the Install Drive on second harddisk, when this is set in BIOS as having the highest boot priority.

Yes, this part of the problem will be easily fixable.But TXT-mode copying XP bootfiles to wrong disk and changing BOOTMGR-type bootsector into NTLDR-type bootsector will be more difficult to prevent from occurring. Both internal disks are SATA and BIOS setting is IDE-mode. Hope you will find a solution. I will try and think about it. Cheers

Yes, that is exactly what I did and reported about as my second test. In grub4dos CLI I see my first harddisk with Windows 7 as hd1. Indeed the XP bootfiles are going to hd1 and the BOOTMGR-type bootsector is then changed to NTLDR-type. But that is what causes the problem, because when you remove the USB-stick and Reboot, then second harddisk gives error NTLDR is missing. Trying to reboot from first harddisk gives then Windows boot config error, since boot.ini wants to boot from rdisk(2) instead of rdisk(1) So the computer is not bootable from any of the two internal harddisks. The problem is that after booting from USB-stick then TXT-mode of XP Setup will place the XP bootfiles wrongly on the first internal disk instead of on the second internal disk where XP is installed. I think it will be difficult (or impossible) for this way of Install of XP from USB to let TXT-mode of XP Setup behave differently ....

That is exactly what I tried and reported the result in the EDIT: section. In that case Install of XP from USB works, but removing AFTER install the USB-stick results in a computer being not bootable from any of the two harddisks, with the errors as described in my post. Otherwise just booting from stick via F8 BIOS boot menu gives in grub4dos cli that Win7 first harddisk is seen as hd1 and my second harddisk is seen as hd2 and the USB-stick is hd0

I did some experiments with the new version 1.0 beta 4 The approach with RAM loaded small ISO and booting only once from USB-stick is interesting, but for my computer configuration I had some problems with Install of XP from USB. I tried to do Install of XP on the second Primary partition of my second harddisk. The second harddisk has in BIOS the highest boot priority and second partition was Set Active. This means my computer is set correctly as to boot from second partition of second harddisk. Windows 7 is installed on the first partition of first harddisk and boots with BOOTMGR menu. Now, when I Install XP on second partition of second harddisk by booting once from USB-stick, then TXT-mode setup is running well, but on reboot for GUI-mode I get boot error NTLDR is missing. It turned out that the XP bootfiles were made on first partition of first harddisk. Moreover, the bootsector of the Windows 7 partition was changed into NTLDR-type. so that the computer was also not bootable anymore with Windows 7 from first harddisk using F8 BIOS bootmenu. Instead I got: Windows cannot start due to config error. The boot.ini that was made wrongly on the first partition of first harddisk, did not have the right arcpath. It tried wrongly to boot Windows from my USB-stick as rdisk(2) instead of referring to rdisk(1) for my second harddisk. After booting with LiveXP I could repair the boot problems and after reboot continue with GUI-mode of XP Setup. Everything else in GUI-mode of XP Setup, including using 5 DriverPacks, making UserAccount at T-13 and Install of Sound and Graphics drivers with DriverForge at T-9 and GUIRunOnce, was working as expected. A drawback is however, that the booting XP partition gets then Drive Letter D: instead of the common drive letter C: Conclusion: The new method is very interesting and promising, but it requires that the XP bootfiles are made on the real boot partition, instead of making them on the assumed boot partition. EDIT: Changing BIOS Setting such that for Install of XP booting occurs three times from USB-stick enables to proceed with GUI-mode and to boot for login with Desktop. So, this seems OK, but ..... However, the XP bootfiles are still made at the wrong place and the BOOTMGR-type BootSector of the Windows 7 partition is changed wrongly into NTLDR-type Removing the USB-stick followed by Reboot gives then the same boot errors as described above.

Nice solution, this PowerPacker for USB-stick

May be you can use the principles used in U_XP_SET: First Connect USB-stick having XP Setup Source folder and then Boot as usual from HDD with Windows XP. Run USB_XP_Setup.exe of U_XP_SET package and Select XP Setup Source on USB-stick and then using GO you produce a WinXP Setup BootFolder next to running XP, which you can select from boot.ini menu next time on booting from HDD and where you can use XP Setup Source folder located on USB-stick. This is Install XP from USB without booting from USB http://www.911cd.net/forums//index.php?showtopic=21883

Breaking News, this sounds very interesting

You can try Install XP from SD card without booting from SD card, but instead boot all the time from the same drive, being your internal harddisk on which you want to install XP. First prepare your SD-card with Make_USB.exe using Format Stick and FAT FileSystem. Then after booting with LiveXP BootSDI.img RAMBOOT Image, you can prepare your internal HDD for Install of XP, using USB_XP_Setup.exe of U_XP_SET package and where XP Setup will be able to use the XP Setup Source located on SD-card. NOT booting from USB or SD has great advantage and can make quite a difference. There is no confusion anymore, since your boot device in XP Setup is always the same, e.g. your internal HDD. More Info: http://www.msfn.org/board/install-xp-usb-a...sb-t121446.html

Interesting Can be quite useful ....

In XP use Disk Management and Set the Windows 7 partition Active, allows to Reboot with Windows 7. However, if the MBR bootcode has changed due to Install of XP then you have a problem and need to fix this with EasyBCD (see below for using EasyBCD) ============================================================== To make XP boot entry in Windows 7 you need: Copy NTLDR, NTDETECT.COM and BOOTFONT.BIN from XP partition to Windows 7 partition. Using Notepad make in Windows 7 partition a boot.ini file with: [boot loader] timeout=20 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect When you have only 1 entry like given above, you won't see the boot.ini menu anymore and will immediately boot with XP located in partition(2) To make this happen: In Windows 7 you need to make in BOOTMGR boot menu a NTLDR boot entry for XP using EasyBCD and Add Entries. Download EasyBCD from: http://neosmart.net/dl.php?id=1 =================================================================== If Windows 7 does not boot then this is due to wrong bootcode in MBR (=sector 0) caused by Install of XP. In EasyBCD use Manage BootLoaders to repair Windows 7 MBR BootCode with Write MBR I am Not sure if EasyBCD is already Windows 7 compatible. If you cannot boot with Windows 7 then Reboot from USB-stick with XP and Set Active XP partition. In any case make first a backup of your present MBR's using MBR_Backup.cmd of U_XP_SET package. You can also study MBR using TinyHexer and File > Disk > Open drive ... > PHYSICALDRIVE 1 =====================================================================

Change your boot.ini on Harddisk XP partition such that it has entry with rdisk(0)partition(2) for XP installed on second partition. On reboot without USB-stick you first need to check / set your BIOS such that you boot from second harddisk (= Disk 1) Your boot harddisk is in boot.ini always referred to as rdisk(0) whatever harddisk it is If you boot from USB-stick than USB-stick is rdisk(0) and your harddisk with XP is becoming rdisk(1) so that in this case boot.ini on stick was working for you.

After booting XP with USB-stick connected, have a look in XP Disk Management. Most likely the partition on which you installed XP has not been set Active. R-mouse on My Computer > Computer Management > Disk Management R-mouse on Partition with XP > Set Active Have a look also at boot.ini on your C: drive of your Harddisk. Check if its boot entry reflects your current partitioning. Use rdisk(0)partition(1) for XP installed on first partition Use rdisk(0)partition(2) for XP installed on second partition

I think, there is no SETUPLDR.BIN in folder XPPC The XPPC.BIN file is a renamed SETUPLDR.BIN located in XPPC folder. So I think it should be chainloader (0xFF)/XPPC/XPPC.BIN

The Format Stick procedure of Make_USB.exe can be useful to you. http://www.911cd.net/forums//index.php?sho...58798&st=28

Install of Drivers and Programs is described in Section 4 of http://www.boot-land.net/forums/index.php?showtopic=5306 Including the 5 small DriverPacks (Chipset CPU LAN MassStorage and WLAN) in your XP Setup Source is quite useful and the extra load of 36 MB of the OEM folder does not take too much time or space. For Sound and Graphics DriverPacks the load is rather heavy and I decided then to provide the specific required drivers in $OEM$\$1\Drivers folder. DriverForge is used automatic at T-9 to install these drivers by using UserExecute command in [setupParams] section of winnt.sif file. In this way the extra load remains limited and all drivers are installed during XP Setup. Post Install of Drivers can be done if needed with DriverForge provided in POST_INSTALL folder of U_XP_SET package. The folder usb_cfg_extra provides a script for Windows Post-Install Wizard (WPI) - http://wpiw.net/ WPI is very handy for the Automatic Install of Programs after Install of XP from USB. WPI is launched manually after XP Setup has completed and after all drivers are installed. The Programs that you cannot install with WPI, can be installed manually from INSTALL_PRGS folder.

rdisk(0) is the bootdisk. When you boot from USB-stick then USB-stick is rdisk(0) and your internal HDD is rdisk(1) You can only install XP on a Primary partition (max=4, but normally 1 or 2 followed by an Extended Partition with Logical Drives) You cannot use for Install of XP a Logical Drive of the Extended Partition. Study first Partitioning of your HDD using XP Disk Management. Trying to launch GUI-mode with rdisk(0)partition(5) is completely wrong For Install of XP on Partition 1 or on Partition 2 of your HDD you should use: multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 1" /FASTDETECT multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT Read again the Section: hal.dll ERROR for Install of XP from USB http://www.msfn.org/board/install-xp-usb-t111406.html For Install of XP you should NOT make new partition as you say you are doing. After booting from USB-stick with TXT-mode of XP Setup, then just Select the C: drive of your Harddisk for Install of XP. If you Delete or Create partitions at that stage, then you get the trouble of not being able to launch the GUI-mode of XP setup. Direct after Delete or Create of Partitions in TXT-mode of XP Setup, you always need to Reboot in TXT-mode of XP Setup. So in that case you go TWICE through the first part of XP Setup. This is the way to prevent your problem of NOT being able to launch the GUI-mode of XP setup. Read again the Tutorial:

In TXT-mode you should NOT delete partition, but just select the C: partition on which you want to Install XP and then Quick Format with NTFS FileSystem. If for some reason you delete the partition, you have to go TWICE through first part of TXT-mode Setup in order to prevent your problem. See http://www.msfn.org/board/index.php?showtopic=111406

SOLVED the problem of missing file setupORG.exe in case of XP Source slipstreamed with DriverPacks. The file setup.ex_ used to edit the floppy image must be taken from the original XP setup source, since slipstreaming with DriverPacks makes a new setup.ex_ which when used will cause the reported problem of missing setupORG.exe Install of XP including DriverPacks did run now very well NOW after second Reboot for GUI-mode the DriverPacks are extracted as it should be Loading of XP_RAM.ISO in only 10 seconds from internal Harddisk into firadisk RAMDISK is preferred, instead of loading the RAMDISK in 25 minutes from USB-stick. In this way one can Install XP from USB without booting from USB.

Including the 5 small DriverPacks (C CP L M and W) is quite useful and the extra load of 36 MB of the OEM folder does not take too much time or space. For Sound and Graphics DriverPacks the load is rather heavy and I decided then to provide the specific required drivers in $OEM$\$1\Drivers folder. DriverForge is used automatic at T-9 to install these drivers by using UserExecute command in [setupParams] section of winnt.sif file. In this way the extra load remains limited and all drivers are installed during XP Setup. In the case of using DriverPacks, what is causing then the Error of setupORG.exe is missing ? Is it may be a name conflict by using twice the same mechanism of fake setup of Pyron ? It would be nice if the problem can be solved.

Internal Harddisk partition for Install of XP was first formatted (e.g. from PE environment) Then BOOT_IMG.exe was used to make internal Harddisk bootable with grub4dos entry in newly created boot.ini menu. After Reboot Select Loading XP RAM install from grub4dos menu as given above. There is no USB-stick used in my approach. There is no boot.ini problem. (booting is all the time from the same Harddisk partition used for Install of XP) boot.ini before Install of XP [Boot Loader] Timeout=20 Default=C:\btsec\RMLD1.bs [Operating Systems] C:\btsec\RMLD1.bs="PE 1 - Boot X78W.img from RAMDISK" C:\grldr="Start GRUB4DOS Menu" boot.ini AFTER Install of XP [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect C:\btsec\RMLD1.bs="PE 1 - Boot X78W.img from RAMDISK" C:\grldr="Start GRUB4DOS Menu"

Successful tested for Install of XP-SP3 on real hardware (including internal multi-cardreader) Did not use USB-stick. AFTER format of Harddisk install partition, I installed grub4dos as boot option in boot.ini menu using BOOT_IMG.exe Then copied folder Inst with XP_INST.IMA and XP_RAM.ISO to Harddisk. Made entry in menu.lst without the mapping for USB-stick title Loading XP RAM install - /Inst/XP_RAM.ISO ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) # map (hd0) (hd1) # map (hd1) (hd0) map --hook chainloader (0xFF)/I386/SETUPLDR.BIN After Reboot Select Loading XP RAM install from grub4dos menu Loading of XP_RAM.ISO in only 10 seconds in firadisk RAMDISK (instead of loading in 25 minutes from USB-stick) TXT-mode FileCopy in only 1 minute GUI-mode has an extra immediate Reboot. Total XP Install time 15 minutes Then tried to do the same with XP-SP3 Slipstreamed with UpdatePack and 5 DriverPacks. After first Reboot for GUI-mode the DriverPacks were extracted successfully. After second Reboot for GUI-mode has problem of SetupORG.exe NOT found. Has to look into more detail what is causing the problem ....

Very interesting development cdob Thanks for sharing XP_INST.IMA

= PROGRAM UPDATE - U_XP_SET Package - Install XP from USB Update - BOOT_IMG.exe - Make_IMG.exe - Make_USB.exe - USB_XP_Setup.exe - Small corrections in routines for Install of Boot Image files Download - U_XP_SET =

There are some problems: $WIN_NT$.~BT\BOOTSECT.DAT is not made correct for NTFS formatted USB-stick, so that TXT-mode will not start. OEM folder with BTS DriverPacks is not copied to root of USB-stick (you can correct for it by manual copy of OEM folder). still testing .... - winnt.sif errors with InputLocale and InputLocale_DefaultUser entries which get closed with 2 doublequote's - original entry of [setupParams] section of winnt.sif gets lost - [unattended] section of winnt.sif not removed At list of partitions in TXT-mode setup an error occurs. USB-stick (1GB) too small for XP Install. Error due to wrongly proposing USB-stick as Install partition.