InsaneMultitasker

@Asmusr - I attached the modified pinball.a99 and speech.a99 files, as well as the three support files that I incorporated into the Pinball source code last year. This should match the binary package I released. The conditional assembly is controlled by this code block in pinball.a99 (search for Geneve9640 to see where I made conditional changes to code and COPY statements): ; [0] 4a standard code; [<>0] use 9640 code Geneve9640 equ 1 ; (0=eq is /4a; <>0 ne is 9640] .ifne Geneve9640 Geneve_bank_delta equ >2000 ;adjust from >6000 to >4000 bank location .else Geneve_bank_delta equ 0 .endif The bank delta is used wherever a bank-specific address/equate is defined. I kept the RS232 debug code in place though the initialization and output are disabled. If Pinball v1.5 source is released, I'll circle back to update the Geneve version as time permits. Oh yes, I reviewed the Flying Shark source and so far I have only located the hard-coded version. I am almost certain I created a conditional assembly version, so I'll look through my files this weekend. According to my notes, I was working on (1) code to simulate the 9901 Row/Column keyboard for better game compatibility and (2) a way to fold the cart header into the build process. I still want to create a simple framework for future games. Maybe I'll have time to pick some of this back up during the winter holidays. Geneve-support.txt Geneve-check_quit.txt speech.a99 Geneve-rs232debug.txt pinball.a99

Maybe your brother-in-law is not feeding his dog enough insoluble fiber as part of his healthy diet

Correct. And for that I am most appreciative. Posting the code is still my intent and the reason for asking you if the published code was current is so that I could apply the updated conditional code before posting here. I have had very little hobby time since last year and I do not see that changing any time soon. (This is also the reason for the Geneve OS delays last year, among other things)

Is the source on Github for the final release 1.5? The file Pinball.a99 indicates version 1.1 near the end of the file. (The commit dates on some sources predate fixes 1.3 to 1.5). I'd like to finalize the Geneve conditional assembly statements and upload the source ZIP here. Thanks. text 'VERSION:' txt_version_no: text ' 1.1 ' txt_hi_score: text 'HI SCORE' txt_kap

Well, there go my plans for a 'cranky' version of the OS error messaging alerts.

My Horizon RAMdisk needed a bit of charging so I poked around MDOS for a bit, and updated the Change Directory (CD) command. It now attempts to validate the existence of the desired folder on any valid device. A few of you have asked for this and it will be in the next release, barring any issues.

If I understand correctly, the likely solution is noted a few posts earlier: leverage the TIPI setting for "NATIVE_TEXT_DIRS". I would suggest reading the linked thread (below) for some background information. I have not tried this setting on my system, but I have used the "?W" option on which this is based.

I use it, particularly for its ability to save and restore the time stamp attributes.

Yes, if a Z3 file exists, I would think it can be converted to run with the /4a interpreters. The reason I suggested reaching out to the site owner/ZIP owner was so that the images can be corrected and posted at the source. An alternative is what you suggest: that someone here converts them and shares the corrected images with the site owner.

I took a quick peek at the disk images and you are correct, only A1RL0CK contains an actual story. the LOAD programs are missing the game title and author, which I think is also part of the automation. I would suggest reaching out to the site owner to find out if the process can be re-run to fix the incomplete /4a disk images. Maybe someone incorrectly used Stefan's build process or tried to convert the z5 files instead of the z3 files.

If whoever created the collection used the same script to convert the files as was used for Tristam Island, file allocation is problematic if any of the files are fractured (i.e., if the file uses more than a single, contiguous set of sectors). If no one else looks at this by the weekend, I'll take a look at the images. Also, the game files must be version 3 (z3) to work with the /4A interpreters.

Very cool. I like that you chose a peppy version of the theme song, even if it is temporary, and even if the note interpretation is different. My memories of the game stem from the C64 back in the day - I loved the digitized speech and especially that laugh just before the intro kicked in.

@RXB have you considered using the Geneve basic math routines for your endeavor? They are all written in assembly and fairly well commented. I believe that @Lee Stewart reviewed some of the math code a few years ago. Using commented source might be easier than trying to disassemble XB3's math routines.

Classic99. 9590. I've gotten a few 200 point blinking flags.

I played LIFT last night and found it to be a fun game. It took me a few screens to realize that I could press left/right while falling to get to the next platform. After a few rounds, I wasn't so likely to paint myself into a corner

I thought it was necessary to set the keyboard 'column' first via LDCR and then read the bits. I've only ever "stored" 8 bits from the keyboard, i.e., STCR *R4,8. Thierry's /4a site has good intel but I don't have the link handy at the moment. edit: here is a link https://www.unige.ch/medecine/nouspikel/ti99/keyboard.htm#quick scan

Interested, but a few stars would need to align to make the drive over.

Nice. Thanks. Advanced BASIC is all assembly so it is a little different parsing routine. I found the code and what it does is it checks each entry. If it finds a string, the length is tested. If the string length is zero, the string is considered a separator and the next item is parsed. (It seems that a string variable might work as a separator here). The routine for load/peek/poke has step to convert strings to integers, which suggests that CALL LOAD(8192,"A") would be valid for a single byte value. I've never tried this.

If this works as an alternative to "", I would be interested in knowing where you made the change(s) to see if they could also be applied to Advanced BASIC. If for no other reason than to see if it can be done though how soon I would try to implement it is another story altogether!

How does this affect backward compatibility? I was wondering if it is an option to check for two successive commas to create the same effect without causing 'trouble'.

Are you able to swap out the 9901 chip? In my repair experience, this component is often the culprit with the Corcomp cards. It might not be your card's issue but it is worth checking into. Multiple drives 'not working' is a bit suspicious beyond a cable or termination problem, IMHO. Edit: Was the REV A card working with drives at one point?

First post has been updated with a link to the MDOS 7.40 (and 7.30) release topic. Shared below as a point of reference.

@9640News - tonight I realized / remembered that the PFM suite was updated in January 2022. Could you please incorporate the files into your release packet and/or add the ZIP to your first post? See the link to the post below. The core was updated to turn off all peripheral cards prior to initiating the standard DSR powerup scan, since a RESET cannot guarantee that all cards have been turned off. The same routine is also implemented in EXEC 2.7, upon return to the OS. The routine to turn off the cards has not been implemented (though maybe it should be!) in the MDOS XOP powerup sequence or GPL. I'll add that as an action item for review. My notes suggest I was planning to add the routine to the OS then simplify both EXEC and GPL. Anyway, I recommend reviewing your EPROM release for this code and if it is not present, consider adding it to a future release.

@Schmitzi must update the PFM Core before loading the new system (or flashdisk) into the device, if he is not on version 8.02. The sequence cannot be reversed (edit: without extra prep) and to be quite honest, I don't recall if the system loader can detect the core version at this time. I will add this to my log.

If you would like to walk through the upgrade process together, we could schedule a time to do so later this year. The programs run from the MDOS command line. the steps are simple so long as you prepare the files.