ilko_t

Please zip and attach WinSetupFromUSB.log found in program's directory.

Please attach txtsetup.sif from USB root too.

Try reading the code in post #90, that's the function, which produces the hash. I couldn't get a chance yet to attempt to understand it and create similar code in AutoIt for example. From what I understood in this matter, that function is far from any famous CRC32 calculation algorithm, even different than RtlComputeCrc32 function, which ReactOS uses and is present in NTDLL.DLL too. Attached is a program, made by someone else, while we tested hash calculation. 2k button uses Win 2K ParentID prefix hash calculation. It may become handy for someone. ParentIDPrefixGen.rar

If you scroll down a bit in the topic you mentioned, you'd see that Porear had the same issue like you have. Save yourself time, unless you are willing to learn process from scratch, use WinSetupFromUSB and prepare the USB disk properly. http://www.msfn.org/board/index.php?showtopic=120444

It's not clear what you've done. Where did you put XP installation files? Where did you start the Setup from? XP can be installed just fine without looking for a CD.

Edit boot.ini on the hard disk. Decrease rdisk value in both lines with 1, i.e. rdisk(1)-->rdisk(0) default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /NOEXECUTE=OPTIN /FASTDETECT becomes default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /NOEXECUTE=OPTIN /FASTDETECT To edit boot.ini- right click on My Computer, select Properties-->Advanced-->Startup and Recovery group Settings and press Edit.

Yes and yes. Remove the newly added RAM and try setup again.Try WinSetupFromUSB as well.

What tutorial did you follow? Have you checked RAM, preferably by removing one or another piece of RAM? I know you managed to install Ubuntu and 7, but anyway, it still makes sense. Have you confirmed hard disk is in good shape indeed? You would have to stick with one method and tell us what exactly happens.

That's ok, I meant I didn't know how you managed to remove that option using nLite as you said earlier. Try changing it to : command0="%SystemRoot%\System32\nLite.cmd" The same issue: http://www.msfn.org/board/index.php?showto...st&p=852261 http://www.msfn.org/board/index.php?showto...st&p=852442

I have no idea where that option in nLite is and what it does. However, since it's working from a CD we should be able to get it working from USB as well. Do you have any idea what is exactly executed by RunOnce? Is it a executing the mentioned nlite.cmd? If it is only it- please attach it with your next post. There could be just wrong path or tag files.

Well, how to say it any clearer?! Put WinSetupFromUSB program in a directory, which do NOT contain spaces in its path, as you did, in "C:\WinSetupFromUSB 0.2.3". In other words- RENAME "WinSetupFromUSB 0.2.3" to "WinSetupFromUSB", or "WinSetup", or "WS" or whatever, but WITHOUT spaces in name. Do NOT put ANY spaces or special characters in name.

I meant WinSetupFromUSB directory. C:\WinSetupFromUSB 0.2.3 -->C:\WinSetupFromUSB

Thanks for the feedback As for rdummy- can you change the line in winnt.sif in ~BT folder from: "sc disable rdummy" to: command0="sc disable rdummy" and try again installation. As mentioned above you'd need to reboot once after the first regular windows login in order to delete the service. As for the missing file- please zip and attach txtsetup.sif with your next post. Is this file part of any slipstreamed windows update or application? What program did you use for the purpose? I don't find this file in a regular XP SP3 downloaded from MSDN.

Have you tried installing the program in folder without spaces in path?

I guess the second line is about USB repair. If it is not there Repair Install from USB will not be possible and Recovery Console won't be able to see the existing Windows installation if started from USB. You'd better decrease timeout value if the menu bothers you. Some details in the posts below this one: http://www.msfn.org/board/index.php?showto...st&p=868227 In this subforum too, it's been discussed numerous times. As for the broken files- that's not normal at all, I've built and tested USB sticks 100s times and never got a single broken file. Refer to the post of cdob.

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS=""USB Repair"" /noexecute=optin /fastdetect rdisk(z)-->rdisk(z+1)

Are those files present in ~LS folder on USB stick? Search for wow32.dll and wow32.dl_ and so on, as some of them may be compressed. Or simply do not type the extension when searching. What subfolder of ~LS are they in if present? Try replacing them manually from your XP source. Turn off AV protection while preparing the stick.

I don't see anything strange in txtsetup.sif regarding the missing files. Did you get past the errors about those files? Do you have an antivirus program turned on while preparing USB stick?

None of the tools in this subforum use their "proprietary" way of copying files, they all use windows commands/API to do that. So we cannot talk about correct/incorrect way of copying. What happened with the missing files? Did you get past those errors?

With USB hard disks you would need a filter driver to present the disk as removable disk. Otherwise Setup will like it as a boot media and will attempt to put boot files (boot.ini, ntdetect.com and ntldr) on it, leaving your destination hard disk without them. Drive letters also become a problem, the USB hard disk will get C:. Further explanation about the filter driver needed: http://www.msfn.org/board/index.php?showtopic=116766 Q14/A14 and the links within.

I guess there are reasons behind that : http://www.msfn.org/board/index.php?showtopic=129454 You mean Setup completes successfully when run from second partition, on USB hard disk or USB stick? Can you share some details about how the disk or stick is partitioned, which partition is active and if you performed any additional steps?

Haven't used USB_multiboot for a while, so won't guidance with it. With WinSetupFromUSB you can do that easily: http://www.msfn.org/board/index.php?showto...t&p=779970: 1. Integrate BTS DP to each of your sources 2. Run WinSetupFromUSB and put each of the sources on the USB stick. To put the second source just run it again and select the new source then follow the prompts when existing setup is found. The program will rename each of the BTS folders, amending presetup.cmd in each source with the new location, apart from the other changes. 3. If your sources use the same DP then all they should be able to share a single BTS folder to save space- leave one only and amend each presetup.cmd file with the name of the folder. Presetup.cmd is located in ~LS\I386\. Another way around when using NTFS on the USB stick, which is preferred for speed anyway, is to use hard links, which will save space from the duplicate files in xp sources as well, not only from the duplicates in BTS folder. Use the included \files\tools\DFHL.exe for the purpose. This way you won't have to edit presetup.cmd files and play with BTS folders either. http://www.jensscheffler.de/dfhl_en.html Reminder- to avoid file deletions on USB stick during setup you should be using XP 32bits sources with SP2 or SP3 integrated. In all other cases some files will be deleted during Text mode phase and you would need to synchronize the source after setup. If you need regularly to install Windows versions different than the mentioned above, you may be better of using this approach: http://www.msfn.org/board/index.php?showtopic=121446

Zip it and attach it here with your next post, forum has an option to attach files to posts, use POST REPLY button and you will see the options.As for the CRC error- triple check if file on the USB stick is OK, there must be something wrong either with the file, or with the hardware as cdob mentioned, the most of the compression programs have an option to test archives. If it is broken- just replace the file to the USB stick with healthy(checked) one. Did you perform both installs- from CD and from USB on the same machine? Do you have a chanced to try with another USB stick?

Are these the only files Setup is throwing error about? Please attach your txtsetup.sif file on USB stick. As for the CRC error- it rather seems corrupted file because of file download or file copy operation. Should have nothing to do with installing it from USB. As for Visio Viewer- is there any error? How is it installed, using what method, what entries in winnt.sif or wherever?

In such cases WinSetupFromUSB adds a line to winnt.sif GUIRunOnce section: "sc delete rdummy"Do you have this line in ~BT\winnt.sif ? Was the first login with an admin account? I wonder where this has failed...