ilko_t

SP4 is the first one, which one is second of the two? What duplicated files? You have duplicated sections in a single file which you need to merge so the application properly would recognize your source is windows 2000.Lets start from a scratch. 1) Slipstream SP4 2) zip and attach txtsetup.sif from the source. I will check it and correct it if needed. 3) Wait for my answer and use again WinSetupFromUSB to reformat the USB stick and prepare it with the modified source.

I am not sure what exactly you did. You need to modify txtsetup.sif in your source as mentioned, wherever it is, not on the USB stick, and rebuild the stick using that new source.

Respect to the response time from Avira, 3 months and a half later

That's very weird, haven't been reported anything similar, it should detect at least your internal drives or complain that WMI is broken. The issue shouldn't be with your stick, but with your Windows. Have you installed changed anything lately? Try repairing WMI: http://www.nliteos.com/faq.html#Q26 http://windowsxp.mvps.org/repairwmi.htm Try also on another computer if you can.

What version are you using? Use latest 1.0 beta6 and post/attach winsetupfromusb.log file found in program directory.

Nope, it does not.It has to be only if you need another Vista/7. There are workarounds for multiple Vista/7 in the same partition, do a little search in this subforum, it's been discussed many times.

In this case delete UBCD folders (check in ISO or winsetupfromusb.log their names), syslinux.dat in root and the entries in menu.lst.

In your source open up txtsetup.sif and merge both [strings] sections into a single one and rebuild the USB stick. AutoIt would read only the first section, hence the undetected windows 2000 strings in the second.

What program did you use to partition and format the USB stick? Does it behave the same way on other computer? Try repartitioning it using RMPrepUSB or BootIce: http://www.boot-land.net/forums/index.php?showtopic=9460

How come i have the same behavior on both computers? And when i hide the first partion and in the same time the 2nd is active/primary .. why its not working? Try adding dummydisk.sys driver as boot bus extender, search in the "historical" thread. Why do you need 2 partitions on the USB stick? Drive letters mess most likely is because you had filter driver (removable-->fixed) running while preparing the stick. You'd need similar driver running to get proper drive letters. Or simply use single partition and no filter drivers. Now I am confused how far did you get, try using tested methods ( single partition and no filter drivers) and start experimenting once you get it working.

If it was added as an ISO just delete the ISO file and the corresponding entries in menu.lst, that's all. IMHO, the UI is quite simple that even a person don't know English much but have knowledge of PC system installation can use it without problem. The user should know what is XP, Vista, Win7, ubuntu etc rather than english.I highly doubt the translation is need. Here to state, I know Chinese. A simple guide(in Chinese) to each options might be more useful and easier to spread this piece of great software. +1

Please zip and attach txtsetup.sif from the small ISO file in WINSETUP directory on USB disk and winsetupfromusb.log from program directory or the backup folder.

SysLinux option requires an extracted ISO, grub4dos compatible ISO option requires ISO file, just a bit easier.

Thanks for reporting. It should also work as ISO, the field "PartedMagic/Ubuntu...", have you tried it?

Can you attach WinSetupFromUSB.log file found in program directory. Try renaming migrate.inf to .bak in ~BT folder. Are you installing from U3 USB stick? Do you have an option in BIOS about USB keyboard? Is it disabled or enabled? What are other USB options set to? What's the motherboard or laptop model? Similar issue:

Nice, removed attachments above.

Lol, killer jet lag, forgot to attach the file And yes for setup.cmd. Txtsetup.sif entries were already commented in the ISOs attached. Edit: Attachment removed.

Try with the file attached. What I did was to comment out both entries for USBBootW.exe and cnf. It's very weird only one of them gives an error. You would also need to comment out (put REM at front) each line mentioning USBBootW.exe in \I386\setup.cmd on the USB disk, for each source there. Please do read next time tooltips for each element in the program you are unsure about

Please zip and attach txtsetup.sif files from each ISO in g:\winsetup\.

are you sure if that option is marked then appears errors like the one i got? if i have to do all the work again that will take a lot of time... if necessary please just tell me the steps to take care of the problem manually.. i'm sure it will take less time than building everything since the begining. My Best Regards Make sure USBBootW.exe is present in USB_disk\WINSETUP\XPpSP..\I386\, if not- get it from program directory and rename it to USBBootW.exe if it's not already.Is it the only file it complains about? A corresponding WinSetupFromUSB.log in program directory or backup folder may also help finding out what's going on.

As for ntdetect.com- check FAQs, for XP the modified file does the trick. Ramdisk.sy_ is not needed at all, it's when building RAM booted PE with XP source. As for the error you are getting- do not select the option "Prepare for USB installation", it's still experimental and meant to prepare to install Windows to USB disk, from USB disk as well. Don't have the source code around to look for mistakes, just do not use that option.

Quite limited spare time, sorry. For the final version there are a few things I wanted to work on: -rewrite the documents, how-to etc. -recreate the problem and find solution for the rare cases when setup dumps "somefile nof found" during text mode stage. -find a workaround for those rare BIOSes which emulate the USB stick as superfloppy and refuse to use it as hard disk type -start XP/2000/2003 setup with only USB disks connected, allowing install from to USB. Currently the nice, infamous 0x7B BSOD appears. Since beta6 is fairly stable and no major issues have been reported so far, you should be good to use it. As for UBCD 5.0- haven't checked lately, but I guess it should work with the "add g4d compatible ISO" option. Want to test?

Haven't tested WinVBLock, at that time it was in early development stage. Don't have any spare time lately for hobby

Thanks, Have I to edit the file WINSETUP/XPhSP3/I386/NTDETECT.COM? Or only put the ntdetect.com created in root? Have to put it in the small ISO file in WINSETUP/XPhSP3, in folder I386 in the ISO image. Other way around is to put it in your source, I386 folder and redo the stick.