+Schmitzi Posted July 26, 2015 Share Posted July 26, 2015 P-Code 4.0: (>1F00) 1 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 26, 2015 Share Posted July 26, 2015 ...ready... hope it helps a bit Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 26, 2015 Author Share Posted July 26, 2015 P-Code 4.0: (>1F00) 061-PCode-RS.jpg062-PCode-RS.jpg Very nice posts! I didn't know you could activate a PCODE card and not run the PCODE software For the Foundation card, I seem to recall it responds to "DSKX." . Is that correct? I believe Fred's Disk Utility program show the DSR headers for the cards in the system. What I need is a unique Device name or unique subprogram that can be used to identify each card. If a DSR is not loaded, it will not be identified. I might consider adding some code to test for CRU responses and memory paging, but that is currently beyond the scope of this release. So, if you have screenshot of the DSR for these cards I can take a look. Or if you have an EPROM dump I can look at it directly. Many options Quote Link to comment Share on other sites More sharing options...
Gazoo Posted July 27, 2015 Share Posted July 27, 2015 Very nice posts! I didn't know you could activate a PCODE card and not run the PCODE software For the Foundation card, I seem to recall it responds to "DSKX." . Is that correct? I believe Fred's Disk Utility program show the DSR headers for the cards in the system. What I need is a unique Device name or unique subprogram that can be used to identify each card. If a DSR is not loaded, it will not be identified. I might consider adding some code to test for CRU responses and memory paging, but that is currently beyond the scope of this release. So, if you have screenshot of the DSR for these cards I can take a look. Or if you have an EPROM dump I can look at it directly. Many options The Foundation card will be difficult to identify. It was originally sold without an eprom. There was also a hacked eprom that made it work as a Myarc 128k card so it could run Myarc Extended Basic 2. It might be best to leave that one alone and let it be reported as undefinable. Gazoo Quote Link to comment Share on other sites More sharing options...
Gazoo Posted July 27, 2015 Share Posted July 27, 2015 The Corcomp Ramdisk responds as 'DSKR.'. I think there's also a CALL to bring up the resident disk manager, but I don't recall what it is. It would probably be better to identify it by the CALL since 'DSKR.' can also be a valid device for a Horizon Ramdisk. Gazoo Quote Link to comment Share on other sites More sharing options...
+Ksarul Posted July 27, 2015 Share Posted July 27, 2015 The earliest Foundation cards were actually a 32K card--that worked just like the TI card. Then came the DSR-free 128K card, with a DSR that came out very soon thereafter (initially as an upgrade, but later it was standard). Last came the hack to make it run the Myarc 128K OS (and their XB 2.11). The hack also included instructions to upgrade the card to 512K (I think I have one that has all of this done to it--but I also have a standard 32K and a 128K (with DSR) version of the card). Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 27, 2015 Author Share Posted July 27, 2015 The Corcomp Ramdisk responds as 'DSKR.'. I think there's also a CALL to bring up the resident disk manager, but I don't recall what it is. It would probably be better to identify it by the CALL since 'DSKR.' can also be a valid device for a Horizon Ramdisk. Gazoo Agreed. A unique subprogram is preferred I could probably do a secondary test for a RAMdisk ROS subprogram to rule out ROS at a detected "DSKR" or "DSKX" device; however, if there is no DSR then the only other method would be to twiddle the CRU bits and look for memory banking in defined areas. If schmitzi can provide the dsr info, we can get one step closer for these cards. Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 yes, I will try to bring up the DSRs tonight. Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 Very nice posts! I didn't know you could activate a PCODE card and not run the PCODE software thanks. With the P-CODE-4.0 (CRU >1F00) that was an easy idea. Just set the switch to OFF, start the PEB, and the TI to the startscreen. Then switch the P-CODE to ON, and boot the wanted tool from disk, or whatever The card is available there, showing her address (but no DSR, as there seems to be none) Maybe this is a way for testing the P-CODE with a diag-tool ? (Is there any Diag-Tool for the P-CODE ?) Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 Cool, thanks Gazoo. I've never looked at the documentation because I do not own one... YET... but it's on my list of future acquisitions! Hi, which RamDisk do you have ? Here some jumpers from my manuals: HRD2000: HRD3000: HRD4000: Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 OkeyDokey. I have rechecked all cards - and pulled my TripleTech in addition - once more with Fred Kaal´s great DU2K Disk Utility Tool. Here are the results: MECHATRONIK 128K: NO CRU, NO DSR: Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 CORCOMP MEMORY PLUS (512K): CRU >1000 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 FOUNDATION 128K: CRU >1E00 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 MYARC 512K: CRUs >1000 & >1900 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 GRAM-1.1: CRU >1700 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 CORCOMP TRIPLETECH: CRU >1D00 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 27, 2015 Share Posted July 27, 2015 thats all have fun ...and many thanks to Fred !!!! http://www.ti99-geek.nl/ Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 27, 2015 Author Share Posted July 27, 2015 From this it looks like we could do the following: 1. CorComp I think we can use RAMGR and/or LOWER to detect. (As a side note, the HFDC and SCSI use >2x routines, so this card may not play nicely with either of those two cards). 2. Foundation 128K card : MEMINIT or MEM96 plus CRU 0x1E00 3. GRAM 1.1: EDITMEM? 4. Triple Tech: already detected via CLOCK. 5. SAMS / AMS / Mechatronix 128, other non-DSR memory cards: requires a different method. Gazoo - is EDITMEM also found on a PGRAM? Any other similar calls you see that would cause problems? I will make some changes and return with an updated version. Quote Link to comment Share on other sites More sharing options...
Gazoo Posted July 27, 2015 Share Posted July 27, 2015 From this it looks like we could do the following: 1. CorComp I think we can use RAMGR and/or LOWER to detect. (As a side note, the HFDC and SCSI use >2x routines, so this card may not play nicely with either of those two cards). 2. Foundation 128K card : MEMINIT or MEM96 plus CRU 0x1E00 3. GRAM 1.1: EDITMEM? 4. Triple Tech: already detected via CLOCK. 5. SAMS / AMS / Mechatronix 128, other non-DSR memory cards: requires a different method. Gazoo - is EDITMEM also found on a PGRAM? Any other similar calls you see that would cause problems? I will make some changes and return with an updated version. EDITMEM is not in the Pgram DSR. CLOCK is though. You may want to have the Pgram identifiable by CALL PG and leave CLOCK for the Triple Tech. RAMGR would probably be the best bet for the Corcomp ramdisk. Gazoo 2 Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 27, 2015 Author Share Posted July 27, 2015 EDITMEM is not in the Pgram DSR. CLOCK is though. You may want to have the Pgram identifiable by CALL PG and leave CLOCK for the Triple Tech. RAMGR would probably be the best bet for the Corcomp ramdisk. Gazoo Good point. The way CFG works is it looks for unique items first, so that duplicates can be weeded out. I'll verify clock comes after the PGRAM Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 28, 2015 Author Share Posted July 28, 2015 Good point. The way CFG works is it looks for unique items first, so that duplicates can be weeded out. I'll verify clock comes after the PGRAM Done Added the GRAM 1.1, Foundation card, and CorComp card to the detection routine. I will give it a test or two before posting. There are a few other cards I want to play with before I wrap this up. Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted July 28, 2015 Share Posted July 28, 2015 Do you need a copy of the QUEST 5.12K RAMdisk DSR? Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted July 28, 2015 Author Share Posted July 28, 2015 My SAMS is packed away so I cannot test on the real hardware. 1 Quote Link to comment Share on other sites More sharing options...
+Schmitzi Posted July 28, 2015 Share Posted July 28, 2015 Do you need a copy of the QUEST 5.12K RAMdisk DSR? Do you have the standard CRU, for my list ? Is is changable ? (Do you have a manual ?) Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted July 28, 2015 Share Posted July 28, 2015 My SAMS isn't packed away and I'll test it for you. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.