ilko_t

The GUI thingie must be WinSetupFromUSB, right? Did you use the latest 1.0 beta5? It should not need and doesn't check for the files mentioned as the method is completely different than in 0.2.3 and prior. What you tried with PEtoUSB will NOT work, wish it was so simple

Each among which folders ? In case of ~BT/~LS folders (vers. 0.2.3 and prior)- the one in ~BT folder. If using any of the 1.0 betas- the one in WINSETUP\source_name\I386 folder. For the record- winnt.sif is for both text and gui modes, although in 0.2.3 and prior [unattended] section is removed for number of reasons and most stuff in it is covered by other means, there are still several settings in data section which could be useful: http://unattended.msfn.org/unattended.xp/view/web/19/SESSID=7f4d85282c7dc30e1f04775c038b1df6/ In 1.0 betas only auto partition option is removed, rest is fine.

Look at setup log files as mentioned above.

I'd try with the latest beta: As for the auto partition during Text mode- it's not a good idea. Setup may attempt to repartition the USB disk, that's why this option is removed by WinSetupFromUSB if found in winnt.sif. The rest of Setup, once file copy has started, can be completely unattended, no matter if the next reboot, for the GUI mode is started from the USB or the internal disk.

Version 1.0 beta5 released, please refer to the first post for list of changes and download links.

@jaclaz - sure, message box or something like this. @class101- You've posted in a topic which is mostly about a new method, which happens to be used in the latest betas of WinSetupFromUSB. The pinned thread for the program itself is already quite long, hence the new topic your posts were moved into If you need the latest or any other version of the program, refer to its thread: There could be some links mismatches, due to forum upgrade.

Since you are getting that far you have passed all issues which could be related to the "install from USB" part. Now you are most likely dealing with faulty hardware, inappropriate drivers, damaged source or something along these lines. Once you get BSOD or error in GUI I'd turn off the computer and run some "portable" OS put on the USB stick to check last lines in the setup log files in \windows folder, there are several of them: http://technet.microsoft.com/en-us/library/cc758337%28WS.10%29.aspx Look below "Commonly Used Log Files". As for portable OS this could be Ubuntu, UBCD4Win, WinBuilder LiveXP or the alikes etc. etc. Quick tip for Ubuntu:

Will add an option to display all drives, regardless their interface, would be easy to code.

The program looks for drives on the USB interface, that was the original idea. Lets see how your drives appear to Windows- please run the attached program with your eSata drive connected. Just run it and let it detect all drives, do not continue any further, it won't work. Copy-paste the log file produced, either by opening the log window and copy-paste or by opening WinSetupFromUSB.log file in the directory where you run the program from. http://www.datafilehost.com/download-e1062bbf.html Will later on split these posts in a new thread as they are not related to this topic.

Got response from VBA32, at last, still expecting from several of the major vendors, strangely, response time is quite slow. Kaspersky removed it from their signatures a while ago, although didn't respond to the emails.

I'd suggest you to use a source without symlinks or ignore the duplicated files, prepare the USB drive and next try the included \files\tools\DFHL.exe. http://www.jensscheffler.de/dfhl Beta5 is to be posted in the next few days.

A couple of ideas: - put your source on USB stick and use grub4dos emulated floppy containing the drivers needed: http://www.msfn.org/board/forum/157-install-windows-from-usb/ - put on USB stick only grub4dos: http://www.boot-land.net/forums/index.php?showforum=66 http://diddy.boot-land.net/grub4dos/Grub4dos.htm Load the virtual floppy as above, next chainload setupldr.bin on the CD.

I add two URL too: http://forum.oszone.net/thread-140892-38.html - last page of GUI updates integrator - more new then jaclaz http://forum.oszone.net/thread-95273-13.html - autorun addon Here is the logic used: Setup.ex_ in source is extracted and renamed to setuporg.exe, if latter doesn't exist (BTS driver packs). Fake setup.ex_ is put into source, it launches setup.cmd at start of GUI mode. Setup.cmd does some jobs and launches BTS presetup.cmd if found. Next renames SetupORG.exe to setup.exe and launches it. Have a look at setup.cmd and adjust if needed. I'll try to change slightly this in beta5 and use some other file name, instead of setupORG.exe for the extracted and replaced setup.exe, whatever it is, so it gets executed after setup.cmd. Well. Here details. We will assume we have a directory on a disk ntfs file system. For economy of a place some catalogues are not copied, and executed by symbolical links. As on DVD after optimisation we have the same picture. By means of subst command I mount this catalogue as an additional disk - CD_rom. At use WinSetupFromUSB there is a double copying! If volume occupied by dvd disk is 4,5 Gb but on flash drive it occupies vore then 8Gb (like a cd-rom without optimithation). In particular I have a directory _Soft_ with volume 3Gb in the catalogue "$OEM $ \$1\ _ Soft_" and as in root catalogue "_Soft_". This two catalogue are identical! There are also some other such catalogues. As that is a pity to me of this place, but each time to alter hands it would not be desirable! What happens if in windows explorer for example you copy your source elsewhere, i.e. in different partition. Does explorer copies files twice or files+symlinks?Can you give me exact step-by-step instructions how to recreate the scenario, including links to any programs used?

I'll be posting the source code with the final versions. The rest of your post I don't quite understand. About the failed writes- it should be something to do with windows or the USB disk, there is nothing unusual in program's file copy part: If Not FileCopy($aFileList[$c], $ddfn, $CopyFlag + 8) Then If Not FileCopy($aFileList[$c], $ddfn, $CopyFlag + 8) Then;Tries a second time If RunWait(@ComSpec & ' /c copy "' & $aFileList[$c] & '" "' & $ddfn & '">' & @TempDir & '\o.tmp', '', @SW_HIDE) = 1 Then $sError = FileReadLine(@TempDir & '\o.tmp', 1) Logging("ERROR!!!--- not copied:" & $aFileList[$c] & ' ' & $sError) FileDelete(@TempDir & '\o.tmp') EndIf EndIf EndIf You may look at source code of 0.2.3, most of those functions are untouched. Can you copy the whole source from the DVD to the hard drive using Windows Explorer? Does this break? That's too much work for th epurpose, there are more important things to implement. On properly working system you should not have any issues. Ditto. I don't understand this, can you provide details? What's BOA autorun setup?

It's in beta5, testing it before posting, but haven't got much (actually any) spare time lately. Meanwhile, working examples: http://www.boot-land.net/forums/index.php?...ost&p=64641 http://www.boot-land.net/forums/index.php?...ost&p=64856 Works for Ubuntu 8.04-9.10, Kubuntu and Xubuntu, the desktop versions.

Now even more AV detect it:http://www.virustotal.com/analisis/dabb3a5...229d-1265653509 which is not unusual, as AV vendors share signatures. The file is the same as in XP_INST.IMA, only cab compressed, just hex compared them in case there was something wrong on my side. I will also send emails to a few AV vendors for reanalyzing.

Split the posts about virus in XP_INST_v04.7z in a new thread: http://www.msfn.org/board/index.php?showtopic=141734

Yep, you got us We got bored and decided to infect with a deadly virus whoever gets curious enough to download that attachment. Seriously, before throwing such questions in such manner, check online with multiple virus scanners: virsusscan.jotti.org virustotal.com Next inform your antivirus vendor for a false positive. If more antivirus program detect the file in question as a virus, inform the developer politely. In sites such as msfn.org, it's quite unlikely someone intentionally to put virus in the program posted.

Try 1.0 beta4, should work fine with 2000. If you get any errors while preparing the USB disk please zip and attach winsetupfromusb.log file found in program directory.

What are you using as a source? Have you tried with original, not modified source? Was h:\winsetup\xppsp2\i386\setup.ex_ present? Can you zip and attach D:\tabletXP\I386\TXTSETUP.SIF with the full WinSetupFromUSB.log file? Use datafilehost.com if attachemnt gets too large, or 7z compression, it may compress it much better.

There is something going wrong: Note double letters for the same partitions.I'd format the disk, unplug it using safely remove hardware icon, reconnect it and then continue. If the error persists- have a look at HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices and delete the entries for F-I and M-J, then reconnect the hard disk. I'll look at the code and see how to avoid those cases. Thanks for reporting.

Can you zip and attach the log file in program directory? Backups of the logs are in backups folder, look for the largest file.

Which part did you find confusing in this thread? http://www.msfn.org/board/index.php?showtopic=138855 You do need the proper SATA driver or if possible, as workaround, to switch to IDE mode in BIOS, which could be named in various ways. Quick search in google for "HP Mini 311 sata driver" http://h30434.www3.hp.com/t5/Operating-sys...p/150454#M22221 BTS mass storage driver pack is also always an option, a good one

@cdob I was thinking what triggers USB drives to be mounted when doing msdosinitiated=1 installs. I guess on the nice machine in question ~BT/~LS install will go through. Attached is comparison between such install and small ISO install with no USB settings changes right after text mode. I've already tried replicating some of the settings from msdosinitiated=1 install, doing them before entering GUI mode, but went nowhere. There must be something which triggers setup device to be mounted. Might be worth thinking a bit in this direction? comparison.7z

Add it to the ISO file in WINSETUP directory. Use UltraISO to replace it directly, or extract contents of ISO, replace NTDETECT.COM and recreate the ISO: mkisofs.exe -v -iso-level 4 -volid ""WINSETUP"" -R -o "L:\WINSETUP\XPpSP3.ISO" "G:\Path_To_The_Extracted_ISO\" Or simply replace ntdetect.com in your source and recreate the USB stick. BTW- similar problem was posted and resolved just one page pack in this thread, a little reading never hurts @VegetaSSJ5- Doesn't this machine support USB boot? If it doesn't I doubt this method will work, there is an valid ARC path needed to the USB stick, or Setup fails with 0x7B when stick is mapped to non-existent drive.