Re: Invalid media Type

"DonLogan" <navajo@xxxxxxxxxxxxxxx> wrote in message news:jgje92th041q6mmfr14jj0vjqrddt661rg@xxxxxxx
DonLogan <navajo@xxxxxxxxxxxxxxx> wrote:

Running W98. Have two disks, c: & d:
D is a 200gig, one partition, data drive. Left a program copying data
to d: overnight. This morning it said disk full, make some space.
Explorer saw d: but wouldn't give me any directory structure.
Looked at d:, over the network, from another machine & same thing.
Rebooted & I'm getting "Error 1 loading OS. May be due to a virus."
Then 4 options. Turned off virus check in bios & same thing. (think
this is some old disk >137 thing left over - will check later)

So booted from CD & get "invalid media type reading drive d. abort
retry fail"
Guess I have partition corruption? Any free utility to clean this up?
thanks

Well I guess the best (only) recommended forensic tool is "resqdisk".

While researching I saw that Stefan (sept 04) took a beating over a
badly formatted resqudisk report, but he did produce a full report!

And now I have a follow-up from Zvi Netiv too!

Wow. Make sure you get his autograph too.


If I disconnected d everything okeydokey. Plug in d and get the "error
1 reloading.....).

This machine doesn't have an a drive that works.

But the rest is rock solid, right?

And this morning this machine wouldn't boot!

Minor detail.

Replaced power supply and now ok. (but machine was up & running fine
when I found it that morning!)

Yes, obviously nothing to do with your problems.
Obviously it was the 137GB Windows bug, as Rod said.

Found a new "a" and replaced.
Updated bios to latest (even though Asus said mine was ok)
Did the resqdisk disk thing. Not intuitive!

Could only get a 1 page printout.

Yeah, that must be real bad, that really goes without saying.
A single page printout obviously can't solve the problem.

Stefan (sept 04) did much better. Didn't want to scrounge too much
time from Netiv so thought easier to start again, in this case. so..

So you wouldn't get an ear full from Netiv?
You probably still will for not trying.

Bullet time, using dos (because windows won't boot when d plugged in).
Downloaded seagate utils.

It wanted to set up & format drive as <137.

So likely it thinks the bios doesn't support 48-bit LBA.
Either that or it is plain stupid.

I said ok. Still got "error 1"
Found you can override <137 & did again.

Still "error 1"
Decided to use 1999 fdisk & format (!!) Still got "error 1"

Thought it might be some shitware (ddm?) on my boot 80gig!

Not so.

You sure?
This is absolutely weird behaviour, not observed with standard bootloaders.

So I remembered Netiv mentioning 63-68.

And it doesn't look like format & fdisk wrote there.

Fdisk doesn't (except maybe an occasional F6), but Format certainly does.

So used the seagate util to zero fill (fast, but was prepared to run full)
& then their format.

AND NOW OK

Now OK what?
Putting nothing but an empty formatted partition on the extra drive solved
the "Error 1 loading OS" error on the boot drive?

(for you rod)

Yeah, thanks 'rod', for mentioning the Resqdisk program to him.
You were such a big help.
.