It does not make sense to me why you have to use a setup diskette, unless
your boot diskette is not properly made.  The message you give below could
explain all your fdisk trouble.  MS makes a virtual disk in ram memory
before it starts to install from a cdrom.  For some reason you have one of
these. You shouldn't allow the setup disk to load cdrom support and continue
with the install, with you knowing the cdrom drive is empty so it will
finish with a dos prompt.  This is not how you should be reaching the A:\>
Use the menu to select boot to command prompt only.  This will prevent the
ramdrive from being installed.  It will also force you to access the copy of
fdisk from the diskette.  Having a plain old boot disk with fdisk.exe on it
would also remove this wrinkle.  I can't tell from your messages, but one of
two things seems likely, 1. you are using a copy of fdisk.exe that is not on
the diskette, and therefore at the critical time when fdisk should write to
disk, it says reports it can't find itself.  fdisk won't access a diskette
so run it from there by typing
a:\fdisk.exe
2. you are trying to do something to the C: drive with fdisk, and C: is not
a hard disk.
Tom Turak

-----Original Message-----
From: John Stoker [mailto:[log in to unmask]]
Sent: Tuesday, November 13, 2001 9:19 PM

Thanks George or Mary
      I tried what you recomended and finally got to this point >volume in
drive c is MS-RAMDRIVE <  directory of C:\
                      File not found
                         !,,837,568 bytes free.
 Then I Tried C:\.Format  got required parameter missing.   But the good
news,I think is that now my boot disk works. This has become a pet project
so
I'll keep pluggin away.    Thanks Again John Stoker

            Do you want to signoff PCBUILD or just change to
                    Digest mode - visit our web site:
                   http://freepctech.com/pcbuild.shtml