HDD upgrade - no boot - 48LBA? KM400-M2

Transfering W98SE from 80G HD to sole 130Gpartition on 160G HD, in
dual boot (w982ed C;/, W2K SP4 D:\on separate HDD)
When the new 160G HD is relocated to primary master ide, the KM400-M2
stops after recognizing all drives, refuses to boot from any disk,
even the floppy, and after long delay issues a hd fatal error warning.

Have gone through the transfer attempt twice, using different W982ed
sources (original then last back-up) to different but identical 160G
targets (WD1600AAJB - of three purchased for anticipated ternary
backup), with the same results.

Original configuration W982ed on 80G C:\ , W2K SP4 on D: still boots
up normally.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

How do I get around it? No indication of 48LBA being addressed in bios
revs - so assume was never an issue..?..but ECS forums are mute on
this 'old' issue and Intel support (48lbachk.exe) no longer available.

WD is no longer interested in W98 (or W2K) issues. Used WD DLG Ver11.0
for the formating, partitioning and file transfer in both cases -
though in the second instance I manually set the partition size rather
than allowing an automatically-enforced 137G limitation that was
W98-OS-triggered in the first attempt.

RL

On 10/31/2010 02:55 PM, legg wrote:
Transfering W98SE from 80G HD to sole 130Gpartition on 160G HD, in
dual boot (w982ed C;/, W2K SP4 D:\on separate HDD)
When the new 160G HD is relocated to primary master ide, the KM400-M2
stops after recognizing all drives, refuses to boot from any disk,
even the floppy, and after long delay issues a hd fatal error warning.

Have gone through the transfer attempt twice, using different W982ed
sources (original then last back-up) to different but identical 160G
targets (WD1600AAJB - of three purchased for anticipated ternary
backup), with the same results.

Original configuration W982ed on 80G C:\ , W2K SP4 on D: still boots
up normally.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

How do I get around it? No indication of 48LBA being addressed in bios
revs - so assume was never an issue..?..but ECS forums are mute on
this 'old' issue and Intel support (48lbachk.exe) no longer available.

WD is no longer interested in W98 (or W2K) issues. Used WD DLG Ver11.0
for the formating, partitioning and file transfer in both cases -
though in the second instance I manually set the partition size rather
than allowing an automatically-enforced 137G limitation that was
W98-OS-triggered in the first attempt.

RL



No matter how you have the drive partitioned,
some bios's just will not support drives that large.

If there is no bios update
then get a PCI controller

legg wrote:
On Sun, 31 Oct 2010 16:32:19 -0500, philo wrote:

On 10/31/2010 02:55 PM, legg wrote:
Transfering W98SE from 80G HD to sole 130Gpartition on 160G HD, in
dual boot (w982ed C;/, W2K SP4 D:\on separate HDD)
When the new 160G HD is relocated to primary master ide, the KM400-M2
stops after recognizing all drives, refuses to boot from any disk,
even the floppy, and after long delay issues a hd fatal error warning.

Have gone through the transfer attempt twice, using different W982ed
sources (original then last back-up) to different but identical 160G
targets (WD1600AAJB - of three purchased for anticipated ternary
backup), with the same results.

Original configuration W982ed on 80G C:\ , W2K SP4 on D: still boots
up normally.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

How do I get around it? No indication of 48LBA being addressed in bios
revs - so assume was never an issue..?..but ECS forums are mute on
this 'old' issue and Intel support (48lbachk.exe) no longer available.

WD is no longer interested in W98 (or W2K) issues. Used WD DLG Ver11.0
for the formating, partitioning and file transfer in both cases -
though in the second instance I manually set the partition size rather
than allowing an automatically-enforced 137G limitation that was
W98-OS-triggered in the first attempt.

RL


No matter how you have the drive partitioned,
some bios's just will not support drives that large.

If there is no bios update
then get a PCI controller

I've just checked the previous ternary set and it seems that a 160GB
drive has been slipped into this group, during the last four years and
has been processed with an ~80GB single partition, without an issue.
It's the same model drive I'm having trouble introducing now, with the
larger partition.

RL

My old computer would not recognize greater than 80g partitions.
No bios update available for it.

On Sun, 31 Oct 2010 16:32:19 -0500, philo wrote:

On 10/31/2010 02:55 PM, legg wrote:
Transfering W98SE from 80G HD to sole 130Gpartition on 160G HD, in
dual boot (w982ed C;/, W2K SP4 D:\on separate HDD)
When the new 160G HD is relocated to primary master ide, the KM400-M2
stops after recognizing all drives, refuses to boot from any disk,
even the floppy, and after long delay issues a hd fatal error warning.

Have gone through the transfer attempt twice, using different W982ed
sources (original then last back-up) to different but identical 160G
targets (WD1600AAJB - of three purchased for anticipated ternary
backup), with the same results.

Original configuration W982ed on 80G C:\ , W2K SP4 on D: still boots
up normally.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

How do I get around it? No indication of 48LBA being addressed in bios
revs - so assume was never an issue..?..but ECS forums are mute on
this 'old' issue and Intel support (48lbachk.exe) no longer available.

WD is no longer interested in W98 (or W2K) issues. Used WD DLG Ver11.0
for the formating, partitioning and file transfer in both cases -
though in the second instance I manually set the partition size rather
than allowing an automatically-enforced 137G limitation that was
W98-OS-triggered in the first attempt.

RL



No matter how you have the drive partitioned,
some bios's just will not support drives that large.

If there is no bios update
then get a PCI controller

I've just checked the previous ternary set and it seems that a 160GB
drive has been slipped into this group, during the last four years and
has been processed with an ~80GB single partition, without an issue.
It's the same model drive I'm having trouble introducing now, with the
larger partition.

RL

legg wrote:

When the new 160G HD is relocated to primary master ide,
the KM400-M2 stops after recognizing all drives, refuses
to boot from any disk, even the floppy, and after long
delay issues a hd fatal error warning.

Check the jumpers on the drive. You probably have a jumper set where it
shouldn't be.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

If the motherboard was made during 2003 or after, it will almost
certainly be LBA-48 compatible.

If the motherboard was made during 2002 and possibly during 2001, then
there's a good chance there will be a bios update for it to make it
LBA-48 compatible if it's not already.

There are test programs you can run from a dos boot-floppy that will
tell you if the motherboard is LBA-48 compatible.

Also note that when it comes to the 128 GB (or 137 GB depending on how
you define a GB) issue, that for win-98 that you can't solve it simply
by making all partitions on a large drive less than 128/137 gb. If
Windows 98 tries to read or write beyond the 128gb point on the drive
(where-ever that might be on a drive with multiple partitions) then the
read or write operation will fail.

This is true for IDE drives, but not for SATA drives that are operating
in true SATA mode (not in IDE-remapped mode).

If I were you, I'd be using Norton Ghost (bootable from a floppy) to
make clone images from one drive to another.

So you've got several issues here. I think your main problem is that
you've got a drive-jumper problem, and then you've got a fundamental
problem with win-98 compatibility with IDE drives exceeding 128/137 gb.

On Sun, 31 Oct 2010 17:07:12 -0600, Paul in Houston TX
wrote:

legg wrote:
On Sun, 31 Oct 2010 16:32:19 -0500, philo wrote:

On 10/31/2010 02:55 PM, legg wrote:
Transfering W98SE from 80G HD to sole 130Gpartition on 160G HD, in
dual boot (w982ed C;/, W2K SP4 D:\on separate HDD)
When the new 160G HD is relocated to primary master ide, the KM400-M2
stops after recognizing all drives, refuses to boot from any disk,
even the floppy, and after long delay issues a hd fatal error warning.

Have gone through the transfer attempt twice, using different W982ed
sources (original then last back-up) to different but identical 160G
targets (WD1600AAJB - of three purchased for anticipated ternary
backup), with the same results.

Original configuration W982ed on 80G C:\ , W2K SP4 on D: still boots
up normally.

Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

How do I get around it? No indication of 48LBA being addressed in bios
revs - so assume was never an issue..?..but ECS forums are mute on
this 'old' issue and Intel support (48lbachk.exe) no longer available.

WD is no longer interested in W98 (or W2K) issues. Used WD DLG Ver11.0
for the formating, partitioning and file transfer in both cases -
though in the second instance I manually set the partition size rather
than allowing an automatically-enforced 137G limitation that was
W98-OS-triggered in the first attempt.

RL


No matter how you have the drive partitioned,
some bios's just will not support drives that large.

If there is no bios update
then get a PCI controller

I've just checked the previous ternary set and it seems that a 160GB
drive has been slipped into this group, during the last four years and
has been processed with an ~80GB single partition, without an issue.
It's the same model drive I'm having trouble introducing now, with the
larger partition.

RL

My old computer would not recognize greater than 80g partitions.
No bios update available for it.

Guess I'll have to change my plans, if it's hardware.

RL

In message , 98 Guy writes:
legg wrote:

When the new 160G HD is relocated to primary master ide,
the KM400-M2 stops after recognizing all drives, refuses
to boot from any disk, even the floppy, and after long
delay issues a hd fatal error warning.
[]
Also note that when it comes to the 128 GB (or 137 GB depending on how
you define a GB) issue, that for win-98 that you can't solve it simply
by making all partitions on a large drive less than 128/137 gb. If
Windows 98 tries to read or write beyond the 128gb point on the drive
(where-ever that might be on a drive with multiple partitions) then the
read or write operation will fail.

There is probably a link configuration on the drive that makes it look
like a 128/137G drive (i. e. you waste the remainder); because of the
limitation above, drive manufacturers started putting this option into
their drives when they were just passing that point. (I'm not sure if
they still do for much bigger drives, but certainly most ones around
160G have this option.) Setting that particular link configuration may
be your only option.
[]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf

We really don't have any enemies. It's just that some of our best friends are
trying to kill us.

"J. P. Gilliver (John)" wrote:

There is probably a link configuration on the drive that makes it
look like a 128/137G drive (i. e. you waste the remainder);

Maybe, but there's a simple solution in any case:

Take the drive in question, attach it to a PC and boot the PC with an
MS-DOS floppy disk that has fdisk.exe and format.com on the floppy. If
you're running win-98, it's trivial to create a bootable MS-DOS floppy.

Boot the floppy, run Fdisk, delete all existing partitions and volumes,
re-start the PC and again boot into DOS, again run fdisk, create new
primary partition, but make the size of that partition 128 gb.

Done.

Reboot, again boot the floppy, run format and format the 128 gb
partition.

Regardless what the drive's capacity is, you're using the first 128 gb
of it, which will make it compatible with Windows 98.

This is assuming the drive is IDE.

If the drive is SATA, you don't have to waste the drive's net capacity
like that - but that's assuming you're running win-98 on a computer that
has SATA ports or at least has a (cheap) PCI SATA controller card.

On Sun, 31 Oct 2010 22:48:22 -0400, 98 Guy wrote:

legg wrote:

When the new 160G HD is relocated to primary master ide,
the KM400-M2 stops after recognizing all drives, refuses
to boot from any disk, even the floppy, and after long
delay issues a hd fatal error warning.

Check the jumpers on the drive. You probably have a jumper set where it
shouldn't be.

The only two jumper positions used on these IDE drives are the ones to
determine master(with slave) or slave positions. The new drives are
formatted, partitioned and files transfered while in sec slave slot,
prev drive still in pri master, using WD mfr DLDIAG ver 11.0.


Is this a symptom of 48LBA limitations in the KM400-M2 MB or bios,
even though the partition size selected is lower than 135G?

If the motherboard was made during 2003 or after, it will almost
certainly be LBA-48 compatible.

If the motherboard was made during 2002 and possibly during 2001, then
there's a good chance there will be a bios update for it to make it
LBA-48 compatible if it's not already.

There are test programs you can run from a dos boot-floppy that will
tell you if the motherboard is LBA-48 compatible.

The ESC motherboard is KM400-M2 V1.0C 08/14/2004.

Also note that when it comes to the 128 GB (or 137 GB depending on how
you define a GB) issue, that for win-98 that you can't solve it simply
by making all partitions on a large drive less than 128/137 gb. If
Windows 98 tries to read or write beyond the 128gb point on the drive
(where-ever that might be on a drive with multiple partitions) then the
read or write operation will fail.

This is true for IDE drives, but not for SATA drives that are operating
in true SATA mode (not in IDE-remapped mode).

If I were you, I'd be using Norton Ghost (bootable from a floppy) to
make clone images from one drive to another.

So you've got several issues here. I think your main problem is that
you've got a drive-jumper problem, and then you've got a fundamental
problem with win-98 compatibility with IDE drives exceeding 128/137 gb.

I noted elswhere that one of the previous back-up set was a 160G drive
with an 80G partition. Same WD model. No issues.

The machine will boot into W982ed or W2K sp4 with the new drives in
the secondary slave position, reporting their 137gbytes / 127G size.

It's only when the new drive is relocated to primary master, with the
jumper relocated to master(with slave), that the machine freezes after
recognizing the drives and refuses to boot from any source, including
floppy.

RL

On 11/1/2010 12:09, legg wrote:

The machine will boot into W982ed or W2K sp4 with the new drives in
the secondary slave position, reporting their 137gbytes / 127G size.

It's only when the new drive is relocated to primary master, with the
jumper relocated to master(with slave), that the machine freezes after
recognizing the drives and refuses to boot from any source, including
floppy.


Try removing the slave and jumpering as single. Some IDE devices do not
play nice together. I have a DVD that refuses to work consistently w/o a
slave attached.

If it works, try swapping the primary slave w/ the secondary.. (rejumper
of course)