Q2004 - backup now fails on XP laptop

running Quicken 2004 Rel 5 - the backup function no longer works - it fails to the local drive. It fails with a couple of dialog boxes:

1 - Error occurred during last task - Please restart Quicken. - Click OK 2 - The instructon at xxx referenced memory at yyy, the memory could not be read. Click OK to terminate the program.

It just started happening - The file was Validated, and is ok... tried deleting the /Backup and re-creating a new /Backup sub-dir - no effect -

Reply to
Phil Schuman
Loading thread data ...

Reply to
Phil Schuman

ahhh - just re-discovered this problem - the laptop that works always has the DVD/CD drive in the modular bay, and the failing laptop always has 2 batteries in the bays, except when a CDrom drive is required for installing software.

Is there any fix for this ?????????????? Quicken 2004 must keep an internal list of drive letters and wants them to be online and avail or it barfs - What's it do with a USB thumbdrive letter ???

Reply to
Phil Schuman

It sounds to me more like Quicken keeps track of the path used in your last backup. It tries to provide that path as the default in the backup dialog. If that path is not valid for some reason, Quicken may have a problem.

One thing you could try. Search for Quicken .ini files. I don't have Q2004 installed so I can't tell you for sure which file to look for; in Q2005 it is QUSER.INI in

D:\Documents and Settings\YOUR_USER_NAME\Application Data\Intuit\Quicken\Config

In that file is a list of the most recent backup files with full paths. Also there is a backup path entry that is separate. You could possibly delete the list and/or modify the "backup path" entry to point to a valid path.

Reply to
John Pollard

BTW - I just noticed that the "incrementing" backups that are created in my \quicken\backup\ sub-dir seem to be created just fine... not sure how often they are created ?? But the manual "BACKUP" command still fails on the exact same computer.

Reply to
Phil Schuman

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.