Search the Community
Showing results for tags 'XP'.
The search index is currently processing. Current results may not be complete.
I have been using Retrospect Prof 7.6.111 on a Dell XPS Gen4 with WinXP Pro sp3 (32bit) to backup up to USB Seagate 500MB and WD 160 MB drives for years without problems except for a few compare errors. Recently I acquired WD Elements 4 TB drive and could not successfully complete a backup without File "xxx": can't read, error -1010 (API request bad); Trouble reading files, error -1010 (API request bad) errors during copy. I tried a borrowed WD 3TB on only 9 GB backup and it copied but got the error when comparing. Tried re-formatting with 512k sectors and then 2 partitions of 1.9 and 1.8 TB got same error so I'm guessing it is not a problem with XP and the drive being over 2GBs.. Drive seems to work fine when manually copying files and only seems to have a problem with Retrospect. Even having the new WD drive plugged in and backing up to the old Seagate drive causes the error in Retrospect. Both are drives connected to built-in USB2 ports, I was planning in installing a USB 3.0 host card after testing the new drive. Has anyone else came across the -1010 error? WD tech sup said it does not sound like a Windows error but rather a Retrospect error. Thanks.
Hello All ! Here's the story... that kept me awake for around 2 days... I have an XP SP 3 VM running under VMWare Fusion 6.0.2 on my Mac OS 10.9.2 Mac Pro (2008), and backed up by a Retrospect 7.7 SBS server. I've been using my VM daily for years, but it was giving signs of malfunctionning (freezes with a black screen after login in). I decided to rebuild it from scratch, by creating a new one with the same characteristics under VMWare Fusion, and then doing a bare metal restoration with the Retrospect 7.7 Rescue CD and my latest backup. It didn't work as intended. I was able to boot the VM from the Rescue CD iso, and got the first dialogs for the restoration. The problem was that the Emergency Recovery Wizard was unable to configure correctly the (virtual) network card: it kept assigning a localhost address (127.0.0.1) which is pretty much useless when you want to connect the Retro Client to the Server in order to restore everything. In fact, the option "Adjust drivers to support new hardware" shown on the documentation page http://www.retrospect.com/en/documentation/user_guide/win/disaster_recovery and that I linked here was missing: http://download.retrospect.com/docs/win/v8.0/user_guide/img/en/addendum_rug-17.jpg I remember doing a bare-metal recovery on a physical PC some years ago using the backup from my server over the network, and it had worked fine. Why isn't this working today anymore ? Is it because I was trying to do it on a VM ? Why is that "Adjust drivers..." option missing from the wizard ? I ended up recreating my VM anyway by first installing Win XP from the CD, then the Retrospect 7.7 client and then doing a full restore on it. After some tweaking around (notably because for some unknown reason the MBR of my VM was messed up, and I had to restore it with the CD console), I finally was able to use it normally. Thanks for your ideas, Paul-Henri