Jump to content

BeeryMiller

Members
  • Content Count

    1,760
  • Joined

  • Last visited

Everything posted by BeeryMiller

  1. There is PSystem source code for the Geneve for MDOS mode that is out there. Beery
  2. Alan, I saw a DOC folder with some email messages, and a MANUAL folder with a CHAPTER1.ppa and a CHAPTER2.ppa set of files. Did you have a word processor file for the manual? Or, do you by chance still have some manuals you would want to sell? If so, I would be interested. If you do have manuals you would sell, hold one back for me as I will be traveling over the next week and will be trying to find Dorothy and Toto in Kansas. Seems she was involved in a bit of a storm recently........ Beery
  3. Alan, I'm not seeing any files at https://github.com/abeard01/fortran99 except for the license and readme files. Beery
  4. Alan, You should be able to easily post the files here. Then, if users desire, they could be added to GitHub, etc. should someone decide to do any updates, etc. I know I have posted files on here that were > 50 MB, so there should not be an issue. If you have not seen it already, as you write a message, there is a paperclip just below where you are typing where you can "choose files" from your PC to post here. Good hearing from you again and glad you made it over to Atariage. Beery
  5. That is what I gather as well. I was wanting to use the FinalGrom as a SuperCart as well as I needed RAM from >6000 to >7FFF as a program had grown too large. Unfortunately, only >7000 to >7FFF is available. What I don't know is if that is a hardware limitation from the design, or if the FinalGrom can be reprogrammed to open up the lower 4K. Beery
  6. Thinking about it, you might be able to use the TIPI, or at least a modified one, with a new DSR specific to your needs. It would talk to a PI, possibly cabled up to one that may already be a TIPI/PI combo on the other GPIO pins. The other direction is to rewrite the python code and wipe out the PI code that interfaces to the TIPI to do your "new stuff" with video. It may not be so much as hardware as just writing new software...…… from scratch.
  7. This is for curiosity's sake. Do those characters generate a single ASCII character? Or is it a multiple character sequence? Inquiring that if they are just redefine characters and lower ASCII values, then it may be just be a redefinition of a character. If it is something outside the normal TI character sequence, then there would need to be a test for a particular character sequence to respond back to and display that character. Like FCTN-Underline to generate the particular key which I am guessing would not be the specific key used, but an example. Beery
  8. I was trying to wrap my mind around this approach with the PI. Are you thinking of using the Cassette port as the interface to the PI? Is there an effective baud rate limitation? Or, Are you thinking of using the TIPI as an interface to the PI? The TIPI/PI combo would need a new protocol and it does allow a pretty large 'in-ram' buffer along with VDP transfers as well. So, the question becomes do you want to transfer all of VDP to PI and vice versa with up to 16K chunks as images? That would probably not be too difficult and would be speedy and something I have suggested in a similar thread in the development forum for using the PI as a frame grabber with a camera. Now, with the 9938 capability, you are going to end up limiting yourself to effective ram. Basically, what you would write to VDP instead needs to be written to CPU ram, and then you limit yourself to at most a 24K image capture of ram on a TI console. You would not get into the 9938 specific graphic modes unless you start fragmenting ram chunks which would likely need a SAMS to even consider it. Then, you would need something on the PI to grab data to display if you wanted to actually see it "live".
  9. Depending upon how large your block is, you might be able to use an index of multiple MOV *R1+,*R2+ instructions to identify where to start within the block of MOV instructions. That would get rid of a DEC instruction, especially if you were going to test after every MOV instruction.
  10. That was traveling to the fair and then presenting. Not the same thing. I can present, but it is really going to boil down to what is presented based upon whether we use Zoom or not. Beery
  11. No, not useless. You have an extra 8K of ram available and you don't have to worry about bank switching code to map routines in and out. In my case, I needed more than the 4K I could have gotten with the FinalGrom99. Beery
  12. Yes, I used the 8K Super cart as I needed the additional 8K of ram it offered in the >6000 to >7FFF space for programming memory. Using 4K Ram like the Mini-Memory cartridge was insufficient with the FinalGrom99. My TIPI/BBS is running as well with one, even though it is not externally accessible at the moment. Beery
  13. I don't doubt there could be an issue with the TI disk controller in Rompage mode. I do not specifically remember the TI disk controller not working, perhaps it may have just been in the format routine????? I'm wondering if you slowed the GPL speed down while in Rompage mode if the issue disappears with the DSR. Beery
  14. Moving response to the topic area Matt referenced.
  15. It sounds like Fctn-S and Ctrl-Q may be sending more than one character to the server instead of being interpreted as a single byte. Unless you are in a half-duplex mode which I do not think is even in Matt's TIPI Telnet client and rare to be seen from other telnet servers, it is the Telnet server itself that receives the character and then echos it back to you where the display routines control the cursor movement. I'm guessing one character that is sent is a non-displayable character, then you have the other character. I think some of it depends upon the particular keyscan mode one is in how things get interpreted. I know it can be complex as I had to write some specific code to handle the arrow keys for up/down/left/right for the Geneve keyboard in MDOS mode with MyTerm so the servers on the other end would respond correctly. Beery
  16. GenPROG using GenLINK has the ability to use the BLOCK command for where you can load code to a specific range of addresses. It could be a block of only a couple of bytes, to 64K if one so desired. You would also likely use the PAGES command to specify the 8K pages. In the case of MDOS, I believe the PAGES identify to the 8K byte page number. I think MDOS at the Command Line Interface (CLI) limits you to something with something less than 64K taking into account the first >400 bytes of memory are OS oriented, and there is some restricted memory above >F000. However, you can use the DSR Load command in MDOS to load a program image file up to the available free memory range if you have previously requested those pages from the Memory DSR. Nothing says that each 8K block could have been previously identified with a PAGE number, and that block mapped to >6000->7FFF with your page reference being an offset into your list of requested memory pages. I hope that makes sense. Basically, you could have a 1.5 MB program image file loadable from a separate file if you had the extra memory, with each 8K block having been PAGE'd and BLOCK'd to be useable at any memory address range you desired. In addition, you could also have a BLOCK range to fit any graphics VIDEO range set if you wanted to copy a block of CPU memory to VDP memory for graphics. Lots of easy options on the MDOS side of things for handling CPU and/or video memory. Beery
  17. Just a short update. I spoke with John today for not much more than about 3 or 4 minutes as he seemed distracted or something..... Anyways, he is still hanging on and he did get the Windows 10 system up and running that was provided. Sounded like he never got the Geneve up and running. If I had my guess, conditions may not allow it to be resurrected, but that is only a guess. Anyways, he sounded like he didn't want to talk but he is still kicking. Beery
  18. I've got to give a shout and thanks to Tator. When I saw he posted in another topic area and was in Argentina, I inquired if he knew a Klaus Gebecke from Buenos Aires. He didn't know him, but Klaus was an avid and pretty brilliant Geneve programmer writing a Tetris game as well as another program called MixPic with some fancy graphics back in the 90's. Turns out Tator did not live too far away from the address I gave him, and confirmed after 25 years, the site had a newer building in its place. I never knew how old Klaus was, so I do not know if is still kicking and with us or not. Anyways, thanks for checking the situation out Tator! I'm posting this here in the rare chance Klaus was to go googling and sees his name pop up on this group. Beery
  19. A page will only be empty if it was never written to in the first place. If there is data leftover from a previous loaded file/document that wasn't cleared, you may get a false report. Beery
  20. I think within MyWord if memory serves me correctly, I saw Peter Hoddie use two different DSNLNK calls. One is the standard DSRLNK. The other "remembered" where it was last called. There was a note in the source about being very careful to make sure the proper DSRLNK was called or one could open the wrong path. I would think a revised starting/ending point could be established in the call so that if it found what you were looking for at CRU >1600, >1400, >1000, etc., it would start at that point the next time it was called and circle back to >0100 less than the starting point. Beery
  21. I have been in contact with Al and I am trying to get the source code to TASM. Beery
  22. No surprises from me, but the GenPROG package with GenASM and GenLINK. GenASM - Single pass assembler, 31 character label names, macros, conditional assembly directives, macro strings. Probably the fastest compiler unless you step to an assembler on a non 9900/9995 CPU. GenLINK - Supports saving files in multiple formats with and without headers, and the ability to create overlays, and no restrictions on the size of program image files. Ability to use libraries. Beery
  23. I tried something last night when copying files from WDS1 to DSK0 (TIPI), that DM2K also created directories on the fly. That makes using DM2K pretty nice for backing up to TIPI, really eliminating the need for the MDM5 backup/restore module. Beery
  24. Here is a complete set of source files that will assemble to the latest known version of MDM5. The assembly process in this zip archives uses the MDOS batch file "ASS" and the Link file "LINK1" to put the various modules together. The code is from the V1.29 codebase, but to differentiate this from any future versions, I numbered it as V1.60 should there ever be a question on its origin. If you have any questions, just ask. Beery MDM5-V129-V160.zip
×
×
  • Create New...