InsaneMultitasker

@Albert Recent versions of Edge wouldn't give me an advanced option to bypass (Win10). Ended up using the info from this site Microsoft Edge: Bypass NET::ERR_CERT_AUTHORITY_INVALID - ShellHacks i.e., click in the white space then type thisisunsafe.

I was able to "accept" the expired certificate with an older version of FireFox. So far no luck with my phone/Safari.

I realized I didn't link to the post I referenced. 21 pages so far of Q&A and good info, IMHO. This links via the topic @arcadeshopper shared in the first post.

Be thankful for the continued support and enthusiasm that is inherent in these developments. The site didn't shut down, the information is all still here, and there is no indication it is going anywhere. If anything, the site will get even better for those who visit - subscribers and free users alike. Seems to me we should be celebrating the success, not griping about an event that hasn't happened or isn't likely to happen. ( @Albert has a thread for Q&A that has a lot of interesting good info as well)

Did you just Rush your test results?

For $1225 less, you can peruse other volumes like this one. https://www.ebay.com/itm/266360443931?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=_glijAtcRyu&sssrc=2047675&ssuid=-T8Sd-FFRwu&widget_ver=artemis&media=COPY

My first two displays were a black&white TV and a 13" color TV, connected via an RF modulator. The centered, 28-column display fit snugly on the black&white TV, particularly at the two bottom corners. The color TV showed a bit more of the display, though I think it had some adjustment knobs at the back. On both TVs (Edit: maybe it was just the color TV?), I could see graphics in columns 1,2,31,32 where the screen was widest, however, it wasn't until I obtained a composite monitor that I could see 'everything' in the 24x32 window. The BASIC reference manual briefly mentions the potential screen limitation, "The graphics subprograms feature a 24-row by 32-column screen display. The 28 print positions normally used in TI BASIC correspond to columns 3 through 30. inclusive, in the graphics subprograms. Because some display screens may not show the two leftmost and two rightmost characters, your graphics may be more satisfactory if you use columns 3 through 30 and ignore columns 1 and 2 on the left and 31 and 32 on the right. Experiment with different line lengths to determine how many positions show on your screen." It seems to me that some games were designed with the column 'limitation' in mind as well.

Maintenance update for EXEC based on my recent activity with the 'FinalGROM simulation' loader. Both EXEC28 and EXEC28DOC are TIFILES format. I included a copy of the notes as a text file, see change log excerpt: - Keyscan table is no longer passed back to the OS, with exception of the CAPS and NUMLOCK status. This resolves 'phanton' keypresses upon re-entry and with certain scan modes. (The keyboard state table was incorrectly being preserved for all depressed keys). For example, After loading EXEC once, the second or third time could result in an unexpected reboot at the command line. - Holding SHIFT-SHIFT-CONTROL (or ctrl-alt-del) too long on exit will no longer restart system. EXEC V28 released 13August2023.zip

OLDCS1GPT, is that you?

I've been using my Geneve system a bit during the past few weeks. With it being so hot outside, it seemed like the perfect time to back up the ramdisks' files and check their batteries. (Note: don't check the batteries before backing up the ramdisk, lest you disrupt the circuit and lose or corrupt files!) Both RAMdisks are 8MB capacity, populated with 16 x 512K low power SRAM chips. The 3000's standard alkaline batteries are still supplying 4.1v after all the system downtime, and as far as I recall it has been 2.5+ years since I last replaced them. I'll check them again in the fall and replace at the 3 year mark. The 4000 runs on rechargeable nicad batteries and their output is at 3.4v. This might be on the low side, I need to check the specs to confirm. The only challenge I faced was that the battery in my multimeter had to be replaced before I could test the batteries.

With much appreciation to @mizapf, we were able to track down the root cause of my Geneve conversion problems. The first problem was one of forgetfulness: I had modified the key EQUates to represent their ASCII equivalents for use with my 2022 loader. The 2023 updated loader now uses the CRU-based row/column values, which it translates to XT state table values as needed. The wrong values had the unintended consequence of passing all keyboard requests to the 9901 CRU-based joystick routine, which then incorrectly tested CRU address 0 (9901 mode setting), and returned NEQ for all key tests. My error was compounded by a surprise: the ROM image that I am using contains all 0x000 in bank >6078. Together with the first problem, Flying Shark thought the "M" key was -always- pressed, so it dutifully passed control to bank >6078 and a host of 0x0000 instructions that the Geneve did not like. I am fairly certain that I downloaded the ROM at the same time as the source files, back in June 2022. I'll review what I have locally either tonight or tomorrow. I confirmed that my earlier release crashes if 'M' is pressed.

Oh, sure enough, with fresh eyes I now see the MOV instruction following the STWP statement. Thank you!

@Asmusr I've been applying my updated Geneve routines and loader to Flying Shark so that I can release the changes. Alas, the game now never makes it past the title screen and the music never starts. I thought the problem was in my keyboard routine, but Pinball is working with the same code. While debugging I came across four places where "shark.a99" is setting the workspace to 0 with "LWPI 0". Maybe this code isn't used? Sharing for your thoughts. See screenshots.

I worked at a Radio Shack for a few months during the early-mid 90s. I learned a lot from one of the workers there who I am fairly certain was a HAM operator and electronics tinkerer. There was no end to customers who came in looking for the most arcane connectors, batteries, and parts. Kinda neat asking them "what are you using THIS for?" I left that job after a few of us were told (not asked) that we had to spend a few days performing a complete parts inventory of everything in the store. A few years ago I visited a RS store and was surprised to find nothing, save batteries, that resembled the parts and components availability from their heyday. At least they didn't seem to be asking for the customer phone number and address at checkout - I loathed asking customers for that info.

You should also be able to pipe DV80 files to the RS232/PIO device with the greater than sign ">" TYPE FILENAME>RS232/1 I believe it also works to “pipe” from CON, i.e., COPY CON RS232/1, until you press CTRL-Z to close the 'copy'

I am not aware of any native parameter passing between ABASIC and the Geneve OS command line interpreter. If it is a feature, I do not recollect seeing code for that express purpose. The speech routines in ABASIC are somewhat isolated but they rely upon helper routines that may be harder to extricate from the source than the SAY routines themselves. As @mizapf noted, parameters are fairly easy to pick up from the command line, so someone would just need to do the work to create a program that speaks. I do not have a speech device in my system nor do I have much interest in speech, so that person is not me

If you are referring to adding DSK5-DSK9 to the TIPI DSR EPROM, coexistence will depend on the user's configuration and their program usage. A few thoughts come to mind: With the /4A, the Horizon Ramdisk and its "partitions" are typically formatted starting with DSK5. to fully avoid conflicts with the floppy controller devices DSK1-4. Devices DSK6-9 and DSKA-Z are also available to the Ramdisk. If you are looking to expand the TIPI to emulate DSK5-9, the Horizon Ramdisk user can avoid conflicts by using Ramdisk drive letters A-Z. Programs that are CRU-aware - such as FC or DU2K - become important for level 2 IO if there is a need for a Ramdisk device to use DSK5-9. I don't know if any /4A users with both the TIPI and Ramdisk hardware use programs that do not allow DSK A-Z, with a need for Ramdisk drives 5-9. The Geneve's boot EPROM reserves DSK6. for a Horizon Ramdisk boot device. I cannot think of any other conflicts, since the Geneve OS manages its devices internally without utilizing the on-card DSR EPROMS. Theoretically, if the TIPI DSK6. mapping is not enabled and the TIPI DSR fails through to the next device, I doubt there would be any issues with the bootup sequence.

That's a nice setup!

@TheMole I sent you a PM with an updated Geneve ZIP just a few moments ago.

Perhaps the interrupt is serviced before the loaded program sets the interrupt mask to 0. My real Geneve does lock up with a different project and removing the RS232 resolves the issue. The loader has been updated and I will PM it tonight or this weekend, for testing.

I pulled the TI RS232 out of my PEB. What I thought was a code issue with another program has been resolved. Now I have two reasons to fix the interrupt handler, thanks to this whole discussion. Nice, indirect way for MAME to debug code!

Yes, it is an original TI RS232. I am wondering if the interrupt is raised as part of the emulated /4a powerup or reset, then never serviced. I'll check the loader and Pinball for anything that might be changing the interrupt mask. For example, the Geneve keyscan might be performing a limi 1/limi 0 which in turn yields to the interrupt handler. I still think that I should update the loader to page in the DSR properly,which would render the whole discussion moot as the interrupt would be serviced. If I have time tonight, I will create an updated loader that I will PM to you and @9640News

My real Geneve has an RS232 and it does not exhibit this issue. Interesting.