Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

  • Days Won


jedimatt42 last won the day on May 7 2017

jedimatt42 had the most liked content!

Community Reputation

2,269 Excellent

About jedimatt42

  • Rank
    River Patroller
  • Birthday 05/15/1973

Contact / Social Media

Profile Information

  • Gender
  • Location
    Beaverton, OR
  • Interests
    Programming, old and new.
    The world of Arduino.
    My TI.
  • Currently Playing
    Mousing around on my TI-99/4A

Recent Profile Visitors

15,224 profile views
  1. The secret is understanding what set of key strings matter. The generic mame documentation said something about using codes in the controller.ini... some google searching led me to stupid words like KEYCODE_F1 or KEYCODE_ESC... So, it seems these are dependent on the controller for the system being emulated? Simply 'F1' works well... 'ESC' not so much... it quits mame. Working option: -uimodekey F1 THANKS!
  2. No, that command line option -uimodekey did not work for me at all... I found that if I use the -ui_active option, then I don't need a uimodekey, and the UI keys like TAB can just be used... but that circumvent the value of the ui mode key. I haven't been using a mess.ini ( mame.ini now, I suppose ) just trying to pass command line arguments to mame from a bash script. I guess per ninerpedia, I will try to force the creation of an ini, and see if modifying that works. What I'm trying to do is test Force Command with hardware I don't own, such as the mame supported HFDC, SCSI, and IDE. Mame should be the perfect tool for that. [email protected]
  3. Super basic mame question, that I can't find the answer too on the internet... I don't have a scrolllock key... so what do I do to get the ui mode? I tried: -uimodekey KEYCODE_ESC I'm on a laptop running linux. Mame docs say: -uimodekey [keystring]
  4. Just to clarify, upgrades are not broken. There are no changes to address this specific issue. It was an individual anomaly not likely to impact users in general. [email protected]
  5. Ok, seems it was just a bad dependency download that got stuck in the pip cache... and sounds like manually deleting the python pip cache and manually re-running the upgrade script fixed it. [email protected]
  6. Looks like there is another third party dependency that has broken out from under the TIPI upgrade process. People should hold off on upgrades, or take the latest SD Card image, until I can post a fix. [email protected]
  7. @ElectricLab will have to address this issue with TIPI Chess v.003 [email protected]
  8. TIPI does not support sector IO, and I have no intention to do so... It is not meant to emulate a floppy or other spinny disk thing... There are no sectors as the files are individually contained as TIFILES files. Sector IO is not the same as Direct Read and Direct Write LVL2 operations, those are supported as they refer to blocks of data within a file. For DSK. device usage ( volume name searching ) ( My TIPI wiki docs are wrong, lacking, and hard to find on this subject ) TIPI.TIMP. can be referred to as DSK.TIMP. if directory TIPI.BUSINESS.TIMP is mapped to DSK3, then it can be referred to ask DSK.TIMP. Mapped drives are searched first from 1 to 3, and then directories immediately under TIPI. are searched second. If no name match is found, it should then attempt your subsequent storage devices. [email protected]
  9. I think no == yes... >83C0 is the workspace used by part of the 4A console rom interrupt service routine. at >0A8A - I wasn't trying to say >83D0 was that workspace, but that they were (with)in that workspace. Most of the console rom service routine uses the GPLWS >83E0, and >83C0 is referred to in TI99/4A INTERN as the INTWS. The console rom interrupt service routine does a healthy amount of mucking in both blocks of memory, and uses both as WS value at different times. Anyway, since the GPL DSRLNK is right after that in the book, I checked, and it also is stashing values into >83D0 and >82D2. [email protected]
  10. Oh, I see code in DSRLNK stashing values into those 2 memory addresses. [email protected]
  11. Why were they able to assume >83Dx still had relevant information at the time control is transferred to a program? Was this a side effect of the DSR, DSRLNK, or EA loaders? >83Dx is in the workspace usually used by the ISR, correct? [email protected]
  12. What about beige consoles... They'll need to find a matching beige bezelled HDMI display. I jest. I actually have 9 80s tech computers connected to one display. I don't think I have any chance of getting one display that matches all of their flair. LOL [email protected]
  13. I think ran into that on whtech... a zip of pages... http://ftp.whtech.com/Geneve/mdos/ABasic/MyBasicManualUpdates.ZIP rtf's for each update page. ABASIC 4.05 - http://ftp.whtech.com/Geneve/@ABASIC405 -- this is an archive file. Maybe that's what people meant be the '@' in the name... ABASIC 3.00 full manual - without community amendments. http://ftp.whtech.com/Geneve/abasic_manual.pdf [email protected] ( Retro Computing is more anthropology than computer science )
  14. Thank you for updating the CALL VERSION and the greeting! I found the 4.05 version on WHTECH, with a changelog from version 4.00 on... Nice to see that sort of thing! ---- It is indeed an impressive BASIC considering features and speed! [email protected]
  15. I have a version of ABASIC for the Geneve, files: ABASIC1-4. CALL VERSION(A)::PRINT A outputs 300 - When it starts, it greets with MYBASIC 3.00 Question 1: Is this the first version released by Myarc? I've seen amended documentation, from 1989 - Walt Howe, but it doesn't say which version of ABASIC it is for... I've seen version numbers implied elsewhere for 4.00 and 4.50... Walt Howe's manual notes refer to a version where the files are named: BASIC1-7 as provided by Myarc on the ABASIC disk. Question 2: Which version is this manual update for? It says it was released by Lou (Phillips) at the Chicago fair ( in 1989 ) Question 3: What is the the latest version of Myarc Advanced BASIC for the Geneve 9640? [email protected]
  • Create New...