www.aiscl.co.uk

The previous version booted as MBR. The first time I tried this, the restored version was in the Boot Menu already. I had tried to use the Windows recovery system to set up the partitions, format the disks, and install a initial dummy Windows system. Then I booted the AIS recovery USB image, and tri...

Just tried it again, and had a slightly different error at the end.

This time the the log messages were:

Tracking: 33887
Location:
Exception: EAccessViolation: Access Violation at address 006C58D1 in module 'AISBackup.exe'. Read of address 00000000
Component: fAquariusBackup

I've been merrily backing up for months and years, and then my laptop boot drive died. Windows 10 64bit. No problem! I have backups! Installed a new clean SSD drive. Downloaded and booted the the AIS USB restore image from a few days ago, which reports itself as AISBackup version 5.4.0.494 in 'Help/...

Barry, I tested the restoration, and noticed a few anomalies: I ran another restoration, to a different partition (T: drive) In the 'AISBackup: Restore destination' dialog box I set the To Path to "T:\", left 'To Root' off, and had the three options 'delete files that did not exist', 'dele...

Barry - thanks for the quick reply. I built the recovery CD on my desktop, and then used it in my laptop to test - I've now retested, and confirmed that when I use it on the desktop the networking does function, so I'll go hunting down the ethernet drivers for the laptop and the other machines I hav...

OK, looks like I'm first! I'm testing the bare-metal restore capability for my Windows XP machines. My machines all back up to a NAS shared over the local LAN. I downloaded the Vista AIK, and made the AISBackup bootable Restore CD as per the instructions. When I booted from the Restore CD, the ether...

OK, Thanks Barry - easy to work around, happy to wait for the natural release cycle.

Thanks Barry - the original problem (bothways synchronisation not working when the source was a network share and the destination a local disk folder) is fixed, in that it now works (apart from the issue below) when the source is a network share. I'm still to confirm the problem I had with not seein...

Sorry Barry, have been on vacation in the intervening time. I'm still thinking myself of the best way to do this, but in the meantime I thought I'd be sneaky and get the result I am looking for by defining the subdirectory I want on the local machine as a network share, and then setting the new driv...

OK, that has now clarified an additional problem with the destination folders that are created. When the directory structure of the 'source' folder is reproduced in the 'destination' folder, the job is reproducing the source directory tree all the way up to the root, rather then just from the nomina...

...or presumably I could manually copy over the files to start with the two areas synchronised, and then alter the job to swap over the source and destinations. I'll try that shortly.
Very good to hear you could find and kill the problem so quickly!

I will send the job files and the verbose logfile. To be clear - when I run the synchronise job the second time, it correctly scans through the files and decides that it does not need to copy any files in either direction. It then pops up the dialog 'OK to delete the files and folders from the desti...

I'm having trouble with getting a synchronisation job working - its not specific to the latest build (281), but it also seems to failing in this build as well as previous builds. The intention is to keep a number of directories on a laptop synchronised with corresponding directories on a server - an...