Page 1 of 1

Versaworks Dual RIP Problem

Posted: Fri Sep 29, 2017 9:06 am
by TLP

I have all of a sudden started to get the message "RIP procedure could not be executed due to insufficient memory" even on a basic 25mm square, anyone else had this and know how to cure it, have not been able to print anything at all, running on windows 10.



Re: Versaworks Dual RIP Problem

Posted: Fri Sep 29, 2017 10:08 am
by Bowber
I've not had that problem but I have just done the latest update and now I can't open any new or previous PDF files.
I've had memory message on a larger print file that the old Versaworks had no problem with though.

Basically Versaworks Dual and my 3 week old printer are just become a rather expensive ornament until they fix the pdf problem!


Re: Versaworks Dual RIP Problem

Posted: Mon Oct 02, 2017 11:24 am
by Kai Perry
We haven't seen any issue with the latest update, try downloading the offline updater from this website, then updating again.

If this doesn't resolve it try initialising the program using the VersaInit from the program list. (This will clear the RIP of files and all settings, remember to write down any settings used)

The insufficient memory error is resolved as per this version.

Re: Versaworks Dual RIP Problem

Posted: Fri Oct 06, 2017 5:04 am
by pgduc
my insufficient memory issue only came about after updating to 1.6.10 :(
others are finding the same?

Re: Versaworks Dual RIP Problem

Posted: Thu Oct 19, 2017 5:09 pm
by Kai Perry
I have tested it with files that didn't work previously and now the error does not show, try uninstalling VersaWorks, installing a fresh and then updating again.

Re: Versaworks Dual RIP Problem

Posted: Thu Nov 23, 2017 12:34 pm
by kylieh
We found a workaround, We did the uninstall, reinstall, different installer etc.

Workaround/what works for us for now.

Right Click and run as administrator
Setup a folder in Windows for you to drop your files into. (Queue A Properties > Input Folder, Action - Do Nothing)
Copy the PDF/EPS/ into the new folder that you referenced in the step above
Continue as normal.

Not elegant, but at least it works for now.