Editing Jobs in CapturePerfect

[gensyscon]

We have a DR-2580c Scanner with Full Size Flatbed.  Firmware v2.07.  Running CapturePerfect v3.0.8209.309.  Currently running 64-bit Windows 7.  The scanner has been a mainstay of our operation for 7 years.  It's a superb system.  

1)  When editing jobs, is there a way to make changes to a job and save it under another name ("save as") to create two similar jobs?  The only way we know to do this now is to create a new job and program it from scratch, which is inefficient and error-prone. 

 2)  Is it advisable (or even possible) for us to upgrade from CP v3.0 to v3.1?  If so, how would we do this?

Thank you.

Moderator Note:  Edited post to remove serial number per forum guidelines.

[Patrice]

Hi gensyscon.

CapturePerfect 3.0 does not have an option to duplicate the current job you're working on, so you will have to create a new job.

As CapturePerfect 3.1 is only available with the purchase of a new scanner, you may want to consider performing an Internet search for software with scanning and editing capabilities, or I would recommend giving us a call at 1-800-OK-CANON (1-800-652-2666), Monday - Friday, 8:00 A.M. - 12:00 P.M., to discuss what options are available.

[bosevii501]

I understand you can't "copy" or duplicate a job as a new job, but, can you point me to where CapturePerfect is storing the jobs so that I can backup that file(s) in the event that we re-image the machine I don't want the user to lose all their job settings.

Thanks,

Brad

[bosevii501]

I posted too soon. I figured out the path and files.

On a Windows 7 machine with roaming profiles it is storing the scanner & job settings at:

C:\Users\[UserName]\AppData\Roaming\Canon Electronics\Cappe3\

Where [UserName] is your logged in UserName.

There is an .INI file and then a bunch of .dat files that seem to be the scanner settings and the job settings. For what it is worth when I called 1-800-OK-CANON (1-800-652-2666), the guy told me there was no ini file and that CapturePerfect stored the settings inside the compiled .exe. I wish i was making this up but that is honestly what he told me...