Finding product key in registry

  • Thread starter Thread starter news.rcn.com
  • Start date Start date
Bob said:
I've had a customer with this problem with an Asus K8S-MX motherboard. It
was caused by the system booting too fast with a Maxtor ATA133 hard drive.
I had him lower the UDMA mode to 5 from 6 and it worked fine, can't be on
Auto either. Perhaps you will be lucky and this will work for you too.
This is actually needed to be done with this motherboard and any ATA133
IDE drive.
Click to expand...

Hi there

Boot up shows me that the board is an Asus V7100Pro: Is this similar to the
one you were using? The drive is an IBM All I could find from looking at the
motherboard specs on the Gateway site is that it says:
a.. The motherboard provides two independent synchronous direct memory
access (DMA) bus-mastering PCI IDE interfaces that support fast IDE PIO Mode
3, Mode 4, Advanced Technology Attachment Packet Interface (ATAPI), and
Ultra Advanced Technology Attachment (UATA) interface devices at speeds of
33/66/100.
b.. Compliant to ATA 4 and 5 specifications.
c.. The motherboard BIOS supports Logical Block Addressing (LBA) and
Extended Cylinder Head Sector (ECHS) translation modes.
d.. The BIOS Setup Utility automatically detects the IDE device transfer
rate and translation mode. This motherboard includes LS-120 support.
Normally, programmed I/O operations require a substantial amount of CPU
bandwidth. In true multi-tasking operating systems, the CPU bandwidth, which
is freed up by using bus-mastering IDE, can be used to complete other tasks
while disk transfers occur. When used in conjunction with the appropriate
driver, the IDE interface can operate as a PCI master capable of supporting
Ultra ATA devices with transfer rates of up to 100-megabytes per second.



Does this mean that I can't use the LOAD DEFAULTS AND EXIT setting to read
the drive and put in the appropriate UDMA setting or that there is somewhere
I can put enter it in the USER setting on IDE 1? (BTW Hitachi Global
Storage tells me that this is not an ATA133 drive but rather an ATA100).

I am starting to think that this OS will never work in a completely
different computer: (Hitachi confirmed this, without prompting, when saying
that I probably need to load the OS again) I shall try an in place upgrade
to XP first to see if that loads the drivers for the chipsets while
installing. But that 7 meg boot segment is still a bit of a mystery
 
For XP and 2000, I've found you need to change the IDE driver to the
standard driver that came with Windows then shut it down before moving it to
the new motherboard. You may also need to delete the Display driver. This
is assuming the old board is working.
 
Bob said:
For XP and 2000, I've found you need to change the IDE driver to the
standard driver that came with Windows then shut it down before moving it
to the new motherboard. You may also need to delete the Display driver.
This is assuming the old board is working.
Click to expand...

I did discover that I can install XP pro and get it working on this machine
so there cant be all that much wrong with the hardware as regards needed
changes on the MoBo or BIOS. I wonder if it is worthwhile deleting that
partition and copying all the windows 2000 files which are now on a F
partition back to the C partition to see if I can get its drivers working?
Or would it be better to downgrade the OS to 2000 and copy all of the files
from F to C? (this wont copy any working OS files which are running when I
do the XCOPY but will copy all of the software files to the C drive)

How did you change the IDE driver on an OS which has the wrong ones loaded?
 
Go to Device Manager, go to the properties of the IDE Controller, and update
the driver for the IDE Controller. Choose to "Install from a list or
specific location", then "Don't search, I will choose the driver to
install", then choose the standard driver. Also uninstall the Display
adapter. Don't reboot in either of these processes. Shut down and move the
hard drive to the computer. Then you will need to install the drivers disk
for the new motherboard.
 
I'm beginning to wonder why I bothered to spend an hour or so documenting a
likely solution for you ... Did you not see it or something?

The method I posted previously is

a) Based on one of a number of different possible workarounds from MS'
own site, which were described in the link I gave.

b) *Known* to work at least sometimes, because it worked for me.

c) Likely to be easily adapted to your particular circumstances.

Sure, it's tedious, but a lot less so than a complete reinstall, and MS'
original version in the section I highlighted would be quicker than mine.
Why not give it a go?
 
Back
Top