joeyaage

Everything works perfectly now with Linux.

Okay. I have a working build batch file. Some of the 'if' statements don't work on error checking the compilation but if the file makes okay then it works. Size checking on .abs files does not work either. These are 'wine cmd' limitations. I had to use the windows version of virtual jaguar with 'wine' from the build batch file to run the project. I could not get the Linux version to run the project (!?!). Now I have a new idea. A version of 'cmd.exe' from windows could be used with wine to run the batch file. This would then run the build batch file without any errors. I might try this. So I just need to put everything on the new PC so I get some adequate speed out of virtual jaguar. Btw. The windows version of virtual jaguar reports 'ANOMALY:REX error' or something similar when the screen goes white. I haven't looked into this much but perhaps it is something to do with the AMD processor I have.

I am still studying the BUILD.bat file. Got about half way through writing a shell script version and discovered that issuing a 'wine cmd /c "buildtool"' command within the script means that you can't check error codes from the command. I suppose I could 'grep' the build.log file. Decided to go back to editing the BUILD.bat file. wine seems to handle the file a bit differently to DOS. I put some quotes around the header 'ECHO' statements because wine seems to parse the pipes and slashes as file descriptors and stuff. This stops all the file not found errors. Mostly the for loop construct needs to be looked at as it currently fails in 'wine cmd'. Thus the CURRENTPATH variable is not set and BUILDPATH is not made. These need setting to the correct values. For some reason the 'IF %PROJECTNAME% NEQ [] GOTO :dobuild' check before the usage info does not work either and so I had to change this. I can now make an .abs with the batch file but it bails out when checking the size of the .abs (for loop, again). I tried to run the .abs with virtual jaguar but no luck yet with it working (hmmm).

I have tried running the BUILD.bat file with 'wineconsole' and 'wine cmd' and get the same results. About 12 or 13 file not found errors and 2 syntax errors followed by the usage information. If you pass build.bat a project file as a parameter it does not find the project file and so does not go to the building part of the batch file. It does echo a list of the projects in the directory though after the usage information. So I need to either edit the batch file or convert it to a shell script (preferable). If I do this I can use the Linux version of virtual jaguar as well. I will test that the windows raptor binaries all work with wine first by hand building a project. Any ideas why my windows version of virtual jaguar does not work on my new PC. Works fine on my XP system (slow) and on my windows 7 laptop (slow) but my new windows 8.1 PC, runs for about 30 seconds before the virtual jaguar screen turns white. I can hear sound working in the background so it has not crashed.

So far so good. Using my old debian wheezy installation for tests. Have compiled virtual jaguar for Linux (works but is slow on a 3GHz pentium 4). Have installed wine and run the RaptorBASIC+ install.exe. Install works okay. All the files are in the right place. Running the wine cmd and checking the PATH environment variable shows the correct settings for windows. I can run the build.bat script but there are multiple file not found errors. So I think the PATH variable needs looking at, alternatively convert the batch file to a bash shell script and use the Linux version of virtual jaguar.

Hello. There is a Basic to C converter for Linux based on BCX. Would it be feasible to set up a Linux RaptorBasic+ development environment? This idea stems from the fact I have a new PC and can't seem to get Virtual Jaguar working properly on my windows 8.1 installation (runs for about 30 seconds and then the screen goes white). I have yet to try virtual jaguar on my debian Linux install but I have faith in it working.

Got a new PC. Gigabyte motherboard with AMD A8-6600K Quad core processor and AMD Radeon R7 200 Graphics card. Running Windows 8.1. Running Virtual Jaguar works for about 30 seconds and goes to a white screen. I found a similar thread on SDLemu forum which suggested it may be an OpenGL issue. I have installed the latest AMD graphics driver. I have virtual jaguar running fine on my 2GHz windows 7 laptop but is slow. I have started with raptor basic and dearly want vj working on the new PC for speed reasons and development with raptorBASIC+.

How is Super gridrunner coming along? How about a port of the Falcon game llama zap. Uses the jag pad for control and the dsp chip for mod tune playback. Maybe the rez is too high for the jag. Would be a bit of a challenge. Would be amazing to play on the jag, though.