ilko_t

On real hardware it will behave in a different way. Use QEMU just for basic testing, until the partitioning screen in Text mode. This is for vers. 0.2.3. With version 1.0 you can go further, but you'd need larger image file as hd1 and the USB disk connected as hd0. After Windows is installed you'd need to change boot priority and boot from hd1. Again, real hardware is preferred.

You cannot. Those are limitations with the previous version. What exactly happens when you boot with the USB stick removed?

What has been changed so this time it found setup.exe? What is "dok"? I guess your USB flash drive? On the machine you tested, how many mass storage devices are present? Including USB card readers, internal hard disks etc. etc. ? To fix quickly the overwritten grub4dos MBR- start the program, choose the USb stick and select only the syslinux option, nothing else, and click GO. Ignore the message about NTFS and syslinux. Alternatively use grubinst_GUI.exe found in \winsetup\files\grub4dos to put new grub4dos MBR. Crosslinking this topic: http://www.boot-land.net/forums/index.php?showtopic=11072

In order to figure out what's happening a few tests would be needed, sorry, I can't think of any other way. First is to test with 0.2.3, which uses completely different method of installing (format or deletion of all contents of the USB disk is needed), second would be to test with a clean, unmodified source. 2003 trials are very good candidates: http://www.microsoft.com/windowsserver2003/r2/trial/installinstruct.mspx?lc=1033 BTW- is setup.ex_ uppercase? Try to make it if is not.

Ok, keep reading what I posted

Same error? About setup.ex_ ? Any other errors? What's the hardware you are installing on? Have you tested with WinSetupFromUSB 0.2.3 ?

It's the correct size. Copy it manually from \WinSetup\files\winsetup\PyronSetup\i386\. Some antivirus scanners still falsely detect it as a virus, so disable temporarily any antivirus software you have running. As for redoing the ISO- it really would be quicker and safer just to redo the USB disk. Test again and report. If you skip that file are there any other files causing troubles? Which ones? Next time put it in a zip archive and then attach it

Is folder \DRIVERS and its contents copied during Text mode? Do you see it once Windows is installed in C: or wherever you are installing to?Are the paths described in OemPnPDriversPath present in HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath ? Try also commenting out/removing LocalSourceOnCD="1" in winnt.sif.

What happens if you do NOT launch PLoP at all and use (hd1)? What hardware are you playing with, motherboard model if desktop or exact model if laptop? @cdob This reminds me the same issues as in here: http://www.msfn.org/board/install-2000xp2003-loaded-small-t139737-page-20.html Time for similar workarounds, adjusted txtsetup.sif and/or use of mnt.exe? Or you have something new in your magic sleeves?

Is file setup.ex_ present in G:\WINSETUP\XPpSP3\I386\ ? What's file size? Open G:\WINSETUP\XPpSP3.ISO or whatever the file name is and extract txtsetup.sif. Zip it and attach it with your reply.

Why (hd2)? How many internal disks do you have? Which one are you installing to? Describe with details. When you see that error can you press shift+F10 to get command prompt and look at presetup.log in \windows\system32\? type presetup.log Post the contents of that file or at least the last few lines.

Can you zip and attach WinSetupFromUSB.log and winnt.sif (removing any sensetive information such as serial number etc.) ? Backups of the log file cab archived are inside WinSetup\backups\ directory, find the applicable one. There is an option to add UBCD4Win/BartPE/Win FLPC/WinBuilder. Have you tried it? That's exactly its purpose.

Why do you need to use this Virtual flash drive? Did you try advanced options-->display disk drives on all interfaces? Sorry, no clue. WinSetupFromUSB comes with QEMU and support for real flash drives. This is tested and supported.

Umm, as I am reading it, mel2000 is attempting to load UBCD4Win as ISO, which supposedly would not work just like that: mel2000, read the pinned topics here: http://www.boot-land.net/forums/index.php?showforum=66

Thanks for getting back. Can you try version 0.2.3 and report if the same issue occurs?

Did you read the pinned FAQs topic? What instructions did you follow? Did you delete ALL partitions, this means ALL, not all except one or two? In which partition are you installing to? Did you try WinSetupFromUSB 1.0 beta6, which should not have any similar limitations? Did you try any of the other methods in the pinned topics? Did you search the subforum a bit? This error has been discussed in details numerous times already.

Do you get it when select "First part of Windows XP Professional setup" or you don't get the menu at all? Does it work in QEMU? Did you try the latest 1.0 beta6?

You get another link

This seems to be some custom script, you'd need to figure out what it does and how can be adjusted. What are contents of the $OEM$ folder, besides RunOnceExCU.exe, if that's the file name? BTW latest version is 1.0 beta6, although beta, it's fairly usable

Hmm, could it be an antivirus program or something of that sort interfered with file copy Were both builds tested on the same hardware, without any changes on it, including BIOS options?

This option applies ONLY to the source being transferred. Sources already transferred has to be manually adjusted as stated already. Was that your question? Please, write with details, do not expect the other person to guess what you mean, or "decode" your posts.

First I tried to slipstream SP3 and some other updates. After that didn't work I tried the unmodified MSDN SP2 ISO image which gives the same error. Both images work fine when burning it to a CD. I attached the files you asked, do you have any idea? Renaming the migrate.inf did not change anything. Thanks! That's very weird. I've just downloaded 2003 server trial German and Chinese Simplified versions: http://www.microsoft.com/windowsserver2003/r2/trial/installinstruct.mspx?lc=1033 Tests in QEMU, using old 80GB hard disk with USB-IDE adapter, under XP SP2 English, 1.0 beta6 : Can you test your build in QEMU? Just run WinSetupFromUSB, select the USB disk and check "Test in QEMU" option to see if you get to the partitioning screen. Added: Same positive result on real hardware- both sources loaded just fine to the partitioning screen. Can you figure out what has changed meanwhile? I doubt it suddenly just started working fine, there must be something changed.

In BTS DriverPacks BASE do you select method 1 or 2 (Settings-->DriverPacks method) ? The option in WinSetupFromUSB is intended only for method 2, the fake setup and OEM folder, I should have clarified that.