Search the Community
Showing results for tags 'Diamond GOS'.
-
It was suggested to open a new thread, so here I go. Simply put, I'm trying to run Diamond GOS 3.0 with the utilities disk in Altirra 4.01. After some struggle I've gotten Altirra seemingly working, GOS boots, but when I install the utilities disk I only get this error. Current Altirra setup: Base system NTSC 130XE Additional Devices None OS Firmware Atari XL/XE OS ver.3 [29F133F7] Mounted Images Disk: Diamond GOS3 Utilities.ATR [93FCA643] Cartridge: DIAMGOS3.ROM [3671BDC5] I am brand new to this, so I don't know enough to know whether I'm making an Altirra mistake, a Diamond GOS mistake, or a general Atari computing mistake. The extent of my Atari computing experience is being fascinated by Basic Programming for the 2600 as a kid, and trying for the last few weeks to get this emulator working. I have never experienced the real hardware. I don't know whether the GOS manual left out a step that was too obvious to need explaining at the time, or if I've broken something that normally just works. Has anyone gotten this working in Altirra? Or if you've gotten it working on real hardware, is there something to the procedure that might not be obvious to a newbie who has only tried emulation? Thanks to anyone who can help. And thanks to this forum for saving GOS 3.0 from becoming lost.
-
Every computer needs a metronome program but only a few Atari8 owners have the Diamond GOS to run this one and even fewer would want to build the simple hardware to hear it. {video removed} It may have been easier to write this one in BASIC but I wanted to get back into Assembly and thought a metronome based on the software timer example in De Re Atari would be a good place to start. The original idea involved pulsing the Cassette Motor Control(CMC) pin on the SIO, then it evolved into a metronome with a bunch of options, and then it digressed back into controlling the timing of the CMC. The first problem was getting the tick to make a reliable POKEY sound. Most of the programming changes seemed to make the problem worse until it stopped entirely. A LED and 330ohm resister was used on the CMC pin to monitor its blinking. It did blink. Gone was the POKEY sound. The second circuit was thrown together with a speaker salvaged from a greeting card. This clicked and blinked. (and hasn't burned out yet) A slider bar to adjust the BPM was going to be programmed but by the time the math started working, Two arrow icons were used. Click one icon to increase the DLI counter (1 = 1/60 second). Click the other to decrease. The DLI counter can be set between 15 and 155 - 60ths of a second(240 - 23 beats/min). This kept the math programming to a minimum and the values were limited to 3 figures to simplifying printing them to the screen. If you find the greeting card speaker to be inadequate, I programed an Arduino to check the output from the CMC and send out a MIDI - NOTEON,C2,127 for each pulse it detects. This so happens to be the base drum. /* This program accepts a digital input to activate * output to a midi device. * * used to test dMetronome on the Atari 130EX. * digital signial from Cassette Motor Control. */ int inPin = 5; //pulse input pin int pulse; //logic value of pin int midiCommand = 153; //noteon channel 10 int midiNote = 36; //C2-base drum int midiVol = 127; //volumn max int midiVolOff = 0; //volumn off void setup() { pinMode(inPin, INPUT); Serial.begin(31250); //midi baud rate } void loop() { pulse = digitalRead(inPin); if(pulse == HIGH){ //send midi data Serial.write(midiCommand); Serial.write(midiNote); Serial.write(midiVol); delay(5); Serial.write(midiCommand); Serial.write(midiNote); Serial.write(midiVolOff); } } The program is on the ATR and titled DMETRON.APP. Boot up with Diamond and connect you device. I have tested the program with Diamond 3.0 on a 130xe using DOS 2.5. It should run on Diamond 2.0 because the diamond functions used are in both carts. dMetron_atr.zip Those long assembly language listings in Analog always intimidated me. I tried splitting up the program into smaller files and #including them. I thought that working with a group of small files would help and it did in some ways. I could test many of the subroutines independent of the others and could find the locations of interest if I remembered which file was of interest. It did slow down development near the end when the locating the numbers on the screen required tweaking. There were two function calls in two files to set up the display. It ended up being somewhat tedious. MAC/65 source code for central program. The rest is in the zip file. DMACROSM.M65 are the diamond function macros with Paraprint modification as described in a previous blog entry. 0100 ;dMetronome 5/2018 0110 ; 0120 ;A Diamond GOS METRONOME program 0130 ;to output a pulse to the SI/O 0140 ;cassette motor control to 0150 ;activate external hardware 0160 ; 0170 *= $2000 0180 ; 0190 .OPT NO LIST 0200 .OPT OBJ 0210 ; 0220 ; LIBRARY 0230 .INCLUDE #D1:SYSEQU.M65 0240 .INCLUDE #D1:LIBRARY.M65 0250 .INCLUDE #D1:DMACROSM.M65 0260 ; 0270 ;JRS SUBROUTINES 0280 .INCLUDE #D2:INFODIA.M65 0290 .INCLUDE #D2:DROPMENU.M65 0300 .INCLUDE #D2:DLITIMER.M65 0310 .INCLUDE #D2:INITICON.M65 0320 .INCLUDE #D2:PRNTIME.M65 0330 .INCLUDE #D2:PRNBPM.M65 0340 ; 0350 PU .BYTE " 030 - 60TH SEC. ",255 0360 BPMU .BYTE "BPM",255 0390 NUMCHR 0400 .BYTE $30,$31,$32,$33,$34 0410 .BYTE $35,$36,$37,$38,$39 0420 ; 0430 START 0440 INIT 0 0450 JSR DROPMENU 0460 JSR PLACEICONS 0465 SYSDRAW PU,11,138,0 0470 JSR INIDLI 0480 JSR INFODIA 0485 SYSDRAW BPMU,25,72,0 0487 JSR PRNTIME 0489 JSR PRNBPM 0490 .INCLUDE #D2:EVENT.M65 0500 ; 0510 *= $02E0 0520 .WORD START
-
While waiting for the arrival of parts for the dTALK project I am going to upload and archive some of the programs from the past. Most of these programs saw the light of day but how much light is questionable. sdump.zip SDUMP.ZIP contains SDUMP11.ACC and SDUMP11.M65 SDUMP11.ACC – is an accessory program that will print the screen display to a printer capable of printing graphics. Its origin is from the “The 49 Second Screen Dump” in Compute!'s Second Book of Atari. To use, put SDUMP11.ACC on your Diamond boot disk. Diamond only allows a limited amount of memory for accessories so you may need to rename other accessory programs to deactivate them. Now when you boot diamond SDUMP 1.1 will appear under “Desk” in the drop down menu. Just click on SDUMP1.1 and it will send the screen to your printer. There was not enough room for error checking so be sure the printer is on and ready to go. This is a scan of a desktop printout make on a Star NX-1000 printer and 850 interface. SDUMP 1.1 fixes an annoying bug that was in the first version.. When the a computer sent the byte $92 to the printer, the printer thought it was the end of buffer and stopped printing the rest of the line. To keep this from happening, when ever a byte = $9B, a $9A is sent to the printer. If you examine the next scan of a print out you will notice there is a missing pixel in the file icon, just above the A. If you notice that a bit is missing, this may be the reason. An accessory will be available to use any time the drop down menu is active and on the screen. People have reported using it to print out the desktop and to make screen dumps in Diamond Write. The accessory can also be utilized with the VIEW-8 program (used to view Graphic 8 pictures saved in 62 sector format). The following scan is an interface for the memocom robot created with the Graphics Master program having been loaded by VIEW-8. At this time, I will make no claims that SDUMP will work with BASIC programs. For the moment, it seems that the ways of the Diamond accessories have been lost to the dark side of my memory. There maybe problems when SDUMP and the BASIC link program use the same memory in Page 6. I won't know(or care) until there is a BASIC program that uses drop down menu. I now have the parts for the dTalk project.
-
Dcalc – The best Calculator app for Diamond GOS This simple calculator written in BASIC for the Diamond GOS environment should be able to handle balancing your check book. If you are trying to get to the moon you may want to double check the math with your slide rule. The program was written in Atari BASIC on a 130XE, Diamond GOS 3.0, 1050 disk drive with Atari DOS 2.5. I have a feeling that there will be some systems that may not be able to run this program. What I would really like to know is the systems you have that can run it. The attached ZIP file contains three files, DCALC.BAS, DIABASIC.OBJ, and DCALC.SYS. It was created on a Windows NT computer after the files were transferred from the Atari. You will need to download and transfer the programs to your Diamond equipped Atari. DIABASIC.OBJ is the page 6 ml program used to transfer control from BASIC to Diamond and back. DCALC will look for DIABASIC.OBJ on Drive 1. DCALC.SYS is a program that should auto-run D1:DCALC.BAS when you exit the Diamond Desktop to Atari BASIC. dcalc.zip To run dCalc 1. Boot up your Diamond Desktop 2. Put the disk with the three programs in Drive 1 3. Open window for drive A. Double Click DCALC.SYS and let run. 4. Choose File-Quit from the drop down menu. 5. Choose YES 6. The program should load and run. If you don't/can't use DCALC.SYS then you can always quite to BASIC and type RUN “D1:DCAL.BAS”. When you are ready to quite the program, clicking the “Q” button in the lower right corner of the screen should take you back to the DESK TOP. The program uses Reverse Polish Notation (RPN) and is different then normal calculator data entry. To Add 2 numbers. Input a number. The BS key is for backspacing. (click 25) Click the enter (click up arrow) Enter second number. (click 32) Click operation button (+) (57 should be in the upper box) The rest of math functions work the same way. The numbers in the boxes will be used and the result will be displayed in the upper box when ever a function key is clicked. This will take some getting use to if you have never used RPN. I am still catching myself trying to use number-function-number-equal. The double arrow icon is used to swap the numbers in the registers. I was thinking that I may want to Invert and divide someday. The only error that should occur is the data overflow error. Atari BASIC can't handle numbers larger then 9.99999999E-94 (or something real close). Type RUN to restart the program. Divide by Zero is an error. Trying to do this should result in a beep. Nothing happens to the registers until a valid operation is attempted. There is plenty of room for improvement. I left the upper left icon (#19) undefined. The only thing that I ask is that you change the title string to indicate that a change has been made. I wrote this program for my own use and to get back into programing the Atari after a 22 year hiatus. So far it has been enough fun to get me thinking about my next Diamond Project.
-
If you found the dialog reference sheet of interest, I'm sure this reference for creating a menu bar will be just as interesting. Menu Bar reference sheet.pdf This next Diamond project was going to be written in BASIC. When I looked at all the information tables, pointers and data strings needing to be defined as BASIC string variables, assembly language seemed to be the way to go. Especially since my assembler is the MAC/65. The Diamond Develop disk has a library with MAC/65 macros for each of the functions. I have found programing the Arduino using their version of "C" to have some similarities to MAC/65, in that, without the libraries I would be in deep do-do. There are some very talented programmers writing code so I don't have to. Thank you. The more library functions I use in a program, the less I feel like I'm writing a program. Using prewritten blocks of code makes me want to call my efforts "building a program". Of course that makes no cents when you consider BASIC is nothing more then macro calls to machine language subroutines. Looking over my library files has made it apparent that I can't remember the what, were and who of some of these library files. I see that I could have used the BGT (Branch greater than) a couple of days ago. Probably would have worked better then the BAW (Branch any where) that I wrote.
-
I think my son starts worrying about me when I get out the old Atari Computer. This time he’s trying to lure me away from the “Atari side” with a Windows 8 tablet computer. Making the jump from NT to Windows 8 and getting use to the new USB keyboard would make anyone miss the good old days. I do long for the day when a system restore was a matter of turning off the computer and reinserting the cartridge. Just yesterday I had 41 updates. Remember the days when you had to get it done right the first time? There were 3 versions of Diamond and can you imagine what it might have become after 28 more….and that’s for one day. Once, I had a hard drive crash on my netbook. I had swapped out the drive for more capacity and saved the old one as a spare. After 4 years there were more than 350 critical updates when the power was put to it. Wish I was getting paid by the hour when I fixed that problem. Now here is another opportunity to get Mix n Match to play on your dAtari system. It may help you pass the time while installing your updates. I’m sorry that it won’t help if you are using an emulator. Mix n Match By the Pack C 1991 Mix n Match is an old game. Simply find the matching symbols on the 6 by 6 play board. Well maybe not so simple, after they have been mixed up and hidden. To run Mix n Match, boot up your computer with the Diamond GOS. Place the disk with MIXMATCH.APP and MIXMATCH.DFT into drive one. Open a window and double click on MIXMATCH.APP. There are three ways to play Mix n Match. Chose which way you wish to play by setting the MODE. Click on the mode type in the menu bar. A check will appear before the mode that is active. PLAYER1 - practice mode. You just keep playing till the board is empty. PLAYER2 - This is the two player mode. Each player can try to make matches until two non-matching tiles are picked. The program will turn control over the other player. Keep an eye on the bottom of the game box. Before a player picks their first square, whoever is up will be in inverse letters. COMPUTER - The computer will give you some competition. I did not give the computer perfect memory so there is a real good chance you can win against it. After the mode is set, select START-GAME from the menu bar. The symbols will be scrambled and the game area will be displayed. Pick two squares by pointing and clicking to them. If they are a match your score will be increased and you will be able to try again. Fail to make a match and control of the mouse should be turned over to the next player. Any time the "QUIT" at the bottom of the screen is inverted you can quit the game by clicking on it. To return to the Desktop select QUIT on the menu bar. ABOUT THE FONT Mix n Match uses a standard 8X8 Diamond FONT. If you get tired of the symbols that come with the game you can create your own. "x" - is used for the game board square. The letters "a-r" are to be redefined for use as symbols. The program looks for a font with the file name MIXMATCH.DFT in drive 1. Save the new font with this file name. Be sure to have a copy of the original font somewhere safe before it is deleted or changed. Zip file contains- MIXMATCH.APP,MIXMATCH.DFT,MIXMATCH.M65 MIXMATCH.zip
-
I am trying to find any information on the origin of the public domain file - DIABASIC.ARC. There is no indication as to where this program came from and or who wrote it. It doesn't seem to have any official connection to Diamond. It is a program to interface The Diamond GOS routines with BASIC. Much like the one in the Development kit but different. I know what the difference is. I'm not sure why. The program is listed in Z-MAG 19 -Sept 89 #175 as a "Genie New 8 bit Upload 4552. It was uploaded 0n August 9 1989. I must have downloaded it from CompuServe around the same time. I'm thinking it might be a log shot that someone remembers. I didn't.
-
Diamonds are forever, unless you expose the chip to UV
k-Pack posted a blog entry in Diamond in the Rough
I started life as a very young child.......... (is there really any other way to start a blog?) I purchased my first 800 in 1982. I packed it up with the other 5 Atari computers and all things Atari for safe keeping in 1996. I would have never put it away except there seemed to be no shared enthusiasm for the Diamond GOS. For me, the lack of software was one of its strongest attractions. The Diamond GOS made the Atari almost a new computer. It took me 10 years to get to the point where I wanted to try some programing with the MAC/65 and here was a GOS sitting there with only a few programs. I did get a a couple of programs running and uploaded to Compuserve. The shareware versions netted me $15. (P.S. I'm still accepting checks) Instead of quitting my day job I thought I would put some of my programming skills to work making my job a little easier. There were a lot of things about programming the Diamond GOS that made the transition to Visual Basic 4 less painful. Well, I don't have to worry about a day job and I believe I'll have enough free time to try some more Diamond programming. It's been slow going. Its taken me 6 months to get my 130XE with a Transkey modification and a 1050 disk drive to the point where I am 60% confident it will boot up. I'm easily side tracked by the items I pull out of a storage box. Each item seems to have a story that longs to be told. I'll try to stay on point but if someone asks me a question.......don't blame me. My next objective is to do a literature search and to look though my old disks for any information. The rest is an item story that longs to be told. (I just wanted to warn you) Back in 1992, when you walked out of the store with your new Atari 800 with 16k of RAM, you probably also had to transport a box of Atari BASIC, a 410 recorder and the whole reason you bought the computer – Star Raiders. Well back then Atari knew how to do it, 'cause after you spent your $1,000 they gave you a free plastic bag to carry it all in. Not just any old bag but a double walled plastic bag with Atari advertizing on it. I remember this 'cause part of that plastic bag got framed and hung over my IBM computer at work for many years. (If I can tell a story about the bag I brought my first computer home in, should I worry?)