Search the Community
Showing results for tags 'Source Code'.
Found 4 results
I added an in-progress Z80 disassembly of Gorf to BallyAlley.com. You can download it here: http://www.ballyalley.com/ml/ml_source/ml_source.html#GorfArcadeDisassembly Here are some additional details about the game: Gorf, is a fixed space shooter arcade game with five different screens. Jay Fenton designed and programmed Gorf for DNA (Dave Nutting Associates). It was published by Midway in 1981. Like Wizard of War, The Adventures of Robby Roto! (and others), Gorf uses what has been dubbed the "astrocade chipset". In 2018, Jamie Fenton (formally Jay Fenton) donated documentation and hardware items to the Computer History Museum in Mountain View, CA. This included Gorf source code and other documentation related to the game. Gorf was not written in machine language, it was written in a Forth-like language called TERSE (Terse Efficient Recursive Stack Engine) that was developed at DNA. After the TERSE source code for Gorf became available, David Turner, an avid fan of the game, began to use the game's source code to disassemble Gorf and comment it. Details of his work, as well as his in-progress Z80 disassembly for Gorf is in this archive. In Dave's notes, he refers to TERSE and Gorf related documents which are available at the BitSavers archive, here: http://bitsavers.org/pdf/nuttingAssoc/ In July of 2017, I reviewed the Gorf arcade game: It's great that the recent archiving of the TERSE source code for Gorf is already bearing fruit. Adam
Hi!, As promised, here is my own disassembly of TurboBasic XL v1.5 (the original published one). Assembling with MADS should generate the same binary as the original (byte for byte), if not, it is a bug and should be fixed. Many labels are still in the original "LXXXX" form, but should be self explanatory from the assembly source, all labels for statement and function execution are of the form "X_", all labels for the syntax tables are "LS*", the corresponding syntax codes are "_S*". Where it made sense, I used the labels from AtariBasic sources, but probably better names and more consistency for many labels is needed, as I only worked in this sporadically over a long time. Hope it's useful to interested people EDITED: Current version of the disassembled sources is at https://github.com/dmsc/turbo-dis turbo-mads.asm
Hi together! Yesterday was historic, after > 31 years a dream came true, we now have the Turbo-Basic XL - Source Code online in PD with permission from the Ostrowski family. :-))) https://atariwiki.org/wiki/Wiki.jsp?page=TURBO-BASIC%20XL What a time! :-) So, now just 4 are missing here: https://atariwiki.org/wiki/Wiki.jsp?page=Articles#section-Articles-SourceCode - Atari Assembler Editor - Atari Macro Assembler and Program Text Editor (AMAC) - OSS EASMD - OSS Basic A+ to complete the OSS vision, which all started with the Atari Basic Source Book. :-) Any help of any kind, even any hint for this goal is very welcome at any time. With this I would like to say thank you to the community for all the help you gave the AtariWiki. It is you, who made Atari great and who keep Atari great. Thank you all.
To share more on the progress, this is the current output of the tool I am working on: http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_A.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_B.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_C.html The content in these files is the original commented source code for TI-99/4A System Rom, created by the TI developers. Basically an assembler source code file is read in by TIcode99 and parsed to generate a new assembler source code file. These html files are something I wanted to do for a long time already, they include rich syntax highlighting, which is only possible because the tool actually understands and categorizes the content in the code. The tooltips (hover with the mouse on certain elements) show you detailed information about the opcode, about the symbols and their resolving, the operand type,... The symbols can be clicked on to jump to the location where they are defined. However with the enhanced tooltips you hardly need to jump for and back just to read the definition of the symbol. All this is done automatically and can be done for any Tms9900 source code file. When I change the render options to always render numbers in hexadecimal format, it generates these instead: http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_A%20-%20Hexadecimal.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_B%20-%20Hexadecimal.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_C%20-%20Hexadecimal.html When I change the render options to always render numbers in decimal format, it generates these instead: http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_A%20-%20Decimal.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_B%20-%20Decimal.html http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_C%20-%20Decimal.html Here are the original source files for reference: http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_A.a99 http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_B.a99 http://www.ti99.eu/wp-content/uploads/TIcode99/ROM-4A_C.a99 See also the formerly used thread where people helped me get this far: http://atariage.com/forums/topic/274552-lots-of-assembler-questions/