Linux Parbreastion Table Tutorials 968

Dave Uhring

Correct -- there's something *wrong* with the HDD *if* using the HDD Manu. utilities to write zeros didn't work.

MS's Orig win98FE FDISK version *does* have issues seeing Drives larger than 64GB (or is it 32GB?) -- there's an "updated" version of it on microcruds site - BUT you do NOT need it! unless you want to install 98. I had this issue with 80GB drives I have, but I also have Debian installed..hence *.linux.* NGs :-)

There's also a *very possible* BIOS limitation you've run into...you need to tell us more specific Hardware info.

Also note - there's always Killdisk -- and *Darin's Boot and Nuke* (dban.sourceforge.net)....but if you *need* to use MS Fdisk, (possibly b-c you don't know linux enough to use the 'dd' commands as noted by another - and are very unfamiliar with creating parbreastions using Linux's fdisk-cfdsik-sfdisk), then go to Microcrud's site and d-l the 'updated' version of Fdisk.

The other possibility is that 3rd party DDO software was used to create and manage HDD parbreastions originally - still...WD Data Lifeguard tools (writing zeros) should have wiped all of that anyway.

BTW - once you use Linux's cfdisk, you would *also* have the opportunity to change-buttign-view the parbreastion *type* to each and every parbreastion, *alter* all the types (and have a list of each type's corresponding hex value, which you would enter)....My point is: using Linux's tools you have MUCH more overall control of each and every parbreastion and HDD, even the *hidden* parbreastions and especially the *usually* (the Microcrud way) non-accessible disk areas.

The GNU-Linux utilities(?) called *hdparm* (for e.g.; # hdparm -ldev-hda) - and *dmidecode* - but especially the former (hdparm) will tell you ALL the commands and capabilities of the HDD.