Below is a long commentary on your messages. First, the short version:
1. Make sure you are using /dev/hdb, not just hdb, to try
to access the drive with fdisk (or cfdisk, or Disk
Druid, or whatever you are actually using).
2. Make sure the drive really is the IDE primary slave
(/dev/hdb), not the secondary master (/dev/hdc) or
the secondary slave (/dev/hdd).
Now, the long version ...
Like Lawson, I'm having some problems understanding just what you did,
particularly how the things you did under Windows and Linux interacted. My
difficultites were compounded a bit by your using different names for your
two messages (the first one came from "fdzgadfgaag", the second from
"Maurice"), making it hard to find your original message just by scanning
the headers list.
Anyway ... my first thought is ... how sure are you that the second hard
disk is the IDE primary slave? DOS/Win will call it D: wherever it is, but
Linux isn't equally flexible -- it uses hdc for secondary master, hdd for
secondary slave, even if there is no primary slave. You might simply be
looking in the wrong place. Clearly you found it once, since you partitioned
it once, but if that was during an install, might you have misread the
device designation?
My second thought is puzzlement over how you found, under Windows, a drive
E:. As you describe your setup, you have
first hard disk - all Windows (details unreported) - hence C:
second hard disk, first partition - also Windows - hence D:
second hard disk, logical partitions inside
extended partition - Linux native & swap - hence no
letter under Windows.
So ... where did E: come from?
There are also size discrepancies between your two messages. In the first
message, you say the second hard drive is partitioned in this way:
>1.96GB = (For Win98) 1st partition
>1.44GB = (Was for Win98) 2nd partition (Extended Dos w/ logical Dos)
In your more recent message, you say DOS fdisk reports these partitions:
> D: 1 PRI DOS 2012 FAT 16 62%
> 2 EXT DOS 1225 38%
Finally, what program are you running that you refer to as "Linux Fdisk"?
The fdisk (not Fdisk) I know of is a command-line program, so you wouldn't
be highlighting or clicking on anything in it. cfdisk has a somewhat more
friendly interface, but it sounds like you are using some X-based front end
to, or substitute for, fdisk. It would also help if you quoted **exact**
error messages from it -- "it says it can't read the device hdb" isn't
quoting an error message, and we still have to guess what you actually saw.
(BTW, you are actually using /dev/hdb, not just hdb, aren't you? If not, try
-- from the command line -- "fdisk /dev/hdb" and see if that gives you
better results.)
I, and others, are pleased to try to do our best to help you, but we really
need you to describe carefully and consistently what you've done, what you
see, and what your system setup is.
At 07:18 PM 10/30/99 -0400, Maurice wrote [in part]:
>Ok... here is all the exact info:
>
>Disk Duid: Error messsage during install: An error has occurred reading he
>partition table for the block device hdb.
>The error was:
>no such file or directory.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
