ilko_t

Don't use FDD option in BIOS. The whole point to present the USB stick as HD, hence use AUTO or HD mode only.

Please attach with your next post WinSetupFromUSB.log file, found in program's directory. What type/model is your USB stick? What operating system are you running all this under?

The USB stick must be seen by grub4dos and Windows setup as a hard disk. So you need to play with such options in BIOS, which will present it as hard disk. Next you need to format it in a proper way, so it boots when that BIOS option is selected. For now it seems to boot as floppy, so grub4dos cannot find its configuration file menu.lst and goes to command prompt. Well, grub4dos actually can load config file from a FD, but Windows setupwill not start from floppy disk. How to format it and boot with that option in BIOS will be matter of experimenting, I hope Jaclaz is reading this and will give his priceless ideas as usual

Yes, it is, in case in BOOT.INI on the hard drive the line about USB repair is intact.

Have you missed the pinned topic?! http://www.msfn.org/board/index.php?showtopic=120444

Jaclaz has assisted you already, you fail to follow his guidance plus you seem to ignore what you have been told to do, several times.I doubt I'd have greater success. You better read his replies to you in full, perform ALL steps, then if still no luck provide the files mentioned in his posts. All this should be done in a new topic, as it goes way beyond what this topic is about.

Here is 0.2.3-test version: http://www.datafilehost.com/download-e5aef115.html

@Jaclaz Would you have a look at mbrdisk2-20090624-021041.dat in the second attachment in the first post and spot anything unusual?

By experimenting

Look here for a way to fix it: http://www.msfn.org/board/index.php?showtopic=135202

@Tulert When you get to grub4dos command prompt, no whatever of the USB sticks you could get it, type the following: root ( and press TAB key. Post the output here, it must be something like: Please open up a new topic and post there.

Thanks for the logs. I need to look why fixing grubinst under Vista/7 broke installation under XP...

I am still not convinced that the hash is actually CRC32, plus the string must be converted to unicode. Look at the HASH_UNICODE_STRING macro posted above, it differs from any other macros I saw for creating CRC32 hash.

Was Windows working fine before you got the error for a first time? If yes- the most common cause would be corrupted files system and/or hard disk playing up. If this happened during setup- how is your hard disk partitioned? Which partition do you install Windows to? Please try to describe exactly what steps you performed in details, I read your post several times and still do not understand the most of it.

XP SP2/3 will NOT delete files. 2000/2003 any version will do. Anything after Vista (including) it will NOT.

http://www.msfn.org/board/index.php?showto...st&p=852517

That would be perfect to be part of MkMigrateInf.cmd, can you help?

You integrate Driver Pack in your source, BEFORE putting it on the USB stick using this program. So the answer comes up by itself- yes, you need to do that for whatever source you are willing to.It could be possible to share drivers pack folder later on, after integration, given that source is the same (XP for example), but it will be looking for that only if disk size is limiting you and/or you are slipstreaming a lot of driver packs, e.g. video, sound etc. From the top of my head one of the changes required would be to edit presetup.cmd in each ~LS\I386 folder and replace name of DP parent directory. You need to create the partitions manually, then the program can help you putting the source in those partitions. Didn't you like the workaround?

For one of my USB sticks ParentIDPrefix in XP is "16f722a4", it is CRC-32 hash of the uppercased unicode string: USBSTOR\Disk&Ven_LEXAR&Prod_JD_LIGHTNING_II&Rev_1100\AA04015900000158&0 which is actually part of the registry subkey: HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR\Disk&Ven_LEXAR&Prod_JD_LIGHTNING_II&Rev_1100\AA04015900000158&0 The comments in the code given above explain fairly well what is what. Next days will be trying to achieve this calculation in AutoIt. If there is anyone interested- here is the code in C, which calculates CRC32 hash: #define HASH_UNICODE_STRING( _pustr, _phash ) { \ PWCHAR _p = (_pustr)->Buffer; \ PWCHAR _ep = _p + ((_pustr)->Length/sizeof(WCHAR)); \ ULONG _chHolder =0; \ \ while( _p < _ep ) { \ _chHolder = 37 * _chHolder + (unsigned int) (*_p++); \ } \ \ *(_phash) = abs(314159269 * _chHolder) % 1000000007; \ }

Glad to read stories of success Not quite sure what your second point asks. The program does not need DriverPack. The hardware and Windows you are going to install may need a driver. Simplest way is to to slipstream Drivers Pack to your source with Windows setup with many drivers at once.Is it any clearer? As for Vista setup- from the first post in this topic: Quick workaround- manually copy to the same partition the other Vista setup files, even in its own folder. Launch first Vista setup. At start of setup choose to repair system then select to go in command prompt, can't recall how these options were called. When you go to command prompt CD to your folder with the second Vista and launch its Setup.exe. Not quite sure if you can start 32bit setup from 64bit command prompt and vice versa.

It seems grub4dos MBR is present, but for some reason is failing to launch grldr, which is grub4dos loader. Open up command prompt, CD to \winsetupfromusb\files\grub4dos\ and type: grubinst -l -v (hd2) Do you recognize your USB stick by its size? If not- change hd2 to hd1. When you recognize your USB stick issue: grubinst -v (hd2,0)replacing hd(2 with whatever number you found your USB stick at. Please post the output of the last command and check if stick boots fine now.

From what I see you have selected to prepare Recovery Console/Boot files only. In this case you should be going to first part directly. What's the error message you are getting? Check in folder BACKUP. Compress all CAB files into a zip archive and upload it here.

Please attach WinSetupFromUSB.log file, found in program directory.

You won't be able to test that in VM, not without some manual intervention during Setup which will be a bit long to go into. Isn't the last machine you played with available to run this command?

What version of the program did you use?