Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


ilko_t

How to install Windows from USB- WinSetupFromUSB with GUI

Recommended Posts

Posted (edited)
On 4/23/2020 at 10:30 AM, jaclaz said:

Now, when you run (WITHOUT mapping (fd0) to (hd1)) 

usb --init

it should produce (hd1) (or drive 0x81) and go on as before, it should do the same as before but with (hd1)

From my first post all this time I experience sudden lockups, freezes and reboots. Several times windows setup tell that "some xxxx line in txtsetup.sif is invalid", grub4dos dies after recognize usb etc. The same UFD with exactly the same files, sometimes boots to windows setup and others freeze etc on this old BIOS. When I remove some stuff using nlite it may go to the famous 7b error, but it never arrive to the screen which shows disk/partitions to choose for the installation to continue. It is not a hard disk controller driver issue either because the disk is IDE.

To investigate further after usb --init I chainload to DOS IO.SYS. This time grub4dos provides me with D drive which is the UFD. Nor the DOS setup (winnt.exe), neither a simple copy of the UFD I386 folder to the internal IDE disk came with success. DOS copy reboot after it copies some 200MB of files. With debug 3 in the winsetup.lst I had found that grub4dos throws some warnings on find and geometry commands "MBR cylinders(xxxxx) is not equal to the BIOS one(xxxx). MBR  total sectors(xxxxxxxxx) is greater that the BIOS one (xxxxxxxx). Some buggy BIOSes could hang when you access sectors exceeding the BIOS limit. Initial estimation blah-blah-blah, err=1  blah-blah" for the UFD, but it throws err=0 for the internal IDE. That same UFD throws err=0 on another newer PC at which both WinSetupFromUSB and the Rufus work fine to the end of the windows setup. Do you believe the "second thought" approach could work in my case?

Edited by seahorser

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...