See below.
BillW50 said:
In Pegasus (MVP) typed:
What do you see when you do this Pegasus? I don't have a floppy drive on
this computer,
*** In these cases I make a boot diskette on a machine that does
*** have a FDD, then burn a bootable CD based on this diskette.
*** I would then test this boot CD on that same machine.
but I did follow your instructions on a bootable removable SD card and I
get the following message:
~~~~~~~~~~
Invalid system disk
Replace the disk, and then press any key
*** Sorry, I have never tried this.
~~~~~~~~~~
I added a few more files like IO.SYS and MSDOS.SYS and then I got the
following:
*** You do not need io.sys and msdos.sys - they are Win9x boot
*** files. It is sufficient to have a WinXP boot sector, which is
*** created when formatting the floppy disk under Explorer or
*** with format.exe, but only on a WinXP/2000 PC.
~~~~~~~~~~
Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file.
~~~~~~~~~~
*** This could happen if the system drive number is incorrect.
*** You can get around the problem by having several lines
*** in a:\boot.ini like so:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows XP
Professional" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows XP
Professional" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows XP
Professional" /fastdetect /noexecute=optin
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="4 Microsoft Windows XP
Professional" /fastdetect /noexecute=optin
*** Note that these are long lines that might get broken up
*** by your newsreader.
***
*** During the timeout period of 5 seconds you get an
*** opportunity to select one of the 4 options, each
*** pointing to a different partition on your first disk.
***
*** If your Windows installation is intact then you will be
*** able to boot into Windows with this boot diskette/CD,
*** even if the hard disk boot environment is damaged.
*** The next step would then consist of repairing the boot
*** environment.