Winsetupfromusb Free Download
Milba Vanpatten
Trying to put XP on hp mini 311 netbook ..choosing option 1 or 2...at least sata drive is recognized which is further than I got before... I choose the partition...all seems well...setup is starting... Then I am prompted to "insert the disk labeled dpms chennel etc...press enter or f3 to quit...pressing enter does nothing... I don't know why it's prompting for the drivers when they obviously were detected in the first step... I'm lost
Mind you, on picky machines DPMS may not work, the safest bet always is to integrate BTS mass storage driver pack with Text Mode option selected, or simply switch the disk controller to IDE/Compatible mode in BIOS.
Just do today so I have the latest 1.0... Single or double... Can't see the driver as screen blanks out too fast... I am seeing my hard disk with partitions so all seems well to that point... I select partition... Setup starts... Then I get the prompt for floppy... I did not press f6 so I don't know why...
It's irrelevant that you get past the partitioning screen. On picky machines this is expected behaviour- Setup would fail to maintain and use the contents of the virtual floppies created and ask for the files.
That winsetup file did the trick. Been struggling with this project to get Xp on this hp netbook for a while. Even with the sata drivers integrated into the install image, nothing worked. Tried Rufus, poweriso, wintoflash, and then found winsetupfromusb.
Very likely your computer is one of those that (for some strange reasons) has issues with MBR style devices if the firmware is set to UEFI only (maybe a DELL?) or that (again for strange reasons) doesn't "like" the grub4dos bootcode (Insyde BIOS?).
If you want to solve the problem with winsetupfromusb, you may want to try (if you are using a UEFI firmware) to enable the CSM (Comparibility Support Module, in practice BIOS, if you have this option) and/or try to change boot order (nowadays on most computer there are two ways to boot from USB, onechanging the boot order in the firmware and one changing this setting on-the-fly at boot time prssing a hotkey - like F8 or F11/F12 and sometimes oine of the two methods works and the other one doesn't).
I create successfully and boot those partitions either through BOOTICE using the U+V2 button, with dummy.sys driver and with WinSetupFromUSB v1.9 FBinstTool. I try to install XP from USB to the internal IDE disk which I know is recognized by WinXP SP3 official ISO disk, so I select the 1st option and check the "Don't check for and install grub4dos MBR" and "Do not copy and use DPMS" at the advanced options, as I already know my UDF can start the grldr and I don't need Driver Pack Mass Storage. I also try both grub4dos 0.4.5c and 0.4.6a versions.
The same issue which hangs plop on this old BIOS happen on another new PC, alas that new PC can successfully install XP without any double partition tricks using the Rufus 2.18 way faster as it uses USB2.0 speeds.
To try to solve this issue I give init --usb command which give me drive 81 for USB on old BIOS but then I can't access files through fdd device with ls. Is it possible shifthd.bat or other script has some bug when USB has two partitions (one is hidden)?
I also try to boot that old BIOS PC with UFD straight through MS-DOS (himem.sys in config.sys and smartdrv.exe) and then start winnt.exe from the UFD drive, which DOS gave it letter C to begin with XP setup. The 1st step of the winnt.exe XP setup process goes very fast like USB2.0 speed, but it suddenly reboot after it process a bunch of files.
I think that either I don't need plop but I don't know how to modify the grub4dos script to begin with usb --init command so whole setup can start from there, or I need to load some DOS USB driver on old BIOS in case of MS-DOS setup. Although by using DOS setup I end with an ugly installation in drive D.
Technically a (real) ZIP drive is a partitioned device with a single partition entry in 4th partition slot (with a given CHS geometry of n/64/32 but that should be later ignored by the NT based OS, as long as PBR iis on sector 32).
About installing starting from DOS, there is a (now old. and if not deprecated at least not recommended anymore) approach that keeps Windows drive letter C:, BUT the install is first done on FAT32 and later the volume is converted to NTFS:
2):
I just try the 1.0 version. At fbinst I reformat the UFD by using chs + zip + force options then I drag-drop grldr 0.4.6a. Test it to see if it boot to grub4dos and is OK. Then I continue with "Add to USB disk" and the two advanced options mention earlier.
The results are exactly the same. The script tries to shift the drive and fail (hang) on plop boot manager. Even Ctrl-Alt-Del does not respond. Do you think it is appropriate to try even earlier WinSetupFromUSB versions and/or try earlier grub4dos?
If I boot from UFD straight to DOS (no grub4dos) and then start ghost.exe from A: it fails, but the same ghost executable runs fine from internal C: in pure DOS.
If I boot straight from the internal C: disk to DOS then DOS doesn't see the UFD (eg. A:) although UFD has FAT32 partitions and its there. Maybe that issue is because UFD has partitions?
I try to follow that approach but I'm stuck in mud. I barely understand 30% of what they say. That is not step-by-step walk-though. He jump to conclusions without to present us how he got there. What commands gave to debug (I assume that he got boot from the internal hard disk to DOS then run debug.exe). How I can get the values for LLLL and SSSS?
I am perplexed by the two partitions (and the specific way you have them) in some cases having two partitions (one hidden) is needed to have the USB stick recognized as hd device, but normally the first partition (hd0,0) is the "good" one and a "dummy" one cylinder partition (not formatted and with a hidden ID *like* 21) is added (RMPREPUSB uses this approach), but this is to somehow "force" the BIOS to recognize the stick as hard disk device, if with your setup it is still recognized as floppy I fon't see the utility of the double partition.
and you should be in the "normal" situation where the internal hard disk is (hd0) and the UFD is (hd1), i.e. what the shiftd batch qould do if the UFD was from the beginning mapped to (hd0) and the internal disk as (hd1).
On all cases the shifthd.bat hangs when it gets to the plop boot manager.
Another issue just before it goes to execute the plop is when it is say "The highlighted menu entry will auto start after 10 seconds" but there isn't any menu entry so probably shifthd.bat has a bug.
(normally the UFD is seen as boot hard disk, i.e . it becomes (hd0) and the internal hard disk is shifted to (hd1) the shiftd bat is intended to remap the dirves so that the internal becomes (hd0) - thus indirectly allowing the setup to install to the C:\ drive - and UFD is shifted back to (hd1))
Didn't try because the main script winsetup.lst needs RDSK variable. I set RDSK=1 in shfthd.bat as I already know that by usb --init one more device (the hd1) appears to grub4dos. The whole setup procedure from start to finish after my modifications to the shifthd.bat runs fine on the newer PC but on old BIOS (AOPEN AK86-L) it freezes when windows setup loads kernel debugger dll. I also try several e820cycles values within winsetup.lst and some grub4dos versions with fbinst without any success.
My modifications (mostly comment out to shifthd.bat) as I know that UFD is detected as fdd and later using usb --init became hd1 and the rest are the originals from winsetupfromusb 1.9. Is there any known issue with windows setup and/or WinSetupFromUSB when the setup freeze at kernel debugger dll?
Yep, that is why I needed the winsetup.lst, it needs to be commented excluding the RDSK and other checks or, much better when experimenting NOT executed and replaced by manual commands (if they work they can be later reassembled in new, dedicated entries in winsetup.lst).
The whole point is that WinsetupfromUSB provides an "automagical" way that works in most cases (but not on this specific motherboard) and we need to manually find a procedure that works and only later modify the .lst accordingly.
then - still on command line - this is corresponding to the "title First part of Windows XP Professional SP3 setup from partition 0", executing these on command line you should see for most commands some feedback :
That error indicate I have to edit txtsetup.sif inside XPpSP3.ISO and change the rdisk(1) to rdisk(2). Then setup goes well until it is freeze on Mylex EXR2000 SCSI atapter. Again I remove all Mylex EXR2000 and dac2w2k entries from txtsetup.sif as I don't have any SCSI adapter. This time setup freeze at Kernel Security Provider.
93ddb68554