Thread: Reformating Problem

  1. #1
    Unregistered
    Guest

    Reformating Problem

    I just installed a new hard drive to repalce my old one. I fdisked the new drive and its set to active. Im getting the error "Invalid Media Type Reading Drive C" whenever i try to touch the c drive. I know this is a common occurence since i Fdisked it but have not formatted it yet. But when i go to format it from the A:\> prompt by sayin A:\>Format c: im getting the exact same error. Its a windows 98 system disk. Any ideas? Ive been hearing that the problem is just that it hasnt been formatted but if i cant format it for the same reason then im kinda screwed...

  2. #2
    Used Registerer jdinger's Avatar
    Join Date
    Feb 2002
    Posts
    1,065
    Sounds like you forgot to include <partition.h> and when linking to "fdisk.lib".


  3. #3
    Unleashed
    Join Date
    Sep 2001
    Posts
    1,765
    > Sounds like you forgot to include <partition.h> and when linking to "fdisk.lib".
    Excellent work.

    OP:
    Put this in general discussion.
    The world is waiting. I must leave you now.

  4. #4
    Sir Mister Insane Sako Klinerr1's Avatar
    Join Date
    May 2002
    Posts
    608
    yeah i was thinking the same? wut the did this have ot do w/ c++. a mod must move this to general
    Email: [email protected] || AIM: MisterSako || MSN: [email protected]

    -the shroom has spoken

  5. #5
    Unleashed
    Join Date
    Sep 2001
    Posts
    1,765
    > wut the did this have ot do w/ c++.
    Do you mean, "What did this thread have to do with C++?" ...?
    If that's what you mean, unless otherwise informed, in my eyes, nothing at all.

    > a mod must move this to general
    Nah. The OP can delete his own thread, and then retype everything in GD as a lesson.

    More than likely this thread is long gone along with the OP.
    The world is waiting. I must leave you now.

  6. #6
    and the hat of int overfl Salem's Avatar
    Join Date
    Aug 2001
    Location
    The edge of the known universe
    Posts
    39,660
    Did you tell your BIOS about the new hard disk before you tried to fdisk it?

    Or at least have a BIOS which autodetects hard disks, and is set to "auto".

  7. #7
    Registered User
    Join Date
    Dec 2001
    Posts
    194
    hahahaha nice one unknown person.

    Original Poster = OP

  8. #8
    Registered User
    Join Date
    Jul 2002
    Posts
    161
    Salem's right. Sounds like a hardware setup problem. You need to go into bios setup. With luck just enterring setup might trigger autodetect.

  9. #9
    Registered User TravisS's Avatar
    Join Date
    Jun 2002
    Posts
    536
    It is auto-detecting it you guys
    Read what he wrote... He was able to fdisk it. If it wasn't auto-detecting it, fdisk would have said "No fixed disk found" or something to that extent.

    I recently had the same problem about a week ago. Really odd. I would fdisk it, it would make it through 100% no errors, but it would show the sytem type as "UNKNOWN". I ignored that fact, rebooted it, tried to format, and I got the whole "Invalid Media Type Reading Drive C" error. So, I tried a different boot disk (I carry two win ME disks (one a CD, one a floppy) and a 98 bootable CD), destroyed the old partition, made a new one, and yet again UNKNOWN system type and "Invalid Media Type Reading Drive C" error. Finally, I tried one more time, still got UNKNOWN system type, but, by some luck, that time it formated

    So, I guess just try it over and over... Not much of a professional hint, but it's the best I can offer. Oh, and maybe use a win 98 boot disk?

    Oh yeah, while my brain is thinking... How large is the drive and what OS is going on it? I ask because FAT32 simply cannot handle a partition size of over 32 gigs. It will partition fully, fdisk will give no errors, but it will be un-formattable (to everything but NTFS).

  10. #10
    Patent Pending GSLR's Avatar
    Join Date
    Sep 2001
    Posts
    134
    a:> format c: /s
    And To All Those Opposed, WELL !!!
    >Deleted< " Looks like a serial no."

  11. #11
    train spotter
    Join Date
    Aug 2001
    Location
    near a computer
    Posts
    3,868
    >>He was able to fdisk it. If it wasn't auto-detecting it, fdisk would have said "No fixed disk found" or something to that extent.

    Actually, if you replaced a 20Gb HD with a 60Gb HD and did not tell the BIOS (or had autodetect on) then fdisk'ed it, the maximum partion available would be 20Gb.

    >>I ask because FAT32 simply cannot handle a partition size of over 32 gigs.

    News to me and a big shock to my 40Gb HD (with a single partion) on Win98SE.
    "Man alone suffers so excruciatingly in the world that he was compelled to invent laughter."
    Friedrich Nietzsche

    "I spent a lot of my money on booze, birds and fast cars......the rest I squandered."
    George Best

    "If you are going through hell....keep going."
    Winston Churchill

  12. #12
    Registered User moi's Avatar
    Join Date
    Jul 2002
    Posts
    946
    Originally posted by novacain
    >>He was able to fdisk it. If it wasn't auto-detecting it, fdisk would have said "No fixed disk found" or something to that extent.

    Actually, if you replaced a 20Gb HD with a 60Gb HD and did not tell the BIOS (or had autodetect on) then fdisk'ed it, the maximum partion available would be 20Gb.

    >>I ask because FAT32 simply cannot handle a partition size of over 32 gigs.

    News to me and a big shock to my 40Gb HD (with a single partion) on Win98SE.
    FAT32 supports sizes up to 2TB (thats 2048GB), although certain implementations (win2k i believe) only support up to 32GB FAT32 partitions.
    hello, internet!

  13. #13
    Registered User
    Join Date
    Jul 2002
    Posts
    161
    Hmm. Well, assuming that it was set up correctly in bios when he ran fdisk then here are a few other ideas.

    Motherboard cmos battery needs replacing.

    Was the drive brand new when you got it? This sort of thing can happen after using non MS partitioning. For example, if linux were installed and incorrectly removed.

    Some WD hd's (and maybe other manufacturer's) do not set dma modes properly on some motherboards and will cause this error. WD has a mode set utility download for this.

  14. #14
    Registered User
    Join Date
    Jul 2002
    Posts
    161
    My bad memory playing tricks again. It's Maxtor hd's that have that problem, and the download fix is on Maxtor's site.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Need help understanding a problem
    By dnguyen1022 in forum C++ Programming
    Replies: 2
    Last Post: 04-29-2009, 04:21 PM
  2. Memory problem with Borland C 3.1
    By AZ1699 in forum C Programming
    Replies: 16
    Last Post: 11-16-2007, 11:22 AM
  3. Someone having same problem with Code Block?
    By ofayto in forum C++ Programming
    Replies: 1
    Last Post: 07-12-2007, 08:38 AM
  4. A question related to strcmp
    By meili100 in forum C++ Programming
    Replies: 6
    Last Post: 07-07-2007, 02:51 PM
  5. WS_POPUP, continuation of old problem
    By blurrymadness in forum Windows Programming
    Replies: 1
    Last Post: 04-20-2007, 06:54 PM