Level1:
GrfDrv is not being loaded automatically by VTIO.
If you merge GrfDrv into the OS9Boot file so it is in memory when using graphic calls system locks up.
Ok after using MAME debugger to see if I could trace the problem down I believe the issue might be in the level1/modules/VTIO.ASM file:
Closest thing I see is it is stuck in a loop that never ends.
Here is the code that seems to be looping without end:
So far I am not up to par to understand what is going on here yet for me to fix it, but I thought I would share what I have found thus far. At least for the locking up part.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok so a quick update. L. Curtis Boyle and I have been working on VTIO for level1 to squash some of the issues.
So far we now have the endless loop taken care of thus far.
A updated VTIO.ASM for level1 has been submitted that will now properly load GrfDrv for level1 if it wasn't previously loaded.
Some of the other issues that were described that are still lurking in GrfDrv have yet to be taken care of. So far it is just display codes $18 and $19 that aren't working as of yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is the script I was using when first facing the graphics issue on NitrOS9, all commands can be put into a single line, I was just seeting them one to a line to keep each step in sequence:
This will select 256x192 buff on white (h0F), clear the screen (h13), center the graphics cursor at decimal 128,96 (h15) and draw a buff colored circle in the center of the screen radius decimal 20 (h1A), the last DISPLAY statement ends the graphics and releases the RAM back to the system.
PROMPT holds the graphics screen until a key is pressed.
Away from my CoCo setup so I can't try assembling the updated VTIO and try it on my system, maybe later today...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok after using MAME debugger to see if I could trace the problem down I believe the issue might be in the level1/modules/VTIO.ASM file:
Closest thing I see is it is stuck in a loop that never ends.
Here is the code that seems to be looping without end:
So far I am not up to par to understand what is going on here yet for me to fix it, but I thought I would share what I have found thus far. At least for the locking up part.
Ok so a quick update. L. Curtis Boyle and I have been working on VTIO for level1 to squash some of the issues.
So far we now have the endless loop taken care of thus far.
A updated VTIO.ASM for level1 has been submitted that will now properly load GrfDrv for level1 if it wasn't previously loaded.
Some of the other issues that were described that are still lurking in GrfDrv have yet to be taken care of. So far it is just display codes $18 and $19 that aren't working as of yet.
Great debugging and fixes! What would be a small "hello world" to test the GrfDrv on Level1?
This is the script I was using when first facing the graphics issue on NitrOS9, all commands can be put into a single line, I was just seeting them one to a line to keep each step in sequence:
display 0F 00 05
display 13
display 15 80 60
display 1A 14
prompt
display 12
This will select 256x192 buff on white (h0F), clear the screen (h13), center the graphics cursor at decimal 128,96 (h15) and draw a buff colored circle in the center of the screen radius decimal 20 (h1A), the last DISPLAY statement ends the graphics and releases the RAM back to the system.
PROMPT holds the graphics screen until a key is pressed.
Away from my CoCo setup so I can't try assembling the updated VTIO and try it on my system, maybe later today...