ilko_t

Just keep in mind to do the fix for XP/2000/2003 installs, link is in the first page next to info for beta7.

Will keep in mind Win 2000 compatibility when coding another version. Can't say more. Can't claim 2000 support for host OS in previous versions as it seems half broken half working. This has nothing to do with WinSetupFromUSB. It uses WMI query to list drives with InterfaceType USB and every other application relying on WMI will behave the same way. Why 2000 lists USB and other disks as SCSI ones in WMI space I have no clue.MS documentation doesn't have a hint about differences in 2000, look at InterfaceType.:http://msdn.microsoft.com/en-us/library/windows/desktop/aa394132%28v=vs.85%29.aspx The proper solution would be to get rid of WMI alltogether but that would require a lot of coding as well as most likely introducing new bugs until everyting gets polished.

Did a few tests under 2000, turned out it's not only displaying the drives is not working, otherwise would have been an easy fix. Unfortunately a few other WinAPIs in use are not supported in 2000. On top of that the included version of WinContig didn't work, nor did BootIce. RMPrepUSB returned an error when formatting the USB disk but it seemed properly formatted. FBInstTool worked fine. I have never tested previous versions under 2000, must rely on user reports. Does everything work properly, apart from USB drives displayed as SCSI ones due to the way WMI works in 2000?

Did you run it on Windows 2000? I have never tested the program on it...Have the previous versions worked with this option enabled? Added: The WMI function used, not supported in 2000 is Win32_DiskDrive.Signature. I can get around this one, but another used in this version and important one is FSCTL_DISMOUNT_VOLUME, which doesn't seem to be present in 2000 either. For a few other used I recall to be present since XP. In short- many of the new features wouldn't work in Windows 2000, so for now, unfortunately, I won't be planning on running the program on 2000 host OS. 2000 being added to the USB disk, as long as program is run on XP onwards is still supported as far as I have tested.

New 1.0 beta8 version uploaded. Please refer to first post for list of changes and download links.

Links work just fine here, Windows 7 x64.

It starts XP setup menu if it was the last one used. In latest beta8 versions, there is another boot menu for Second part and consequent boots of Vista/7/8 Setup, which becomes default if First part of this setup was used once, making the setup unattended in the same way as with XP/2000/2003.Timeout value can be edited in file menu.lst and in winsetup.lst for XP/2000/2003, change the values per your needs.

How large is the hard drive? Does XP SP3 behave the same way on this laptop? You'd have to delete all partitions and create new ones. Here are several other reports for the same problem on this laptop: http://hongkongphooey.wordpress.com/2008/04/29/how-to-install-windows-xp-on-the-hp-2133-mini-note/

It's hard for me to figure out what exactly you want to achieve. How would only different winnt.sif help you achieve that? There are possible sollutions, for example placing it in a virtual floppy, or maybe in the small ISO file... You may also want use NTFS and hard links on the USB disk in order to save disk space, DFHL.exe is included in \files\tools. As a side note- as far as I know as rule of thumb, BTS stuff goes last, after using nLite.

I'd look for issues with the hard disk. Try to delete all partitions with say PartedPagic, do not create new ones. Try again creating them from Text mode. Test the hard disk with tool from its manufacturer. The issue doesn't seem to have anything to do with the fact that it's install from USB.

Can you delete all partitions and create new ones, while in Text mode? For the Second part you may also try booting from the internal disk, instead of the USB one. I guess you used WinSetupFromUSB, which version?

Only displaying in GUI is in MB, GB and so on according to the actual bytes. Internally, all sizes are in bytes, so if it doesn't complain about lack of free space all should be good.

Oops, my bad, re-uploaded.

RC8 re-uploaded, please let me know if everything is fine, went back to the old functions for total and free space: http://code.google.com/p/winsetupfromusb/downloads/detail?name=Win%20Setup_1_0_beta8_RC8.7z&can=2&q=

It uses WMI for the purpose, which for some reason does not work reliably on this machine. In previous versions for disk size and free space were obtained from AutoIt functions DriveSpaceTotal and DriveSpaceFree. In next RC will go back to AutoIt or WinApi functions, as a workaround for broken or buggy WMI, thanks for the report.

Attached is a simple VBS script,taken from here, using WMI do enumerate logical disks and display their properties. Can you run it on this machine and see if it returns logical disk size and free space properly for the USB disk in question? Remove .txt extension so it becomes "LogicalDisk.vbs" and double click on it. Will post it when finish with the RC versions.LogicalDisk.vbs.txt

Can you attach the log file in WinSetup directory along with a screenshot from Disk Management console? If you know how to integrate BTS mass storage drivers that would be a safer bet since it's longstanding and tested solution. DPMS uses the same drivers set, but in a different way. It wouldn't hurt at all to have DPMS included as well, if you decide to add a source without mass storage drivers integrated, since the menu is optional anyway.

That's fine, by design. Boot.ini on the internal hard disk is created with the proper values with all 1.0 versions, hence no need of second boot from USB and amending boot.ini on the internal disk. There is possibility you are booting from the internal disk every time, for some reason. The error message changes, because NTLDR throws 2 different messages: 1) The ARC path is not valid at all, i.e. there is no such device/disk - "Windows could not start because blah blah" 2) There are no Windows files/directory in the specified ARC path, but it points to a valid device/disk- "hall.dll not found ..." Try some other options in BIOS for USB boot or the hotkey boot menu, that would be the first advice I can think of.

Can you check with WinPE what are contents of boot.ini on the internal disk and also post a screenshot of Disk Management whilst in WinPE? You may also try building the stick with the latest version of WinSetupFromUSB from here: http://code.google.com/p/winsetupfromusb/downloads/list

1) Here is alternative translator, I can barely understand what you are saying even with alternative translations, try using it too when reading in English: http://itranslate4.eu/ Or get someone to put all this in understandable English. Currently it is not. 2) The drivers included in beta8 versions, BTS mass storage drivers pack, are NOT to be used with nLite, no idea why and what are you doing with them and why mentioning them at all, if that's not misunderstanding in first place. 3) I have no clue when you get BSOD, what drivers you backup and why, and whether you did disable rdummy service or not. 4) My recommendation remains the same- use the very latest version available, ignoring if it says Beta, RC, Alpha or whatever.

The "compilation of drivers" is the latest BTS mass storage drivers packs, which is widely tested and used, and are not intended whatsoever to be integrated with nLite. And the "solution" has been tested as much as possible by several people, before posting it here. The DPMS solution used in the latest version is relatively new, OPTIONAL and is yet to be widely tested, and surely that's something everyone has to contribute towards a bit with informative feedback in order to get things going. As a side note, I don't quite get the point of your post, thanks for the feedback anyway, even put in this negative way, but for the rest you have to be more detailed and first figure out what is what, and finally ask for a refund.

You are missing SATA/AHCI/RAID drivers in your source. Integrate them in your source before creating the USB stick (nLite, manually or use BTS mass storage drivers pack), switch SATA/AHCI mode in BIOS to IDE/compatible to avoid the need of such, or try the latest version of the program from here: http://code.google.com/p/winsetupfromusb/downloads/list selecting the"Auto-detect and use F6 SCSI/RAID/SATA Driver" entry first, then First part of setup.

1) Use latest beta version in first post, or the latest development one from here: http://code.google.com/p/winsetupfromusb/downloads/list 2) Check if rdummy service is running and disable/delete it if it is.

Which version did you use? I am confused. Do you mean at the end of preparing the USB disk program told you to boot from USB twice? That's a remonder/instructions for proper installation on the target disk/computer when installation already started, applies only for pre 1.0 versions and has nothing to do with safety of the disk you are working from to prepare the USB disk. Did I understand you correctly? To confirm- you do NOT have to reboot the computer you are preparing the USB disk on. When program finishes the stick is ready to be moved to the target computer and program does not touch or need the internal disk you are preparing/working from. It will not format or change automatically anything. If have to boot from that USB disk on a computer, select target disk and choose to format it in order some changes on internal disk to be made.

Something/somebody must have deleted/erased/eaten it Find who/what that was and tell it not to touch innocent empty tag files ever again! Put the line back. Create an empty file in root of the USB disk and name it usbdrive.tag. Do the same for Program Directory\files\grub4dos\. Or better off, re-download the program, there could be other files missing/deleted/eaten by the same evil creature.The file would not have been used if there was no need of it. Added: by the way- always use recent 7-zip version to extract the program. Some other programs, "compatible" with 7z do not handle 7z archives properly, in particular ignoring empty files, which most likely is your case.