Try looking in registry
HKEY_LOCAL_MACHINE
HARDWARE
DEVICEMAP
Scsi
peter
"Seaking" wrote in message
...
Hi again.. yes, he actualy was able to install the drive to his
install and access it right away, read/write.. reformat, no probs it
was a perfect drive on any machine except mine..

I had this problem before a long time ago on another machine and the
hard drive would work on any machine except the one that pooched the
format (power bump rebooted the machine during the format)..

Do you remember that in Win98 you could reboot into Safe Mode and then
go into Device Manager and actually see a list of every device the
system had ever laid eyes on? If you uninstalled those non-existant
devices and then rebooted your system would perform a weeeee tad
better.. (power tweaks stuff) Well no dice in this case..

I did do the cmos reset and nope.. no dice.. it's in the registry I'm
thinking..

Still working it though.. will find a solution.. I have dood coming
today with the new drive to test that.. =)

On Fri, 01 Oct 2004 00:13:05 GMT, "peter" wrote:

Has your friend tried reformatting the drive??
Have you tried.(this is a real pain) clearing your CMOS?? unplug ..remove
battery..wait 2 minutes...reinsert battery...replug...restart.
I suggest you write your settings down before you do this......easier to get
back to normal.
Your right its a real dilema I cant even try to duplicate this on my test
system.
peter
"Seaking" wrote in message
news
Hi, the system's PSU is a 450W Enermax and it did run the HDD properly
before it pooched the format.. I ever went as far as disconnecting the
other storage HDD's 'just in case' it was a wattage problem but no,
that's not it..

At the first go I did have the SATA drivers in and the system saw the
drive, the OS saw the drive and went as far as formatting it... and
pooched the format.. and no nothing.. by 'pooching' the format I mean
that it stalled at 59% complete and stayed there for quite a few
hours.. nothing I could do but reboot the system and then all fell
apart. Still trying to book time with my buddy for him to bring
another SATA drive to test in mine while mine works 100% in his
system..

I took care of the shyte sound drivers by deleting the latest drivers
and installing the originaly from the MoBo installation CD.. Go
figure, the old ones worked 100% better than the newest one.. HA!

I'll let you know about the HDD issue though..

Thanks!

On Wed, 29 Sep 2004 00:32:05 GMT, "peter" wrote:

When I hear of it accessing and stopping and accessing and stopping the
first
thing I think of is power problems.
With that many HD/CD/DVD drives on your system I hope you have an excellent
and
I mean excellent not just good power supply that delivers at least 200w on
the
+3.3 and +5.0 voltage lines.One Hard Drive can take anywhere from 5 to 15
W,a
CD
and a DVD up to 25w each.Thats just drives..then there is RAM...the
CPU...video
Card...NIC...etc etc.
I am assuming that you did load the SATA drivers...the BIOS will recognize
without drivers but not the OS
peter

"Seaking" wrote in message
m...
On Sun, 26 Sep 2004 19:30:38 GMT, "peter" wrote:


case I dont like some part of the new ones.
Tell me about the SATA problem
willing to help

Lock and load as this SATA prob is a bit involved so let me start with
the basics.. it's a bit of a story..

I bought a Samsung SATA HDD (120G) to mount in my system as a storage
drive. I got it installed and seen by the system, up to the point of
being formatted and the system locked up.. after that, anytime I boot
up with the drive installed I go through endless error loops where the
system access the drive.. silent.. access.. silent.. access... and
on.. and on...

System is the mobo Rev2 and at the time, was BIOS 1003 now it's 1008,
and now all the drivers are updated with the latest which didn't help.
I have 1 HDD on each mobo Pri and the DVD burner on IDE2. On the
Promise ATA100 card in a PCI slot I have two other HDD storage drives,
and on a promise ATA66 I have a DVD reader.. (this is all a throw back
from old days where best action comes from single units per channel,
right or wrong, this is how I normaly do it). The SATA drive was
installed and the jumper moved to ENABLE and while it worked OK the
first time, it doesn't on this mobo now.

The hard drive was taken to a pal's house, installed in his system as
a storage drive and it works great! But install it in mine and it's
all duff..

For all intended purposes, it would be as if this mobo remembers this
particular HDD as being duff and won't talk to it and goes into
conniptions. I have another drive coming in to test to see if the
system will see it or not.

How does this sound so far? You can email me if you wish at seaking at
eastlink.ca

Thanks in advance!