Re: Imaging and verification

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks. Will use the CD boot version for dos to avoid any un-noted hardware
conflicts that may exist in XP.
The windows version says its for externals anyway.

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?
"JS" <@> wrote in message news:OMoRz02kJHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
Seagate Diagnostics:
http://www.seagate.com/www/en-us/support/downloads/seatools

--
JS
http://www.pagestart.com


"Lil' Dave" <spamyourself@xxxxxxxxx> wrote in message
news:OlKZHU2kJHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
Operating 2 SATA drives. They are identical 250GB Seagate SATA2 drives
operating in SATA1 configuration speed (motherboard limitation), and I'm
using the stepdown to SATA1 jumper on both SATA drives. Bios remaps
these to primary ide master/slave, nothing physically on primary ide
Also using a USB external drive. Each physical drive has a partition
that I direct as target for imaging, primarily the boot partion image as
source (on SATA1).

Imaging and verifcation are always successful on the USB drive.
Verification rarely fails on the 1st SATA drive (master). Verification
always fails on the 2nd SATA drive (slave). The imaging program also has
an asset to review the internal of the image file, verify, and export
that image file. I can export a previously verified image from SATA1 to
SATA2, but, that exported image fails verification afterwards. When I
source the image file from the USB drive and export to the SATA2 drive,
then verify, that verification is successful. The time to make the same
image is a-l-w-a-y-s less when targeted at the SATA2 drive.

I have to use the SATAs as mapped ide as to allow Millenium and 98SE to
run. They won't work on the SATA controller bios configuration.

What's going on regarding SATA2, and is there a fix?

--
Dave

CDOs are how we got here.
A modified version, new taxes in the future, is how Congress will get us
out?





.

Relevant Pages

  • Imaging and verification
    ... operating in SATA1 configuration speed, ... using the stepdown to SATA1 jumper on both SATA drives. ... Verification rarely fails on the 1st SATA drive. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Imaging and verification
    ... Seagate SATA hard drive. ... using the stepdown to SATA1 jumper on both SATA drives. ... Verification rarely fails on the 1st SATA drive. ... export that image file. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Imaging and verification
    ... operating in SATA1 configuration speed, ... using the stepdown to SATA1 jumper on both SATA drives. ... Verification rarely fails on the 1st SATA drive. ... Two exactly identical model of hard drives are never 100% ...
    (microsoft.public.windowsxp.hardware)
  • Re: Cant boot off of new SATA drive
    ... You boot from the install CD, select Recovery Console mode, and use the bootcfg utility to alter the boot.ini file. ... You will use Recovery Console mode for the first instance of Windows, the one on the IDE drive, because that is where you need to edit the boot.ini file. ... controller isn't configured to boot from any drives connected to it). ... Windows installed on both your IDE and SATA drives and switch between ...
    (microsoft.public.windowsxp.hardware)
  • Re: Help! Drive Image 2002 question
    ... >>> have restored my entire primary partition ... >>> to a Drive image file on a different partition. ... You cant restore TO an image file. ... > the logical drives, I used the tools found in Control Panel/ ...
    (comp.sys.ibm.pc.hardware.storage)