Format C [HD] and D&E gone missing

  • Thread starter Thread starter Jan
  • Start date Start date
Here it is!
Thanks, Jan
Click to expand...

The partition tables were not edited. The explanation probably is that
you did not have free environment space for setting the findpart
environment variabel to "edit" as done by the batch file.

Delete the fp2-1.txt file and try to figure out how to increase the
DOS box environment space. Then run the batch file again, and reboot.

Or you can get Findpart for DOS at my page, copy that findpart.exe and
the jarek1.bat file to a DOS boot floppy, boot to the floppy, and run
jarek1.bat, which still contains:

set findpart=edit
findpart 2 0 1 * 0C 0 1 1 2244 254 63 0 4982 255 63 26
findpart 2 0 2 - 0F 2245 0 1 4981 254 63 0 4982 255 63 26
set findpart=
findpart 2 table fp2-1.txt
 
Svend,
OMG I cannot believe it. Its all there and workable. I cannot thank you
enough I thought I was done for. I did the [Findpart for DOS at my page]
suggestion, and noticed a new drive showing up so got excited and for
good reason. So how can I thank you Svend, seriously!
Also to all the others. Thank You for helping me thru this.
Sincerely,
Jan
PS So how on earth did I do this?
I still cannot believe this fix happened via a few emails YAHOO!!
 
Svend,
OMG I cannot believe it. Its all there and workable. I cannot thank you
enough I thought I was done for. I did the [Findpart for DOS at my page]
suggestion, and noticed a new drive showing up so got excited and for
good reason. So how can I thank you Svend, seriously!
Also to all the others. Thank You for helping me thru this.
Sincerely,
Jan
PS So how on earth did I do this?
I still cannot believe this fix happened via a few emails YAHOO!!
Click to expand...

Nice.

You had EZ-drive installed in the MBR of disk 1. EZ-drive is a
program, which can be used if the BIOS does not support the full disk
size. The partitions of disk 2 would only be seen if EZ-drive was
loaded, in DOS and Windows 98. That is something EZ-drive does to
protect the partitions from being accessed without BIOS support.

Then you booted directly to floppy or CD-rom, so EZ drive was not
loaded, and made something that wrote to the MBR boot program. That
could be "fdisk /mbr" or installing Windows 98.

No one knows the exact behavior of EZ-drive and the DOS/Windows
treatment of EZ-drive, I guess, since it is not documented, and too
time consuming to figure out.

Since your BIOS supports the disk sizes, the problem could be solved
by editing the partition tables.
 
Wow Thank You So much for all your help Svend.
Does this mean I will always have this problem if I have to format
again? If so how can I prevent it? Sorry to take up more of your time I
feel greedy already.
Thanks Again Svend
Jan
 
Svend Olaf Mikkelsen said:
Svend,
OMG I cannot believe it. Its all there and workable. I cannot thank you
enough I thought I was done for. I did the [Findpart for DOS at my page]
suggestion, and noticed a new drive showing up so got excited and for
good reason. So how can I thank you Svend, seriously!
Also to all the others. Thank You for helping me thru this.
Sincerely,
Jan
PS So how on earth did I do this?
I still cannot believe this fix happened via a few emails YAHOO!!
Click to expand...

Nice.

You had EZ-drive installed in the MBR of disk 1. EZ-drive is a
program, which can be used if the BIOS does not support the full disk
size. The partitions of disk 2 would only be seen if EZ-drive was
loaded, in DOS and Windows 98. That is something EZ-drive does to
protect the partitions from being accessed without BIOS support.

Then you booted directly to floppy or CD-rom, so EZ drive was not
loaded, and made something that wrote to the MBR boot program. That
could be "fdisk /mbr" or installing Windows 98.

No one knows the exact behavior of EZ-drive and the DOS/Windows
treatment of EZ-drive, I guess, since it is not documented, and too
time consuming to figure out.
Click to expand...

But you did, apparently.
Since your BIOS supports the disk sizes, the problem could be solved
by editing the partition tables.
Click to expand...

Or run EZ-DRIVE uninstall. Or reinstall of EZ-DRIVE on the boot drive.
 
But you did, apparently.
Click to expand...

No. I know something, but the hole issue is so confusing, including
the EZ-drive (and Ontrack Disk Manager) programs. The only solution is
to try to forget it, and solve cases as they occur.
 
Back
Top