ilko_t

Nope, the procedure is the same.Do you use in Windows where you prepared the USB stick Hitachi microdrive filter driver or dummydisk.sys to make USB sticks seen as removable? Can you compress and attach WinSetupFromUSB.log, it contains information how Windows saw the USB stick. You may find backed up log files in d:\programs\WinSetupUSB\backups\ directory, just renamed with date-time stamp, just pick the largest one if you have many. Did you by any chance move the radio button USB disk type to fixed? Mind you file size given to fsutil is in bytes.

I doubt it's possible using this way of installation. Unattended section is removed because even with an empty section Text mode setup will attempt to install windows where ~BT and ~LS folders are. Adding Repartition=Yes most likely will make Setup to attempt to repartition the USB disk, NOT the internal hard disk, and will fail of course because the Setup files are there and USB disk is write- protected. If that's so important to you to automatically repartition the disk, you may play with this way of installing: http://www.msfn.org/board/index.php?showtopic=119742 However, it has limitations and you will not have an "universal" USB disk, understanding of the Setup process is also required. Just an idea, not tested which disk will become target with Repartition=Yes.

As for the drive letter- did you use USB hard disk? Or USB stick which is seen as fixed by windows? Did you install WinSetupFromUSB in a path without spaces or special characters in it? Do you have migrate.inf in ~BT folder on the USB stick? Does it say about U: ? As for the program files location- that's actually the last workaround left for fixing because of the removed unattended section. Maybe adding a line to presetup.cmd like: REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion" /v ProgramFilesDir /t REG_SZ /d "D:\Program Files" /f md "D:\Program Files" Similar for CommonFilesDir if is desired. This is not tested, just an idea. Not sure if Setup already placed during Text mode files for WMP or IE in c:\program files. Tests needed. If presetup.cmd is too late to apply this changes, then we may have to use any means during text mode, setupreg.hiv, setupoem.inf or something like this. Not sure when this key is created during Text mode, it's not present in SETUPREG.HIV or HIVESFT.INF so must be dynamically created at some point. Hope cdob is reading this, he is pretty good at this stuff. edit: BTW - quick and dirty workaround: unattended section is remove because even with an empty section Text mode setup will attempt to install windows where ~BT and ~LS folders are. But it will fail and return to partition selection screen if in that partition has less free space than the defined in txtsetup.sif. Limited solution- put back unattended section, edit txtsetup.sif and set required free space more that you have free space on the partition on the USB disk/stick. Or create a dummy file, occupying so much space so it becomes less than the defined in txtsetup.sif: fsutil.exe file createnew dummyfile.dum 1000000000 The latter is tested and works, but has limited usage.

Winnt.exe with the proper parameters will prepare the SSD with all needed setup files. After that USB sick is no longer required, so I wouldn't worry about the drive letters. Not sure though if it would preserve them, the file used for the purpose is migrate.inf in ~BT folder. After winnt.exe is completed check if migrate.inf exists in the SSD\$win_nt$.~bt\ and delete it if does. Unplug the USB disk and start the laptop from the SSD to start Text mode setup.

As for winnt.exe- you need to use /t:X or was it /t:X: where X: is the drive letter for the SSD disk/partition. http://www.microsoft.com/technet/prodtechn...t.mspx?mfr=true I guess for NT 4 parameters are the same. As for the error during 2003 setup- you will have to format the partitions in question using other program- gparted, format from DOS etc. 2003 setup detects the previously placed setup files, from winnt.exe, and refuses to format such partition, thinking its contents are critical for the setup.

Yes- Ubuntu cannot find the big squashfs file (filesystem.squashfs), as it is not where is expected. It's location perhaps could be passed as a kernel parameter, just an idea: try boot=/ubuntu/casper or ask in ubuntu forums for the proper syntax, if possible at all. initrd=/ubuntu/casper/initrd.gz is wrong. Should be initrd /ubuntu/casper/initrd.gz. Look at the examples given.

WinFLPC is already supported, look at the first post in this thread. As for NT- hmm, I doubt. It's very outdated, does it support USB at all? http://support.microsoft.com/kb/q196661/ You may play setting it up when booted into PE, using winnt32.exe, just an idea.

Have a look at this thread: http://www.msfn.org/board/index.php?showtopic=119742 Not tested if booted from CD-like media. Downsides- USB card readers or other internal hard drives may and does shift USB disk location- \device\harddiskX\partitionY.

Have a look at these posts too: http://www.msfn.org/board/index.php?showto...st&p=797585 http://www.msfn.org/board/index.php?showto...st&p=815048

@James_patageul About UBCD4Win- you should have ubcd4win.lst in root of USB stick, menu.lst entry should be like: title Start UBCD4Win root (hd0,0) configfile /ubcd4win.lst About ISO files- some examples which do work: http://www.boot-land.net/forums/index.php?showtopic=5041 You may also look at the subforum, the question has been discussed many times with detailed answers: http://www.boot-land.net/forums/index.php?showforum=66 About Ubuntu: http://www.msfn.org/board/index.php?showto...9&hl=ubuntu For newer versions you have to check and amend kernel parameters if necessary, check isolinux.cgf or syslinux.cfg in Ubuntu ISO. edit: I've noticed your partition with XP Setup is FAT32, have a look at this thread: http://www.msfn.org/board/index.php?showtopic=125116

Sorry, I did not understand what you exactly mean. Is it automatic selection of the boot menu upon start? Right now what it does: -upon first start of Text mode part, the GUI part is made default -on next relaunch, as the GUI mode is set default, it will be started There is a timeout value in seconds in menu.lst and winsetup.lst, after those seconds the default entry is auto launched (now is GUI mode). You can see the timer on the bottom of the grub4dos screen. If you press any key this timer will stop and default entry will not be auto launched. I thinks timeout value in both menu.lst and winsetup.lst was decreased to 10 in 0.1.1, but you could also play with it- just open up menu.lst and winsetup.lst in Notepad and change timeout value to what suits you. The default entry stays GUI mode, so for the next full setup Text mode must be selected manually, GUI mode will remain default and auto selected if you don't press any key. Did this answer your question?

You are welcome, happy holiday to you too

Well, just check for BOOT.INI on old hard drive active partition. Most likely it become first at boot order and it's BOOT.INI is used. Reformatting if it's just because of this issue is overkill, we just have to figure out which BOOT.INI is used and correct it's entries.

Which one is the first line? Which one do you exactly see and use? Default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS only shows which line, listed under [Operating Systems] is default: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer I asked to you to remove /usepmtimer from default=... line, as AFAIK it is not expected there and may lead to unpredictable results. Did you remove it and test? Have you connected another mass storage device (card reader, hard disk etc.) after the setup?

Remove /usepmtimer from the second line and decrease timeout value to 1 or 2 so the USB repair entry won't bother you. [Boot Loader] timeout=2 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 /usepmtimer multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="USB Repair NOT to Start Microsoft Windows XP Professional" /noexecute=optin /fastdetect About /usepmtimer switch: http://support.microsoft.com/kb/895980

Glad you made it As a matter of fact, similar, if not the same error is displayed while presetup.cmd finds USB drive letter and there is an empty card reader attached, but clicking IGNORE gets you going, haven't read a report, when it hangs. In your case I suspect Windows itself was screwing up, as we removed those lines in presetup.cmd, which find the drive letter. Next time promise you pay more attention to the questions you are were asked, no matter how irrelevant they may seem to you. As for the USB entry in menu- read \WinSetupFromUSB\Docs\HOW-TOs.txt

Internal card readers connect to the USB bus as well, so in our case internal=external. In both cases they create for windows a disk drive, with no disk in it. You have to disconnect the card reader, leave ONLY one hard disk connected, start Text mode, recreate partitions on it, deleting the old ones, RESTART computer right after that part (F3 key), without continuing Text mode, start Text mode again and install Windows in the first newly created partition if you set up BOOT.INI like this. Then report what happens at GUI mode. dd is to be run on the same computer, so ignore it for now.

You could try another XP. Nope.You did not answer if you have USB card readers and did you unplug all unnecessary hardware, mass storage devices to be specific. Empty card readers or printers with such DOES matter. During Text mode how many disks did you see on the partitioning screen?

You may leave just this: REM ===========Added by WinSetupFromUSB============ IF EXIST %systemroot%\system32\setupold.exe DEL /F %systemroot%\system32\setupold.exe IF EXIST c:\boot.003 DEL /F c:\boot.003 REM ====================END======================= EXIT

grub4dos loads NTLDR, which loades boot.ini for boot options. After that grub4dos has nothing to do with installation or whatever. On the error box you are getting, is there IGNORE button? Did you try it? Do you have card readers? Did you unplug them? You don't mean PC restarts, but setup continues to a blue screen/backgroung (not BSOD), which throws you that error, right?Find presetup.cmd in ~LS\I386 folder on USB stick. Open it up and remove all lines, but last one- EXIT. Go through Text mode again, then tell what happens during GUI mode.

I've never seen that error. A few random ideas: - disconnect all unnecessary hardware- USB card readers, CD/DVD, the second hard disk etc. - add this switch to BOOT.INI on the USB stick /SOS and start GUI mode again .... [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 0 1" /fastdetect /sos How far does it go? What is the last output on screen you can see?

You need to figure out which partition is active, or set the partition where windows is on active. Then place boot files on it. Amend BOOT.INI on that partition, so it has the proper rdisk and partition values: http://www.msfn.org/board/index.php?showtopic=116766 Q4/A4 You may use any kind of partition tool, GParted for example. Look at this post and the pictures in it too: http://www.msfn.org/board/index.php?showto...st&p=815523 Deleting all partitions should not be necessary, as long as BOOT.INI has the correct values and you have the proper partition set active.

What did you use to prepare the USB disk? The part it asks you for a CD- is it during Text mode or GUI mode, when exactly?

Would start windows if you boot again from USB? What does BOOT.INI contains on the USB stick? How do you know "wxp is on multi(0)disk(0)rdisk(4)"?