Just keep booting from the USB stick until setup is complete, so that the virtual floppy drive is present throughout all stages of the installation process. For more information please refer to the [ USB mass storage specifications ]. The exact process that this solution goes through looks like this:. With nothing but your USB key, the drivers and the installation CD you can set up ancient Windows pretty much anywhere, as long as you still have an optical drive at least.
The USB floppy thing — How to add non-supported drives. This requires copying the entire CD off to another Windows machine, modifying a small file and rebuilding a new ISO using [ nLite ] though. Open it with your favorite text editor and locate the following part in the Section [HardwareIdsDatabase] :. Depending on your operating system, this may be found on totally different line numbers. SIF , like this:. SIF shown with an invalid non-floppy device here, but it works exactly like that with any unsupported real USB floppy drive.
But with that, you can now use any previously unsupported USB floppy drive for F6 driver installations. That may be especially true if you have to deal with lots of different machines with different SATA AHCI driver requirements or other storage controllers. Building new ISOs using nLite over and over again can be time consuming after all.
All rights reserved. I am re-building another machine with XP bit on it, and I have gone through the painstaking task of installing XP. I have done this several times and — as you know — the Windows XP bit CD install disc can take over an hour to install. Instead of the install CD and optical drive, is it possible to install XP from another hard drive?
If all the files on the install CD were copied across to a HD and the then run setup. Also, Could a USB drive containing all the install files be used some way like this? If it was done via USB 3 with its drivers, it would cut down the time dramatically.
I know this works for USB 2. As you mention in the USB 3. A virtual machine with a physical USB drive piped through to it should be good enough for a quick test I guess. Searching, I found a number of tricks to speed things up. Enter taskmgr, Processeses and right click setup. This cut down the time to approximately 25 minutes to get XP bit up and running.
EXE and setup XP bit to another partition. It did work but was problematic and I am still working on it. I am not too sure if it cut the time less than 25 minutes. I need to get away from floppy drives. This is not working, tried 2 different computers.
It starts from pendrive, loads the f6-images, ask to boot from CD, yes, windows-setups starts, but ALWAYS when setup starts to load files after the F6-question both machines immediately restart! I tried different usb-ports, pendrives, changed the optical drives, RAM, but it is always failing. I have Windows Pro on a thumb drive, how would I go about using a secondary thumb drive to boot up the necessary drivers to install Windows ? So you might want to do that instead. If you still wish to insist on an F6 solution with two USB pen drives, please read on!
One idea to solve this is to replace the BCDL boot loader with yet another syslinux one. That one would be booted by a corresponding boot track loading ldlinux. Unpack that. On Linux, check which device node the drive has e. The command shown above will allow you to identify your USB disk, but the disk id at the end is decimal, not hexadecimal. On top of that, it might be a negative number Windows wrongly interprets larger numbers as signed integers instead of unsigned ones.
On Windows, the same disk shows up with disk id To convert it to an unsigned decimal integer, calculate 2 32 - The reason this way doesn't work for disk drivers is because Windows must have access to the disk all the time during installation. Temparary disability to use 3D graphics, sound and network during Windows installation is acceptable, but disability to use hard disk even temporary disability makes Windows installation effectively impossible.
So, unlike other types of drivers, disk drivers must be installed not after Windows installation, but along with it. But how? Windows provides special mechanism for that purpose: loading drivers during Windows Setup, when Windows Setup had not yet loaded Windows Kernel, and operating in Text Mode. What's why these drivers are officially called 'Text-Mode Drivers', but people usually search for them in Google as 'F6 Floppy Drivers', so I prefer to call them that way.
Back to the subject. How do there drivers differ? What's special about Text Mode Drivers? The only type of disks which are readable at that time are BIOS disks. Nothing more. For that reason, Windows must load Text Mode Drivers from floppy.
Everything else is inaccessible under BIOS. Unfortunately, for some notebooks there's no such option in their BIOS setup. Windows already contains hundreeds of drivers for wide range of supported hardware, but not for everything, unfortunately. For example, Windows has builting support for ATA disk controllers see figure above in this article. So, all you need is just to add intergrate your particular driver to the long list of 'default' drivers.
There's a special software for that purpose called nLite. Then click 'Next':. Choose your device from the list. If you already have one on your USB bootable drive that you use with grub4dos, then cut and paste the following entries into it.
If you do not already have a menu. BIN chainloader 0xff. OEM entries. The file is in the Beta Downloads page on this website. Now it is time to make your bootable USB drive. If you want to wipe a USB drive, reformat it and make it bootable, then proceed as follows: 6. You should now have a bootable USB drive which has the four or five files listed at the beginning of this section. You will need to boot from the USB drive twice.
Please watch the YouTube video ,. Plug in the USB drive to your target computer. When the USB drive boots, you should see a menu similar to this one:. If you do not have enough memory in your system, the iso will be mapped directly and the XP GUI may or may not crash!
0コメント