Jump to content

InsaneMultitasker

+AtariAge Subscriber
  • Content Count

    3,742
  • Joined

  • Days Won

    1

InsaneMultitasker last won the day on August 18 2019

InsaneMultitasker had the most liked content!

Community Reputation

3,944 Excellent

About InsaneMultitasker

  • Rank
    River Patroller

Profile Information

  • Gender
    Male
  • Interests
    TI-99/4A, Geneve, terminal emulation and BBSs, Anime ;)

    Employee of Cecure Electronics (1990s) where I repaired and upgraded Myarc & TI hardware.

    Geneve librarian for Milwaukee Area TI User Group

    SysOp of HeatWave BBS, operating on real hardware at 38.4Kbps. See signature for current Telnet address.

    Author of S&T BBS Software and other TI/Geneve programs

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think we may need to bring in an interpreter.
  2. Not much. The 6K ros stub (that originated from the Hoddie ramdisk eprom) installed by Form3MEG and FORM v1.23 was only used for boot purposes. GenCFG and MDOS 7.30 whittled the necessary information down to a few flags and data points and a few fake routines to accommodate the Geneve Boot EPROM. The spoiler contains what is saved in the DSR space by GenCFG. Note: when ROMPAGE is active, if a program calls the HD device or low level opcode >10, the fake IO routines should simply return, forcing DSRLNK to pass the call to the next peripheral.
  3. Took a break from the SCSI code this weekend to work on the IDE low level code. A new powerup routine now tests for device IDE1 and if found, its card's CRU address is saved and the sector IO address is cached. These two saved values simplify the low level call and eliminate the need to scan the card during each read/write operation (~faster). This implies that the IDE card will be usable at other CRU addresses in the future. I don't yet know if a similar powerup/CRU caching approach is feasible for SCSI and TIPI, though it is certain both cards would benefit from more than is coded within the OS.
  4. The ramdisk operates as a "floppy" style device, there is no support for directories in this configuration. It operates the same as a TI, CorComp, or Myarc floppy controller in this regard. Adding sub-directory support would require a rewrite of the device service routine for the card. I have contemplated the time needed to undertake this project, and it has always been more than I am willing (and able) to commit. The Horizon 4000x series (and 3000?) do provide more DSR memory in the form of a 32K chip, however, there are only two 'windows' into each 8k bank (6k and 2k), and bank switching trampoline code would be required. Certainly not impossible as we know the HFDC code lives in 16K and manages both hard and floppy devices, but with different memory access windows for buffering and management.
  5. fyi, the image was updated a few days ago. The scratchpad loader replaces the older option 5 loader.
  6. Has it only been 16 months? I looked at the code tonight and I might have an idea on why this is happening. Can't test right now but I've noted it in the source. Also looked at the clock code a bit more for IDE support and tried to determine how/if I can change the disk-centric code to allow for any device in the save options. I'll queue it up for the fall timeframe, for after I finish the Geneve OS cleanup.
  7. I only noticed it 2 years ago and if I remember correctly, it was the result of discussion about editing topics and/or messages that clued me in.
  8. For ANSI escape sequence (cursor positioning, color, etc) if your file display routine appends cr/lf to each record, you'll almost certainly end up with interrupted commands and/or a cursor on the next line. If you stick with DV80, one method would be to delineate the file type by using a prefix or suffix, such as "A_MENU1" or "MENU1_A", then use that special pre/suffix to suppress cr/lf for that file.
  9. @9640News - I should have asked what you meant by ANSI menus. If you are referring to color/ansi code type of files, see my previous post. If you are referring to IBM graphics type menus without any ANSI escape codes, those can be done easily enough with DV80 files. Since the late 80s, I've used FunnelWeb to draw all of the basic menus that you see on Heatwave (and S&T BBS) and those are saved as DV80 using the PrintFile option, to avoid saving the tabs information
  10. I use Display Fixed 128 format for all of my BBS ANSI and "PC" text files; this was done for a few reasons including (1) to allow uploading of PC text/ansi directly to the system since a non-ti file transfer defaults to this file type and (2) to distinguish them from DV80 text files. DV80 files typically are output to a caller by adding a CR/LF combination whereas the PC files already contain CR/LF and/or ansi positioning codes. The only challenge for me is that when uploading from the PC, the file size is a multiple of the record size (for xmodem, this is 128 bytes). For PC files without one or more terminating bytes, I run a tool in my remote administration program to add a terminator based on the actual file size. I have to do this step manually.
  11. Spent some more time playing with the SCSI yarn ball. One of the error reporting routines uses R4 to save/restore the error code. During a write operation, R4 is used as a loop counter and is set to 0, destroying the previously set value (to the error code label) and subsequently causing the SCSI DSR to write the error value to address >0000. I am fairly certain the SCSI DSR is paged into the mapper from >0000->1FFF during this operation, so the OS vector at @>0000 is not overwritten. I'll confirm and then work on removing all of the extraneous error report code from the read and write routines. The SCSI DSR maintains a list of the device IDs that have been started with the SCSI "START" command since powering on the system; a warm restart does not clear this table. I've noted this for another day.
  12. And for those who love boxed releases, this has some really cool detail... https://www.polyplay.xyz/Hibernated-1-Directors-Cut-TI-99-4A_1
  13. For those interested in Infocom / Interactive Fiction , check out the release of Hibernated-1 (Director's cut). The TI disk image download will be updated to include the F18A version of the interpreter in the (very) near future.
  14. Will you include warning stickers? The extender boards make testing so much easier. It is of course important not to "rock" the card while power is ON and as silly as this may sound, one must pay attention so as to not insert the card "backwards" into the extender. thank you for making them available.
  15. You can also use the /more switch that was added a few versions earlier. "TYPE A:PFMDOC /more" The output commands like TREE, DIR, etc. use their own output routines so support for this switch exists only in TYPE at present.
×
×
  • Create New...