wolhess Posted December 21, 2020 Share Posted December 21, 2020 Hi @jedimatt42, With version 1.11 my AUTOCMD script no longer works. I only get the system prompt. AUTOCMD1 I then made a simpler script and it worked up to the readkey command. Readkey is not executed - the system prompt appears. AUTOCMD Everything worked with V1.10. 1 Quote Link to comment Share on other sites More sharing options...
+Vorticon Posted December 21, 2020 Share Posted December 21, 2020 37 minutes ago, wolhess said: Hi @jedimatt42, With version 1.11 my AUTOCMD script no longer works. I only get the system prompt. AUTOCMD1 3.13 kB · 1 download I then made a simpler script and it worked up to the readkey command. Readkey is not executed - the system prompt appears. AUTOCMD 384 B · 1 download Everything worked with V1.10. I noticed that. Anything that came after setting up XB did not work. However, setting up XB at the end of the script solved the problem. Quote Link to comment Share on other sites More sharing options...
dgrissom Posted December 21, 2020 Share Posted December 21, 2020 I have to agree with wolhess & Vorticon My AUTOCMD stops processing at XBMOD=SXBG After it fails: I have a script/batch named "X" (One letter because I am a lazy typist. ? ECHO PLAY CHRISTMAS MUSIC CD TIPI.MUSIC.TIXMAS STARTXMAS "STARTXMAS" start doesn't run. It is a READKEY menu script with 10 selections. (First line is "BEGIN:") Quote Link to comment Share on other sites More sharing options...
+Vorticon Posted December 21, 2020 Share Posted December 21, 2020 4 minutes ago, dgrissom said: I have to agree with wolhess & Vorticon My AUTOCMD stops processing at XBMOD=SXBG After it fails: I have a script/batch named "X" (One letter because I am a lazy typist. ? ECHO PLAY CHRISTMAS MUSIC CD TIPI.MUSIC.TIXMAS STARTXMAS "STARTXMAS" start doesn't run. It is a READKEY menu script with 10 selections. (First line is "BEGIN:") Try moving your XB setup commands to the end of the script. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 21, 2020 Author Share Posted December 21, 2020 I'll fix it today. Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 21, 2020 Author Share Posted December 21, 2020 Looks like I totally broke scripting... part compiler not behaving like I expect, and part me missing an increment command. We'll see. 1.11 is a dud. 1 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 21, 2020 Author Share Posted December 21, 2020 @wolhess, @dgrissom, @Vorticon Update 1.12 - fixes this mess. 3 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 21, 2020 Author Share Posted December 21, 2020 (edited) so, I'm more of a defaults kind of user... or the defaults are what I use.. LOL.. so when I switched the script file closing to be only approved commands, any variable assignment fell into the unapproved commands... ( they don't have well known names, since users can set their own for their own purposes. ) Anyway, setting variables still closes the script... I'll try to prevent that in a later update. But now it resumes properly. Note: because it closes the script, and then to resume has to sequentially read from the beginning of the file to the next line, setting environment variables will be most efficient if they are up front (for now) Edited December 21, 2020 by jedimatt42 Quote Link to comment Share on other sites More sharing options...
fabrice montupet Posted December 22, 2020 Share Posted December 22, 2020 (edited) Happy to see the SYSINFO Command! Just for information: On my European computer, SYSINFO displays "TMS9918A PAL". In fact, it should display "TMS-9929A" because a TMS-9918A is only for NTSC. Do you plan to allow the creation of a simple text file on a device? Like COPY CON as on MS-DOS. It would be very practical to quickly and autonomously create AUTOCMD files. Edited December 22, 2020 by fabrice montupet Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 22, 2020 Author Share Posted December 22, 2020 17 minutes ago, fabrice montupet said: Happy to see the SYSINFO Command! Just for information: On my European computer, SYSINFO displays "TMS9918A PAL". In fact, it should display "TMS-9929A" because a TMS-9918A is only for NTSC. Do you plan to allow the creation of a simple text file on a device? Like COPY CON as on MS-DOS. It would be very practical to quickly and autonomously create AUTOCMD files. Thanks for the TIP... I knew 9918 was a little wrong if PAL, but wasn't confident I could assert the 9929A. Then there is the NTSC 9928A, ( I think, and I don't believe that is detectable.. or matters, custom one-off mods ) 9938 and 9958 can be switched PAL or NTSC, but the chip is detectable directly. --- I'd like to get to '>' output redirect, probably not ever going to get to '|' pipe or '<' stdin in redirection. But I'd prefer to have a tiny embedded editor, and solve that problem in a better than minimal way. Quote Link to comment Share on other sites More sharing options...
fabrice montupet Posted December 22, 2020 Share Posted December 22, 2020 Yes, a real embedded text editor is the better solution, it is also my opinion. In fact, I thought about the command COPY CON not to give you too much work ? 1 Quote Link to comment Share on other sites More sharing options...
fabrice montupet Posted December 22, 2020 Share Posted December 22, 2020 (edited) I am surprised by how the COPY command works. Configuration used for the test: a stock TI-99 / 4A, a TI floppy disk controller, one single floppy drive. The floppy disk inserted in DSK1 contains the BASIC program: TEST I type: >CD DSK1 >DIR FC lists me the contents of the floppy disk: NAME TYPE P RECLEN SECTORS ---------------------------------------------------------- TEST PROGRAM P 81 16 Everything is normal so far. Now, while I don't have a second drive, I type: > CD DSK2 The command is accepted. This seems to mean that the management of a disk in DSK2 is accepted. So, I type: > DIR The command is well accepted and just sends me a carriage return. But it shouldn't because this drive is missing. We should see displayed: "No disk in Drive" or better : "No Drive". Because otherwise, one could be tempted to launch a command of the type: > COPY DSK1.TEST DSK2 Which of course doesn't work. Edited December 22, 2020 by fabrice montupet 1 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 22, 2020 Author Share Posted December 22, 2020 Yes, DIR not erroring is something I just haven't gotten around to fixing. This error is not limited to floppy controllers. Quote Link to comment Share on other sites More sharing options...
+Vorticon Posted December 22, 2020 Share Posted December 22, 2020 11 hours ago, fabrice montupet said: Do you plan to allow the creation of a simple text file on a device? Like COPY CON as on MS-DOS. It would be very practical to quickly and autonomously create AUTOCMD files. I was just thinking that the other day. That would be a very handy feature indeed. I second the request, although I suspect it's not a trivial one by any stretch. 1 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 22, 2020 Share Posted December 22, 2020 18 hours ago, jedimatt42 said: Update 1.12 - fixes this mess. Yes, now all works again! Thank You! 1 Quote Link to comment Share on other sites More sharing options...
Asmusr Posted December 26, 2020 Share Posted December 26, 2020 On 12/22/2020 at 1:30 AM, jedimatt42 said: Thanks for the TIP... I knew 9918 was a little wrong if PAL, but wasn't confident I could assert the 9929A. Then there is the NTSC 9928A, ( I think, and I don't believe that is detectable.. or matters, custom one-off mods ) 9938 and 9958 can be switched PAL or NTSC, but the chip is detectable directly. I don't think the 9928A is used in any TI model. It's either 9918A NTSC or 9929A PAL. F18A NTSC is also misleading. To be consistent it should be F18A VGA. 2 Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 26, 2020 Author Share Posted December 26, 2020 4 hours ago, Asmusr said: I don't think the 9928A is used in any TI model. It's either 9918A NTSC or 9929A PAL. F18A NTSC is also misleading. To be consistent it should be F18A VGA. How about 50hz or 60hz as the point is the interrupt rate. 1 Quote Link to comment Share on other sites More sharing options...
Asmusr Posted December 26, 2020 Share Posted December 26, 2020 3 hours ago, jedimatt42 said: How about 50hz or 60hz as the point is the interrupt rate. Yes, that would be my preferred option. 1 Quote Link to comment Share on other sites More sharing options...
wolhess Posted December 28, 2020 Share Posted December 28, 2020 Hi @jedimatt42, with the version v1.12 of Force Command the prompt command does not work as described in the wiki. Now I can make all character after the "prompt=" to the system prompt. Is this right? What about the crubase or the drive/path information? Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 28, 2020 Share Posted December 28, 2020 Sorry to bother people with very basic questions, but I'm starting all over from scratch with the new versions of Force Command and the TIPI versions, I've also decided to make Extended BASIC 2.8 GEM my BASIC of choice due to the built in T80XB routines. With that in mind, I really need the following two questions answered... XBMOD= (for the cartridge) XBADDR=(for the entry point at T80XB) Thanks! Quote Link to comment Share on other sites More sharing options...
dgrissom Posted December 28, 2020 Share Posted December 28, 2020 Omega-TI I've not used the 80 column version. (Alas, another Christmas with no video upgrade. ? ) Check the link below for most of the listings. I didn't specifically see a 80 column in the list. I have used the 40 column (T40XB) a number of times. Commands · jedimatt42/fcmd Wiki · GitHub DavidG Quote Link to comment Share on other sites More sharing options...
+jedimatt42 Posted December 28, 2020 Author Share Posted December 28, 2020 I may have to update that page if the cart menu for GEM has changed. 2 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 29, 2020 Share Posted December 29, 2020 17 hours ago, jedimatt42 said: I may have to update that page if the cart menu for GEM has changed. As of yet, I'm unaware of a published entry point for the T80XB XBADDR. Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 29, 2020 Share Posted December 29, 2020 On 12/28/2020 at 1:14 AM, wolhess said: What about the crubase or the drive/path information? Yeah, I've noticed that too! Whenever I change the prompt to something else that valuable information vanishes, so I had to type: "PROMPT=" to revert to normal. I guess my OCD is showing over a ">". Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted December 29, 2020 Share Posted December 29, 2020 @wolhess In that AUTOCMD file: ... have you thought of adding the SYSINFO command? It's kinda neat, even if it does not recognize a Triple Tech card. 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.