ilko_t

The option is: Must be set to USB-Harddisk, using option 0 to change it.

When preparing the USB disk with USB_multiboot did you select disk type- FIXED?

http://www.msfn.org/board/winsetupfromusb-...-1-t137731.html Integrating BTS driver packs option is not applicable as is not available for x64 versions.

@mjphelan Did you replace ubcd4win.lst in USB stick with another one? The program should add that file to the root of USB stick with the correct syntax, no double slashes. Look at \WinSetupFromUSB\files\grub4dos\ubcd4win.lst. Double slashes worked with older grub4dos versions, which were(are?) used in UBUSB, but not with newish versions.

Can you zip and attach with your next reply txtsetup.sif?

Could you reply to the request of Jaclaz? It would be interesting to find out why it's reported with wrong geometry. BTW- HDHacker can be found in \WinSetupFromUSB\files\tools\.

Glad you got all solved

Where is exactly WPI folder at your CD? I can include that location to be copied if present... As for the deleted files- during Text mode USB is write-protected by an registry entry merged from migrate.inf. This works for XP SP2 and 3 only. Default behavior of Setup when msdosinitiated=1 is to delete files as they are copied, mostly the compressed ones. During GUI ~BT and ~LS folders are deleted at T-1. This is taken care of at start of GUI by changing msdosinitiated=0 in $winnt$.inf in system32 folder, which is winnt.sif replica used during GUI. So in short- this is limitation with this method of install. Until a way to protect files from deletion, or trick Setup not to delete them comes up, there is no much to be improved. Alternative ways of installing, which do not have this limitation: http://www.msfn.org/board/2-t137714.html http://www.msfn.org/board/2-t121446.html

You most likely have UNATTENDED section in your original winnt.sif file. If it's present EULA ate Text mode is not displayed.WinSetupFromUSB removes that section just for the Text mode stage and merges is back at start of GUI mode in \windows\system32\$winnt$.inf. The reason for that is that if the section is present, even empty, Setup will attempt to install Windows on the USB stick without asking user, and will succeed if the is enough space on it. If EULA bothers you put EulaCompleted="1" in DATA section. As for the password- try without quotes ", also look at setup log files in Windows directory for any other clues. How is WPI launched? Where are its files placed and at what stage they are deleted? What exactly is deleted?

Maybe the new version of RMPrepUSB is worth a try? http://www.boot-land.net/forums/index.php?...;showtopic=7739 http://www.datafilehost.com/download-d9c267f2.html

1) No idea of the top of my head. 2)Yes, for this method of install from USB, for installs of any Windows versions but XP SP2 and SP3.

Did you complete the first part of Setup, the text based? Did you install Windows on the first partition of the internal disk? Do you have any other partitions on the internal disk? This can be seen on the partitioning screen during Text mode. It clearly displays partition Y [FILE_SYSTEM] TOTAL_SIZE (AVAILABLE_SPACE). You are interested in partition Y, the one you are installing Windows to. That number Y should be present in BOOT.INI--> partition(Y). If you have used the latest versions of the program you should have a few entries below the line "TRY THESE IF YOU ATE GETTING HAL.DLL...error". Just test them all one by one. The error about missing hal.dll means that NTLDR did not find next files required to continue boot in the path specified in the selected entry in BOOT.INI. Since we are booting from the USB stick, the boot.ini file which is applicable is the one on the USB stick. Check FAQs, Q4/A4: http://www.msfn.org/board/faqs-t116766.html Amend BOOT.INI on the USB stick accordingly, or use the pre-made entries if used the latest version of the program.

Your BIOS shows the USB stick as a floppy, rather than a hard disk which is needed. Check in BIOS if there is an option about USB mode- USB-HD, USB-ZIP, USB-FD or something similar. You'd need HD mode. Google- ing around it appears that option should be in Integrated Peripherals-->USB Storage emulation set to HDD. http://www.avforums.com/forums/home-cinema...ml#post10480758 What program did you format the USB stick with, RMPrepUSB? Grub4dos version should not be relevant for your problem. As for the "history" links- those are older grub4dos versions. No need to play with that for now. BTW- thanks for the detailed reports, it's pleasure to help people who post all the relevant information.

While in grub4dos prompt issue: find /winsetup.lst cat (fd0)/winsetup.lst cat (hd0,0)/winsetup.lst Please post the output of each. Next- try replacing file GRLDR (without extension!) in USB stick root with one from the latest releases here: http://nufans.net/grub4dos/ For example: http://nufans.net/grub4dos/grub4dos-0.4.4-2009-10-06.zip <--- latest one http://nufans.net/grub4dos/grub4dos-0.4.4-2009-05-13.zip <--- randomly chosen http://nufans.net/grub4dos/history/ : http://nufans.net/grub4dos/history/grub4do...-2008-05-14.zip http://nufans.net/grub4dos/history/grub_for_dos-0.4.2.zip Please report if you have success with any of them, mention grub4dos version, it also appears at the top of the "light-blue Windows XP Pro install options screen".

It has nothing to do with partitions. As cdob already pointed out Setup would place boot.ini at hd0 as reported by BIOS. This is the booted disk, the USB one.Grub4Dos can manipulate that and "swap" them. In this scenario hd1 will be the next disk according to boot order in BIOS, typically the internal hard disk. In case of two- it should be the one which is higher in BIOS boot order. This is desired behavior, it doesn't matter how many internal disks you have as long as next in boot priority is the desired one. AFAIK behavior with USB card readers present for example is unknown. This might shift internal disk to hd2 etc. Now the "buggy" motherboards/BIOSes, which no mather what you do display the USB stick as a FD became useful- USB stick is fd0 and internal disk is hd0, no need of extra "exercises" to get proper boot.ini.

What's actually the issue? Please next time attach as a file such lengthy log, rather than copy-pasting it. Compress it if it exceeds allowed file size for attachments, or use free file share sites to upload it, such as www.datafilehost.com.

Look at \WinSetupFromUSB\Docs\HOW-TOs.txt.

You seem to be using GNU GRUB, which is NOT the needed Grub4DOS. Install and use the latter: http://diddy.boot-land.net/grub4dos/Grub4dos.htm

It's on blue background, right? Lets try again:

Are you using XP at least SP2 or 3? If not- slipstream SP3: http://www.google.com/search?hl=en&rlz...sp3&spell=1

Maruco, your reports are quite confusing and differ from each other Please answer all question asked, also mention what is written on the blue screen, what error code? That's the most important part of the blue screen. Look at the pinned FAQs thread too, is that error code mentioned there? Do not QUOTE lengthy posts just to answer them, use ADD REPLY button instead, this makes thread much easier to read.

So when you choose TXT mode you get HAL.DLL not found error, right? If yes- try changing C:\btsec\XPSTP.bs to A:\btsec\XPSTP.bs and report if you get past HAL.DLL error. Try with B:\btsec\XPSTP.bs too. You may get another error later on, that's fine, the point is to check if your USB stick is seen by BIOS as floppy disk (getting drive letter A:), rather than a hard disk. What laptop is that? Do you have any option in BIOS for USB mode- FD, HD, ZIP etc. ?

Do you reach any boot menu at all, or you get HAL.DLL error right after you start from USB? Do you pass the first part of setup, the text phase?

Meanwhile you may try this: http://www.msfn.org/board/2-t137714.html

The lines in red are what you have NOT done: WinSetupFromUSB.log is also incomplete. All this requests have a reason behind and are also to save both parties time. Please read and follow carefully. Although unrelated- it seems your source now is missing 3 files iastor2,3 and 4.sys, present earlier in C:\Boot\XPOEMENG\I386\. Did you make new changes to your source?