ilko_t

I see folders $OEM$, this is not OEM. Do you have folder G:\WINSETUP\OEM ?

Where do you select "share"? Why "share"? Describe in details what exactly you are doing. I can barely understand you, with the very limited information you provide...

Since you are using multi partitioned USB stick you must be using some filter driver, such as Hitachi microdrive filter driver or dummydisk.sys, right?Same drivers should be used, or Windows Setup / BartPE won't see anything but the first partition, hence the BSOD, refer to this topic: I used the last version from the first post: 1.0 beta6 Please zip and attach the following files:txtsetup.sif from the small ISO file in \WINSETUP directory on the USB stick ( ISO file name varies according to your source, just pick one) txtsetup.sif from \WINSETUP\XPpSP3\I386\ ( XPpSP3 varies according to your source, just pick the same name as the ISO file you got the other txtsetup.sif) WinSetupFromUSB.log from program's directory or the \backups folder in it. Try also renaming \WINSETUP\XPpSP3\I386\migrate.inf to migrate.inf.bak in both sources and see if you get any further, reference: Are you using original, not modified sources?

It's in the source, you do not manually put it anywhere. The program does NOT slipstream driver packs, don't take it wrong, it has to be done in advance.

If the sources in question all have BTS DP slipstreamed they can share a common OEM folder- \WINSETUP\OEM. The option has to be selected when transferring each of those sources to the USB stick. If this option is not selected, OEM folder will go inside each source, say \WINSETUP\XPpSP3\OEM, \WINSETUP\XPhSP2\OEM and so on. This also can be manually achieved, if source is already transferred, by editing \WINSETUP\XPpSP3 (or whatever this folder name is) \I386\presetup.cmd and correcting the paths in it, and eventually moving OEM filder to \WINSETUP\OEM if not already present.

What version of the program did you use?

The mini ISO. Attach txtsetup.sif, menu.lst, winsetup.lst and contents of BOOTWS folder. It could be more simple to redo the USB stick, modifying the original txtsetup.sif beforehand. Change the lines: [Strings] ... ... productname = "Windows XP ђdition familiale" .... spcdname = "CD du Service Pack 2 pour Windows XP ђdition familiale" to productname = "Windows XP home edition" .... spcdname = "Service Pack 2" and redo the USB stick.

Edit txtsetup.sif [setupData] section in the small ISO file and rebuild the ISO with the edited txtsetup.sif. Can you zip and attach your original txtsetup.sif? Lets see if something can be fixed in the program.

In latest 1.0 beta 5 and 6 you can add all Ubuntu desktop variants- 8.04 till 9.10, Kubuntu, Xubuntu... Up to 99 Windows 2000/XP/2003 sources. Several Windows 7/Vista setups in different primary partitions. Basically unlimited number of Linux variants, manually added to stick and loaded by grub4dos or syslinux. Whatever can be easily automated and there was interest in it is already implemented, for the rest some manual work is needed, just ask how

1) How did you prepare the stick, which method/program/guide ? 2) What source are you using, modified, nLited, slipstreamed SP2/3 etc. ?

Do you use "Safely remove hardware" icon?

You have other options to play with in RMPrepUSB- NTFS, single/multiple partitions, forced LBA, you can try BootIce as well with its several options, it's included in the latest betas...

What do you mean, can you elaborate a bit? For example. After installing distributivs of WinXp to flash i need make some ntfs links on the flash. I have common folder with name "_soft_" for some various OS-es, which contain software for installing. Teh directory _soft_ must be present in WinXP/$OEM$/$1, Win7, ..... and simple in root of flash drive. And than i need copy some files to flash. When the source code of your nice script will be availible, i will make it. With regards! Why this has to be automated and performed by the program? It seems specific to your needs task. And what's the problem to perform manually these actions, once the program finished its job?

jrr, you'd have to take it easy and reply with details to the questions asked, RMPrepUSB settings in particular, rather than posting video tutorial which you followed, to the letter or not. Do NOT expect someone else to spend of his/her own spare time (this includes watching video clips), if you are not willing to spare some of yours

Windows 7 Please post the log file either from program directory or by checking "show log" checkbox and copy-pasting whatever is inside.

What do you mean, can you elaborate a bit?

You my learn about grub4dos here: http://diddy.boot-land.net/grub4dos/Grub4dos.htm http://www.boot-land.net/forums/index.php?showforum=66 The included in \files\grub4dos\README_GRUB4DOS.txt also has number of examples.

Another response, few weeks later, from GData:

Please do not double post. Your first thread is visible enough and if there is someone willing and able to answer, you will get it in that thread.

Right, here is the interesting part my original question was towards: If I may rephrase my questions: Is this issue acknowledged by whoever is needed? Are there any workarounds, apart from editing old posts and replacing that no longer accepted syntax? Are friendly links going to remain default after this upgrade? Does one need to manually edit forum links in his replies and replace those friendly links, in order to stay "future proof"? Slightly rhetoric one- what is going to happen on the next upgrade (eventually there will be such, right?) if the new friendly links become once again unrecognisable?

I am aware of that, but this is not where the problem is, nor seems proper solution. I hope it's not the only one possible. Do you suggest going to each and every topic and edit the links, which are not using this syntax? How much knowledge is going to be buried? Currently links to specific posts also use friendly names, as links to topics do, e.g. if one copies link location for this post he will not get the syntax you mention, but will get the "friendly" name.

I am quite curious what is going to happen with the links mess after forum upgrade, is this taken care of? This old working one for example opens forum main page: http://www.msfn.org/board/WinSetupFromUSB-with-GUI-t120444.html The new working link is this:

After the first part did you boot again from USB? Did you try all the entries "Continue GUI Mode Setup XP + Start XP from HD 0 - Part 1" and so on?

No idea what "additional config" you have in mind. There is no automated way in the program if that's the question. You need to integrate the appropriate mass storage drivers or switch to IDE emulation in your BIOS. Search the forum or google if don't know what this is about, here for example: