Hello, You are still going to have a problem using fdisk to get rid or to change the Linux partition. I believe you are having trouble getting into fdisk possibly because.....because you are using the windows 98 floppy disk ...try this you will want to enter fdisk from the A:\ prompt and then type fdisk

0

Not that up on Linux - haven't used it - yet... But I think the issue is the mbr??? you need to run the: fdisk /mbr command from a DOS/'9x bootdisk/prompt. More on this whole issue below. Fdisk 'will' handle (delete) some W2K partitions. If ntfs in Extended then it won't, but if ntfs in Primary then it will. ntfs = non-DOS partition. W2K = fat132 (even fat16) then Fdisk will remove it regardless. Fdisk tutorial: http://support.microsoft.com/support/kb/articles/q255/8/67.asp http://www.compguystechweb.com/troubleshooting/fdisk/fdisk_scr.html Removing linux partition(s): A trawl via google.com for: removing linux partitions brings up much info; e.g. http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/install-guide/ch-uninstall.html http://www-uxsup.csx.cam.ac.uk/redhat/RHL-6.2-gsg/s1-q-and-a-removing.htm http://www.tldp.org/HOWTO/mini/Install-Strategies/x412.html

0

Arachian, when exactly do you get the error message? From the A:\> prompt (after booting with a bootdisk) if you type: fdisk (ENTER) Does fdisk start? If so, choose (Y) to enabling large-disk support, then choose option 4..Display partition information. What is listed? Or is this when the error pops up? Post back. Dave

0

Dave, it gives me the error after fdisk starts and asks me if I want to enable large disk support...obviously I hit 'Y' and strike 'enter'. After this, it gives me the error, "error reading fixed disk." Thanks...I hope this is helpful.

0

I'm not familiar with Linux, but I imagine that it has a partitioning/unpartitioning tool built-in. Try using this. Another option would be to try the Linux forum. Check this link from the MS Knowledge Base: Removing Non-DOS Partitions If the BIOS correctly recognizes the HD but Delpart doesn't & the Linux partitioning tool won't work, the only thing left to try that I can think of is a "write zeros" program. You can get killhdd.bat here: KillHDD.bat Hope something here helps. Dave

0

If it helps, I used Partition Magic to do the partition.

0

Arachian, yes that does help. Sometimes fdisk has a problem dealing with partitions created by third-party programs. Try removing the partitions with Partition Magic...either by using the DOS bootdisks or by popping the HD into another computer that has Partition Magic installed on it (as a slave drive). Remove the partitions, then reboot with a Windows bootdisk & try to create the new partition(s) using fdisk. Hope this helps. Dave

0

Last time this happened to me I went into the bios and turned the boot sector virus protection off and it went good as gold - email me if this works plz.

0

Michael Edwards, this did not work. Thanks. Anymore suggestions out there? any and all are welcome. Thanks.

0

A few 'wild-card' guesses and no more than that: Presuming the drive is still OK - hasn't died... Does it actually spin up at switch on? Does this system still boot at all (to either OS)? Is drive still set to be Primary Master; and is it detected in bios settings - i.e. do the drive settings show up in cmos page? Have you tried the Auto detect state, and LBA as appropriate; likewise tried manually entered all settings? Boot with a DOS/'9x bootdisk; at the a:>\ prompt type: fdisk /mbr (note the single space between fdisk and /mbr) and Press Enter. This erases bootsect info. Perhaps also run the sys c: command ('9x/DOS bootdisk) to reset mbr (bootsect) to DOS/'9x level and see if drive will boot to a prompt? Reboot (via bootdisk) and then see if Fdisk will run correctly? Perhaps visit the web-site for the drive make and download the LLF (or more correctly/preferably the MLF) util; this will write zeros to the drive and reset it back to factory gate status - providing it can find/detect the drive... MLF = Mid Level Format; LLF = Low Level Format. A 'true' LLF is not advised for current/recent drives; it can render them useless. There is a Debug routine for a true LLF that will wipe the drive... used carefully. The M$ KB for it: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q106419 Sadly... http://www.computerhope.com/issues/ch000379.htm doesn't give much hope... tends to suuggest the drive is toast...? But this one suggests a util (that may recover it - if possible): http://www.me.umn.edu/~ap/partition.html A search in the web (google.com) will bring up a few sources for the util suggested. If possible get the (util suggested) version from your drive's web-site? Again be aware of a true LLF as opposed to a MLF; possibly the suggested util is actually an MLF as opposed to an LLF? Similarly a search in google.com for: error reading fixed disk using Fdisk will bring up both of the above and many other similar resources/ideas etc... "Strongly advise" that you read the info at: http://www.pcguide.com/ref/hdd/geom/format_Low.htm re' LLF and debug routines - "before" using a true LLF/Debug... The web-site immediately above is probably one of the best for HD issues. Have you tried a Linux boot-disk to access the drive etc.? Finally was this system running OK prior to your current machinations; what exactly did you do to set this train of events in motion? Have to say I'm not sure the future's rosey for this drive - but one never knows?

0