Last week I updated my trusty, previously stable Studio Edition to v2010.210 and ever since I've had sluggish performance, I/O errors when recalling jobs with layered PSD files (e.g. 89 MB size), "unable to load file ... aborted" messages, and crashes.
Running Win XP SP3, Intel Pentium 4 CPU 1.80 GHz, 1.25 GB RAM.
Wondering if I should revert to the previous version or -- ?

Thanks, Fred - much appreciated. I believe my last version was v2010.209 and I realize Mike hasn't been updating Studio for some time.

Strangely, the program is running ok today; I tried loading it "Safe Mode" (Shift-click-program-icon) and though I couldn't tell if it was indeed in Safe Mode, it printed the large layered PSD that seemed to be causing trouble yesterday. Intermittent problems are always the hardest to troubleshoot!

My QImage Save folder is showing some files with X's in their icons, which might explain something (see screen shot here: http://www.claireart.ca/QImage_Save_folder1.jpg).

Will check for viruses or malware, though I think those are unlikely culprits since I dedict this older PC to my Epson printing and almost never launch a browser from it, except to check for updates; don't do any email on it, either.

Might just have to do a lot of decluttering, deleting old files, free up more space and memory, and perhaps delete possibly corrupted qimage.ini, qimagepr.ini, icm.ini and sizes.ini files.

You are probably right ;-)

When I do so, I'll do a fresh install on my newer machine which is faster & has more memory.
Of course this will require editing the paths in all my saved jobs to match new drive names, something I've been avoiding! If I recall correctly, I can do this via Notepad.

One other "trick" to avoid doing this and an alternative to Fred's suggestion is to recall the Job as usual. You will get red hatched areas on the preview because the images were not found.
The Job data says what images were used (see screen shot below) so browse to that folder on the PC drive now in use and add the images to the Queue again then re-save the job.
You may find this quicker than editing a batch of .txt files and only do when required.
Terry