New Seagate ST3802110A hard disk and Found new Hardware in win2k s

[Guest]

Made an image of a windows 2000 Pro SP3 on a new Seagate 80GB drive,
ST3802110A. Everything comes up and works from the new drive, however, I
keep getting a Found New Hardware wizard after every boot (this machine has
to boot often) and it prompts me to install drivers for the new seagate disk.
On Seagate's site it says that Windows doesn't need drivers for the Seagate
disks (internal disk). Contacted Seagate support and they think it might be
the system is set to roll back driver upon rebooting, and that I should
contact MS support. Has anyone else seen this before?

 

[Gary Chanson]

Made an image of a windows 2000 Pro SP3 on a new Seagate 80GB drive,
ST3802110A. Everything comes up and works from the new drive, however, I
keep getting a Found New Hardware wizard after every boot (this machine
has
to boot often) and it prompts me to install drivers for the new seagate
disk.
On Seagate's site it says that Windows doesn't need drivers for the
Seagate
disks (internal disk). Contacted Seagate support and they think it might
be
the system is set to roll back driver upon rebooting, and that I should
contact MS support. Has anyone else seen this before?

How did you create the image?

Does the hardware wizard install the proper driver or does it ask for
it?

When the machine reboots, is it a normal shutdown?

 

[Guest]

How did you create the image?

I used an old Software, PowerQuest Image 2002, and did a disk to disk copy.
It runs from 2 floppy disks. This software is not recommended because it
rendered the original disk unusable by changing the length of the partition
table on the original older Maxtor disk. Got this when I wanted to start the
disk to disk copy and it wouldn't let me do this if I didn't say yes (the
length numbers are not the same as what I got prompted for):

The program has detected an error 110 on partition starting at sector
8193150 on disk 1. The length of the partition in partition table is
incorrect. The CHS length is 8225280 and LBA length is 72099720. The
program has determined that the length can be changed to the correct
value of 72099720. Would you like the program to fix this error?

After, the original disk now comes up with "non system disk error". Luckily
the new disk, seagate, comes up with everything intact, besides this "Found
new hardware wizard"...

Does the hardware wizard install the proper driver or does it ask for
it?

It asks for it, and when I do a search on the computer for it, it cannot
find any. And since you don't get any drivers shipped with a seagate disk, I
can't add any. Everything works on the machine after I hit cancel, but the
prompt comes back every time after a boot. Because there are non-technical
people using this at night, and it is a critical pice in a production line,
we don't want them to se this prompt and start doing anything with it.

When the machine reboots, is it a normal shutdown?
Not always. There is an old buggy program that somestimes freezes the
machine. The machine is built into a suncell production line machine, but it
is old. I am trying to convince the customer to upgrade the hardware, and for
the love of god, get a server in there with RAID. But that won't happen in
the near future.

 

[Gary Chanson]

How did you create the image?

I used an old Software, PowerQuest Image 2002, and did a disk to disk
copy.
It runs from 2 floppy disks. This software is not recommended because it
rendered the original disk unusable by changing the length of the
partition
table on the original older Maxtor disk. Got this when I wanted to start
the
disk to disk copy and it wouldn't let me do this if I didn't say yes (the
length numbers are not the same as what I got prompted for):

The program has detected an error 110 on partition starting at sector
8193150 on disk 1. The length of the partition in partition table is
incorrect. The CHS length is 8225280 and LBA length is 72099720. The
program has determined that the length can be changed to the correct
value of 72099720. Would you like the program to fix this error?

After, the original disk now comes up with "non system disk error".
Luckily
the new disk, seagate, comes up with everything intact, besides this
"Found
new hardware wizard"...

Not good! If you want to fix the old drive, there are tools which can
probably rebuild the partition table for you.

Does the hardware wizard install the proper driver or does it ask for
it?

It asks for it, and when I do a search on the computer for it, it cannot
find any. And since you don't get any drivers shipped with a seagate disk,
I
can't add any. Everything works on the machine after I hit cancel, but the
prompt comes back every time after a boot. Because there are non-technical
people using this at night, and it is a critical pice in a production
line,
we don't want them to se this prompt and start doing anything with it.

It sounds like something got trashed, maybe a .INF file or a driver
file. It should identify the drive and automatically install a standard
driver without ant user intervention.

I can suggest two ways of dealing with it. If everything seems to work
properly as is, let the hardware wizard disable the device instead of
cancelling so that it will stop bothering you. One thing you should check
is read/write speed.

The other approach is to do a repair install from the Windows setup CD.
Note that you may need to do this from a setup disk which includes service
packs.

Which reminds me that I was going to ask why the machine doesn't have
SP4 installed. There's even a small chance that installing SP4 would fix
your problem.

When the machine reboots, is it a normal shutdown?
Not always. There is an old buggy program that somestimes freezes the
machine. The machine is built into a suncell production line machine, but
it
is old. I am trying to convince the customer to upgrade the hardware, and
for
the love of god, get a server in there with RAID. But that won't happen in
the near future.

I don't think this is relevant although it may be a concern of its own.
You didn't say whether the volumes on this drive are formatted as NTFS or
FAT32. FAT32 doesn't handle repeated crashes very well.