Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Days Won


InsaneMultitasker last won the day on August 18 2019

InsaneMultitasker had the most liked content!

Community Reputation

2,273 Excellent

About InsaneMultitasker

  • Rank
    River Patroller

Profile Information

  • Gender
  • 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. The 9901 also seemed more susceptible to failure on the CorComp cards. I don't know if this has to do with its direct connections to the PEB bus but that was always the first chip to suspect when I came across a dead CC FDC (and other CC cards with the 9901) that required repair. Often the customer indicated they had pulled the card too soon after powering down the box or (as I often suspected) pulled/inserted the card with the PEB still on. This was around the time when people were replacing the loud fans with silent fans, the former being a good reminder that power was still on (and a reason that my test/repair PEB still has the original, loud fan still today!)
  2. I tested the posted version and the original. No difference. Atrax how come you aren't using the options?
  3. Yep. I tried your sequence by trying to load DSK1.LOAD from TIPI and it worked. Both using Fctn-7 just to drop into standard XB and as a load/run. I also tried using TIPI.TERM80.LOAD and that seemed to work. Can you load the file manually, i.e., go into XB and type "OLD TIPI.GAMES.EA5.LOAD" Lunch is over... will look again this evening.
  4. OK so it is an F18A modified console then. I'll test your sequence on my system. The easy way to chain IMHO is to use the Fctn-4 feature to save the options to disk in a separate file. It is hardcoded at the moment; that will change. The options file is just the information from the menu. So you can load them into memory without loading the full MENU. I think Atrax is using that feature not sure of anyone else besides me. I have a few plans to improve upon what is saved in that options.
  5. Oh ok. So we are talking the 40 column boot right? Attach a copy here and I'll look tonight. (The 80 column menu lets you save and load the chained options (menus) so that's why I was not tracking)
  6. I would first ask why are you loading BOOT from BOOT? On my system I periodically load the latest version of boot from boot for testing. I've never tried an XB program load in this situation. Are you using a standard XB cart or some variant? If the latter, which one?
  7. Is RAMOS a catalog program? Sounds familiar. Did you show it at Lima back in the 90s? Would be nice to see a few screenshots, even if they are emulated. A lot of us use emulation for things these days
  8. Atrax uncovered a problem with the 40 column menu. After you edit the menu options and attempt to save the file back to the ramdisk, the save routine masks the drive unit number to 1-9. If you use a drive letter (e.g., A-Z) for your ramdisks the save fails. I'll patch the MENU739c program when I have time and in the interim: Search for first occurrence of hex string >D060 400F 0241 0F00 and change to >D060 400F 1000 1000. The offending code copies the drive unit number from the ROS memory space (>400F) and masks it before being moved into the DSR PAB. The >1000 >1000 overwrites the instruction with NOP. BF MOVB @>400F,R1 Got CRU >D060,>400F '.`@.' 292E ANDI R1,>0F00 drive# (1-9 only?) AI R1,>3000 >0221,>3000 '.!0.' 2936 MOVB R1,@BG DN() >D801,>3548 '..5H' 293A MOVB @>4017,R1 color >D060,>4017 '.`@.' 293E MOVB R1,@VDPREG patch vregs 7 >D801,>3CC2 '..<.' 2942 MOVB R1,@BASREG " " >D801,>3B12 '..;.' 2946
  9. I am not ambitious enough to program CFG to identify every piece of TI gear. We have these things called "eyes" and "hands" to help us with that. For cards that have unique DSR entries, I will add dedicated detection when the details are shared with me. I am also not interested in determining every different flavor, e.g., does it really matter if the card is WHT SCSI or ASCSI. Hsgpl, SCSI, SAMS are detected. Some devices are not CRU-based which is what CFG is looking at, though I can add non-CRU devices if needed. I don't think there is a way to detect the SID-Master cards from my discussions with Hull. Is there a routine that would identify speech?
  10. You can always do what others have done before you -- leave that floppy drive hanging over the edge of the PEB and use the alcove for storage! Half-heights are much nicer than the full height unless you want the latter for nostalgic reasons. And there are other options you can explore for drives such as the Lotharek floppy emulator. Edit: Does that Shugart have a spot for a terminating resistor pack? Seems to me there should be one installed when the drive is alone in the system.
  11. Dan have you checked continuity between the two sockets or did you just perform a visual inspection? Use your meter to check between socket 1 pin 2 and socket 2, pin 2. Proceed to pin 3, then 4, etc. Pins 1 and 20 won't have continuity between sockets but should have continuity with their origins elsewhere on the board. Check for ground and power continuity. Secondly, use your meter to test for shorts between adjacent pins. If you find continuity between pin 18 and 19, for example, there may be a short that needs inspecting and cleanup. And like Vorticon said you may have a bad chip or two.
  12. Thanks guys... I didn't realize the chipset mattered when I went hunting for VGZs of a few games I used to play long ago. I'll give the SN76489 format a try...
  13. Two questions 1. Is there a MOD converter that can be used with the 60Hz player? 2. I am trying to convert a few VGZ files from this site https://vgmrips.net/packs/ and am running into trouble. I've tried a few different chips and received messages like the one below. Any hints or suggestions? D:\>vgmcomp "goonies-02.vgz" v106 - 12/27/2016 Reading goonies-02.vgz - 4047 bytes Decompressed to 21769 bytes Unusual clock rate 0Hz. Scale factor 1.#INF00. weird refresh rate 0 goonies-02.vgz
  14. Yep, Triple Tech should identify as "clock card" via detection of its dsr entry "CLOCK". Does the FORTI have an EPROM and if so, can someone tell me its device names/subprograms? I didn't think the PGRAM was visible to the system except for when it had control? MBP card is not detected but I do have code I could add if someone has a card for test purposes.
  • Create New...