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

If you partition the Disk with Win98 Fdisk
And win2000 is a new install
You need to get win2000 setup to Reformat the partition to make it to
install right!

On Tue, 9 Nov 2010 08:01:03 -0600, "Hot-Text"
wrote:


http://www.ecsusa.com/ECSWebSite/ECS...yword=KM400-M2

KM400-M2 (V1.0)
Socket 462 for AMD K7 processor
DDR 333
AGP 8X
6 Channel Audio
USB 2.0
10/100 LAN
Color Map
ATA133

or

KM400-M2 (V3.0)
Socket 462 for AMD K7 processor
FSB 333
DDR 333
RAID0, RAID1 support
Serial ATA
ATA133
AGP 8X
10/100 LAN
6 Channel Audio
USB2.0
Color map

On (V1.0) you have to go in to Award BIOS setup

IDE connectors
Master
And put the Head drive on User
16383 cylinder
16 heads for it be at 15 heads need to be 16
63 SPT

All WD EIDE drive 8.5 GB and larger use 16383 cylinder, 16 heads and 63 SPT
due to interface retractions

http://wdc.custhelp.com/cgi-bin/wdc....7%2C295#jumper


I don't think a WD drive smaller than 20G has ever been used on this
system.

The '124gw98on160G' drive functions by itself in pri master, and will
also function as slave on sec ide.

An identical drive with a smaller partition '80gw98on160G' will also
boot in pri master for a dual-boot situation with W2K in pri slave.

The SATA section of the motherboard is unpopulated, so it's not V3.0.

I'll take a look at the manual drive settings available in the bios,
to see if there's anything that looks likely.

RL

On Tue, 9 Nov 2010 21:13:33 -0600, "Hot-Text"
wrote:

If you partition the Disk with Win98 Fdisk
And win2000 is a new install
You need to get win2000 setup to Reformat the partition to make it to
install right!


It's a clone of an 80G W98 bootable partition in a working system,
transfered using WD DLG 11 in DOS. The source drives are simply
getting old.

The target's partition size was a default limit for the W98 OS, set by
the DLG tool. A slightly smaller one set manually had the same dual
boot issue on a subsequent target using a different, older back-up
source.

RL

On Tue, 9 Nov 2010 08:01:03 -0600, "Hot-Text"
wrote:


On (V1.0) you have to go in to Award BIOS setup

IDE connectors
Master
And put the Head drive on User
16383 cylinder
16 heads for it be at 15 heads need to be 16
63 SPT

All WD EIDE drive 8.5 GB and larger use 16383 cylinder, 16 heads and 63 SPT
due to interface retractions

http://wdc.custhelp.com/cgi-bin/wdc....7%2C295#jumper

I don't see anything in the WD published literature that refers to
these settings. Where did 16383 come from?

Bios auto settings for varying access modes:

Access Mode Auto CHS LBA Large
data given given given given
cap 160G 160G 160G 160G
cyl 65535 65535 16642 4095
head 16 16 255 240
precomp 0 0 0 0
LZ 65534 65534 65534 65534
sect 255 255 63 255

User setting options are only writable in CHS access mode, but these
cause alterations in the others, subsequently, if the other access
modes are reverted to:

Access Mode Auto CHS LBA Large
data rewrite written given given
cap 160G 160G 160G
cyl 16383 1027 1092
head 16 255 240
precomp 0 0 0
LZ 65534 65534 65534
sect 63 63 63

I exited without saving, so the bios is still in autodetect default.
If you can confirm a source for your 16383 number, I would consider a
boot attempt with chs-entered values.

RL

"legg" wrote in message
...
On Tue, 9 Nov 2010 08:01:03 -0600, "Hot-Text"
wrote:


On (V1.0) you have to go in to Award BIOS setup

IDE connectors
Master
And put the Head drive on User
16383 cylinder
16 heads for it be at 15 heads need to be 16
63 SPT

All WD EIDE drive 8.5 GB and larger use 16383 cylinder, 16 heads and
63 SPT
due to interface retractions

http://wdc.custhelp.com/cgi-bin/wdc....7%2C295#jumper

I don't see anything in the WD published literature that refers to
these settings. Where did 16383 come from?

Bios auto settings for varying access modes:

Access Mode Auto CHS LBA Large
data given given given given
cap 160G 160G 160G 160G
cyl 65535 65535 16642 4095
head 16 16 255 240
precomp 0 0 0 0
LZ 65534 65534 65534 65534
sect 255 255 63 255

User setting options are only writable in CHS access mode, but these
cause alterations in the others, subsequently, if the other access
modes are reverted to:

Access Mode Auto CHS LBA Large
data rewrite written given given
cap 160G 160G 160G
cyl 16383 1027 1092
head 16 255 240
precomp 0 0 0
LZ 65534 65534 65534
sect 63 63 63

I exited without saving, so the bios is still in autodetect default.
If you can confirm a source for your 16383 number, I would consider a
boot attempt with chs-entered values.

Without trying to be unkind to the other poster, if you continue trying
to follow his incorrect suggestions you may find yourself in an
irreversible situation. Your mobo and BIOS recognize drives greater
than 8.5GB and 32GB, so you do not have any of the limitations Hot-Text
is referring to, and making changes in disk geometry in the BIOS will
likely lead to the loss of you data.

Please wait for and continue with Bill Blanton's direction.
--
Glen Ventura
MS MVP Oct. 2002 - Sept. 2009
CompTIA A+
http://dts-l.net/

On 11/9/2010 21:16, legg wrote:
On Tue, 09 Nov 2010 07:45:41 -0500, Bill Blanton
wrote:

On 11/8/2010 19:58, legg wrote:
On Thu, 04 Nov 2010 13:21:16 -0400, Bill Blanton
wrote:
With no idea if you're still having hardware issues, all I can suggest
is clear the disk signatures, and make sure boot.ini is correct.

Any time you clone in an NT boot situation and then hook up the origianl
disk the disk sig situation needs to be addressed. Either delete or
copy/delete.

I had some time to run partinfo on the problematic drive, in it's solo
boot master position. It reported as HD0 - 0x00000000.

9x does not assign signatures to its disks. It's probably 0 from the
fdisk /cmbr you did on it. Does it show up as initialized in 2K's disk
managemnet?


When later mounted in sec slave, in a good W98/W2K dual boot set-up,
W2K gave it an E1 11 c9 aa signature (reading backwards in the
registry). Also reports as 128G healthy and active partition in disk
management.

I'll see whether the signature takes, when it is next mounted in a
solo boot or no boot situation.

The problem now is that it's going to to remembered as H: (or whatever)
and not get the C: when booted to 2K. It would be better if the sig was
0 for the first boot.

I cleared the mbr of the 124Gon160G W98, ran partinfo on it alone.

Then, with W2k in the primary slave slot I tried to boot up - got the
same disk failure message after the usual wait.

This time, however, I noticed the massage at the bottom of the boot
screen had changed to 'press F1 to continue'. The prompt to enter
setup was shifted to the right.

It's possible that this message was there on previous attempts - all I
noticed previously was that the usual prompt to enter setup wouldn't
take.

That's probably a sign of the BIOS barfing on the hardware configuration.

I'm pretty sure this line was shorter before - simply missing
the 'bypass cmos test' prompt after the cmos test ended or was
bypassed.

F1 got a boot to W2K CD and the recovery console.
'fixmbr' (not 'fixmbr C:', perhaps a mistake, perhaps not)

reboot, same delay, same disk fail message.
F1 got a boot to W98 boot floppy this time, to run partinfo again,
saving the file to C:\partinfx.txt (to differentiate it from the
previous report).

Rebooted solo 124Gon160G W98 in pri master (had to ok a boot sector
rewrite) without signs of damage. First partinfo report was present
indicating sig was cleared at that time, but the second partinfx.txt
file was not there.

Rebooted to W2K with old W98 80Gon160G restored to pri master, without
event. No signs of damage, both disks looking fine in Disk management
and registry lines looking unchanged for those partition signatures.

Partinfx.txt appeared in the root of D:........ The partinfo program
had recognized and reported pri slave as HD0, when the test was run.

Sounds like the first drive was not being seen during that particular
partinfo, and the first partition on the second drive was enumerated as C:.

I know you have the jumpers set correctly. Are you using an 80-wire
cable? Have you tried cable select on both drives? If not, that's
something to try. Make sure the master's on the end of the cable(black)
and slave is in the middle(gray).

The only other idea I have is to move the W2K disk to the secondary
master and shuffle whatever you have on the secondary controller. You'd
need to adjust boot.ini accordingly.

On 11/10/2010 10:03, glee wrote:
"legg" wrote in message
...
On Tue, 9 Nov 2010 08:01:03 -0600, "Hot-Text"
wrote:


On (V1.0) you have to go in to Award BIOS setup

IDE connectors
Master
And put the Head drive on User
16383 cylinder
16 heads for it be at 15 heads need to be 16
63 SPT

All WD EIDE drive 8.5 GB and larger use 16383 cylinder, 16 heads and
63 SPT
due to interface retractions

http://wdc.custhelp.com/cgi-bin/wdc....7%2C295#jumper


I don't see anything in the WD published literature that refers to
these settings. Where did 16383 come from?

Bios auto settings for varying access modes:

Access Mode Auto CHS LBA Large
data given given given given
cap 160G 160G 160G 160G
cyl 65535 65535 16642 4095
head 16 16 255 240
precomp 0 0 0 0
LZ 65534 65534 65534 65534
sect 255 255 63 255

User setting options are only writable in CHS access mode, but these
cause alterations in the others, subsequently, if the other access
modes are reverted to:

Access Mode Auto CHS LBA Large
data rewrite written given given
cap 160G 160G 160G
cyl 16383 1027 1092
head 16 255 240
precomp 0 0 0
LZ 65534 65534 65534
sect 63 63 63

I exited without saving, so the bios is still in autodetect default.
If you can confirm a source for your 16383 number, I would consider a
boot attempt with chs-entered values.

Without trying to be unkind to the other poster, if you continue trying
to follow his incorrect suggestions you may find yourself in an
irreversible situation. Your mobo and BIOS recognize drives greater than
8.5GB and 32GB, so you do not have any of the limitations Hot-Text is
referring to, and making changes in disk geometry in the BIOS will
likely lead to the loss of you data.

I agree. It could boot or partially boot, and in the meantime, the OS is
writing to unintended regions of the disk.

Please wait for and continue with Bill Blanton's direction.

Thanks for the confidence Glen, but I'm pretty much out of ideas at this
point. ;-/

Bill Blanton wrote:

On 11/10/2010 10:03, glee wrote:
"legg" wrote in message
...
On Tue, 9 Nov 2010 08:01:03 -0600, "Hot-Text"
wrote:


On (V1.0) you have to go in to Award BIOS setup

IDE connectors
Master
And put the Head drive on User
16383 cylinder
16 heads for it be at 15 heads need to be 16
63 SPT

All WD EIDE drive 8.5 GB and larger use 16383 cylinder, 16 heads and
63 SPT
due to interface retractions


http://wdc.custhelp.com/cgi-bin/wdc....7%2C295#jumper


I don't see anything in the WD published literature that refers to
these settings. Where did 16383 come from?

Bios auto settings for varying access modes:





Access Mode Auto CHS LBA Large
data given given given given
cap 160G 160G 160G 160G
cyl 65535 65535 16642 4095
head 16 16 255 240
precomp 0 0 0 0
LZ 65534 65534 65534 65534
sect 255 255 63 255

User setting options are only writable in CHS access mode, but these
cause alterations in the others, subsequently, if the other access
modes are reverted to:


Here!

autodetect default need to be set to (USER)

Access Mode Auto CHS LBA Large User LBS Ok
data rewrite written given given
cap 160G Pc will set up
cyl 16383 You Set to
head 16 You Set to
precomp 0 Pc will set up
LZ 65534 Pc will set up
sect 63 You Set to



I exited without saving, so the bios is still in autodetect default.
If you can confirm a source for your 16383 number, I would consider a
boot attempt with chs-entered values.

Without trying to be unkind to the other poster, if you continue trying
to follow his incorrect suggestions you may find yourself in an
irreversible situation. Your mobo and BIOS recognize drives greater than
8.5GB and 32GB, so you do not have any of the limitations Hot-Text is
referring to, and making changes in disk geometry in the BIOS will
likely lead to the loss of you dat



His PC is not that new! and it not the Drive sides it the HEAD #'s it not
recognize by BIOS it have be giving 255 or 240 out!



I agree. It could boot or partially boot, and in the meantime, the OS is
writing to unintended regions of the disk.

Please wait for and continue with Bill Blanton's direction.

Thanks for the confidence Glen, but I'm pretty much out of ideas at this
point. ;-/

Last ideas here too But i in the last two weeks in been working on HDD
bigger thing 20 GB and a old BIOS and it made the Heads 15 not 16 it h

On Wed, 10 Nov 2010 20:18:19 -0500, Bill Blanton
wrote:


Rebooted to W2K with old W98 80Gon160G restored to pri master, without
event. No signs of damage, both disks looking fine in Disk management
and registry lines looking unchanged for those partition signatures.

Partinfx.txt appeared in the root of D:........ The partinfo program
had recognized and reported pri slave as HD0, when the test was run.

Sounds like the first drive was not being seen during that particular
partinfo, and the first partition on the second drive was enumerated as C:.

I know you have the jumpers set correctly. Are you using an 80-wire
cable? Have you tried cable select on both drives? If not, that's
something to try. Make sure the master's on the end of the cable(black)
and slave is in the middle(gray).

The only other idea I have is to move the W2K disk to the secondary
master and shuffle whatever you have on the secondary controller. You'd
need to adjust boot.ini accordingly.

I'll try the cable select option again first - it seemed to work
(once) before, a week ago (usenet msg at 1011011852). Will try to
figure out what was being done then, to prep it, and try not to make
the same mistake that prevented it from happening again. Hope it
wasn't just accidentally hitting F1 instead of esc (or both out of
frustration).

RL

On Wed, 10 Nov 2010 22:15:02 -0500, legg wrote:

On Wed, 10 Nov 2010 20:18:19 -0500, Bill Blanton
wrote:


Rebooted to W2K with old W98 80Gon160G restored to pri master, without
event. No signs of damage, both disks looking fine in Disk management
and registry lines looking unchanged for those partition signatures.

Partinfx.txt appeared in the root of D:........ The partinfo program
had recognized and reported pri slave as HD0, when the test was run.

Sounds like the first drive was not being seen during that particular
partinfo, and the first partition on the second drive was enumerated as C:.

I know you have the jumpers set correctly. Are you using an 80-wire
cable? Have you tried cable select on both drives? If not, that's
something to try. Make sure the master's on the end of the cable(black)
and slave is in the middle(gray).

The only other idea I have is to move the W2K disk to the secondary
master and shuffle whatever you have on the secondary controller. You'd
need to adjust boot.ini accordingly.

I'll try the cable select option again first - it seemed to work
(once) before, a week ago (usenet msg at 1011011852). Will try to
figure out what was being done then, to prep it, and try not to make
the same mistake that prevented it from happening again. Hope it
wasn't just accidentally hitting F1 instead of esc (or both out of
frustration).


There were no surprises re-booting with both drives jumpered CS.

New W98 solo pri master CS - boot to floppy - partinfo (reads zero on
C: later) - fdisk /mbr - OK'd boot rewrite - partinfo (reads zero on
C: later). Shutdown.

Add W2K pri slave CS - boot to disk fail message - F1 to floppy -
partinfo (reads zero on W2K D:, as HDD0, later). Did not F1 to CD, as
a recovery console fixmbr would be pointless while W98 on C: is not
recognized.
...............

Shifted W2K to sec master CS, optical to sec slave CS.

Booted up to (no boot options) W98, accepting boot rewrite.
Disk and partition order/assignment is unaffected in W98:
C:127G (w98)
D:17.5G (W2K)
E:28.3G (LIB01)
F:28.3G (LIB02)
G:CD

I manually edited boot.ini on C: to reflect the new drive physical
position for the W2K line -
multi(0)disk(0)rdisk(2)partition(1)\WINNT="W2Kpro SP4" /fastdetect

reboot to Partinfo shows that C: signature is still zeroed.

Reboot to W2K CD (had to accept a boot rewrite to do so ( ? ).
In the recovery console, ran fixmbr (again, not fixmbr C.

Reboot to W98 (again, no boot options)
Partinfo shows that C: signature is now 6EBE6EBE

Reboot to savepart.
Manually altered C: sig from 153b153a to 6ebe6ebe
(all other sigs still familiar)

Reboot to W98 (still no boot options)

An old floppy boot crutch (ntldr, bootsect.dos, ntdetect.com and
rewritten boot.ini) could get a boot option screen. Selecting W2k only
got a 'could not start because of hardware configuration problems'
message. Would have expected 'ntldr missing' if I'd simply missed a
valid target. Perhaps the crutch files are outdated.

RL