Greetings Ray and Chuck; thanks for your input.. I'm using v 2.12 of
both Fdisk and CFdisk, neither of which was the problem so the
subject line was, actually, in error..
Apprently I had three malfunctions at a time, masking the true
problem: One bad HD, a flaky flat HD cable and me... Doing all this
on a newly received MB didn't help.. Changing more than one
parameter at a time not a good idea sometime..
The HD is in the eCycle carton getting ready for Earth Day and the
cable, either evaluated critically or in the copper recycle bin..
All of the above coupled with me, somehow, losing the CMOS set up and
having to restore defaults and go from there - didn't help... Messing
with older, circa '92, drives didn't help either.. <grin>
Back to the drawing board, later, with a newer drive, etc...
Appreciate!!. Enjoying the list that supplies much of my learning
curve..
On 03-13, chuck gelm wrote:
> Ray Olszewski wrote:
> <snip>
> >I don't know what version of fdisk Slackware is shipping. MY Debian-Sid
> >system
> >is perhaps six months out of date, and it has fdisk version 2.12 ("fdisk
> >-v") and cfdisk and cfdisk 2.12 (cfdisk -v"). With these versions, I've
> >seen no problems with drives up to 250 GB or so.
>
> My Slackware v9.1, kernel 2.4.22, has
> fdisk v2.12 &
> cfdisk v 2.12
> ;-)
>
> HTH, Chuck
>
--
Hal - in Terra Alta, WV - Slackware GNU/Linux 9.0 (2.4.20-1)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
