dhe

One addition, I'd like to see, is a hotkey tied to custom keyboard overlays.

One improvement, I don't think anyone will debate is editors with color syntax highlighting! 😃

So the basic steps of compiling a program are: Edit Source>Compile>Link At this point you should be able to go to E/A and run your program. Don't do that yet. Instead, while in development, use: Edit Source>Compile>Link>Load and Run (all from fortran99's menu). Because there are errors, that you will only find out about if you use fortran99's load and run facility. (ie.. E/A will only do what it's told, fortran99 tries to help you out.) In that, Fortran99 is a lot like Assembler. Yep, it all assembles (compiles) nicely, but doesn't run, and will fail silently. Once of course, you verify everything runs as you would like, you can give others your executable and they can exec with E/A option 5. A note about linking, when asked you can skip the part about scan library - that doesn't work very well, so when asked: 'Scan Library Name?' go ahead and give FL - you'll know from the linker listing if you need to add others - READ THE LISTINGS You will also be asked about Symbols, while it appears you can create your own, your given some basic symbols set DSK1.TESTSYM - loading that in with the linker didn't cause any problems. Note: There are some issues with Classic99, I have not been able to nail them precisely all down, but have gotten in to sitations, where DSKx couldn't be seen at all. Getting a fresh start - closing Classic99 all the way, restarting and apply a cold start got everything back on to the correct path. For those interested, here is my classic99.ini >>List ini here<< D:\classic99>type classic99.ini [audio] max_volume=80 samplerate=22050 [Disk0] Type=0 [Disk1] Type=2 Path=D:\classic99\mydisks\DSK1\fortcomp.dsk FIAD_AllowMore127Files=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 [Disk2] Type=2 Path=D:\classic99\mydisks\FORTSRC\source.dsk FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 FIAD_AllowMore127Files=0 [Disk3] Type=2 Path=D:\classic99\mydisks\OBJECT\object.dsk FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 FIAD_AllowMore127Files=0 [Disk4] Type=2 Path=D:\classic99\mydisks\LIST\list.dsk FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 FIAD_AllowMore127Files=0 [Disk5] Type=2 Path=D:\classic99\mydisks\EXEC\exec.dsk FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 FIAD_AllowMore127Files=0 [Disk6] Type=1 Path=d:\classic99\mydisks\utils\ FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 [Disk7] Type=1 Path=d:\classic99\mydisks\scratch\ FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 [Disk8] Type=0 [Disk9] Type=1 Path=d:\classic99\dhe\ FIAD_WriteV9T9=0 FIAD_ReadTIFILES=1 FIAD_ReadV9T9=1 FIAD_WriteDV80AsText=0 FIAD_WriteAllDVAsText=0 FIAD_WriteDF80AsText=0 FIAD_WriteAllDFAsText=0 FIAD_ReadTextAsDV=1 FIAD_ReadTextAsDF=0 FIAD_ReadTextWithoutExt=0 FIAD_ReadImgAsTIAP=1 FIAD_AllowNoHeaderAsDF128=0 FIAD_EnableLongFilenames=0 IMAGE_UseV9T9DSSD=0 DISK_AutoMapDSK1=0 [CF7] BIOS= Disk=.\cf7Disk.img Size=134217728 [emulation] AVIFilename=C:\Classic99.AVI cputhrottle=1 systemthrottle=0 maxcpf=48388 pauseinactive=0 ctrlaltreset=0 invertcaps=1 speechenabled=1 system=1 slowdown_keyboard=1 ps2keyboard=1 sams_enabled=1 sams_size=3 [joysticks] active=1 joy1mode=0 joy2mode=1 [roms] cartgroup=0 cartidx=2 [video] FilterMode=4 frameskip=0 fullscreenmode=6 heatmapfadespeed=25 hzRate=62 MaintainAspect=1 EnableF18A=1 Enable80Col=1 Enable128k=0 InterleaveGPU=1 StretchMode=2 Flicker=0 ScreenScale=1 ScreenX=650 ScreenY=472 topX=1247 topY=355 [debug] ScrambleRam=0 CorruptDSKRAM=0 [tvfilter] hue=100 saturation=100 contrast=100 brightness=100 sharpness=100 scanlines=1 [LastDiskMRU] MRU1=D:\classic99\mydisks\EXEC\exec.dsk MRU2=D:\classic99\mydisks\LIST\list.dsk MRU3=D:\classic99\mydisks\OBJECT\object.dsk MRU4=D:\classic99\mydisks\FORTSRC\source.dsk MRU5=D:\classic99\mydisks\DSK1\fortcomp.dsk MRU6=D:\classic99\mydisks\dsk1\FORTRAN.DSK MRU7=D:\classic99\mydisks\dsk1\fortrancom.dsk MRU8=D:\classic99\mydisks\dsk1\fortran.dsk MRU9=D:\classic99\mydisks\dsk1\TP99COMP.DSK MRU10=D:\classic99\DSK1\TP99COMP.DSK [LastPathMRU] MRU1=d:\classic99\mydisks\scratch\ MRU2=d:\classic99\mydisks\utils\ MRU3=D:\classic99\mydisks\exec\ MRU4=D:\classic99\mydisks\utils\ MRU5=D:\classic99\mydisks\list\ MRU6=D:\classic99\mydisks\object\ MRU7=D:\classic99\mydisks\FORTSRC\ MRU8=D:\classic99\mydisks\DSK1\ MRU9=D:\CLASSIC99\MYDISKS\DSK1\ MRU10=D:\classic99\mydisks\dsk2\ [LastCartMRU] MRU1= MRU2= MRU3= MRU4= MRU5= MRU6= MRU7= MRU8= MRU9= MRU10= D:\classic99\

Vorticon, One of the items I noted reading through the errata, was the support for predit. That by far was my fav editor. I tried multiple times to contact Thomas Bentley to see if I could get the source code. (no luck on even the contact). Do you know where I could find the program and manual? It's a real let down, that FORTRAN has such stringent column requirements, yet the editor doesn't show what column your end! 😃 If anyone has contact information for Al Beard, I'd be happy to reach out to him, and see if he still has source and would be willing to share. Dano

Thanks Vorticon.

I told you all.... We should have bought the extended warranty! 😃 For cleaning, either CRC or Deoxit seems to be favorites. so to sum up... Work the tops if you can. I used old business cards to clean contacts and GROM ports, thne if you have to remove just the bottom and reflow just the bad keys with new solder. I've used: MG Chemicals 8341 No Clean Flux Paste - it does a very good job of making solder flow on older connections.

That's beyond strange...

The fortran99 challenge: 1) Download the fortran99 disks that are available here on atariage. 2) Use them with your favorite emulator. 3) Write a simple 'hello world program' 4) Let everyone know: a) emulator used. b) steps taken to compile and run. I've failed, I hope many of you can do better! Thanks, Dan

I had the same problem, after pulling my TI out of the closet where it had set for 20 years. Most likely problems no contact when key is pushed down. The fix can be easy if you have an old style keyboard. Take off the key cap, take some contact cleaner on a piece of paper, slip it between the two pray-mantis hands - push down on the key, pull the paper with the contact cleaner out. Repeat several times. If it's a newer style keyboard with a Mylar back it may require soldering and or drawing new traces. I was that guy, who pulled all of his black keyboards out and replaced them with keyboards from radio shack, because I liked the feel better, woe be unst me, 40 years later.... d.

C234567 20 FORMAT (F15.5) 30 FORMAT ('NUMBER') WRITE (6,30) CENT = 0.0 READ (5,20) CENT

Any users out there? I downloaded the disks from atariage. I tried setting them up both as a fiad and as a disk with classic99. That didn't make a difference. I have a simple program that writes (or should 'hello world' and waits for a return to be entered). Compiles with zero error. Link - no errors - create a program sample_x and sample_y. When I try to run sample_x - it loads, but then runs the linker from fortran99 - so I believe somewhere the linker isn't working as it should. Looking at the object file I see some of the strings from my source code. dano

Thank you for your work on the emulator. I initially tried to use WorkShop to rename the disk, that of course didn't work out well for me!

Thanks for the heads up, it took me a while to figure out the combo of tidir and settings in classic 99 to make everything happy.. I'm might not be done, but I'm on my way. I eventually, through a long journey had to go the *.dsk route, as the fortran compiler is really coded for dsk.fortcomp.* - so in this case the disks name was essential. d.

Hi, I downloaded the fortran (disk/files) available here on Atariage. Looking at the files - they have a TIFILES header. I'd like to use these with Classic99 - what is the easiest way to convert these to a compatible .dsk file? Also, so there an image for a DS/DD .dsk file for classic99? Thanks, Dano

once we settle on an algorithm, I'll give a shot at doing it in fortran99.

Maybe next year we can have a contest of sorts. Well make sure everyone uses a standard algorithm and people can pick a language to calculate PI in?

At the time, I didn't figure Tony Lewis would have spoken about a card, unless he was pretty far down the road, not like Randy Holcomb of Computer Shopper, who for almost a year said 'next month' well put a tms9995 accelerator in a console.... Since we strayed to relatively rare hardware, there where some guys at a Chicago Show in the late 90's - they where hot in to the Geneve. I think they wrote a hypercard application in forth. I also seem to remember they were going to make a forth processor card for the geneve, I didn't pay much attention at the time, because their projected price for the card, was more than the geneve itself. But they were showing some demo's and boy that card could compute. I think, it was based around a commercial chip that was just a forth engine? Maybe on of these: http://www.ultratechnology.com/chips.htm That card would be another truly RARE item, if it made it's way to ebay! 😃 d.

The ESD Floppy & Hard Drive Controller works great when paired with Tony Lewis's Co-Processor Card (I crack me up)!

Intro from Michael Bunyard of the Bunyard Manual Fame. If any additional questions come up, I will bundle them up and send them off next week. Dano The TI Home Computer System My involvement with the TI-99/4 and A was minimal, but I was working on a sister program in the same physical area that could have been the first PC. I knew basically what was going on with the /4, though. While our product was being evaluated by a potential customer, the TI computer division based in Houston found out what we were doing, and they decided that they were better equipped to supply this product even though their solution would cost twice as much as ours and occupy much more space. Our potential customers were not impressed with the new TI solution to their problem, but we had been shut down. I chose not to transfer to the new solution group, but I chose to stay in Lubbock to work in the Test Equipment Group. I am pleased to note that we were using a text editing program (PDWF) on the larger TI systems at this time that was a significant help for writing (and preserving) specifications, etc. PDWS was adapted to run on the TI PCs, and I continued to use it there. In the Test Equipment Group I built some test equipment for the /4 Production area. The TI99-4 was designed by new hires that had no design experience, and apparently never consulted TI device literature on the 9900 uP that indicated that a short etch across the device connection was required for the two Ground pins. It turns out that one Ground pin served the I/O buffers, and the other served the uP logic. The former task had momentary short term current spikes, and it required special bypassing. Additionally, there were some race problems in the DRAM design area that were never quite resolved. This was also true for the magnetic tape READ/WRITE circuitry. Finally, TTL compatibility for the custom devices was never specified. Thus, the /4 and /4A were not easy to fabricate in production. The /4 physical configuration was changed to another keyboard for the /4A, but that was about all. The product was still hard to build. The next /4 system improvement was the Expansion Box. Our slang for the Expansion Box was the “Johnny Box”. We named it after the Software Manager in our area. I was in that effort from the beginning, and did most of the design work. I slightly modified the existing P-Code and Disk Controller designs. I started over on the RS-232 board to comply with upcoming noise requirements, and I redesigned the timing and control of the DRAM Card. I felt we had a decent design for the Johnny Box, and it passed EMI tests. We also designed in plans for later expansion. Gate Arrays were just coming out in about 1981, and I was asked if I would design one for the /4A. I had previously provided a processor design as a trial design for Jack Kilby’s group for one of the first TI gate arrays. I said yes, and then designed a gate array to eliminate much of the discrete /4 logic. This was the quality improved or /4QI, but there was another problem that existed and it arose. It seems that our purchasing group had ordered enough components to last the projected life of the /4A in order to get the lowest prices. Thus, it didn’t make financial sense to implement this change. I still have a /4QI that was given to me. Another group was put together to design a replacement for the /4 series with much more power as well as a much better user interface. This was the Armadillo or 99/8 and this was in the 1982-83 time frame. It was not long before that program was shut down. I still have a set of the specs I wrote for that machine. About 50 of the production design /8s were built. I used the new 16Kx4 DRAMs which eliminated the DRAM race problem. TI and many other companies tried to set the price of a component in an effort to lower component costs. The effects of this concept were not pleasant. The main TI /4 problem surfaced in the transformer area. When a vendor price was set by the user, the vendor had to cut costs to make a profit. In a transformer, copper wire and steel “laminations” for the core are the major costs. Decreasing the size of the copper wire produced more transformer heat generated for the same load requirements. The same holds for decreasing the “iron” in the core. Several product vendors had fire trouble, but to my knowledge, TI didn’t. Corporate management came to Lubbock to make sure it didn’t. I was not involved in this in any way. I personally think that this problem was the straw that broke the camel’s back, for the Home Computer program was shut down shortly thereafter. Additionally, the TI CEO had just lost his life while in Europe; so, the upper management levels had changed. I will close with a bit of philosophy. I believe that simplicity is excellence. The best design is something that the production operation can understand and fabricate rather than the most sophisticated design. I used this philosophy in my designs. I just happened to be in the right place at the right time to get to do several things that nobody else got to do.

I guess given my own recent issue with cc-40 memory upgrade chips and what I'm reading in a number of threads on this forum... When getting CFC (Chips from China) to attempt a repair, one should take each chip with a grain of salt and either check it in a working unit or in a tester, before trying to use it in a repair to save hair pulling.... Getting a sealed and tested chip from Newark is now a thing of yester year.... =(

Let me try again, if one needs to buy working 9938's where does one go? 😃

What was the seller name of the good 9938?

Ok... Lucky Day Today, and confirming having tools pays. I received two more 8K 6264, this time, I tested both with the TL866 BEFORE doing an install. Both checked good. I installed them in the two sockets, I'd installed and got System Initialized, and FRE(3) - reported the correct amount of memory. I still have a few pixel rows out. I ended up replacing the LCD Display in my Tandy Model-1 PC - 4 times (don't ask). So I'm betting the CC-40 uses Z-Strips, they would mean I need to unhook the display and clean all contacts with IPA. I think I'll wait until I can find a cheap unit on ebay, before I try my test. I'd like to thank everyone who offered advise to help me finish up this project. d.

ok... this is fun... I'll see Gary's Thermal Printer, and Raise you a Hexbus adapter! 😃

Where's the SAM's PhotoFacts when you need them? 😃