I have not made a satisfactory workaround to the SBC problem yet.
If one has the ability to modify RedPower then I highly suggest implementing the solution indicated previously.
I am curious if, but don't believe this should, break any existing FORTH or MS-BASIC.
You can find the project here:
http://bahproductions.com/RedC-9-21-2014.rar
./dist/ Precompiled binaries, config files, etc. Output destination for included code projects.
./RedC/ The RedC project files itself.
./rpc8e/ The 6502 C compiler source and redpower CRT
Just using the project:
1) Run the precompiled project ./dist/bin/RedC.exe
Setting up the development environment:
1) Run ./rpc8e/BUILD.bat and wait for it to finish- takes a while. You can check the readme.txt file here for some more information.
2) Open ./RedC/RedC.sln in Visual Studio 2010 or later. To make debugging work properly, go to the Debug tab in the project settings and set your working directory to C:\[wherever you unpacked the rar]\dist\bin\. Note that RedC.exe and the BUILD batch file are already set to output to this \dist\bin\ path.
This package includes everything up to and including the simulator breakpoints feature, but just prior to any work on the SBC problem.
Note any capitalized code comments are from the Scintilla.NET sample- my comments are generally all lowercase.
Please note that the "Build & Inject" feature (which puts your IMG data directly to a floppy disk in your inventory) is unfinished.
In MainForm.buildAndInjectToolStripMenuItem_Click() you will find hardcoded player name and FTB directories from testing purposes.
Please reply here if you want to discuss the state of any unfinished or planned features, the state of the CRT, or the SBC problem.
I would prefer to have any reasonably complex discussion via voice chat, eg. steam, skype or teamspeak.
If one has the ability to modify RedPower then I highly suggest implementing the solution indicated previously.
I am curious if, but don't believe this should, break any existing FORTH or MS-BASIC.
Here's the redpower CPU's SBC implementation:
int v = ((regA - val) + (flagC ? 1 : 0)) - 1;
flagC = (v & 0x100) == 0;
flagO = ((v ^ regA) & (v ^ -val) & 0x80) > 0;
regA = v & 0xff;
This would all work if the first line were rewritten to:
if(!flagC) val++;
int v = regA - val;
You can find the project here:
http://bahproductions.com/RedC-9-21-2014.rar
./dist/ Precompiled binaries, config files, etc. Output destination for included code projects.
./RedC/ The RedC project files itself.
./rpc8e/ The 6502 C compiler source and redpower CRT
Just using the project:
1) Run the precompiled project ./dist/bin/RedC.exe
Setting up the development environment:
1) Run ./rpc8e/BUILD.bat and wait for it to finish- takes a while. You can check the readme.txt file here for some more information.
2) Open ./RedC/RedC.sln in Visual Studio 2010 or later. To make debugging work properly, go to the Debug tab in the project settings and set your working directory to C:\[wherever you unpacked the rar]\dist\bin\. Note that RedC.exe and the BUILD batch file are already set to output to this \dist\bin\ path.
This package includes everything up to and including the simulator breakpoints feature, but just prior to any work on the SBC problem.
Note any capitalized code comments are from the Scintilla.NET sample- my comments are generally all lowercase.
Please note that the "Build & Inject" feature (which puts your IMG data directly to a floppy disk in your inventory) is unfinished.
In MainForm.buildAndInjectToolStripMenuItem_Click() you will find hardcoded player name and FTB directories from testing purposes.
Please reply here if you want to discuss the state of any unfinished or planned features, the state of the CRT, or the SBC problem.
I would prefer to have any reasonably complex discussion via voice chat, eg. steam, skype or teamspeak.