Printable View
What a schedule! Or maybe it isn't that but whatever you do, I hope it is rewarding and you enjoy.
Those are my sentiments exactly--everybody is learning in these threads. Well, I am at least and hope others are. Haven't done anything since last night yet but I will and let this be known here; maybe tonight, I hope.
Something is wrong and I am really getting uptight about this inability to copy my hard drive using DI. I suppose I may still--tho don't see how--be doing something wrong.
I used the proper settings before burning, ran a scandisk, closed all apps. and turned off Nortons AV. The burn and verifying went smoothly UNTIL disk #4 got the error #1805 popped up. The meaning of this error is "#1805 Err write failed
Error encountered while writing image to file. This error usually occurs when
Drive Image runs out of space in the partition to which it is writing an image file."
It was disk #4 where I was stopped in the burn process the last time I tried to back up the HDD.
End of another frustrating try!!
Make new DI boot floppies and see what happens. I am using the boot floppies and not trying it from windows.
I wonder if the darn install or something attached to it is bad. :confused:
I haven't ever used the boot floppies that I first made. I understand you want me to make 2 new floppies and boot from them and then try the burn from DOS instead of windows.
I checked properties in these 3 completely burned disks 1 thru 3 and each of them appears to be ok. The 4th disk appears to be empty and the burn was not done even tho the disk was in the burner for about 25 minutes.
I then checked the 5 disks I burned on the 27th(the 4th disk of which gave me that possible corrupt error--the disk is full) andall 5 disks appear to be ok.
I am also tempted to clean my HDD and try to restore it using these 5 disks and see if they are in fact a full burn. I would have some work to do if the restore was not successful. Am not too sure I want to find out that badly ;) Guess I am gonna have to try it sooner or later; otherwise I'll never know.
I could try another burn using Backup Now Deluxe before I get my refund from NTI. What say you?
Sounds like a good plan.
I perfer using the boot floppies as that is what I am familiar with.
And that seems to have less overhead problems to me. IE, no problems from Windows .
Have had to use a alt backup program to get backup a few times. After things just disappeared for some reason.
Just thought I'd jump back in with an idea. It might be just a problem with heat building up in the cdrw drive from the long period of burning and testing. Try pausing 5 to 10 minutes before inserting each cd to allow things to cool down and see if that helps.
Gerdog
No that makes sense. Never had to fight that problem myself.
Can't address the heat theory but anything is possible--they say!!
Well, I got to disk #5 today and then got an error #1810--image could not be opened message.(Guess verifying was taking place at the time.) At least my error numbers are getting higher :D Am gonna just put aside the DI for a while, I think. Can't figure what is happening and that last burn took nearly 3 hours!! Entirely too long, I think but then again, what do I know:p I wonder if that first time I ran DI and chose to let it make a partition on my only drive may have caused any of this.
Now I have begun to chicken out and not wipe my HDD in order to try an install of the backup.
BTW Train, I did not use the floppies to run the burn in DOS this last time. I stayed with windows only because that appears to be the method PQ wants us to use. Maybe I'll try that tomorrow.
I did try the Backup Now Deluxe again. The first 5 disks burned just perfectly but disk 6 had an error. This disk was writing just 2% of the HDD, according to the progress window. 2% away from total burn--may as well have been 98% :rolleyes:
I ain't letting this thing whip me--------yet :p
Have you run a thorough scandisk on the hard drive recently to make sure there are no errors? I was thinking that I always scandisk and defrag right before making backups, and I don't have any problems. I was also wondering what brand and speed of cdrs you are using. I bought a second hard drive shortly after getting Drive Image, and only backed up to cds once because it's so much quicker to backup to and restore from hard drive. I can imagine your frustration after getting it so close to finishing.
Gerdog:
Yep, I try--and do--to remember to run scandisk and then defrag and turn off all apps. running(I use EndItAll) before trying a burn.
Earlier today I found scandisk to take an extraordinarily long time to finish it's run but I don't recall if there were any errors. Generally, this runs very quickly on my PC and this time I almost thought I had mistakenly run in "Thorough" but I didn't. Defrag, using the ME app. took a good deal longer also. Figured these two steps took longer because of that "partition" that was put on my HDD. Don't know that and probably never will know the answer to the longer run times.
I have been using Imation 700MB/80 Min without a hitch. I tried some untried CDs today with the BackUp Now Deluxe software but the first 5 were error free and the 6th one had a "gotcha". These blank CDs are Digital Media CD-R 650MB/74 Min. In both cases I burned at 600MB media and high compression. Everything appeared to have been done by the book and your instructions/suggestions.
I will add though, I am using a new I/O Magicwriter 24X10X40 IDE AND I never installed the software that came with it--CD-Maker2000. I just checked to be sure and the burner works with both types of blank CDs.
Scandisk taking a long time. Do you have it set to prompt you when it finds a error?
Also, how many passes is it set to do?
Start, run[type in] scandisk.ini , hit OK
scroll down to this line;
NumPasses = 1 ; 1 through 65,535 (anything over 10 is slow)
Well, I set mine to ;
NumPasses = 5 ; 1 through 65,535 (anything over 10 is slow)
The go to File in the menu and select save.
Also, after you defrag next time , defrag a 2nd time see how long it takes. Should be faster and see it moves a bunch of stuff again. Use the graphic mode to watch it.
Just wanted you folks to know, I paid the ransom about 6:30 tonight--local--and now I see you all have escaped :D Good for me.
I just let scandisk do it's thing; including fixing errors and very seldom does it take more than maybe 3-4 minutes to run. Defrag may take a couple of minutes longer. You must have read my inquiring mind because I did run both scandisk and defrag after their long "runs" and both were back to about normal.
I just ran scandisk--took almost 2 minutes with no errors and then defrag took almost 4 minutes.
A few weeks ago I was thinking of putting a second hard drive in my PC and was also going to keep my old slower burner as a slave to the new burner. I found that I didn't have the correct cables to do either. Well, the cable for my already installed HDD had a 3 connector on it but I wasn't ready to install the HDD and I was ready to install the new burner. The weather was sorta threatening and I didn't want to risk going out soooo I just changed the cables. Now my question is, is it possible that this could be contributing to my burning difficulties?? I never changed the cables back to their old positions on the 2 drives and I never re-installed the old burner nor the 2nd HDD. May as well change the cable back cause I have no need for them to be switched. I just thought of this and wanted you to know. BTW, the cables looked pretty much the same and so I don't know if they are 40 wire or 80 wire cables and whether much heat is generated by either.
ATA 33 ribbons [40 wire] just limit hdds to that speed is all. For most folks, they would never notice the difference. But if your master slave configuration is wrong, that needs to be fixed.
Nope. Both drives are set to master.