InsaneMultitasker

For those of you with a TIPI, here is a quick method I am using to assign a folder to a TIPI DSKx device via the command line. Create a DV80 file, call it something like "MAPDSK1", with the following line: ECHO DSK1_DIR=%1>PI.CONFIG Save the file then at the command line type: MAPDSK1 MYWORD This will take the parameter "MYWORD", assign it to %1 in the batch file, and echo the string "DSK1_DIR=MYWORD" to PI.CONFIG. You can verify the mapping by typing the config file: TYPE PI.CONFIG Don't forget to remap the TIPI DSK device to the OS DSK device number via the MDOS REMAP command, unless your TIPI is at CRU >1100 in which case DSK1-4 should be REMAPped by MDOS at startup.

I've gotten so far as to assemble the EDITOR and CONTROL files. I then disassembled EDITOR v1.22 and identified where code was added in three locations to fix boundary conditions and editor mode tests. It still isn't clear to me if the source was edited later or if the changes were removed from the final v1.22 distribution. It is also possible that the V1.22 distribution disk had two (or more) variants: one with the fixes and one without. Disk Utilities reports 14 sectors with differences: some are BSS directives which were not cleared by the tools, others may be code related. It would be good to gather samples of V1.22 for comparison. Since we don't know what tools were used, we have to make a few educated guesses for the remaining programs.

@9640News or perhaps @mizapf can add to my comments. Most of the files in the ZIP are "TIFILES" format. The easiest method to manipulate the files is to use either TI ImageTool or TI99Dir to copy the files into the disk images or location of your choosing. A few PDF files are also included, these are to be read with a standard PDF viewer. The UPDATE file is the release file to describe some of the work and changes. the PFM update utilities are included in the MDOS 7.30 and 7.40 releases,with instructions in TIFILES format. The programs were tested on real hardware using the PFM+ device and PFM 512 (Atmel and Winbond chips). It is important to follow the instructions and preparatory steps.

Just don't call it Colonel! Your comment reminded me of this article about the English pronunciation of 'Colonel', which sounds like 'kernel'. Long ago, I thought the former was spelled like the latter until I used the wrong spelling in a school paper. My English teacher thought I was trying to be funny (I was not). I never made that mistake again. https://learningenglish.voanews.com/a/words-and-their-stories-colonel-or-kernel/3952233.html

This was my thought, too, or batteries not reaching their full charging capacity (if rechargeable). There could also be a malfunctioning component in the circuit draining the batteries prematurely. Over the past year I've had my system off for 3-4 months at a time without any loss of data. The 3000 uses alkaline batteries (the AAs last about 2 years) and the 4000 uses rechargeable batteries.

One thing worth mentioning is that v7.40 is less restrictive and allows you to configure the TIPI, SCSI, and IDE controllers to "any" CRU addresses. (The HDFC is still 'locked' to >1000 or >1100) For the typical user, the prescribed addresses are recommended, however, for those of you weaning yourself from floppy disks, the TIPI can be used at CRU >1100 which will auto-map the DSK1,2,3,4 devices to the TIPI "dskx" devices. There may still be DSR routines that are not fully coded to protect against wrong usage, such as trying to FORMAT A: on a tipi "disk", and I'm not sure that all of the GPL support is 100% functional. 7.40 also implements the SCSI DSR fixes that were identified last year, such as no longer activating ID 0 for all ID calls, and other items noted in the Geneve OS development topic.

Does anyone have the Myarc addendums that includes the various updates to software? There are two on WHT but the more recent updates for MyWord and a few other programs seem to be missing. I checked my printed files and seem to be missing those later addendums, and I no longer remember if they came from Myarc or if they were files on disk for the user to read/print. Nice to see the Myart manual!!

Thank you, @9640News, for keeping things moving to get us to this release point. I attached CRCOS7 and its documentation. Mostly cosmetic changes in the program and docs to account for using either SYSTEM-SYS or SYSTEM"/"SYS, depending on the user's system. We can always corral more programs into a package down the road, like MyWord, MYS/Power, etc. CRCOS74.zip

@jedimatt42 - I updated from 3.13 to 3.14, moved the modifier from the alias mapping "URIx=value" to the open statement, e.g., OPEN #1:"URI1.?J.request.json", and was able to successfully retrieve information via JSON query.

I've trying to pull some data using what to me should be a simple JSON query. I can copy/paste the full result into the JMES tutorial and query it there, but I am having no success with XB. The program halts with "IO Error 37 in 110", the PRINT #1 statement. The log shows 'illegal read mode' but the program never reaches the LINPUT. If I comment out the PRINT statement, LINPUT generates an error as well. Is this another gap in my JSON knowledge? If I change the OPEN statement to "INPUT" mode and skip the PRINT, then LINPUT works and A$ contains all elements. Short program and log in the spoiler. Thank you.

This is advisable when you are not certain a card like the ASCSI is functional as troubleshooting with a TI console is much more forgiving. Your Geneve lockup could be a symptom of a Geneve EPROM that requires an update (and locks up when a file is no found), a bad system or load file, a damaged ASCSI card, etc. Problem isolation is your friend. Edit: Check for shorts between input/ground and output/ground at the regulator. Also check regulator output with nothing else in the PEB, if you have a PEB extender card. The Mini Memory cartridge and most debugger software e.g. SBUG are handy for turning on a peripheral card and inspecting the >4000 RAM address space. I usually start with MM because it doesn't require a disk peripheral or any cards besides the flex interface and the device you are trying to inspect. Minimem steps <do not type the brackets below> C1100 <enter> <1> enter (turns on dsr) <.> M4000 <enter> to view one byte at a time starting at 4000. don't turn on more than one base CRU at a time. Turn off/on the console to reset, or redo the CRU operation with a <0>.

@9640News, I sent you my remaining "cosmetic" OS updates and comments for the 7.40 release. I will check a few utilities for updates since April 2021 and let you know if I think any should be included. As best I can tell, I was trying to fix two related problems but only 'knew' there was one. I wish I had written a simple separate test program last year. It was very tempting to redo the COPY command to utilize the FDR like all other programs, except for the record-to-block IO that is intertwined with the routines. That is, the CON, RS232, and PIO devices. All's well that ends well.

As I think I mentioned to @Lee Stewart during our exchanges at the time, I recalled reading references to (and perhaps explanations for) NUD and/or LED in some of the documentation that members here have preserved from various estates and auctions. I could not, however, find the right documents and searching the forums wasn't fruitful. I was interested in knowing how the terms fit into the Geneve's Advanced BASIC source code (which is derived from XB and Myarc XB) since many labels and some comments reference these then- and still-peculiar terms that Lee asked about. Neat stuff though a bit more advanced than I am able to fully parse myself.

I'm seeing a bit of 'double' text in your post

I re-checked routine >14 and added a test for >15; both are adhering to the same boundary condition. No further concerns from my perspective. @9640News please confirm at your convenience. Log report (two different files; one is an output file) 2023-05-02 22:27:04,700 LevelTwo : INFO direct output 2023-05-02 22:27:04,704 LevelTwo : INFO unit: 0, blocks: 1, filename: TIP, startblock 5 2023-05-02 22:27:04,705 tinames.tinames: INFO TIPI.TIP.TIP -> /home/tipi/tipi_disk/TIP/TIP 2023-05-02 22:27:04,706 LevelTwo : INFO tifiles.getSectors: 5 2023-05-02 22:27:04,707 LevelTwo : ERROR request exceeds file size: t: 1408, s: 1408, e: 1664 2023-05-02 22:29:19,893 LevelTwo : INFO direct input 2023-05-02 22:29:19,896 LevelTwo : INFO unit: 0, blocks: 1, filename: TIP, startblock 5 2023-05-02 22:29:19,897 tinames.tinames: INFO TIPI.2023.TIPS.TIP -> /home/tipi/tipi_disk/2023/TIPS/TIP 2023-05-02 22:29:19,898 LevelTwo : ERROR request exceeds file size: 1408, start: 1408, end: 1664

Update 3.11 resolved the boundary condition error in my test program. @9640News and I will test a bit more, but so far so good!

I think so, provided the reported and/or calculated total size is meant to represent real file size (blocks*256)+128 versus the /4a-side file size (blocks*256). The 128 bytes in the log entry is what caught my attention when I tried to compare block size totals. After the update is released, I'll run my tests on direct input/output. Are there any other operations that might be affected or need a quick test, or is this isolated to direct input/output? Thanks for isolating the cause!

Sounds good. I did not close the loop on my/our end either, as non-hobby items have been the priority for me. Thank you. I can see where clarifying the logging will help, as I didn't notice that there were two entries for 'block 0' I altered my test program to read only the additional info block, and the log shows that activity as unit 0 blocks 0 start block 0. I then ran the complete test. The file data follows the format "blocks 1, startblock x". x starts at 0. The spoiler contains the log.

The MODE command appears to make the baud rate persistent until another MODE command is executed or a cold restart of the OS. This is probably intentional. Walking through the RS232 code reminds me of the opening to Infocom's Sorceror; I feel that I have entered the Geneve OS's "twisted forest"...

This is a good clue for me. The reason I started looking at the tables is that my AUTOEXEC no longer contains a MODE RS232/1:38400 statement, yet the OS is initializing the port at 38.4K, contrary to what is seen in the table and contrary to what I recall from earlier releases. I have not yet determined the reason nor will I delay the 7.40 release for this. I am a bit perplexed though...

MDOS initializes the RS232 ports during a reset. A table manages the settings for the serial and parallel ports. While documenting the source, I realized that the powerup routine is not using the correct table entries. In the code snip below, >0300 is loaded into the RS232 control register. I believe this means 8 bits, no parity, and 1.5 stop bits. I think MDOS should be changed to initialize the control register to >8300 for 8N1. And I see no option in the OS to set 1.5 stop bits; only 1 or 2 stop bits are allowed by the MODE and OPEN routines. * port status flags . . each port gets 12 words . . * first 12 words are last status stuck in buffer * 2nd words are current port characteristics * STATAB DATA STAR1,STAR2,STAP1,STAR3,STAR4,STAP2 STAR1 DATA >0300,>01A1,0,0,0,0 DATA >0300,>01A1,0,0,0,0 STAR2 DATA >0300,>01A1,0,0,0,0 DATA >0300,>0034,0,0,0,0 9600 baud default

Hi @F.G. Kaal I downloaded the latest GDM2K from your web site. Thank you! I am using it now and it is working well. I noticed you included EXEC 2.4G. This is an older version. It is OK to retain because it is the special version by Tony (Gazoo) but it does have some issues that were part of the base 2.4 release. The MDOS 7.30 package included EXEC version 2.7 (Release March 3, 2021) which fixes some bugs and updated the powerup sequence. Maybe include both in the next release? I need to find a way to consolidate my latest versions, in a topic or site, as I had trouble finding the right post/file (Edit: corrected link, clarified a few things)

Logging in on my phone didn't restore the ability to click on the last post time/date to get to the most recent post. So it would seem the "mobile" template is the difference here. I tried your suggestion: I changed the setting from "Take me to beginning" to "take me to the latest content". Now, when signed into my phone, if I click on the date or the topic, it puts me at the end of the latest comment. (which means I have to scroll up to see any posts). On my PCs, I can get to the latest post but clicking on the link to the topic now opens the latest post as well. I don't really like this but I'lll try it out for a while. It would be nice if the old functionality was restored

Hi @jedimatt42, @9640News and I wanted to run something by you related to the level 2 boundary checking fix for direct input and direct output. We seem to be running into a similar situation where we are able to exceed the declared file limit by one block (sector). To confirm what we are seeing, I wrote a short test program that reads a file one block at a time starting with block 0. My example file (TIP-BAD) is a PROGRAM image 1070 bytes in length (4 blocks * 256 bytes/block + 46 bytes in the fifth block) which should present a maximum of 5 blocks via direct input. Here is the pertinent information thanks to TI99Dir: TIPI allows the test program to read a non-existent block 5 and generates an error on block 6. We are expecting the error to occur when trying to read block 5. (Edit: to clarify, the log and input routine are base 0, starting at block 0). The TIPI log reports a file size of 1664 bytes which seems to be the sum of (6 blocks * 256 bytes/block) + 128 TIFILES header bytes. This might suggest that the TIFILES header length of 128 and an extra block are being added to the file size for the bounds check routine. FYI, the file type e.g., PROGRAM, display variable, etc. did not matter - I was able to read one block beyond the true size in all test cases so far. And for reference, I am using the 3.x branch. Thank you.

In my post from April 4, I "linked" to what I believe is the original version, which is the game intended for this month's competition. The later posts contain neat history and variations that I'm sure some of us have not seen and/or had forgotten about for a long while. You still have two days to run the original and give it a try