I recently installed the new SuperLab version on a new computer and re-activated my license. Now when I start SuperLab, I get the error message “failed to update user configuration file”. The error log says:
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
3:14:46 PM: can’t remove file ‘C:\Program Files\SuperLab 4.0\SuperLab.ini’ (error 5: access is denied.)
3:14:46 PM: Failed to update user configuration file.
Now SuperLab is somewhat unstable, and crashes frequently. Any suggestions?
This is a known issue. It’s limited only to Vista. As far as we’re aware, SuperLab has not actually crashed and is running normally; this is just Vista misinterpreting SuperLab’s behavior. We’re looking into the issue, but don’t have a fix for you at the moment.
Because SuperLab crashes regularly while operating under Vista, I have to save my work very frequently. At first, after a fresh boot, everything goes well. After a certain number of programming steps have been made or the experiment has been run several times, SuperLab gets more unstable. After two crashes, I’ve learned that the computer must be restarted, because if I continue to re-open SuperLab after a crash, the experiment the crashes become more frequent, progressing to the point that the file I’m working on becomes corrupted, and I have to go to the backup. I guess I should have bought Windows XP with the new computer I bought to deal with the hyperthreading problem, as SuperLab wouldn’t run properly with my Pentium M processor, but I didn’t know that SuperLab is unstable with Vista when I bought the new computer. Now I’m living with the unstable SuperLab on Vista.
All it says is “SuperLab.exe is not responding?” Does this happen only while running an experiment? Does it happen when exiting an experiment? Does it happen when canceling? Does SuperLab ever provide an actual crash report? When the experiment is corrupted, did SuperLab crash while saving? We aren’t seeing this message with remotely the frequency that you are.
From the little bit of information you’ve given, your issue sounds like a hardware problem and not a software problem. Under no circumstances should a SuperLab crash require you to reboot Vista. Likewise, the fact that the issue gets worse the longer your machine is up also points to hardware. Have you tried using this computer for other tasks? Do you have crash problems in other programs?
Once Windows says that SuperLab is no longer responding, I have the choice of letting Windows solve the problem (it doesn’t), or shut down SuperLab. SuperLab generates no log. The computer is new, and basically has little more on in than SuperLab, other than FireFox. No other crashes have occurred on the system. When SuperLab boots, as I mentioned in a previous post, it tells me that I must either delete or save preference files, and I’ve been deleting them.
I have learned that if I leave a program open and the Windows screensaver comes on, SuperLab crashes. This may be what is causing at least some of these problems.
When SuperLab is open. The cursor goes into wait mode, and when any action is taken the Windows message (SuperLab.exe is not responding) comes up.
I’m using 4.0.3c.
I’ve reinstalled the program, and cleaned out the files that had to be removed manually.
When I first started using this computer, I attempted to install with the CD that originally came when I purchased SuperLab. When I learned of the new update, I installed it over already installed one. Perhaps this caused problems.
It does this as soon as you launch SuperLab? Wow. That’s definitely not supposed to happen. You shouldn’t have any problems installing over top of an existing installation. Likewise, you shouldn’t have to manually remove any files in order to reinstall. This sounds to me like it may be a corrupt install, which is a bad sign on its own.