Drive Image 2002 problem

[mubs]

I booted off DOS floppies, imaged the system partition (disk 0) on to disk 1. Now I reboot into Windows, and I can't do much with the image files. I need to move them to a machine that has a DVD burner, but I can't.

Windows (XP, but I vaguely remember having this problem on W2k as well; don't remember how I solved it then) will let me delete the files. But it won't let me rename them, or copy/move them, even to another partition on the same friggin system (what kind of crap is this?). An window pops up:

Error copying file or folder
Cannot copy file-name-is-displayed-here: Access is denied.
Make sure the disk is not full or write protected and that the file is not currently in use.

These files were created from DOS floppies; I verified with Sysinternals ProcessExplorer that no process has them open. There's massive amounts of disk space ( 2 new 250GB drives). The filesname extensions are somthing.PQI and somthing.002 (2GB filesize limitation, so multiple files were created).

I know some folks here have used / still use DI. Help, please?

 

[mubs]

Holy Capola! I booted into safe mode and tried copying/renaming the files. Same error message!

In the meantime, I found Terabyte Unlimited. Among other products, they have a Dos-based (what I want) imaging program that is simply blindingly fast. It's horribly simple to use, can write to and read from USB and 1394 devices, and is $19! They have a link to 3rd party freeware, one of which is:

DOS UDMA Driver

If the BIOS interface to your hard drive(s) does not support UDMA IO then you may want to consider using this driver to gain a significant amount of IO speed. The results are dramatic. Many of the BIOSes setup UDMA then turn around and use PIO instead. Worse yet are the newer BIOSes that use PIO0 instead of PIO4.

They're probably using it, from the speed of their product. It created the image directly on my 1394 HDD (so I can take it to the system with the burner), and verified the image (byte for byte) without a hiccup in no time flat. There is a God!

ps. I'm assuming there won't be any problems if I have to restore.

 

[LOST6200]

weird. I have used DI 20002 for years and trhe is no problem when copying and or moving terabytes of the PQI friles from drive to drive or partition to partio in Windows. some other software must not like yuor files,

 

[mubs]

Weird indeed. This system has a virgin Win XP Pro SP2 install with all the updates, MS Office 2003 up to date, Adobe Premiere Elements, Adobe Photoshop Elements, Sony Vegas DVD Movie Studio and a few utilities. The idea was to first install all the sw that requires activation, image that to use as a baseline, then continue installing the other apps.

Like I said earlier, I remember having this same issue on my laptop (W2k) as well. For the life of me I can't remember how I got around the problem then. My age is really catching up on me. When I was younger, if I couldn't solve a problem or couldn't remember something, I'd get really hot under the collar. Now I just plain don't care.

BTW, I'm very pleased with Image for DOS so far.

 

[Sol]

I'd have to guess that the original problem was that you were imaging onto an NTFS partition (Assuming of course that you actually were) and the dos NTFS driver wrote the files in a way that windows didn't like. NTFS doesn't seem to me to be the most well defined and stable file system in the universe. I've seen WindowsXP machines choke on NTFS partitions from other WindowsXP machines (ended up with a whole lot of scrambled mpegs, aparently due to fragmentation. It was possibly the coolest file corruption ever although it helped that none of the files were critical and that the original machine could still read them) so a third party, dos based ntfs driver having trouble wouldn't surprise me in the slightest...
Of course if you were using a FAT file system on the second disk then that makes no sense... But then neither does a FAT file system on a 250GB drive so it all evens out...

 

[mubs]

I think you've hit the nail on the head, Sol. DI 2002 is old enough now, and while this problem didn't exist in the pre-SP3 days of W2k, it seems to now, after MS updated NTFS to, what's it now, version 5?

Yeah, the destination for the image files was NTFS. Too bad. I may just have to stop using DI. Oh well, the Terabyte product seems like a good replacement. I'll try that one writing to an NTFS partition tomorrow and post back here. Too late now, going to bed.

Looking at the time of my (this) post, seems like the System clock is off? Even the one-hour Daylight Saving Time doesn't account for it being 2 hours behind PDST.

 

[mubs]

Confirmed. When I have DI create the images to a FAT32 partition, no problems copying it. Thanks Sol!

 

[Bozo]

Right click on the folder that has the DI files in them. Select 'Sharing and Security'. Go to the security tab. Select the full control check box for the proper user. Then click the 'Advanced' button. Check the box that says to make all the files under that folder the same as far as sharing and security goes (i can't remember off the top of my head)

XP sees files that were added by a different application while it was down as rogue files and locks them down as a security risk.

I hope I am making sense.
I run into this all the time as Drive Image is my backup software of choice.

Bozo :mrgrn:

 

[mubs]

Thanks for the tip, Bozo. It's too late now to check your suggestions, but I'll save your suggestions and try them if I run into this in the future.

 

[mubs]

Continuing the saga. I screwed up and created image files on an NTFS partition again on another system (had to; no space elsewhere). This was XP Home, so Bozo's instructions couldn't be used; there was no 'Security' or 'Advanced' tab/buttons. After googling a bit I learned the following:

For XP Home you'll need to boot into safe mode and log on the administrator account.

I was getting impatient, so I just killed the files and re-imaged with Image for Dos (see earlier posts of mine). Not only is it blazing fast, XP doesn't have any problems with files that IfD creates on NTFS partitions when it runs off a DOS boot floppy.