 |
 |
 |
|
 |
You are not logged in.
Hi,
Being part of the team, developed XP install from USB, thought you may be interested in a new program- WinSetupFromUSB.
It's with GUI and preparing USB disk/stick with XP/200x setup files is matter of a few mouse clicks. There is no guide or screenshots as the usage should be quite easy and straightforward, and tooltips will show up on every element of the GUI. Reame.txt file should also help you get started.
Hope it helps all of you, who need to install Windows from USB, or use it's other features, such as adding GParted (free partitioning manager), Vista Setup, BartPE/WinFLPC, or SysLinux to an USB disk or stick.
Here you can get the latest program:
http://www.msfn.org/board/WinSetupFromU … 20444.html
If you have any issues with the program you may post here or in the dedicated subforum at MSFN:
http://www.msfn.org/board/Install-XP-from-USB-f157.html
Good luck. 
Latest - vers. 0.2.3 - 06.July.2009
Download: 0.2.3 mirror
- RMPrepUSB replaced HP USB format tool and PEtoUSB, thanks to Steve6375 from boot-land.net forums making RMPrepUSB package and letting me include and redistribute it.
- Grub4dos bootsector&MBR detection and installation changed.
- added possibility to boot other ISOs, which can boot using grub4dos CD emulation. Here you can find number of examples:
http://www.boot-land.net/forums/index.p … topic=5041
vers. 0.2.2 - 15.June.2009
Download: 0.2.2 mirror
- MkMigrateInf.cmd updated for some systems with strange MountedDevices values. (thanks to cdob)
- added several check if grub4dos bootsector was installed properly, if not- grub4dos MBR is written instead. The problem appears on some Vista/7 systems and NTFS formatted USB sticks.
- fixed touchdrv.exe execution syntax (thanks to Wimb)
vers. 0.2.1 - 09.Apr.2009
Download: 0.2.1 mirror
- fixed an issue with grubinst on some systems where the backup files do not appear in the program directory
- NTFS warning message displayed once only
vers. 0.2.0 - 06.Apr.2009
Download: 0.2.0 mirror
- boot from USB disk is now required TWICE only, first start of Windows can be performed from the internal disk
- DOSNET.INF parsing redone
- program install and windows source now supported in paths containing spaces
- winnt.sif unattended section is now FULLY supported, including custom directories and drivers paths
- presetup.cmd checks if boot filea are present on the target disk and if not copies them. Useful for 2000 installs
- binifix5.cmd is launched before start of GUI mode, new option intruduced '/norepair', which will not add USB repair entry in boot.ini
- added extra entries in BOOT.INI to test if getting HAL.DLL/NTOSKRNL.EXE not found errors
- Windows setup tag files are copied to USB drive root in order to support some BTS DP base versions
- GParted replaced with PartedMagic, versions above 3.0 are supported
- grub4dos updated to the 0.4.4 Final
- syslinux.exe updated to 3.73
- QEMU updated to the latest 0.9.1 snapshot, which should support Vista
- various other fixes
vers. 0.1.1 - 23.Oct.2008
Download: 0.1.1 mirror
- fixed DOSNET.INF parsing if path contains comma(s) and if some rare setting are used in directory section
edit:
Vers. 0.1 released:
Download: 0.1 mirror
- unattended section handled better- if BTS drivers pack was not used, fake setup as per Pyron's method will be executed. This will launch presetup.cmd and when done real Setup will be started. If OEMPreinstall = yes is found $OEM$ folders will be copied to their place by presetup.cmd. If OemPnPDriversPath is found, paths in it it will be scanned by SPDrvScn in order to add those paths to
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ DevicePath
http://www.vernalex.com/tools/spdrvscn/index.shtml
If you need to disable driver signing errors add an entry in ~LS\I386\presetup.cmd to start WatchDriverSigningPolicy.exe and copy the latter from \WinSetupFrimUSB\files\winsetup to your USB disk.
Credits to Driver Packs team, Ercofra, schalti, Pyron, a06lp and iLE.
http://www.msfn.org/board/install-OEM-d … 23023.html
http://www.msfn.org/board/index.php?showto...ost&p=87594
Should work if installing x64 Windows too.
This part is not fully tested, feedback is welcome
- fixed bug when source is on a CD or mounted ISO and winnt.sif ot txtsetup.sif not edited because of the read-only attributes.
- boot.ini is fixed during GUI part of setup.
- USB letter is fixed to U: in case of removable USB disk and U: is searched first among the drive letters to avoid at least some of the silly windows errors with empty card readers.
- fixed bug when more than 9 disks are present (again empty card readers). Program will not continue if target USB disk has number in Windows > 9, as grubinst.exe doesn't work yet if disk number is 2 digits.
- added support for GParted vers. 0.3.7-7 and 0.3.9-4
- Grub4Dos updated to 0.4.4 2008-10-12
- little improvements in tooltips, error messages, logging and program code
- fixed WinBuilder copying
- source code included
- unattend.txt no longer used if winnt.sif is not found
Last edited by guеst (2009-09-14 3:26:27 am)
Offline
Hope you like it
FYI- a quick list of FAQs:
http://www.msfn.org/board/FAQs-t116766.html
Offline
I would like to say this program worked perfectly. I have tried many many programs to try to boot an XP install from USB but none of them worked for me, except this one.
Good job.
One thing I did find and I expect its already been pointed out because of where the installer points to but if you try install into Program files (in Vista anyway) it wont run correctly, I've had this problem before and its because of Vista blocking the program for writing to the directory for some reason. It can be fixed by changing the folder permissions but its easier to just install elsewhere
Offline
Thanks : )
I'd rather keep the install folder in the root of a disk, as it has inside other files (ReadMe, logs, MBR/bootsector backups, MultiPartitionUSB folder...) which have to be easily accessible.
Offline
I sadly have to say this just didn't work for me, I guess there's a reason it's still in it's beta stage. It's probably due to the fact it was an nlite CD i used for all my machines.
Basically, creating the usb drive worked, altho it took quite sometime, half an hour if not longer.
Then I ran part one, worked fine, did part two, again worked pretty well up until literally 1 minute left and only removing temp files where it seemed to become stuck and leaving it for a good 5-10 minutes made no difference.
Then just quickly trying the process again the USB disk seemed unable to format the install partition in stage 1. Luckily using my old cd drive again didn't give me any trouble.
Offline
Sly wrote:
I sadly have to say this just didn't work for me, I guess there's a reason it's still in it's beta stage.
If I put it another way- Alpha had over 10 000 downloads and only a few minor bugs reported. Also keep in mind that USB boot can be hardly put in stable stage, as there is not industrial standard, various manufacturers implement their own way of USB boot in BIOS/motherboards. And most importantly- the way we use is "cheating" microsoft's procedures of setting up from hard drives and no matter how well tested it will always be in "experimental" stage, no matter if the program is in Alpha, Beta or whatever stage. If you ask me- I'd never put it out of Beta due to the mentioned reasons.
The initial thread in MSFN forum had over 200 000 hits, and guess how many active contributers, even with feedback only - count them on the fingers of your right/left hand. The more people help, at least with feedback and tests, the better and faster everything will happen. It's beyond one's capability to test all scenarios, mixtures of nLited/slipstreamed/customized Windows sources, USB devices, and different motherboards with their USB boot abilities. Critic is easy to give, lets try to contribute ; )
Sly wrote:
It's probably due to the fact it was an nlite CD i used for all my machines.
Depends. As you describe it it shouldn't be the problem. There is one critical option in nLite which must not be used and the program detects if it was used, giving warning.
Sly wrote:
Basically, creating the usb drive worked, altho it took quite sometime, half an hour if not longer.
Copy speed depends on USB disk/stick speed and often on formatting. NTFS usually performs way faster on slow drives. What hardware are you using and in what FS did you format it in?
Sly wrote:
Then I ran part one, worked fine, did part two, again worked pretty well up until literally 1 minute left and only removing temp files where it seemed to become stuck and leaving it for a good 5-10 minutes made no difference.
Which means Setup was deleting the ~LS and ~BT folders, most likely. This to happen, something must have been wrong in your WINNT.SIF file. Did you play with it AFTER you run WinSetupFromUSB? There are entries, which presence is critical, program mentions that in a message box.
Sly wrote:
Then just quickly trying the process again the USB disk seemed unable to format the install partition in stage 1. Luckily using my old cd drive again didn't give me any trouble.
I guess the error was due to the missing files in ~LS folder or the whole folder, without which Setup cannot perform format.
If you give more details I could help you more.
Offline
With both versions (alpha and beta) I get this error:
Formated a 1GB Kington USB with HP tool. The process start, WinSetupFromUSB ask to permanent U: Usb drive letter, and then i get the above error.
Last edited by Hemin (2008-09-17 4:29:41 am)
Offline
Sorry If i sounded like I was being offensive, I wasn't trying to be a critic, lol. I'm off to uni soon and if this works it means I won't need to bring a bulky USB CD drive with me in case of Windows needing a reinstall. The application actually looks very good. As for nlite, well I wasn't sure if you had supported the use of nlite XP files so I thought it best to mention. I used a OCZ 2GB Secure Digital 'Hi-Speed 150X' card, with a FAT32 format, tho on my next attempt I'll use NTFS as you suggested.
Now I hate to say it but the fault could have quite likely been caused by a hardware issue, as of late my 1000H has become more unstable, blue screen etc and I thought it was a BIOS/software fault but it turns out it's the 2GB ram module I installed in there. So it's quite likely that during the install the memory failed on one tiny location and messed up the system.
My apologies, I'll try to use this again soon and hopefully give some more positive feedback.
Offline
Sly wrote:
I'm off to uni soon and if this works it means I won't need to bring a bulky USB CD drive with me in case of Windows needing a reinstall.
Just make an image of your install once you get it the way you like it. Then there is no need to reinstall XP.
For example, I boot to Ghost 2003 from a 4GB thumb drive, and can restore the image that is on the same thumb drive.
Offline
Hemin wrote:
With both versions (alpha and beta) I get this error:
http://img171.imageshack.us/img171/9333/errormm8.jpg
Formated a 1GB Kington USB with HP tool. The process start, WinSetupFromUSB ask to permanent U: Usb drive letter, and then i get the above error.
What version of Windows are you running the tool on?
In WinSetupFromUSB folder there is a WinSetupFromUSB.log file, please check if it's over 50-100KB and upload it compressed somewhere, i.e. www.mediafire.com . If file is not big enough- have a look in \BACKUP folder, upon execution the program backs up the previous log file and compresses it in CAB format. Find the biggest one and upload it.
Thanks for the feedback.
Offline
This worked perfectly for me on my nlite'd SP3 install.
Anyone who is having major problems should check out and buy a U3 Memory stick from Sandisk or someone. They're only about £7 from Ebay etc for a 2GB, they're special because as well as a normal removeable drive it also emulates a CD drive, so you can install any ISO image file onto it and the PC thinks its an actual CD drive.
Offline
Hi. Have a brand new EEEPC 900 16G and I made it all the way to choosing the partition to install in Windows XP setup, and it gave me this message: "You computer's startup program cannot gain access to the disk containin the partition or free space you chose.". It continues, basically saying it doesn't have to be a hardware issue, just that sometimes the software in the install process can't access the drive.
Help
--Shawn
Offline
MouseMat wrote:
This worked perfectly for me on my nlite'd SP3 install.
Anyone who is having major problems should check out and buy a U3 Memory stick from Sandisk or someone. They're only about £7 from Ebay etc for a 2GB, they're special because as well as a normal removeable drive it also emulates a CD drive, so you can install any ISO image file onto it and the PC thinks its an actual CD drive.
Here is step-by-step guide how to "hack" the CD emulating drive on them and upload a custom ISO:
http://www.msfn.org/board/Install-XP-fr … 21502.html
For the procedure described in the first post there is no need to use such drives.
slockard wrote:
Hi. Have a brand new EEEPC 900 16G and I made it all the way to choosing the partition to install in Windows XP setup, and it gave me this message: "You computer's startup program cannot gain access to the disk containin the partition or free space you chose.". It continues, basically saying it doesn't have to be a hardware issue, just that sometimes the software in the install process can't access the drive.
What type of USB stick are you installing from?
What drive letter did the _USB stick_ get during Setup? When you run WinSetupFromUSB did it detect it as FIXED or as REMOVABLE? Did you change this setting?
And the internal disk, what drive letter did it get during Setup? Did you fix USB drive letter to U:?
Offline
odious_m wrote:
Just make an image of your install once you get it the way you like it. Then there is no need to reinstall XP.
For example, I boot to Ghost 2003 from a 4GB thumb drive, and can restore the image that is on the same thumb drive.
I have considered it but it's not something I really like using, It brings up problems in the idea of points of failiure, such as what if th image got corrupted, plus you are supposed to have a liscence for ghost so if I can go the legal option I will, tho some might say fiddling with a XP installer is just as 'illegal'.
Either way, ghosting is a pain over a fresh install from an nlite disc.
Offline
Sly wrote:
I have considered it but it's not something I really like using, It brings up problems in the idea of points of failiure, such as what if th image got corrupted, plus you are supposed to have a liscence for ghost so if I can go the legal option I will, tho some might say fiddling with a XP installer is just as 'illegal'.
Either way, ghosting is a pain over a fresh install from an nlite disc.
I always verify my images and have never had a corrupt one in the 6 years that I've used ghost.
A full restore takes 1 reboot and less than 10 minutes. I can't imagine a fresh install from an nlite disc being any more painless.
But, different strokes and all of that . . .
Offline
guеst wrote:
Hemin wrote:
With both versions (alpha and beta) I get this error:
http://img171.imageshack.us/img171/9333/errormm8.jpg
Formated a 1GB Kington USB with HP tool. The process start, WinSetupFromUSB ask to permanent U: Usb drive letter, and then i get the above error.What version of Windows are you running the tool on?
In WinSetupFromUSB folder there is a WinSetupFromUSB.log file, please check if it's over 50-100KB and upload it compressed somewhere, i.e. www.mediafire.com . If file is not big enough- have a look in \BACKUP folder, upon execution the program backs up the previous log file and compresses it in CAB format. Find the biggest one and upload it.
Thanks for the feedback.
Hi guest,
Running on a Windows XP Pro with SP3. All logs (included backups), are only 16Kb big. Uploaded the las log to mediafire
http://www.mediafire.com/?ogrjujlwz4t
Offline
As far as i remember, the key needs to be 1GB once it is formatted, which is not the case with a 1GB key.
Use a 2GB stick.
Offline
brucine wrote:
As far as i remember, the key needs to be 1GB once it is formatted, which is not the case with a 1GB key.
Use a 2GB stick.
I have tried with a 2GB without success.
Offline
Hemin wrote:
Hi guest,
Running on a Windows XP Pro with SP3. All logs (included backups), are only 16Kb big. Uploaded the las log to mediafire
http://www.mediafire.com/?ogrjujlwz4t
Please get this file, put it in C:\WinSetupFromUSB folder and launch it:
http://www.datafilehost.com/download-881df9ad.html
When the error occurs don't close the program yet, click SHOW BUG REPORT and make a screenshot, copy folder C:\WinSetupFromUSB\TEMP somewhere, close the program now, then copy WinSetupFromUSB.log to where you copied C:\WinSetupFromUSB\TEMP, ZIP the TEMP folder with the log file in it and upload it in mediafire.com.
I'd need this archive and the screenshots of the error.
For now it seems to be AutoIt bug, occurring only on some systems, could be a bit tricky to figure out where exactly it fails.
Thanks for your help.
Last edited by guеst (2008-09-18 8:44:35 pm)
Offline
guеst wrote:
When the error occurs don't close the program yet, click SHOW BUG REPORT and make a screenshot, copy folder C:\WinSetupFromUSB\TEMP somewhere, close the program now, then copy WinSetupFromUSB.log to where you copied C:\WinSetupFromUSB\TEMP, ZIP the TEMP folder with the log file in it and upload it in mediafire.com.
I'd need this archive and the screenshots of the error.
For now it seems to be AutoIt bug, occurring only on some systems, could be a bit tricky to figure out where exactly it fails.
Thanks for your help.
The zipped temp folder with log file inside:
http://www.mediafire.com/?tnbrtj4jyzn
Screenshot Error: 
I tried to run the program in a Virtual Machine with a windows XP and all run ok
Offline
Hemin wrote:
The zipped temp folder with log file inside:
...
I tried to run the program in a Virtual Machine with a windows XP and all run ok
Duh, it doesn't make sense at all to fail at that stage. I triple checked the code and can;t see anything weird. As you say it works on another installation.
The only way I can troubleshoot it further is to install AutoIt and Scite editor on the failing Windows and see exactly where exactly fails, using the source code.
If you have the time and willingness to do that, drop me a line on PM with your ICQ, Skype, email or MSN. Thanks for the reports.
Offline
guеst wrote:
Hemin wrote:
The zipped temp folder with log file inside:
...
I tried to run the program in a Virtual Machine with a windows XP and all run okDuh, it doesn't make sense at all to fail at that stage. I triple checked the code and can;t see anything weird. As you say it works on another installation.
The only way I can troubleshoot it further is to install AutoIt and Scite editor on the failing Windows and see exactly where exactly fails, using the source code.
If you have the time and willingness to do that, drop me a line on PM with your ICQ, Skype, email or MSN. Thanks for the reports.
Sounds like he might be missing a required component on his computer?
or something not registered/registering, or user access restrictions.
Last edited by Rory (2008-09-20 8:36:33 pm)
Offline
Rory wrote:
Sounds like he might be missing a required component on his computer?
or something not registered/registering, or user access restrictions.
Most likely- stopped seemingly unrelated service, unregistered or missing dlls, security permissions, go figure...
I've had one similar report, on Vista x64, but the guy never came back with any extra information and on my side I can't reproduce the problem at all.
Offline
My laptop have a lot of software garbage. May be some software are not compatible with WinSetupFromUSB... Don't worry because i get it working on a virtual machine.
Thank you
Offline
