Any suggestions anyone? There’s a USR subroutine that scrolls the wrong part of the screen when the Disk System is enabled. Here’s some of the code:
| CODE |
| 4 DEFUSR0=474:DEFUSR1=490:FORX=474TO484:READY:POKEX,Y:NEXT:FORT=490TO542:READZ:POKET,Z:NEXT 5 DATA 173,159,160,10,79,246,01,93,126,180,244,16,142,25,223,16,191,63,226,142,25,192,198,1,166,132,183,63,225,58,166,132,167,31,188,63,226,38,246,182,63,225,167,132,30,18,198,32,58,198,1,30,18,16,191,63,226,58,140,27,192,38,217,57 |
The rest of the code is just ECB using the USR routine or doing typical, vanilla ECB commands (LINE and GET among other things).
Tell you what… I have another project I have to work on so it will be done by CoCo Fest.
I’ll see about fixing the 1 hard coded patch I made to BASIC so that it will work based on the detected system. Then I’ll have to focus on the other project for a while but you should be able to use that as an example to modify any BASIC POKEs to video RAM. Once the other project is done I’ll come back and see if I can figure out what is going on. I have a hunch that the BASIC code is overwriting low memory in places and the USR1 function is trashing higher memory. I can’t be certain though.
Thanks, man. Waiting’s no problem, since I’m balancing more than one project at the same time myself. I guess when I posted the code to the forum, I started an epidemic or something here …