Rod Van Orden

INFO UPDATE There are three disk images on the website: EDT/FLR Image contains SYSTEM.FILER, SYSTEM.EDITOR, SYSTEM.PASCAL, SYSTEM.SYNTAX and MODRS232.CODE ASM/LNK Image contains SYSTEM.ASSMBLER, SYSTEM.LINKER, DSV9900.OPCODES, and 9900.ERRORS P-COMPILER Image contains SYSTEM.COMPILER, SCREENOPS.CODE, COMMANDIO.CODE, and SYSTEM.LIBRARY My problem is that I cannot extract these system files for placement on DSK1. I have used TiDir for years without difficulty. And the Message I receive there is that the DSK files I downloaded from this forum are not really DSK files. Therefore Classic-99 can't see them when the p-code card is selected. Are you able to do the file Extractions?

This is more of a file conversion problem. I can't extract the files I need from the DSK images....... It is not a Claasic-99 problem. Rod

Hello all! I have been reviewing the UCSD p-system once again. I have managed to get some success running under Classic-99. This was the result of placing the ROMS and GROM file references into the right places. The main command menu lines come up under Classic-99 V365. H for halt brings you back to the TI Powerup Screen and out of the p-system. There are some Other things it will do. However, the big problem I am having now is with the disk images. The system tries to look for this information on DSK1. And all I receive is error messages saying the files can not be located. The files in question are: SYSTEM.EDITOR SYSTEM.FILER SYSTEM.COMPILER SYSTEM.ASSMBLER SYSTEM.LINKER This information is supposed to be in the DSK files downloaded from the site. However, I have used every tool I've got to try to extract these System Files from the DSK files. And I have not met with any success. I think I have been mixing apples and oranges with the file formats. Does anyone out there in Pascal land have any suggestions? I do have the original diskettes packed away in a safe and dry place. I have all four disks (the fourth one is the Utility Diskette with the 11 utilities. After I set up a new desktop computer, I will try generating disk images of all. As I recall these originals are all SSSD. But I think the file formats aren't exactly right for DSK images. I am looking for suggestions......... Rod Van Orden San Diego, California

Hello, all! I haven't had much time to try things with TurboForth lately. However, I do want to try running the emulators and/or simulator on Android. Recently, a Windows-7 emulator was offered up to Android OS users. I am trying to fire off an EXE file with it. If I am successful, I should be able to emulate a TI-99/4a on my tablet along with TurboForth. Has anyone played with this approach? Rod Van Orden San Diego, California

Lee: I am having some difficulty setting up Classic99 with the UCSD p-System files. I have the DSK files, but I'm stuck on how to set up Pascal on the drives. The message I get when selecting the Editor is: EDITOR.SYSTEM not found. Rod

Gazoo: Thank you for the info and link on the XB V2.5 documentation. It is exactly what I was looking for...... There is a whole lot of TI stuff out here, and sometimes its hard to find the "tree" you need because the "forrest" is in the way...... The sad fact is I have been running XB V2.5 for the past 2-3 years without knowing all the enhancements that Tony Knerr had assembled...... I was using the TI XB manual, and everything worked very well..... Thanks again! Rod Van Orden San Diego, California

RE: UCSD p-System OK. I have two, 8K binary image ROM files, and one, 64K binary image GROM file. Any thoughts on what I should do with them? (Keep it clean!)

Rich: When Extended Basic V2.5 was released, was there some sort of documentation or a manual with it? Or was it just a bug fix for TI Extended Basic V1.0? You have very good documentation for RXB, by the way! Outstanding work! Rod Van Orden San Diego, California

Hi gang! I think you could probably do MULE in RXB 2012 with assembler routine interaction. However, I would strongly encourage you all to gravitate towards TurboForth. If you do TMS-9900 assembly language, do it in TurboForth..... The bitmap graphics support needs to get squared away first (or else use TI Forth). I have found that programming in Forth allows you to test and develop so much easier than the typical development cycle. And you generally have more memory to mess with. By the way, Happy New Year! Rod Van Orden San Diego, California

Howdy, All! Many thanks to the folks who worked on getting Turbo-Pasc'99 in shape. I downloaded the files from the resources here, and then proceeded to try out TP99 with emulator / simulators environments. As mentioned before, it doesn't operate with Ti994w. However, it performs like a champ with Classic99 and Win994a. I did something stooooopid and accidently trashed my Win994a simulator environment. But since I am a "backup" fanatic, I just whipped out all my CDs and restored every file, etc. That gave me an opportunity to redo the file layout and how I use Win994a. That simulator has a hard drive simulation, as well. I installed every Turbo-Pasc'99 file on HDK2, and everthing seems to work fairly well. I placed all my work with TurboForth on HDK1, and TMS-9900 assembly language files on HDK3. Any TI-Forth, or anything else, is still on the simulated "floppies". I must admit, it seems like a "throw back" to actually look at old pascal stuff again. I feel "spoiled" by doing things now in TurboForth. I am actually preferring TF to any other........ It looks like the WiPoSoFt folks put together a pretty basic system to support some, but not all, of the V9918 capabilities. In version 2.0, they delivered Text-1 and Graphics-1 modes, and no delivered support for bitmap or multicolor modes. I don't see sound, sprites and a few other things (pointers, etc). It does support arrays and a whole host of basic routines..... If we can do some in-line code within a procedure, we should be able to make up all the rest of it. But it does seem a little hard to do with only about 14K left. At least they provided a couple of peek and poke routines. That would be a start...... Good job on reviving some software from 1986.......! ROD VAN ORDEN San Diego, California

My transition to Forth programming has been a little easier because I began using an HP-35 calculator back in the late 1960's, early 1970's. Just knowing Reverse Polish Notation (RPN) and thinking in it automatically helped to make Forth a lot easier. Forth is EXTENSIBLE ------ And it (in my opinion) is more powerful than any of the C language variations, and is a lot more easier to handle than trying to do everything in assembler. Knowing RPN and assembly languages will help your efforts as Forth grows on you (and it will)......... Rod Van Orden San Diego, CA

Mark and Lee: I saw your posts here on files with the naming problem. With several emulators / simulators in use, we should all be careful to check the names. As Lee has suggested, if the TI name and the PC name match (Use TiDir and/or the Win994a Manager), then everything will run smoothly. I've caught myself several times now...... I want to name the words routine: WORDS+, not WORDS++. I worked up some fixes, as Lee suggested, and there was some improvement; however, I am strongly considering completely rewriting the WORDS+ routine. I think the original WORDS routine under Forth-83 should remain exactly the same, whenever it returns in the cart (or not). My purpose in putting WORDS+ together is to come up with a more useful tool in addition to WORDS. I have some deadlines I need to meet at work this week, so I'm totally shot until at least mid week. Back to you then. Rod

Lee: Thanks for the look / see. I will finish off the WORDS+ corrections this weekend. Have a good weekend. Rod

Lee: It looks like you and Mark have been really busy here. Things are looking good! I am uploading a file for an expanded version of the words definition. I called it WORDS+ I combined a few things, and I used some of the code you sent me. I'm in the ballpark....... but I'm not finished yet. The routine reads the TF Word Dictionary. However, so far I have not corrected the logic (or illogic) which reads passed the end of the dictionary in memory. This shows up in the last display screen of the running routine. The TF word EXIT seems to be the last word in the dictionary. I could test for that and stop the loop at that point. There may be a half dozen other ways to do this. Anyway.... take a look and let me know what you think. Rod Van Orden WORDS+.zip

Don't worry, Lee. When Einstein came up with E = M C **2, he hadn't run that yet either........... har har har.........! Rod