Jump to content

FALCOR4

+AtariAge Subscriber
  • Content Count

    184
  • Joined

  • Last visited

  • Days Won

    1

FALCOR4 last won the day on August 17 2019

FALCOR4 had the most liked content!

Community Reputation

364 Excellent

About FALCOR4

  • Rank
    Chopper Commander
  • Birthday 02/27/1958

Profile Information

  • Gender
    Male
  • Location
    California
  • Interests
    Tinkering with the 99, air rifle collection, off road motorcycling, enjoying the grand kids!

Recent Profile Visitors

1,770 profile views
  1. I started with a TI-58C. I remember really wanting a 59 but I couldn't afford it at the time. I used the 58C until several of the buttons stopped working then went over to an HP15C which I still have today along with a 12C and 16C. Their buttons all still work 😆
  2. I had "briefly" considered designing a new version of the GK but I'm not convinced that there would be much interest in it given the FinalGROM and UBERGROM carts, emulations, etc. Even if I went ahead with the project it would likely be a kit as I wouldn't have the time to put many of them together. I wouldn't be able to produce a metal case either so it would have to be a printed plastic case. My to-do list is long <sigh>
  3. Thanks apersson850 for letting me know, change made.
  4. This may be out there somewhere but if not, here is the TI logotype (c) for TEXT mode (40 columns as opposed to 32 columns). If you have pics like this to share I'd love to see them. TI Logo CHAR data for TEXT mode.pdf
  5. I was cleaning up my desk at work today and came across this cartoon a friend of mine gave me years ago after discovering I enjoyed programming assembly language on the TI. It was in fun and I certainly didn't take any offense but it got me thinking about structure in assembly language programming. So, do we have examples of what "good" assembly language programming looks like? And, why is it "good?" If you do, I'd love to see it and hear your philosophies about it.
  6. That's pretty nifty, Rich! How did you implement it? Are you using the GPL Call IO command as part of the code sequence? Just curious.
  7. Here's an E/A5 V9T9 format version of KEYBITs that runs in expansion memory. KB
  8. That really happens with the FCTN key. Also the 1,2,3,4,5 keys since they are all on the same line as the alpha key. Just one of those goofy design choices that TI made. Try this; press the FCTN, Shift and D keys together. You'll notice a fourth "phantom key" pop up.
  9. Here are pics I send to sellers to help determine QI MoBos from non-QI, if that's helpful. Like Ksarul stated. the CRU lines don't come out to the cartridge port on the QIs.
  10. On the 256k and 1M cards you only need to send one byte in the MSByte of a WORD. In the 4M and above cards you need to send two bytes in a word; the 1M bank number in the LSByte and the page number in the MSByte. The LS612 always overwrites the LSByte write with the MSByte write. On the 4M and above cards the LSByte is latched and presented to the LS612 on the MSByte write cycle. And on the larger cards, you only get the page number, duplicated in the MSByte and LSByte, when you read back a register. The latch containing the bank number does not read back on the data bus. SAMS registers explained_Srt_AP edits.rtf
  11. One other tid bit of information that may help. The top SRAM on the PCB is the lower half of the total memory and the bottom SRAM IC is the upper half of total memory. If a test program makes it through the first half of memory and then flags errors afterwards then it is usually the bottom memory chip on the PCB. If the software doesn't function at all or errors out somewhere in the lower half of memory then it may be the top SRAM IC. In that case you could swap ICs and try again.
  12. I'd be very interested in getting some of the plastic plunger replacements when you get things worked out to your satisfaction. I have the same issue with one of my good consoles with cracked posts that cause the keys to stick.
  13. Sometimes you may want to scan a key or two directly from the keyboard in your software rather than going through the TI KSCAN routine. This routine, that loads into cartridge ROM, is a quick and easy way to identify the key column and row that you can use for directly addressing the TMS9901. Also see Thierry's page on the TI keyboard implementation for a good rundown on how it works. Just another tool in the tool set. And, yes, the columns are listed vertically and the rows are listed horizontally 🙂 KBCART.bin KEYBITs.pdf
  14. Definitely try that first. I had a similar problem that cleaning solved. I ended up cleaning the pins of the ICs, using contact cleaner on the pins and sockets, then swiping a thin film of dielectric grease on the pins before reinserting them. The card has been rock solid since. Hopefully something like that will work for you.
×
×
  • Create New...