wolhess

Hi Jedimat42, I'm using a TI Diskcontroller with the 40/80/80 track mod and a 3,5" drive as DSK2 and a 5,25" drive as DSK3. I have no physical DSK1 so it's always mapped to a tipi folder. I used force_command and it works between mapped tipi folders and between a mapped tipe folder DSK1 and my physical drives DSK2 and DSK3 very well. One thing I tested today in force_command 0.8: [1000.TIPI.] <-- tipi root folder $ COPY MM.MM-GER 1100.DSK2. <-- the file MM-GER was in the folder TIPI.MM. copied_block 7 of 7 [1000.TIPI.] $ DIR 1100.DSK2. Diskname: $0 Available: 1438 Used: 65442 Name Type Reclen Sectors -------------------------------------------------------- MM.MM-GER DIS/VAR 80 8 [1000.TIPI.] $ CD 1100.DSK2. [1100.DSK2.] $ DELETE MM.MM-GER cannot delete file DSK2.MM.MM-GER [1100.DSK2.] $ I think the file can not be deleted because there is a dot in the filename after the copy! Wolfgang

Yes, I use DM2K to list files in my TIPI folder, and then select multiple files to copy to a physical disk. DM2K works mostly between TIPI folders and physical drives, but sometimes I get a drive or file error, then DM2K shows me only the physical DSK2 and DSK3 and not the mapped folder in the TIPICFG. I think that was my problem yesterday when I tried to update tipi to 1.40 and it went awry. Today I used some programs like REMIND ME and DM2K and everything works fine. Then I made the update to 1.40 and it works as expected. Everything is OK.

Yes, copy function works very well between TIPI folders and physical disc drive. But DELETE works only from the path you are currently. [1000.TIPI.MM.] $ COPY MM-X 1100.DSK2.MM-X <-- This works very well! [1000.TIPI.MM.] $ DELETE 1100.DSK2.MM-X <-- This isn't working file not found TIPI.MM.1100.DSK2.MM-X [1000.TIPI.MM.] $ CD 1100.DSK2. [1100.DSK2.] $ DELETE MM-X <-- This is working! Wolfgang

No, I only accepted the autoupdate displayed on the TIPICFG screen. Maybe it had something to do with the fact that I used DM2K before the update. Sometimes, when I use the DM2K tool, I get access to the DSK1, DSK2 and DSK3 shown. Yesterday I had DSKx drives mapped to TIPICFG, but only DSK1 displays the TIPI directory. DSK2 and DSK3 both showed the directory of physical drives in the PEB. Then I made a new SD card with vB0.29 and update to vB0.36. Now everything works again with Beta0.36. But I will do the auto update today at 1.40. Now I have created some images of the different TIPI versions with my configurations. So I can try the update with and without DM2K.

Hello jedimatt42, Today I have the update on version 1.40 activated and my TI99 worked about 15 minutes on the update. I thought there is something wrong. The TIPI card LED flashes and nothing happens. After 15 minutes I reset my TI and as I assumed, the PI / TIPI was faulty. The TI could not start anymore. After selecting XB in the FG99 the screen stays blue and the TIPI card is constantly lit. Now I have restarted the PI and then turned on the TI99. After selecting XB or TI BASIC everything seems to be OK. But a CALL TIPI leads to blockage and the TIPI LED lights up permanently. I think I have to create a new SD card. Can I download the version 1.39 or 1.40 somewhere? On your website I found only the version b29. Greetings from Germany Wolfgang

That sounds very good! Yes, please a small tutorial would be very helpfull.

Another question, is it possible to extend the compiler with a userruntime in order to use own assembler routines, which are integrated with LOAD in XB, also in the compiled version? As it works with the XB256 extensions! For example, I would like to use the 40 column mode of XXB or use my own routines to support large integer numbers or floating point calculations. Wolfgang

Hello senior_falcon, I am currently working on a program that can alert appointments from REMIND ME (by John A. Johnson). Here I use the calendar file of REMIND ME, but work with a temporary file, which I would like to delete after editing. This works in XB with: CLOSE # 1: DELETE However, in the compiled program version, the file persists (I use Isabella5). Is it possible to delete files in the compiler version? Excuse me if I make too much effort for you! wolfgang

Hi, the described changes I made exactly as described and it works already almost perfect. Thanks a lot!

Hi Senior_Falcon, Thank you for providing the version 5 of Isabella! To upgrade to Isabella5 do I have to use all the files from the new package or can I simply copy the RUNTIME files? I changed some Files e.g. LOAD and COMPILER for using on "DSK3.", because my programs are using always "DSK1." and they look there for the program config files. Is there a way to use the XB256 / LOAD flexibly from DSK2 or DSK3? At every compiler run, I have to change the DSK1.LOAD to DSK3.LOAD. The first time I use it, the compiler looks for the RUNTIME files on DSK2 instead of DSK3. But this is correct for the second and further compiler run on DSK3. I would wish that the compiler can be consistently start from "DSK3." with all the default settings for compiler and assembler. Only the program should be set of DSK1 or variable as it does. Wolfgang

Happy Birthday wishes you Wolfgang from Germany. I know that very well when it seems that everything is going downhill; My mother is the same age and needs help almost every day. I wish you many more healthy years and lots of fun with your computer hobby and this TI forum. Wolfgang

Yes, Ti99Dir is a great support in programming on a real TI. I see all the directories on my TI system here and test on a second TIPI system. I use the tool to copy files between my TIPI systems and create a backup on the PC. The best, however, is a great overview if I show a listing in Ti99Dir. This helps to edit and troubleshoot the program.

Now I tested it with the old runtim7 and it returns as expected. I do not see any difference between the two runtime versions.

... If you eliminate the lines with CALL ERR, does the original RUNTIME7 detect the error and send the program to line 1000? Or do you need the more recent version I posted ... I had tested with the new runtim7. I like to use the old runtime again tomorrow. Then we see if there is a difference.

Hello Senior_Falcon, my OPEN problem is homemade! In my ERROR routine I have used CALL ERR (C, T, G, Z) to intercept different situations depending on line number. CALL ERR () does not generate an error message in the assembler, but the compiled program stops, so a RESET is required. This happens in the TIPI mapped DSK1. same as in the physical DSK2. Even with the new runtime7 there is no difference. If I use my program without Call ERR, then the program runs as expected! Sorry for the inconvenience! Here is my test program: 100 CALL CLEAR 110 ON ERROR 1000 120 OPEN # 1: "DSK1.TEST", INPUT, DISPLAY, VARIABLE 130 LINPUT # 1: X$ 140 CLOSE # 1 150 PRINT "LINE 150" :: END 1000 PRINT "DISK ERROR" 1010! CALL ERR (C, T, G, Z) 1020! PRINT "IN LINE:"; Z 1030 RETURN 150 Without lines 1010 and 1020 everything is OK!

Can I simple rename the runtime7 for using in my real System? I converted the txt runtime file and it works on the real TI!

Hello, Thank you for your time and support. I had tracked the problem with "open" in my program and had reached the row number 1000 in XB, but not in the compiled version. Maybe that's because my DSK1. Is a mapped TIPI drive. I'll try that again with my physical DSK2. Wolfgang

Hello Senior_Falcon, I created my first XB program after more than 30 years and used your XB compiler. It's great, what speed can be achieved, so the time for the program start of> 3 min. shortened to about 20 sec. Thanks again for this tool. When I switched to a version compatibel with the compiler, I noticed some issues I did not find in the description: Using DIM A$(X) Variables: 1. ACCEPT AT (10,1): A$(X) does not work! This is compiled without error, but when the program reaches the command, the computer locks up. - Workaround ACCEPT AT (10,1):B$ :: B$=A$(X) 2. CALL DP(A$(X),D$,P$) does not work! This is compiled without error, but when the program reaches the command, the computer locks up. - Workaround B$=A$(X)::CALL DP(B$,D$,P$) ACCEPT AT COMMAND DISPLAY AT (24,1):”Continue (Y/N):Y” :: ACCEPT AT(24,16)SIZE(-1)X$ If you enter in XB a “N” or a “Y” you will hear a BEEP In the compiled version you will hear a HONK. That irritated me when testing. OPEN COMMAND ON ERROR 1000 OPEN #1:”DSK1.PROGRAM”,INPUT,DISPLAY,VARIABLE LINPUT #1:X$ CLOSE #1 If the file does not exist you get no error message and ON ERROR 1000 is not working. The program continues with reading something from memory or the computer locks up. - Workaround If I need a data file the program creates the file and stores the filename in a log file. Before I use file name in the OPEN statement, I look in the log file. If the program name exits, the program continues and if not the program creates the new file and stores the new name in the log file. Maybe you can add these hints in the documentation of your next version. regards Wolfgang

WOW, Thank you for the new version. Is it correct that the program only works from the "TIPI.BROWSER" folder and not from a individual path? I tried to load it from my "TIPI.TOOL.BROWSER" path but the program stops with the message no Font file in "TIPI.BROWSER". I'm using your program as a EA5 file and it works fine from the "TIPI.BROWSER" folder. INT1_EA5.zip I converted it with the RAG LINKER

Hello to everyone in this excellent forum. Not everyone regularly looks into the TI-99 / 4A Development Forum, so I want to briefly inform you here about a menu program for TIPI users, which I have provided today under the following link. https://atariage.com/forums/topic/289955-mega-menu-for-tipi/ Please scroll to Message # 4 for the new version and have fun!

MEGA MENU v2.16 - new version - Mai/08/2019 Hello, Today I present my new version of the MEGA MENU program. The program now runs with a standard XB cartridge and the main program is compiled with Senior_Falcon’s XB256 compiler. The speed of the program is quite acceptable (I think!). New in Version 2.16 - You can use Mega Menu with standard XB and hopefully with all XB cartridges - CTRL+T starts the SETUP program You can change the language between English and German with the built-in setup program and you can configure the printer and the file number for saving a menu screen to disk. - Extentions in the MM config menu: - You can specify the boot drive from which the program should start. Default is DSK1. - The path of the program is the default DSK1 mapping for tipi. That can be changed. - For each menu item you can specify a path for DSK1, DSK2 and DSK3 individually. - For using in standard XB and for an EA3 program now a LINKNAME can be configured - The main program and the setup program are compiled with the XBGDP, the Extended Basic Game Developer Package Version “Isabella”, provided from Senior_Falcon. - The Mega Menu program package in the ZIP file installs only one directory "TIPI.MM." in the TIPI main path. All other directories are created under "TIPI.MM.P.XXX". Thus, the program package can be easily tested and, if desired, also removed. Attached is the complete MM package with the program files and the DEMO programs. For installation, all files are simply unpacked into the TIPI directory. "TIPI.MM" contains the Mega Menu programs "TIPI.MM.P" contains the DEMO program folder and programs MM216.zip Here is the new manual: MegaMenu-216.pdf And here is the complete package with all programs in DSSD 80 TRACK disk image files. An Overview of the DSK content and the copy paths is in the pdf on page 14! MM216-DISKS.zip

No, I only use the ti-mode for DSKx mapping.

I did some tests with Tursis scratchpad loader and with the paragon ea5 loader and both are working for me. Now I can run ea5 programs and I get access to PI.http... from standard XB. Thank you.

Thank you for the fast answer, I will take a look at this and make some tests.

Hi Greg, Your Example works in TI BASIC. I tried to call the chatti program from an XB program, but I got a "SUBPROGRAM NOT FOUND IN 10" Is there a solution to do this in XB?