Really odd Drive Image 2002 problem.

[chas0039]

OK, I give up. I am using Powerquest Drive Image 2002 and I can't get two things to work. Both of these problems are when I use it in DOS mode. First, I cannot get it to do a disc to disc backup even though I resize the source partition to smaller than the destination. No matter what I do it tells me that the destination is too small. I have tried every possible method of doing this and it won't work. It does work when the source is smaller than the destination and there is no resizing, like when I copy a 60 gig. to an 80 gig. I also have a weird problem when I try to do an image backup. It works and all the files are there but none of them can be moved or opened. I get an access denied error message. This is really weird as it is only a problem when I go from disc 1 to disc 2. When I go the other way all is fine. Disc 1 is an SATA 200 and disc 2 is an EIDE 80. In all other respects, everything else is fine.

Any suggestions will be greatly appreciated.

[crazythunder]

it probably has something to do with the sata controller and the eide controller. do you have to install floppy disc with sata drivers before pq loads? i have version 7 and have to load the drivers before the app loads or it will not see either of my sata drives under xp. did you try to resize from windows or with a partition magic boot disk and then reboot with drive image ? maybe it needs to be resized first? without drive image doing it. are you using max compression?

[chas0039]

I have tried with a number of different options and none of them seem to make a difference. At this point I am ding everything from DOS discs as I cannot get Drive Image to work in the Windows system. It will not recognize the fake floppy reboot system when it reboots from DOS. My MB needs no different drivers as it has native support. In addition, I have been able to do these things before with this same hardware. The only thing that seems to be a constant is that whenever I try to image or copy the partion on my SATA drive it now gives me files that are not accessible. Any other files I image from other partitions work. The only thing I was able to do was disc backup from an old 200 SATA to a new 200 SATA. It is almost as though it fails when I go from SATA to EIDE but EIDE to SATA or SATA to SATA works. I do know I have been able to go from SATA to EIDE in the past with the same hardware. I am almost to the point where I am concluding that there is something wrong somewhere with the actual files on the SATA drive that make the image corrupt or innaccessible. It cannot be the drive itsself as it is brand new and the problem was there with the old SATA drive.

Thanks for the help. I went for 2002 because a number of reviewers found it was the only version they could make work with SATA.

[crazythunder]

on a couple of rare occasions, i've had kinda the same problem with a coupleof backup programs. turned out to be one of those bugs i just couldn't figure out. i ended up formatting, reinstalling windows, reinstalling backup app, and then restoring image. it still saved me alot of time not having to reinstall EVERYTHING. good luck.

[stiltman]

do you get the same errors if you use a scripting file?

second time I posted this

[chas0039]

If you mean by a scripting file, running it from within WIN XP and then letting a batch file run the program after rebooting, I cannot get that method to work even though I have uninstalled and reinstalled the software. It just reboots windows. This is what leads me to believe there is something fundamentally wrong with the Win install. Running from the DOS prompt should have limited any flaws in Windows but I guess not. If you mean something else, let me know.

[stiltman]

you can run the batch script file from a DOS prompt. That's what I meant

I don't have any of my script so I would have to google them just as you.