ilko_t

You are right, where is my brain The reason is that on removable drives Setup will not recognize the second partition and will bluescreen with 0x0000007B. On fixed disks this doesn't happen as far as I remember, but we need to make them removable anyway, because of the boot.ini/ntldr/ntdetect.com placement, using rdummy.sys. So the second partition won't be recognized again. In your case, with removable drive, SetupSourceDevice = \device\harddisk1\partition2 won't work as well, as Setup won't find the second partition, unless you add cfadisk or dummydisk during Text mode, but as I mentioned, this will make Setup place boot files on the USB drive, rather than on the internal hard disk, plus drive letters will be shifted. Can't think of any quick solution to your problem, will post later if any idea comes up. Again, sorry for misleading you.

What bootloader is currently on the stick? To have both I guess you should use two setupldr.bin files and winnt.sif renamed to winnt.sdi for example. One of setupldr.bin's (from server 2003 SP1 which you should already have used when making BootSDI) hex edited to use winnt.sdi, fix checksum check after hex editing. Copy ntdetect.com to root. winnt.sdi: [SetupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdpath=BootSDI.img"Beware, small/capital letters do matter, BootSDI.img <> BOOTSDI.IMG. Alternatively- do you have LiveXP_RAM.iso already created? Use grub4dos ISO emulation to load it: title Start LiveXP_RAM ISO map --mem /LiveXP_RAM.iso (hd32) map --hook root (hd32) chainloader (hd32) Load normal LiveXP title Start LiveXP chainloader /setupldr.bin Start grub4dos either via an entry in boot.ini: c:\grldr="Start Grub4Dos" or install Grub4Dos MBR or bootsector on the USB stick, using grubinst_GUI: http://nufans.net/grub4dos/grubutil/grubin...-2008-01-01.zip Latest grub4dos/grldr file: http://nufans.net/grub4dos/

I did try several times, couldn't manage to get it screwed. Can you zip all your program log files from \backups\ directory and attach them here or upload at www.datafilehost.com for example? Comes from MkMigrateInf.cmd. Compare:http://www.911cd.net/forums//index.php?showtopic=19663 0x00030001 is a flag, but what exactly it means I cannot see: http://msdn.microsoft.com/en-us/library/ms794514.aspx

Setup already creates a bunch of log files in \windows\. I am not aware of any additional parameter, which would cause more verbose output. As for the errors above- I'd ignore them if setup went fine.

Yep. And MS guys screwed up something in the FAT/FAT32 driver in windows after 2000. You can put many things. Any Windows PE would work just fine, NTFS support is as in normal Windows.Grub4dos is happy with NTFS, so everything is up to what you are booting with it. Vista Setup/Vista PE is fine as above. GParted 0.3.4-8 is OK from NTFS, later versions- not. PartedMagic (after 3.0 tested) is fine too. Ubuntu maybe fine too. Second partition is always an option. Most likely- no, it should not interfere. Not quite sure which lines should be amended. Do a quick search at msfn.org, I've seen many topics about modifying disk space requirements.

Just make a second partition, set it active and prepare the setup files there. No need to use SetupSourceDevice directives in this case.

What's your idea? How putting Setup files in a second partition will make them safer to viruses etc.? As for your question- SetupSourceDevice = \device\harddisk1\partition1 Do you notice partition1? It could be partitionN. But boot files, ~BT folder has to be in the active partition anyways.

Wow, nice The only ideas I have about not getting U: - A-Data USB stick has the removable bit flipped, but then why your windows was seeing it as removable, but not the Setup? Or it has abilities to emulate CD-ROM device, does it? Other than that I am clueless why this would happen. As for the dummy file- did you try to create a second one? Other way is to edit txtsetup.sif and space requirements. Mind you- FAT32 could be VERY slow, NTFS outperforms it in times: http://www.msfn.org/board/index.php?showtopic=125116 Anyway, glad you made it and thanks for reporting back edit- BTW I wonder how you managed to place 5.5GB file in FAT32 partition. The maximum file size is 4GB - 1byte, maybe this explains the error you had. Try putting 2 dummy files.

1. Build UBCD4Win, the source you give it must NOT have custom drivers integrated. http://ubcd4win.com/howto.htm Do not select burn to CD and create ISO. 2. Start WinSetupFromUSB. Format the USB stick. Select UBCD4Win/BartPE/WinBulder option and with the browse button point it to D:\ubcd4win422\BartPE\ if you installed UBCD4Win to D:\ubcd4win422\ 3. Copy manually your customized XP CD to the USB stick, say in U:\XP_CD\ if U: is your USB stick drive letter. 4. Start from USB on the laptop and launch UBCD4Win. Open My computer and check what drive letter got your internal hard disk/first primary active partition. most likely C:. Check USB drive letter as well, say it's F:. Start->control panel->computer management will give you access to Disk management too. You can check all the above there. Once there go to start->cmd ( command prompt). Once in the back box type F:\XP_CD\winnt32.exe /noreboot /makelocalsource /syspart:C: /tempdrive:C: /unattend:F:\XP_CD\I386\winnt.sif 5. When copying is completed shut down the laptop, remove the USB stick and start from the internal hard disk. Setup should start from Text mode as normal. You do NOT need the USB stick anymore.

migrate.inf: [Version] Signature = "$Windows NT$" [Addreg] HKLM,"SYSTEM\MountedDevices",,0x00000010 HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",%REG_DWORD%,1 HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\ 5C,00,3F,00,3F,00,5C,00,53,00,54,00,4F,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6D,00,6F,00,76,0 0,61,00,62,00,6C,00,65,00,4D,00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,31,00,36,00,66,00,37,00,32 , 00,32,00,61,00,34,00,26,00,30,00,26,00,52,00,4D,00,23,00,7B,00,35,00,33,00,66,00,35,00,36,00,33,00,3 0 ,00,64,00,2D,00,62,00,36,00,62,00,66,00,2D,00,31,00,31,00,64,00,30,00,2D,00,39,00,34,00,66,00,32,00, 2 D,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7D,00 [Strings] ;Handy macro substitutions non-localizable REG_SZ = 0x00000000 REG_BINARY = 0x00000001 REG_DWORD = 0x00010001 REG_MULTI_SZ = 0x00010000 REG_SZ_APPEND = 0x00010008 REG_EXPAND_SZ = 0x00020000 winnt.sif: [data] floppyless="1" msdosinitiated="1" winntupgrade="no" win9xupgrade="no" EulaComplete="1" Quickly prepared USB stick with 'Copy setup boot files only' option checked.

I have re-read all the posts above. What is strange is that it make an extra step when using rdisk(2), whereas it should be rdisk(1), which should be your internal disk. rdisk(0) is the USB stick if booted from it. This means that most likely the USB card reader shifts disk order, but even with that you should be able to continue setup with the proper boot.ini entries. It may give you again "Windows could not start because of a computer disk hardware configuration problem" if windows is installed in another folder, not Windows. multi(0)disk(0)rdisk(2)partition(1)\WINDOWS If that's not the case then maybe USB card reader gets on the way only during ntldr/ntdetect.com phase, and later on does not, thus windows losing location to the Windows folder. After a few attempts to start it perhaps the file structure got corrupted, hence the so called F8 menu. Maybe the best option for you would be to start Setup from PE environment (BartPE, UBCD4Win, WinBulder...), put XP source on the USb disk as well, and copy all setup files to the hard disk winnt32.exe /noreboot /makelocalsource /syspart:F: /tempdrive:F: where F: is the first primary partition on it, made active. Add /unattend:winnt.sif if you have customized answer file in your source. Winnt32.exe is in I386 in your XP setup source/CD. After that step remove the USB stick and start from the internal hard disk. Setup should start from Text mode just as if started from a CD. Using this way USB card reader will not get on the way, shifting hard disk order.

Ok, you got me here. When you changed HD mode did you retry Text mode part or just went to the GUI mode? Try redoing Text mode.

I am getting lost here. You are saying you start from USB every time. On the USB disk you should not have anything about Vista or Ubuntu. Using menus to launch Second part of setup (GUI mode) should not get you to the screen posted above. That's Vista's boot manager. Why are you saying it's not Vista? Where did it come from? Where did Ubuntu come from? Didn't you format the partition on your hard disk?

Can you elaborate about the F8 screen? Is that with the options about Safe mode, Safe mode with networking etc. etc. ? What is the exact error message when you select which option? Is it on a blue background, with error code 0x0000007B or something similar? If yes- try redoing the Text mode again, formatting the partition in question. Do you have in BIOS options about the Hard disk mode IDE/SATA or AHCI off/on? Try disabling AHCI/setting it in IDE compatible mode.

Open up BOOT.INI in the USB stick with Notepad, delete contents and copy-paste this: [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="Second part of XP Professional setup from hd 0 part 1" /FASTDETECT multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Second part of XP Professional setup from hd 1 part 1" /FASTDETECT multi(0)disk(0)rdisk(3)partition(1)\WINDOWS="Second part of XP Professional setup from hd 2 part 1" /FASTDETECT multi(0)disk(0)rdisk(4)partition(1)\WINDOWS="Second part of XP Professional setup from hd 3 part 1" /FASTDETECT multi(0)disk(0)rdisk(5)partition(1)\WINDOWS="Second part of XP Professional setup from hd 4 part 1" /FASTDETECT multi(0)disk(0)rdisk(6)partition(1)\WINDOWS="Second part of XP Professional setup from hd 5 part 1" /FASTDETECT Go through Text mode again, delete ALL partitions on the internal disk and create a new single one. Install in it. When starting Second part, try the above entries in the boot menu one by one. Does one of them continue with the GUI mode? Which one? Use the same one to start Windows for first time.

Is any of those files read during Text mode? The idea is to use 4 different sets of txtsetup.sif/setupldr.bin and the above mentioned files renamed. Using txtsetup.sif we can rename a file while being copied. txtsetup1.sif DPCDLL1.DLL--->DPCDLL.DLL PIDGEN1.DLL--->PIDGEN.DLL Would that work? A script prior to Text mode would have downsides: -adds an extra step to the setup process, very few people read ReadMe files and many already fail when installing from USB simply because they don't start from USB for the second or third step, no matter if you put that info in warnings, message boxes or whatever. I'd keep it as close as possible to normal CD-like install. -as it has to be DOS based, limits us to FAT16/32, unless we find freely redistributable DOS with NTFS support. The ones I know about, AFAIK we may not redistribute. Hopefully I am wrong. FAT16/32 impacts file copy speed during Text mode A LOT. I'd rather stick with NTFS when possible. Have a look at this quick comparison: http://www.msfn.org/board/index.php?showtopic=125116 I've seen reports on some systems file copy with FAT32 used, may take as long as 1.5 hours NTFS cuts it down to 12-15 minutes on the same machine. If the above can't work, my opinion for setups like yours, is that the best way remains PE based disk and launching setup from there, or preparing the setup files on the destination disk, manually or by script changing the files required for your needs. Wimb has already made a working solution: http://www.msfn.org/board/index.php?showtopic=121446 In the latest version he mentioned an option to put all needed files on the destination disk, just like what winnt32.exe would do. With slight modifications or additions this could be made to suit your needs. Another plus is that this method does not have the limitations for the unattended section, which I believe you use.

If you cannot figure out how to amend BOOT.INI just post here your current BOOT.INI on the USB stick. Take a picture of the partition screen during Text mode setup, post it here as well.

Just correct BOOT.INI on the USB stick. Look the post above yours, understand what it says and fix your boot.ini. Did you start from USB for second time, to continue installation? Did you start from USB for third time to log into Windows for first time? You have to start from USB 3 times: 1. Text mode part 2. GUI mode part 3. First start of windows

Hi, Nice to see you around 1. WinSetupFromUSB for example can put up to 10 different 2000/XP/2003 in the same partition by patching setupldr.bin and setupdd.sys. Same can USB_multiboot. Downside is that full source is copied. However, with the included \files\tools\DFHL.exe and using NTFS, occupied disk space could be reduced dramatically. Credits to cdob and Jaclaz for the idea. 2. Unfortunately not possible as of now . If someone, someday, makes windows driver for the grub4dos ISO emulation, life will become sooo easy: title Start XP Pro Setup map --mem (hd0,0)/xp_pro.iso (hd32) map --hook root (hd32) chainloader (hd32) title Start XP Home Setup map --mem (hd0,0)/xp_home.iso (hd32) map --hook root (hd32) chainloader (hd32) ... Attempts to use windows ramdisk.sys have failed so far, plus we'd hit the limitation of 500MB maximum size even if possible. The grub4dos way seems the easiest and straightforward, but until such driver is made we can only wish. Alternative way for using ISOs- USB sticks with controller, which can emulate CD drive: http://www.msfn.org/board/index.php?showtopic=121502

From the post given you above:http://www.msfn.org/board/index.php?showto...mp;#entry815523 Do you see partition1, partition2 and so on? The number of the partition where Windows is being installed to has to match the one in BOOT.INI. In the above example Windows is in partition2, so BOOT.INI must have partition(2). Got it? The part in WinSetupFromUSB BOOT.INI adjustments was put there on purpose, tooltips for each element tell you what is what, just hold the mouse pointer above element Anyway, glad you made it

Make BOOT.INI on the USB stick like this: [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="Second part of XP Professional setup from hd 0 part 1" /FASTDETECT multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Second part of XP Professional setup from hd 0 part 2" /FASTDETECT multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Second part of XP Professional setup from hd 0 part 3" /FASTDETECT multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Second part of XP Professional setup from hd 1 part 1" /FASTDETECT multi(0)disk(0)rdisk(2)partition(2)\WINDOWS="Second part of XP Professional setup from hd 1 part 2" /FASTDETECT multi(0)disk(0)rdisk(2)partition(3)\WINDOWS="Second part of XP Professional setup from hd 1 part 3" /FASTDETECT As I get it you passed Text mode and you fail at starting GUI mode. Try the above options one by one. Add more lines if necessary, you should get the sequence. Check FAQs: http://www.msfn.org/board/index.php?showtopic=116766 Q4/A4. Check this post too: http://www.msfn.org/board/index.php?showto...st&p=815523 Does partition number as shown on partition screen at Text mode match partition(X) in BOOT.INI? Do you have card readers in this machine? Try disabling them if possible. Is this a laptop or a desktop? Try using another USB port for the USB stick.

Hmm: http://support.microsoft.com/kb/234048 Did you put back unattended section? Does it include oempreinstall=yes? That version of GParted is not supported yet, on the screen it says from which to which versions are supported- 0.3.4-8 to 0.3.9-4. With the next version will add the newer GParted, or just replace it with PartedMagic, which includes GParted along with other tools.No idea why menu.lst would disappear, I cannot recreate the problem, nor I see anywhere in the code when menu.lst could be deleted. Maybe if you tell me the exact steps to reproduce it I could fix it. To fix it manually without starting from a scratch: Copy menu.lst and default if not in USB root from \files\grub4dos\. Add the following lines to menu.lst: title Windows XP/2000/2003 Setup- First and Second parts root (hd0,0) configfile /winsetup.lst savedefault title Start UBCD4Win root (hd0,0) configfile /ubcd4win.lst Assuming winsetup.lst and ubcd4win.lst are still intact in root.

So file is fine and USB stick should have one single partition after HP tool. Try on another computer.

Try another computer first, there are no disk changes if you do not continue setup. Use F3 or just power off the computer once you finish looking at the partition screen. migrate.inf now looks fine, except the binary data is on multiple rows. Is it the board changing that, the program you open up migrate.inf with or an error when it was produced? Just make sure 5C,00,3F,00,3F,00,5C..... is one whole line. I use Notepad++ instead of Windows Notepad, has tens of great features. In this case view-->wrap unselected. Try deleting all partitions on the USB stick, use one whole partition and redo the preparation, this may matter.BTW how did you partition it?

Open regedit with the USB stick inserted and go to HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices Do you see multiple entries \DosDevices\R: where R: is USB stick drive letter? If that's not the case- I am running out of clues why Setup ignored migrate.inf. Can you run the Setup on another computer just to the partition screen in Text mode, is the USB stick U:? Did you copy paste here all contents of migrate.inf? Binary data must be on one whole line and a few other lines are missing in what you posted.