Drive Snap: Drive Snapshot Frontend

we could speculate possibles but who knows when the errors came about. i don't think so. i wonder if you mean disconecting while pc on, not necessarily it look like not so important files that were damaged anyways.

 

@rrrh1

yes the bad command. i will send you an update. anyways your problem help me solve a bigger issue.

 

No .i disconnected with pc off, it is no problem , xp is running fine
Lin

 

@linp i would take a new image and delete the old if everything is fine as you say.

 

Good idea ,i'll do that
Lin

 

rrrh1

markymoo

markymoo

Thanks !!

rrrh1 (arch 1)

 

After more modifications and testing with 2 drives the Auto Restore now works on.

NTFS and NTFS
FAT32 and FAT32
NTFS and FAT32
FAT32 and NTFS

No matter what the drive letters are.

Basically it works good

 

rrrh1

in the end the problem was the ISO was being built too fast and a file got missed. we solved it. thanks for your participation.

 

Is the revised corrected download back at the first post?

Thanks for a lot of attention given this DS frontend.

EASTER

 

What is the most up to date version ?

Can it be downloaded from your site yet ?

rrrh1 (arch 1)

 

no not yet. making some finer adjustments so it works fully universal. unless you have problem the version up there already should be fine.

 

A few more ideas with Drive Snap...

Instead of making a automatic CD for each image. A automatic CD that works for all images but you can set in Drive Snap which image you want the restore CD to work for. A CD with a pop up menu in DOS that you can select your image to restore it and recovery from bootable USB stick.

 

Oh yeah!

 

If this would really be feasable ,i think you would have achieved the ultimate ,reliable backup solution !
Lin

 

I like that too. As you have to "press any key to boot from CD", a feature which I like, seeing a menu would be just a few more clicks.

I like "press any key to boot from CD" because it means you can leave your computer and when you return you will be looking at the desktop of your restored OS.

 

I have a problem with scheduled task , i get the message : "schedule failed"
this is in the log : "
"c.job" (Drive) 22-5-2008 15:00:00 ** ERROR **
Unable to start task.
The specific error is:
0x80070005: Access is denied.
Try using the Task page Browse button to locate the application."

Lin

 

@linp

Goto Start Menu/Run and type services.msc Ok and look for Task Scheduler. Is it started? and are you running from Administrator account?

 

Yes
Yes

 

@linp alot comes up on that error but possibly a hotfix needed if a certain security update is on.

http://support.microsoft.com/kb/904423

http://www.instant-registry-fixes.org/resolve-error-message-0x80070005-access-is-denied/

http://www.google.co.uk/search?hl=e...x80070005: Access is denied&btnG=Search&meta=

 

Update ,
i did some testing, nothing wrong with task scheduler ; here is what happens :
i make a schedule in Drive Snapshot , so this file is created : G:\Drive Snap\autobackup.bat
when i go to TSch the task won't run . i open properties , the "run" field is : G:\Drive Snap\autobackup.bat without semicolons
the "start in " field is : G:
i then use the "browse" button to go to the file ;the "run" field is now : "G:\Drive Snap\autobackup.bat" ,with semicolons ,still doesn't run.
Now i alter the "start in " field in: "G:\Drive Snap" the task runs ok now
Something to do with "start in" ?

Update 2
Problem found! placing Drive Snap and snapshot.exe in the root solves all problems
@Markymoo
in your third post you say : " The requirement is Drive Snapshot has to be in the same folder as Drive Snap "in my case this is not working ,not with scheduling anyway.

Thanks .i'll look into it later when i got more time.
Cheers .lin

 

@linp

Hello linp, Drive Snap and Drive Snapshot still need to be together no matter what. When you add a job to the Task Scheduler, there is a argument limitation of TS not being able to pass the 'Start in folder'. It assumes the same location as the Task Location. If the folder name has spaces then it fails. Drive Snap overcame this limitation but it seems it's not working correctly. Try calling the folder DriveSnap or Drive and add a new task just for now to confirm it works fine as that. I will fix. I included the Test Scheduled task so you know if the task will run correctly on the day. Thanks again for reporting the few bugs.

 

Calling the folder "Drivesnap" solved the problem.
Cheers ,Lin

 

@linp You can go back to having 'Drive Snap' with a space. Despite passing long folder names in quotations it still failed to pass folder names with spaces in TS but i fixed, it be in the next update.

 

Please increment the demand by 1: I'd like to have 120DPI available too. (Actually I run at 130DPI, but 120DPI would be better for me than the current implementation.)

Thanks,

Robert

 

I don't see a control for "Maintenance mode" -- is it in there somewhere?

If not, please consider putting it in (if possible). I would prefer to run DS-DS sometimes with Maintenance mode on, and sometimes with it off.

Robert