SmartBASIC - A Coleco Adam Forum

To tell the truth I’m not sure how - I really don’t understand the parameter blocks. I’m tempted to post all the source code so others ( you? ) can play with it. Normally the OS takes care of the size calculations like the extant number etc... so I have never messed with that. The extant and number...

Milli wrote: ↑

Thu Feb 04, 2021 9:16 pm

I’m glad you’re making use of it

Do you think you're going to fix the file size reporting issue?

One other thing: the file size is incorrectly reported by the STAT command.
I have made your 8meg CP/M image my main work image as it simplifies my life quite a bit by keeping all my development files in one place.

56h is used by the pattern descriptor table.
I just realized that CP/M on the Adam does use some sprites for the cursor and the I-VI key display, so it's probably taking the upper 16 sprites for its own use.

During the development of my current project with Turbo Pascal 3 and the graphic extensions, I encountered an odd bug where the pattern of any defined sprite beyond the 16th sprite was getting corrupted. I poured over my extensions code but could not find any problems there. Then I remembered the VD...

Looks like that image is causing some issues.
Turbo Pascal locks up intermittently and the display scrolling does not seem to work with the editor.
Adamed does not work at all.
Does the image make changes to the standard Adam VDP layout? Did you make changes to the BIOS calls?

Norton is flagging your website as a known dangerous website. Any idea why?

joltguy wrote: ↑

Wed Nov 11, 2020 9:00 pm

Wmaalouli wrote: ↑

Wed Nov 11, 2020 4:56 pm

Sorry but I have no idea how to fix that...

No problem at least now I know.

Now back to CharDef!

Interestingly, Chardef will actually save just fine to the M drive, so I'm not too clear why it wouldn't work with Adamed.
I wonder if Milli has any thoughts on this.

Ah looks like you are right! I don't know how the M: drive is set up on the Adam since ramdrives are not exactly standard in the CP/M world. Drives A to D all work fine, and I use the standard CP/M calls for drive access. Sorry but I have no idea how to fix that...

I just gave it a try for the first time on my ADAM and noticed the enhancements you made (vs what I saw in the video). Great updates! The update to I/O is especially useful (being able to specify a drive prefix) and I am hoping you will add a similar enhancement to AdamEd . Currently AdamEd always ...