Just searched the forum for a thread of the Vectrex emulator ParaJVE and didn't find much. So I'm starting a new one...
ParaJVE is an excellent Vectrex emulator programmed by Parabellum. ParaJVE can be downloaded via www.vectrex.fr . ParaJVE is programmed in Java and will run on Windows systems. Not 100% sure but it's supposed to run on MacOS, too.
Also tested with the same configuration (same Windows build and exactly same Java Version) and it works. I think I used this emulator last time with Windows XP. I cannot remember how perfect the emulation was on XP, but now on Windows 10 I'm not sure, if it has a very little bit timing issues, but it looks not bad and the games are playable. But I also didn't test 1 hour now, just started some ROMs without doing the optimal settings.
I remember that I used this emulator very often in the past for demos (demoscene) or other binary files, before I got a Vecflash and a Mateos Cart... With these cartridges, there is really no need anymore for this great emulator, just maybe for testing files that are not running on original hardware. And sure, it is a very great emulator for people with no original hardware, they will love playing the games on the emulator.
Yesterday, parabellum (aka Franck Ch.) replied to me. With Franck's help I could track down the problem very quickly: A while back I had edited the configuration file and added Vec-Man. My entry was wrong which caused ParaJVE to no longer start. I simply replaced my erroneous configuration file with my back-up configuration file and voila: ParaJVE starts and works like a charm, again.
- Make a back-up of the configuration file of ParaJVE before your edit it.
- Be aware that ParaJVE may no longer start-up if there are invalid entries in the configuration file. The dump/output (see below) helps you to track down problems even within your configuration file.
Below please find some steps that help to track down problems when running ParaJVE.
ParaJVE: Tracking down start-up problems If you should experience problems when starting ParaJVE you can try out the following steps:
Open a DOS console
Start ParaJVE with the "ParaJVE_console.exe -debug -noredirect" command (the parameters are not mandatory but help to gather more info).
ParaJVE will start and output its problem to the console. Either you try to interpret the output yourself or send the output to parabellum .
Note: Alternatively you could also start ParaJVE with the command "ParaJVE_console.exe -debug -noredirect 1>2>dump.log" to have the content of the console to be redirected automatically in the "dump.log" file.
ParaJVE: Tracking down freeze problems If you should experience freeze problem, i.e. ParaJVE freezes and no longer works, then perform the follwing steps:
Open a DOS console
Start ParaJVE with the command "ParaJVE_console.exe -debug -noredirect 1>2>dump.log" to have the content of the console to be redirected automatically in the "dump.log" file.
Once the freeze occurred, select back the DOS console, and hit CTRL+BREAK (or CTRL+PAUSE depending on your keyboard). This should dump the whole JVM state if it responds
Then send the contents of the dump.log file to parabellum for analysis.
Last Edit: Sept 20, 2019 11:12:26 GMT -5 by hcmffm