speccery Posted December 1, 2020 Share Posted December 1, 2020 @jedimatt42 thanks for the support & pointers, I'll take a look. I might add the F18A style 80x30 mode with extended attributes to icy99. Having the ability to have per character cell attributes seems a lot better than only having the 80x24 2-color display - although that is a huge improvement over the 40 columns mode. Quote Link to comment Share on other sites More sharing options...
speccery Posted December 1, 2020 Share Posted December 1, 2020 (edited) 6 hours ago, jedimatt42 said: I'll fix up the building instructions. that'll help, and can fix all my references to xdt99 tools so no editing is required. One more thing - for me "python" runs python2, I am wondering does it link to python3 on your development system? My understanding is that just "python" normally would launch python2 and python3 needs to be explicitly specified. Edited December 1, 2020 by speccery Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 2, 2020 Author Share Posted December 2, 2020 14 hours ago, speccery said: One more thing - for me "python" runs python2, I am wondering does it link to python3 on your development system? My understanding is that just "python" normally would launch python2 and python3 needs to be explicitly specified. I don't use the system python on my machines, so yes, it defaults for my user to python 3. But I like to at least fix my makefiles to not be so assuming. 2 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 2, 2020 Author Share Posted December 2, 2020 find . -type f | xargs grep "\.py" | egrep -v "python3" now shows no python invocations without explicit use of python3 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 2, 2020 Author Share Posted December 2, 2020 24 minutes ago, jedimatt42 said: find . -type f | xargs grep "\.py" | egrep -v "python3" now shows no python invocations without explicit use of python3 but of course I broke things 1 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 2, 2020 Author Share Posted December 2, 2020 8 minutes ago, jedimatt42 said: but of course I broke things ok, fixed. 2 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 5, 2020 Author Share Posted December 5, 2020 Update 1.6 - in post #1 Added date command and bar command. date will print current date time. bar will show a title bar in the top row that doesn't scroll away. Use the CLOCK environment variable to control which source clock device is used. Tested PI.CLOCK ( this is the default if the variable isn't set ), and CLOCK ( classic99, should work for triple tech cards ) Implemented IDE.TIME, but I don't know how I can test it. So maybe you guys can confirm if it works or not... ??? Bar updates about every 15 seconds if the blinking square cursor is displayed. That may change. Inverse colors only operate in F18A 80x30 mode. 40 column display abbreviates 'Force Command v1.6' to just 'v1.6' - it would have fit, but I felt it was too much. https://atariage.com/forums/topic/290966-force-command-ver-16-kinda-like-commandcom-from-1985/ 4 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 5, 2020 Author Share Posted December 5, 2020 Oops, I missed a spot for the IDE.TIME, so don't bother testing that yet. -M@ Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 5, 2020 Share Posted December 5, 2020 33 minutes ago, jedimatt42 said: Hmmm, looks like when things slow down in January I'm going to have to update after all! Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 5, 2020 Author Share Posted December 5, 2020 30 minutes ago, jedimatt42 said: Oops, I missed a spot for the IDE.TIME, so don't bother testing that yet. -M@ Oh, no, the thread title changed again... you know what that means LOL... So the IDE.TIME is worth testing now. 2 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 6, 2020 Share Posted December 6, 2020 Hello @jedimatt42, in my script for FC the command readkey is no longer working. In v0.M and in v1.1 it works as I expect. In v1.5 and in V1.7 the TI hangs with bad sound after a readkey. AUTOCMD.zip I have stripped down my script to test readkey at the command line. The working v1.1 The TI stops with continuous sound after a key is pressed The TI stops with continuous honk sound after a key is pressed This is the system I was testing: TI EU console FG99 with FC Speech synthesizer PEB with TIPI, SAMS 1Mb (incl.32KB) HRD4000B, TI Disk Controller with 80 Track mod. 1 x 5.25 "DS80SD, 1 x 3.5" DS80SD, 1x5.25 "SS40SD floppy drives 1 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 6, 2020 Author Share Posted December 6, 2020 @wolhess Here is a fix: Update 1.8 - fix readkey I moved the readkey command to a different ROM bank, and missed where it called another function without a bank-switching wrapper. 3 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 6, 2020 Share Posted December 6, 2020 (edited) Oh, you are fast !!!! I will make a test. EDIT: It is working now! Thank you. Edited December 6, 2020 by wolhess Tested 1 Quote Link to comment Share on other sites More sharing options...
dgrissom Posted December 6, 2020 Share Posted December 6, 2020 19 minutes ago, jedimatt42 said: @wolhess Here is a fix: Update 1.8 - fix readkey I moved the readkey command to a different ROM bank, and missed where it called another function without a bank-switching wrapper. Hate to bring this up, on v1.8. I noticed that the "xb" and "fg99" are both throwing an blinking error light on my FinalGrom99. Screen just goes green and "stares" at me. (This makes me uncomfortable.). 1.5 seems to work OK. my settings for testing: XBMOD=SXBG XBADDR=25458 For Testing the current 1.8 FC files are not located in the Root of my FG99. Shown, if the above settings are impacting the file execution? 1 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 6, 2020 Share Posted December 6, 2020 1 hour ago, wolhess said: Oh, you are fast !!!! I will make a test. EDIT: It is working now! Thank you. I have another quirk too: I used two different FG99 cartridges in my tipi system and both are working fine. Without any error. I checked TI XB and XB 2.8 G.E.M switch to FC1.8 and back. AUTOCMD.zip But if I use one of these FG99 in my none tipi system I get after some disk access only a blue screen. My none tipi system configuration: TI EU console prepaired with a snug REPL99 card FG99 with XB 2.8 G.E.M. and FC PEB with snug EVPC2 (V9938) RGB output, 32KB memory expansion CorComp Floppy Disk Controller DSDD 3 x 3.5 "DS40DD, 1 x 5.25" DS40DD floppy drive RAVE99 with speech card P-Code Card FC v1.1 is working with this system! 1 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 6, 2020 Author Share Posted December 6, 2020 40 minutes ago, wolhess said: I have another quirk too: I used two different FG99 cartridges in my tipi system and both are working fine. Without any error. I checked TI XB and XB 2.8 G.E.M switch to FC1.8 and back. AUTOCMD.zip 1.19 kB · 1 download But if I use one of these FG99 in my none tipi system I get after some disk access only a blue screen. My none tipi system configuration: TI EU console prepaired with a snug REPL99 card FG99 with XB 2.8 G.E.M. and FC PEB with snug EVPC2 (V9938) RGB output, 32KB memory expansion CorComp Floppy Disk Controller DSDD 3 x 3.5 "DS40DD, 1 x 5.25" DS40DD floppy drive RAVE99 with speech card P-Code Card FC v1.1 is working with this system! At the blue screen, if you blindly type: WIDTH 40<enter> Does the display correct itself? I added PAL detection, and 9938 detection and the 9938 80x26.5 mode a few releases back. These work on the mame eu evpc configuration. This is probably the problem. I've never heard of a REPL99 card... so don't know how that plays into things. Quote Link to comment Share on other sites More sharing options...
+mizapf Posted December 6, 2020 Share Posted December 6, 2020 The REPL99 is from SNUG and delivers the GRMCLK line from the missing video processor. If you have a EVPC card with V9938, you have to remove the 9918/9929 VDP in the console. By this, you lose the GRMCLK as well, so your GROMs and sound stop working. The original way was to use a separate cable from the external EVPC card back to the console. The REPL99 goes into the open socket of the video processor. 1 1 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 6, 2020 Share Posted December 6, 2020 2 hours ago, jedimatt42 said: At the blue screen, if you blindly type: WIDTH 40<enter> Does the display correct itself? I added PAL detection, and 9938 detection and the 9938 80x26.5 mode a few releases back. These work on the mame eu evpc configuration. This is probably the problem. I've never heard of a REPL99 card... so don't know how that plays into things. I will check it tomorrow. Thank you. I wanted to ask for the 80 character support. But I thought I could get it to run normally first. In version FC v1.1, entering width 80 results in the message that is not supported. I will contact you when I have tried this with v1.8. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 7, 2020 Author Share Posted December 7, 2020 For the 9938, I set register 0x08 to 0x08 to enable 64K memory type. I would say, I don't know why I do that. It just seemed to make sense when I quickly went through some documentation on setting up the mode. I verified, this still works on my MAME configuration. If typing WIDTH 40 works, and things look fine, then I believe I'm detecting the video chip correctly, but not initializing it for the mode correctly... maybe need to zero out some registers? I set registers: 0 = 0x04 // 80 columns 1 = 0x70 // text mode, unblanked, with interrupts 2 = 0x03 // pattern name table ( address 0x0C00 ?? this is not on purpose ) 4 = 0x02 // pattern definition table (font) address 0x1000 8 = 0x08 // 26.5 row mode 9 = 0x80 // non interlace So, register 2 is being set wrong, but still functioning in MAME when I place data in 0x0000 for the name table... It should have been showing up as blank for me, as the rest of my code thinks the name table is at 0x0000. Setting register 2 to 0x00 also still works in MAME... so... that's super weird. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 7, 2020 Author Share Posted December 7, 2020 10 hours ago, dgrissom said: Hate to bring this up, on v1.8. I noticed that the "xb" and "fg99" are both throwing an blinking error light on my FinalGrom99. Screen just goes green and "stares" at me. (This makes me uncomfortable.). 1.5 seems to work OK. my settings for testing: XBMOD=SXBG XBADDR=25458 For Testing the current 1.8 FC files are not located in the Root of my FG99. Shown, if the above settings are impacting the file execution? This is still working for me with default XB, and Super Extended Basic, although my module name for XBMOD is SXB_G Quote Link to comment Share on other sites More sharing options...
dgrissom Posted December 7, 2020 Share Posted December 7, 2020 55 minutes ago, jedimatt42 said: This is still working for me with default XB, and Super Extended Basic, although my module name for XBMOD is SXB_G I'll try to rename and or try regular ole Ex. BASIC. It could be it was Sunday and my TI was taking a rest? ? Quote Link to comment Share on other sites More sharing options...
+Vorticon Posted December 7, 2020 Share Posted December 7, 2020 So I finally got the chance to upgrade to version 1.8 from my current version 0.M (yes I know, I'm way behind...). Unfortunately, when FC starts up, it gets stuck at the prompt and I get a constant wailing from the console. No issues if I revert back to 0.M. Is there something I'm missing here? My TIPI is at version 2.12 with TIPICFG at v11. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 7, 2020 Author Share Posted December 7, 2020 1 hour ago, Vorticon said: So I finally got the chance to upgrade to version 1.8 from my current version 0.M (yes I know, I'm way behind...). Unfortunately, when FC starts up, it gets stuck at the prompt and I get a constant wailing from the console. No issues if I revert back to 0.M. Is there something I'm missing here? My TIPI is at version 2.12 with TIPICFG at v11. I don't remember what fileset was used in 0.M, but I did some shuffling between naming the ROM 8.bin or C.bin... If you currently have both a FCMD8.bin and FCMDC.bin, the 8.bin might have gotten loaded, and been incompatible with the launch address baked into the GROM. ?? Guessing... IDK, looking at the code, I think the address in ROM that the GROM jumps into has been pretty stable. The zip has a bunch of files in it now... only FCMDG.bin and FCMDC.bin go on the FinalGROM99. (There should be no other FCMD?.bin on the SD-Card) I believe I switched to a 128k ROM at about 1.0. I increased the start delay time in the FC.FCMD EA5 program that switches the FinalGrom cartridge back to Force Command, since you have to give it more time to load before jumping into the cartridge space. It has been adequate on my system... But that shouldn't be an issue from the FinalGROM99 menu. Unfortunately, this just sounds like the problem I get when I haven't reseated my cartridge in a while. Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 7, 2020 Share Posted December 7, 2020 15 hours ago, jedimatt42 said: At the blue screen, if you blindly type: WIDTH 40<enter> Does the display correct itself? I added PAL detection, and 9938 detection and the 9938 80x26.5 mode a few releases back. These work on the mame eu evpc configuration. This is probably the problem. I've never heard of a REPL99 card... so don't know how that plays into things. No, blind typing width 40 doesn't work in my system. I have no AUTOCMD file in DSK1. and I see no disk access after loading FC. With v1.1 I see the disk access and I get the FC prompt after loading. 1 1 Quote Link to comment Share on other sites More sharing options...
dgrissom Posted December 8, 2020 Share Posted December 8, 2020 On 12/6/2020 at 10:49 AM, dgrissom said: Hate to bring this up, on v1.8. I noticed that the "xb" and "fg99" are both throwing an blinking error light on my FinalGrom99. Screen just goes green and "stares" at me. (This makes me uncomfortable.). 1.5 seems to work OK. my settings for testing: XBMOD=SXBG XBADDR=25458 For Testing the current 1.8 FC files are not located in the Root of my FG99. Shown, if the above settings are impacting the file execution? An update: Everything is now OK! Turns out it wasn't FCMD at all. My TIPI SD card got hosed (We've had a number of power outages in our area. (I believe due to new building projects in our neighborhood.). Thanks to jedimatt42 for reaching out and helping me! Based on what I found on/with the card, its a wonder that FCMD worked at all! Thanks! David G 3 1 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.