If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
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 |
#2
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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 |
#3
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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 |
#4
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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. |
#5
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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 |
#6
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
On 10/31/2010 07:01 PM, legg wrote:
On Sun, 31 Oct 2010 16:32:19 -0500, 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 If you have on operating system installed on one drive then add an add'l drive that is larger than the bios can support... all you need to do is *disable* that channel in the bios. The machine should now boot normally and the operating system should see the drive. If you are using XP_sp3 or above, the entire 160 gigs should be available. have a look in disc management |
#7
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
On Tue, 02 Nov 2010 07:44:42 -0500, philo wrote:
On 10/31/2010 07:01 PM, legg wrote: On Sun, 31 Oct 2010 16:32:19 -0500, 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 If you have on operating system installed on one drive then add an add'l drive that is larger than the bios can support... all you need to do is *disable* that channel in the bios. The machine should now boot normally and the operating system should see the drive. If you are using XP_sp3 or above, the entire 160 gigs should be available. have a look in disc management No WXP on this system. The system will boot the W98 2ed OS, on the new 160G HDD, with single 125/137G partition, in primary master position, provided the primary slave slot is empty. If there's a slave installed (W2K sp4 alternate boot OS), then it won't boot from anything, not even a floppy. RL |
#8
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
On 11/2/2010 17:24, legg wrote:
On Tue, 02 Nov 2010 07:44:42 -0500, wrote: On 10/31/2010 07:01 PM, legg wrote: On Sun, 31 Oct 2010 16:32:19 -0500, 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 If you have on operating system installed on one drive then add an add'l drive that is larger than the bios can support... all you need to do is *disable* that channel in the bios. The machine should now boot normally and the operating system should see the drive. If you are using XP_sp3 or above, the entire 160 gigs should be available. have a look in disc management No WXP on this system. The system will boot the W98 2ed OS, on the new 160G HDD, with single 125/137G partition, in primary master position, provided the primary slave slot is empty. If there's a slave installed (W2K sp4 alternate boot OS), then it won't boot from anything, not even a floppy. Does the BIOS see the primary drive if the slave is connected, or is it a soft boot failure? |
#9
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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. |
#10
|
|||
|
|||
HDD upgrade - no boot - 48LBA? KM400-M2
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. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Upgrade from Windows 98 English to Windows Me Upgrade EDTN in Hebr | Idanbjacobs | General | 1 | October 25th 08 07:37 PM |
Windows 98 Boot.ini/Boot loader disiperance | dragonfly | General | 2 | June 5th 07 10:53 AM |
Restore Win98 boot from dual boot | Michael Fisher | General | 2 | February 4th 07 03:48 AM |
with oem 98 can not get a windows 98se upgrade disk and do an upgrade at all | DJW | Setup & Installation | 8 | November 26th 06 03:00 PM |
me boot and safe mode boot problems | knacked | General | 2 | February 5th 05 03:09 PM |