Thanks for the write up!
Check the folders and they are indeed empty. How would a program be affected by a heating or cooling problem? We have 2 machines that talk to the Roland and the other one is working just fine. It's only this one that stopped after a couple of weeks of use...
guess i gotta call up the tech service again.
When computers overheat, it's much like a human. They start seeing things that aren't there and processing them incorrectly. Eventually what will happen is the computer will misinterpret an instruction such as "move the 4'x8' sign from the floor to the table" to "move the 4' x 8' sign from the floor the Laser Printer", as the laser printer wasn't supposed to be involved in the equation at all, a crash occurs. Heat issues are hard to diagnose in that they don't really have a trigger, it's when the processor gets too hot that it starts to act funky, which could be seconds after starting up, or hours into printing. Given that we're now in Summer, heating issues will pop up more frequently as rooms that may have been at 70 degrees fahrenheit may run up to 90, which can increase a computer's temperature substantially as well since most rely on air intake & exhaust for a lot of its cooling.
If your Versaworks is always dying on startup, then it is probably not a heat issue unless you experience similar issues with other applications and eventual OS crashes. If however it seems to be fine for 30 seconds, then crashes, then immediately crashes, then starts up works fine for an hour, then crashes, that is more indicative of a hardware issue, which is generally in order of most to least plausible: heat, RAM, or power supply.
If the hardware issue is ruled out and the program always crashes at the same point on startup, I would probably look at some form of compatibility setting, or some other companion software is missing. My first suggestion would be to try running Versaworks as an Administrator (right click the icon, choose Run As Admin). If that still fails, I know my versaworks has the Visual C runtime in its folder, so you might want to check your Versaworks folder for vcredist_x86.exe or something similar and try launching that. That file will launch an installer for the Visual C runtime (which is like a toolbox for many applications developed for Windows). The runtime should've probably been installed with Versaworks, but may have failed for some odd reason, which is now causing you issues, because the application is saying "pass me a hammer" and there is no toolbox and no hammer.
All else fails there's Roland tech support, hopefully either the tips here or Roland themselves will get you sorted though!
