wolhess

Here it is: Disk memory System p22p23.pdf

Hi Omega, if I do a CALL FC from XB40 and/or XB80 it works in my tipi system fine. But I don't have a F18A or a 80 column card in my tipi system! In my none tipi system with a 80-Column card I can't run the command CALL FC because I get an error message. This is I think it needs the tipi system. But I can run FCMD from my MEGA MENU program with RUN an EA5 program (item 4) even with an EA5 loader from XB 2.8 and XB T80.

Hi @senior_falcon, I tested your new version right now and it works perfect, even if I break my program and make a CALL HELP the font and colors are right. Thank You!

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?

Hi Beery, I tried my XB catalog program on real TI with TIPI and I can show all 3000+ files of the DL folder. It takes more than 30 minutes to display all files. The XB program shows the files all in alphabethical order and if I have folders there are also in alphabetical order between or with normal files. Here is my version of the XB CAT-program modified but based on the one from the TI Disk-manual: It accept 1-9 and A-Z for DSK1. - DSK9. and DSKA. - DSKZ. It also accept a TIPI path like TIPI.AH.DL with or without the last dot. The program maps a tipi path to "DSK4." and if you only have entered "TIPI" or "TIPI." then "DSK0." is used. XDIR

Hi, I checked the new version and tried to use CALL HELP. If I break my Mega Menu program (same compiled version as in post #357) the color and font it is good but if I then CALL HELP I get a wrong color and font! After HELP finished I get the correct font and color again. I tested it on real TI and in classic99 with same results. When I run XB 2.8 from FG99 without autoload and tried then the CALL HELP command the color and font is good.

Yes, now all works again! Thank You!

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.

Hi, The difference is that in tursis EA module the editor and asembler are in the module and do not require a disk. Here is the bin: NEWEAG.BIN

Yes, I used three physical disk drives DSK1, DSK2 and DSK3 to load the EA5 program EDIT40 from the EA module! Before I unmapped these drives from the tipi system, so I have direct access to the real floppy disks. I also have the tipi on cru:1000 and the TI-Controller on cru:1100 and I used the TI-EA module from the FG99. EDIT: I just tested with Fred'S EA IV and EA V (newest release) and it doesnt't load from option 5! Then I tested it with tursis EA complete and with this it is working fine like with the original EA module.

I can run EDIT40 from physical disk drive 1-3, from tipi maped DSK4. and from Ramdisk DSK5. All running with TI Editor/Assembler Option 5 without a problem. Wolfgang

Hi Harry, The font problem after break is solved with your new version. Many Thanks! Wolfgang

Unfortunately not, the error message "ERROR 007 File error" remains when EDIT4080 is started by AUTOCMD. If I run it from the command line with LOAD DSK2.EDIT40 it is working!

Hi @jedimatt42, I think your assumption is correct. The VDP interrupt is generated on the EVPC2 card for the VDP RAM (192KB) there. And in the console I had to disconnect the EXTINT connection to the PEB. You can see this in the REPL manual on page 15. repl99x.pdf It's in German, but the picture tells you something! I'm using a PAL console, but it seems to work without a problem.

Hi @jedimatt42 Today I have tested version 1.9 and 1.10_test in my PEP Disk Only System with EVPC2 (V9938). After turning on PEB and console for the first time, the system continues to hang with a blue screen. If I the reset the FG99 or powercycle the console, both versions are working with 80 characters per line. Super!!!! I can start XB directly from AUTOCMD or from the command line. I can also run any EA5 program. However, I noticed two things: 1. When I run Fred Kaal's EDIT4080 v3.0 from FC and want to edit the DSK1.AUTOCMD file, the following error message appears immediately without disk access: Other text files from DSK1 or DSK2 I can open and edit without problems. If I run the EA cartridge (TI, EA Complete or Fred Kaal's EA V v5.6) I can load and edit the DSK1.AUTOCMD file. EDIT: If I load DSK1.EDIT40 from the command line then I can open and edit the file DSK1.AUTOCMD! 2. When I try to start an XB program with "XB TEST" I get the following error message. Note: I don't have a TIPI card in this system! Maybe it works only with tipi. Thank You for making this version, so now I can use 80 column FC in my TI system with the EVPC2 card. Wolfgang

This is my preference too.

Yes it autoloads direct from any XB. Right now I tested it in classic99 so I'm sure the same result is with classic99 and it is! MM252C99.zip You must map the folder in the zip file as a FIAD folder for DSK1. in classic99 and deselect "Write DV80 as Windows Text". Then run your XB. The program will autoload and show the main menu screen. If you then make a break (FCTN+4) you will see the magenta font. The menu selections doesn't work at all because I'm using a TIPI configuration. For a small test you can try selection "7" KALENDER or Selection "E" - EDIT40. After Quit the program "Remind me" or the "Editor" you come to the TI Title screen and can run the XB 2.8 again. This works on my site. This is a small manual for the complete program: MegaMenu_252.pdf Thank you for your time an effort.

Hi @senior_falcon, thank you for working on my issue. Today I tried the new version XB28GEM1208 and I got nearly the same result as before. But if I now reload XB2.8 the colors are correct even if I run without autoload. Only if I break (FCTN+4) my Mega Menu program, then the colores are changed like in this picture.

Yes, now ALLFILES is correct too and the tool is working perfect. Thank You @BeeryMiller

Hello, the CALL PEEK(8198,A,B) is: 170,85 but the CALL PEEK(9456,A,B) is: 131,160 The MegaMenu program was compiled with the runtime routines in low memory and loads with 32K loader as a large program. It shows 6944 Bytes left and low memory 15366 - 16383 free. The program is fully working and I usually don't break the program. If I run a XB program from the menu it works with the normal color and font. And here are the result of your second message about call peek(9436,....) If I run the program from the XB prompt and from the screen above the color changes to Black on Cyan. So a second run and any further run shows Black on Cyan. I have no custom font configured. I use the default files as provided. Only at the magenta screen I use CALL LOAD(9456,23,2) to get a better readable screen:

This is working. After RUN I see the strange screens and the message: If I break the program I get the color and font I assume: If I autoload my Mega Menu program in XB 2.8 I see this: It is correct! If I break the program the color and the font is changing to this: If I run XB 2.8 without autoload I get this font from the beginning: I think this is not the default font, but I will try to patch the bin file with my default color/font.

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.

@BeeryMiller, the fileCreator version 4 is working without an error. The BBS Library files are all correct. Only the file ALLFILES is not correct in the header. The value of level 3 is still >3F XX but this causes no errors.

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.

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!