Jump to content

Search the Community

Showing results for tags 'assembler'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Atari Systems
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Lynx
    • Atari Jaguar
    • Dedicated Systems
    • Atari 8-Bit Computers
    • Atari ST/TT/Falcon Computers
  • Gaming General
  • Marketplace
  • Community
  • Game Programming
  • Site
  • Classic Gaming News
  • The Club of Clubs's Discussion
  • I Hate Sauron's Topics
  • 1088 XEL/XLD Owners and Builders's Topics
  • Atari BBS Gurus's Community Chat
  • Atari BBS Gurus's BBS Callers
  • Atari BBS Gurus's BBS SysOps
  • Atari BBS Gurus's Resources
  • Atari Lynx Programmer Club's CC65
  • Atari Lynx Programmer Club's ASM
  • Atari Lynx Programmer Club's Lynx Programming
  • Atari Lynx Programmer Club's Music/Sound
  • Atari Lynx Programmer Club's Graphics
  • The Official AtariAge Shitpost Club's Shitty meme repository
  • The Official AtariAge Shitpost Club's Read this before you enter too deep
  • Arcade Gaming's Discussion
  • Tesla's Vehicles
  • Tesla's Solar
  • Tesla's PowerWall
  • Tesla's General
  • Harmony/Melody's CDFJ
  • Harmony/Melody's DPC+
  • Harmony/Melody's BUS
  • Harmony/Melody's General
  • ZeroPage Homebrew's Discussion
  • Furry Club's Chat/RP
  • PSPMinis.com's General PSP Minis Discussion and Questions
  • PSPMinis.com's Reviews
  • Atari Lynx 30th Birthday's 30th Birthday Programming Competition Games
  • 3D Printing Club's Chat
  • Drivers' Club's Members' Vehicles
  • Drivers' Club's Drives & Events
  • Drivers' Club's Wrenching
  • Drivers' Club's Found in the Wild
  • Drivers' Club's General Discussion
  • Dirtarians's General Discussion
  • Dirtarians's Members' Rigs
  • Dirtarians's Trail Runs & Reports
  • Dirtarians's Wrenching
  • The Green Herb's Discussions
  • Robin Gravel's new blog's My blog
  • Atari Video Club's Harmony Games
  • Atari Video Club's The Atari Gamer
  • Atari Video Club's Video Game Summit
  • Atari Video Club's Discsuuions
  • Star Wars - The Original Trilogy's Star Wars Talk
  • DMGD Club's Incoming!
  • DASM's General
  • AtariVox's Topics
  • Gran Turismo's Gran Turismo
  • Gran Turismo's Misc.
  • Gran Turismo's Announcements
  • The Food Club's Food
  • The Food Club's Drinks
  • The Food Club's Read me first!
  • The (Not So) Official Arcade Archives Club's Rules (READ FIRST)
  • The (Not So) Official Arcade Archives Club's Feedback
  • The (Not So) Official Arcade Archives Club's Rumor Mill
  • The (Not So) Official Arcade Archives Club's Coming Soon
  • The (Not So) Official Arcade Archives Club's General Talk
  • The (Not So) Official Arcade Archives Club's High Score Arena
  • Adelaide South Australia Atari Chat's General Chat & Welcome
  • Adelaide South Australia Atari Chat's Meets
  • Adelaide South Australia Atari Chat's Trades & Swaps
  • KC-ACE Reboot's KC-ACE Reboot Forum
  • The Official Lost Gaming Club's Lost Gaming
  • The Official Lost Gaming Club's Undumped Games
  • The Official Lost Gaming Club's Tip Of My Tounge
  • The Official Lost Gaming Club's Lost Gaming Vault
  • The Official Lost Gaming Club's Club Info

Blogs

There are no results to display.

There are no results to display.

Calendars

  • AtariAge Calendar
  • The Club of Clubs's Events
  • Atari BBS Gurus's Calendar
  • ZeroPage Homebrew's Schedule

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website


Facebook


Twitter


Instagram


YouTube


eBay


GitHub


Custom Status


Location


Interests


Currently Playing


Playing Next

Found 45 results

  1. I posted a scan of a photocopy of the SDS Programmers Guide in the Development Resources sticky, but it was suggested I start a new thread, so here it is. I have some other stuff, SDSMAC source listings, additional documentation, etc. to put here, too. Coming soon. Anyone else have anything relevant, please post away. The SDS consists of a GPL assembler, linker, simulator, and debugger running under DX10 on a TI 990 mini, typically a /10. TI BASIC programs can be converted to GROM format to run on the simulator. jbdigriz HCM_SDS.pdf
  2. Since the game is still WIP, I decided that it is better to continue here. Below you find the latest versions: Robot_City_20191110.zip Robot_City_20191118_RC1.zip Robot_City_20191124_RC2.zip Robot_City_20191125_RC3.zip Robot_City_20191126_RC4.zip Robot_City_20191201_RC5.zip Robot_City_20200425_RC6.zip Robot_City_20200426_RC7.zip Robot_City_20200427_RC8.zip
  3. A project I have been working on for the last two years is nearing completion i.e. my next book called 'Programming Games for the Colecovision and Adam in Assembler'. It includes a tutorial section working through the steps of creating a game, with a Z80 assembler primer and information on how to set up a cross development environment (similar but extended from my Let's Make a Retro Game series). It also includes a complete Colecovision BIOS reference guide, covering ALL of the jump table BIOS calls with explanations and examples for using each call. There are extensive memory and port maps, also with explanations etc. It will have a dedicated web site section where you can download the code (for lazy typers :)). The early pre-order link for the Kindle edition is available here. Cover is still a draft. Shortly after I have released the Kindle Edition, there will also be a physical print edition available on Amazon's print to order service, which I used for my last book and has been received well. It does have some colour screen shots and pictures in it, let me know how many people would be interested in a full colour edition, rather than a colour cover with black and white interior. The book is currently 90% complete, with the majority of the content completed, but I have about ten quality read through passes to do and need to tidy-up/check all the source code etc. I am aiming for a 1st August 2020 release date at this stage.
  4. IDE for developing in TI99 Assembler on the PC (Windows) (using NotePad++ Editor, xdt99 Cross-Assembler and MAME Emulator) https://github.com/miriki/TI-xdt99-IDE/ Hi, all! A few may have noticed: In an xdt99 thread I have published a Batch for DOS that shortens a lot of typing work when developing software. After years of abstinence from the TI99 I actually remembered the "good old days" developing tools and libraries again and tried to recall what I was doing those days. Well, 35 or so years... Firing up the MAME emulator, using TI99_4ev as machine, a cartridge with Editor/Assembler inserted and the needed disk in DSK1 mounted I started typing a few lines while reading through a bunch of books and forum articles. Hmmm... A PC keyboard and the function keys of the TI99, two worlds collide. Yes, the editor _was_ a very good one, at least that days. But nowadays I really, really prefer the comfort of NotePad++ or at least any other GUI based editor. Then I've read about the one or another Cross-Assembler to develop in Windows and using the output to mount within MAME. Almost right from the beginning I got stuck with xdt99, a collection of not only a cross-assembler, but other tools like a "disk creation", too. An integration into "IntelliJ IDEA" sounded good, but.... Hmmm... Maybe I have not digged deep enough, but there is only the editor used for syntax highlighting, isn't it? Putting things together: A batch for DOS (Windows, Microsoft, sorry...) was created that enabled the workflow from editing the Assembler source code assembling the source code into object code creating a disk which contains the object file starting an Emulator with this disk mounted plus a few more tasks... To be honest: I don't like DOS batches with more than, let's say, 25 or so lines. The syntax is ugly and the CLI commands are far from comfortable - not comparable with a high level language. Changing default values is a pain, (re)storing user settings a tremendous effort and doing all with user parameters results in a jungle of % characters shattered across the lines. So I used that batch only as a sketch for a "real" project: An IDE for those tools written in a high level language. I decided on C# (VB.Net would have been the alternative), because it is the preferred language right now in our company. Training... If anybody would like to have a look at it: I just published that project on GitHub. That was kind of training, too. We use Azure DevOps in our company and I have to get familiar with those cloud based team thingy. So hopefully I published correctly - it is my first published project over there. https://github.com/miriki/TI-xdt99-IDE/ This is the main page of the project. There is a README, but empty as of now. You will find a subfolder "TI xdt99 IDE" though... There is a subfolder "snap" which contains a few screenshots of the published project: Settings_Xdt.png shows the settings to include the tools from the xdt99 package. Settings_Mame.png shows parameters for the emulator, including configuration of the peripherals etc. Settings_Ide.png shows the standard working area with buttons to start actions and checkboxes to set options. Output_CommandStack.png shows the list of calls to external tools like the editor, assembler etc. Output_Standard.png shows the standard output of the last command, for example the directory of the disk. Output_Errors.png shows the error output of the last command, if there is any. Emulator_AutoStart.png shows the XB output from DSK1.LOAD if "catalog" and "autostart" is checked. Output_Result.png shows the loaded and started demo program I was just working on. Another subfolder "publish" contains a "setup.exe" that should install the IDE. I'd like to get feedback, if that thing runs without any problems. But what has to be done? Well... Perhaps it is best to show my setup: E:\TI99 mame64.exe >roms ti99_*.zip >hash ti99_cart.xml (thanks again, mizapf!) >cart editass.zip minimem.zip exbasic.zip >disk *.dsk >hard *.chd This should be enough to start MAME using e.g. ti99_4ev as machine. Try it... mame64 ti99_4a If successful, try inserting a cartride: mame64 ti99_4a -gromport single -cart exbasic If successful, try connecting a peb with a hfdc in slot 8, a disk drive connected and a disk inserted: mame64 ti99_4a -gromport single -cart exbasic -ioport peb -ioport:peb:slot8 hfdc -ioport:peb:slot8:hfdc:f1 525dd -flop1 disk/flopdsk1.dsk whew... After the first start of MAME there will be a few more subdirs like cfg, nvram etc. You might like to start MAME with -createconfig and edit the output mame.ini to suit your needs. I added cart and cart2 subdirs to the roms path, disabled the info screen at startup and the like... Then I added a subdir >xdt99 xas99.py xdm99.py xbas99.py >lib vdptools.a99 >projects >gmode gmode1.a99 etc. The "lib" folder contains a "vdptools.a99" file right now. There are only a few routines to avoid "BLWP VSBW" etc. in it. The "projects" folder contains the, as you already might have guessed, projects I am working on - for example a "gmode" subfolder. And in the "gmode" folder there are gmode1.a99, tmode.a99, mulcol.a99 and bitmap.a99. With this setup the settings on the XDT and MAME tabs should be self explanatory, kind of... The right hand side shows extensions for the filenames. For example the source "gmode1" gets expanded to "gmode1.a99" for the editor, is compiled into "gmode1.obj" and will become "GMODE1O" when copied to the TI disk. You may change the settings on the MAME tab and can use the IDE purely as a frontend, if you like. The "run" button will start the emulator without fiddling around with an assembler or anything else. BTW: Settings are loaded at startup of the IDE and saved when the IDE is closed or any external program is called. The IDE tab is the "all singing, all dancing" desktop for your development. The left box lists all subdirs aka projects, the right box lists the source files in that (selected) project. The selection is shown additionally in the two textboxes in the upper right (for later extensions). The "edit" button starts the editor, the "assemble" buttons starts the xdt99 cross assembler. It creates the object, image and rpk files, if checked. If "all" is checked, not only the actual selected source but all within the project will be assembled. The "disk" button creates the disk to be mounted for the emulator. It copies the source, list, object and image files, if checked. Again: For "all", if checked. Additionally it can create a DSK1.LOAD to show the contents of the disk and / or load and run the object file of the selected source. The "emulator" button starts the MAME emulator with the configured devices. If set up properly you might select "TI Extended Basic" from the master selection, get the disk contents displayed and after "please wait..." the compiled program should start. The "ADE" button is a shortcut: (A)ssembler, (D)iskManager and (E)mulator - all in one shot. So after editing / saving the source the test only needs 1) click on "ADE" button, 2) any key at the master title screen 3) "2" for XB, then wait... and enjoy! The menu at the top has no function as of now. The status bar at the bottoms shows info about running external tools to the left, "idle" to the right otherwise. Have fun! Michael
  5. I am writing some assembler code with the Editor / Assembler. When I assemble the code and use PIO as the list file name I get a DSR ERROR : 0302. If I leave the list file name blank or list to disk I have no issues and the code assembles with no errors. I am able to print a disk catalogue to PIO from the Disk Manager 2 module but I have not tried printing any other way than from disk manager and E/A. I have had this same issue with a Lexmark printer and an Epson printer. My assembler options are RLS. Any ideas what the issue might be?
  6. I'm working on several different TI-99/4A related projects at any time (there's a Top 10 out of 146). Surely giving it more thought than actual coding. Most certainly less than an hour of coding per week. Much is design and decisions anyway. Committing is perhaps crucial but then again. Real life is a bitch. Lately I've got this headache. Right now the plan is; get away from the computer, get away from screens - tv and gaming, get some exercise, go for a walk and get some fresh air, be positive and enjoy, be serious, commit and take responsibility, take action and stick to it, navigate and listen, and be there for the family. Your input is appreciated.
  7. 2019.12.29 I've found a bug, that only shows up in the disk version here at my end. I forgot to clear a memory location used for scoring. Files updated. blockc.bin block.dsk Filename: BLOCK - - - - - The idea will be to insert pairs of colored blocks into two piles, one on either side of the screen. Create a group of three or more adjacent blocks of the same color and they'll disappear, gaining you points. Pile up too many and you lose the game.
  8. merryc.bin merry.rpk - - - - - Things to do: * Christmas music * Christmas tree * Something else ...
  9. Hello all, I am a new to this forum. I would like to program the 2600 as a hobby. I have been reading posts this morning on how to begin. I am hoping that some of you nice folks can save me some time. I have read about DASM, batari Basic and others. Can someone answer a few questions for me and save me a great deal of time. Maybe this will help others also. What editor assembler software is used most these days? What do you recommend? Please leave a link. I have downloaded Barair Basic and and IDE and will install it today. Any useful links? Any other software that you folks use? I downloaded Stella and I have ordered a Harmony cartridge. I know these questions have been asked before but I ask for your patience and help. I hope to start writing some code today if I can get the software I need in place. Thanks to all of you in advance. Ed Cheek
  10. Is there any reason to own a mini-memory cartridge if you own Editor/Assembler cartridge. I been eyeing a guy on eBay who been selling off about 1/2 dozen mini-mem carts and trying to justify to myself the purchase of one.
  11. walker7

    Section Header 0

    From the album: The Best Assembly Computer

    This is what the section header for the main program would look like. Note that it doesn't have a section number.
  12. A good assembler has ROM section headings. These are a way to cleanly divide the source code into settings, so you can definitely figure out at which address each section starts. Think of an assembler as if were like Microsoft Word. Section headings could appear as solid-colored bars with text on them. The user should have control over what color to make the bar. They also might have control over the font. For example, your main program header might look like this (note that all images are simulated): Notice I used the Roco font. Anyone familiar with Sonic The Hedgehog 2 will recognize this, but it's the actual font, not the Sonic 2-rendered one. Every computer program needs a vertical blank (or "V-Blank") routine. Its header might look like: One common thing to have in any program are math routines. So, you might include a section like this: For a hardware/software implementation, fonts could use a bitmap. Up to 96 different character glyphs can be stored. In addition, the numbers could be made a little bit bigger if the user chose to. Each character's bitmap can be stored using 1, 2, or 4 bits per pixel. For each character, the size needs to be specified, as well as where its glyph data can be found. For file storage, section headers could use this format (each pair of letters represents a byte): hh ff rr gg bb ll tt tt ... hh = Token for a section header (a fixed value). ff = Flags. If bit 7 is set, restart the numbering at 1. If bit 6 set, toggle whether the number is shown for this and later sections. rr gg bb = Section header color, a 24-bit RGB value. ll = Length of text. tt = The text shown. It doesn't include "Section #". It's in ASCII. Let's say that the section header token is $00, and I'll use the vertical blank section header as an example. The byte stream in the source file would look like this: 00 C0 00 60 20 0F 56 42 4C 41 4E 4B 20 52 4F 55 54 49 4E 45 53 The 00 signals the start of the section header. C0 means to make this section #1, and turn on section numbering (by default, it's off). 00 60 20 is the RGB value. It produces a dark green color. The 0F determines how many characters there will be in the section's name. The rest is the text, in ASCII. The text says "VBLANK ROUTINES". Section headers are not taken into account when compiling a ROM. They are there to cleanly divide source code. When the file is opened, the number of headers is counted, and section numbers are assigned accordingly.
  13. Just stumbled into a bug with MADS' built-in ADW macro when used with (ZP),Y: LDY #$04 ADW (OBSPEC),Y PTR2 PTR4 A334: A0 04 LDY #$04 A336: 18 CLC A337: B1 C1 LIMITCLIP.OFFSCREEN LDA (OBSPEC),Y A339: 65 E2 [email protected] ADC PTR2 A33B: 85 E6 STA PTR4 A33D: C8 INY A33E: B1 C1 LDA (OBSPEC),Y A340: 65 E3 ADC $E3 A342: 85 E6 STA PTR4 ; <<<<<<< should be $E7, not $E6 LDY #$04 MWA (OBSPEC),Y PTR4 A334: A0 04 LDY #$04 A336: B1 C1 LDA (OBSPEC),Y A338: 85 E6 STA PTR4 A33A: C8 INY A33B: B1 C1 LDA (OBSPEC),Y A33D: 85 E7 STA $E7 ; <<<<<<<<<<<<< $E7 = correct Using the latest build here, and I'm sure ADW used to store the MSB correctly in older versions. Haven't looked to see if the bug exists in SBW as well.
  14. Hi! I'm using DASM and I don't know if I am doing something wrong or this is just a bug on the compiler. I have this code in one .asm file: genAutoMaskTable ldx #0 On other .asm file, I just include the first file and use the names as if they were local jsr genAutoMaskTable When I run DASM, genAutoMaskTable points to GENAUTOMASKTABLE: 0bd1 And the JSR from the main file is right, as you can see: 1C:06 20 D1 0B jsr genAutoMaskTable But.... the code is not there, it is one byte after the calculated address D2:0B A2 00 ldx #0 Any ideas?
  15. snakec.bin - - - - - Origin https://en.wikipedia.org/wiki/Snake_(video_game) Back in 2005 I did a routine for scrolling a line of text. Added a few bits to make a demo. It scrolls the text and reacts when you press fire, but otherwise stalls / stalled (wasn't brought any further).
  16. hi there, it is done, after the atari 2600 game AXE, here the latest real retro game SQUAREZ 2015. it is a demake of a quite addictive flash game. it is simple: make as much points as possible. collect the bonus and avoid the squares. simple to understand. but don't be too greedy! of course programmed in assembler (much more fun than the 6502 on atari2600). but don't look into the code - i will never get into the assembler heaven with this. the game was tested with ParaJVE (Emulator) and on one my real vectrex. the vectrex is quite a cool hardware with cool libraries. quite a cool game engine (we had to say in our days .-). i will never understand why atari didn't brought this out itself - they were the masters of vectors. after the vectrex shootemup (on this i work at the moment) i would like to finish my intellivision game. is there someone who would sell me a multicard, so that i can test the software on real hardware? thanks for any help or tipp or someone who would sell it to me. have fun [email protected] ;*************************************************************************** ; SQUAREZ 2o15 BY LA1N ; (A RE(DE)MAKE OF THE WELL ; KNOWN FLASH GAME SQUARES) ;*************************************************************************** ; ; @ixistenz ; ; THIS IS A DEMAKE OF THE FLASH GAME SQUARES (2002)! ; I THOUGHT IT IS A SIMPLE GAMEMECHANIC HHH ; CODED IT AFTER AXE (ATARI 2600) AND INTELLIVISION GAME* ; * NOT YET RELEASED ; ; MECHANICS: MAKE AS MUCH POINTS AS POSSIBLE. ; COLLECT FOR POINTS. AVOID SQUAREZ! ; THERE CAN BE AT LEVEL7 UP TO 12 SQUAREZ ON SCREEN! ; DONT BE TOO GREEDY! ; ; YOU WILL FIND OLDER PROJECTS OF LA1N AT HTTP://WWW.LA1N.CH ; OR LOOK FOR OUR GAMEART AT HTTP://WWW.AND-OR.CH ; ; CREDITS GO TO RICHARDH FOR HIS MULTICARDS (THANKS!) ; ;*************************************************************************** SQUAREZ2015.BIN squarez.asm
  17. squaryc.bin - - - - - Well, steering a mouse with a joystick is perhaps not optimal, but here goes anyway. For this demo, you'll get to move around leaving a trail behind. No, it's not going to be another snake game. You accelerate and de-accelerate. If you hit the borders, you'll bounce off. Just like Parallax Starfield, you'll be able to form some pretty perfect circles, that is, if you know how to apply the right pressure(s) at the right time. And there's a bit of friction as well. As for the registration point of the mouse, I'm using the same original default from the Amiga Workbench 1.x.
  18. parac.bin - - - - - In the footsteps of managing 32 sprites, without more than 4 sprites per horizontal line, as explored in Bubbles (demo). If you keep a number of sprites stacked vertically (no vertical overlap), they will only occupy 1 of the 4 sprites allowed horizontally. In Bubbles I made each stack move up with their own individual speed. This time I will try and move the 4 stacks in any direction. Here's a quick setup of 4 stacks. Oh, and instead of having 8 sprites in each stack (or plane), it's 6 + 7 + 9 + 10 = 32 sprites. The number of stars close to you are less than those far away.
  19. I think we need a thread like the development thread for just the software we make. I have found it a 'hit or miss' when trying to keep up with the various games, apps, virtual-cartridges people are coming up with on this board. We could put the beta and completed versions on the thread. Be glad to monitor it. Just a thought.
  20. Now that I have a working disk manager, I want to start doing some Coleco ADAM Z80 Assembler for EOS. I've found an online IDE that looks perfect. Does anyone have an INC file that defines all of the entry points to the EOS public functions? Remember, sharing is caring. And BTW, this would be put on the ADAM Wiki for posterities' sake.
  21. I am trying to run assemly code on altirra 2.5 emulator and it crushes i use assembler edtitor rom for the assembler programs following the stack dump : CPU: Illegal instruction hit: 0056 (8158: 14, 30) A=10 X=00 Y=00 S=FF P=30 ( ) 0055: 02 COLCRS bad i've tried differnt cpu & memory setting and it wont help i use 32 bit won 7 os . 10X
  22. Hello, I recently got a 130XE off EBay as a way of getting back into Atari 8-bits. (I sold my original Atari 800, with a Happy 1050, in 1985 to upgrade to an Amiga 1000). I have an Assembler/Editor cartridge left over from my '90s retrogaming collector days. I think it would be fun for learning 6502 programming since it's on the actual hardware. When I get going with "real" projects, I would switch to a cross-assembler and I wondering which is best to use for a newbie. I definitely would use WUDSN IDE, since I'm already familiar with Eclipse. ATASM seems nice because it is compatible with MAC/65, but judging from this forum all the cool kids seem to be using MADS. My concern with MADS is that if you know only English, the documentation seems a bit like folklore. It also seems like a "power user" tool that might be overwhelming at first. Interested in hearing comments from people who are using these tools now. Thanks!
  23. Dear friends When I bought my first Atari 800XL, in 1984, I immediately realized to have in my hands not only a good “game machine” but also a powerful ‘didactic’ instrument to learn. I enjoyed myself with several good games published in the first half of the 80’s and then, I started to program with the excellent Basic available on the Atari 8 bit trying to explore and exploit the graphic and the sound of my machine. Italian books or magazines were almost not existing and, obviously, Internet was far to be a solution… I didn’t stop in my passion and, with many difficulties, I was able to get some documents in English from the USA. With these info and billions of hours awake in the night, I made the jump from Basic to the ‘mystic’ Machine Language... In those years it was very popular “Winter Games” by Epyx but, unfortunately, it didn’t exist an Atari version. For this reason I decided to try to convert the Ski Jump event and to show my creation to Lindasoft, a mythical Italian software house supporting the 8-bit world. The meeting was very positive and they asked me to complete an ‘Atarian’ version of winter games. I finished the game and it was published (obviously without the Ski Jump event, too similar to the original from Epyx) but, due to the Italian Atari market, based mainly on systems connected with cassette recorders, Lindasoft decided to sell it only on tape... a multi-event game is conceptually made to be run by diskette and the cassette version was not a good idea. Now, after a lot of years, and thanks to the support of Filippo Santellocco ( http://www.santelloc...atari/index.htm ) and other friends, It's possible for me to recover this old program and to share it with all you in this complete and never released disk version. I've prepared also an English version of the instruction manual and I recommend you to read it before to play White Circus is a multi-event sport game, it runs on all Atari 8-bit systems and it gives you the opportunity to compete with your friends in 5 different winter disciplines. Please remember: currently my English is very far to be perfect, but it was absolutely terrible when I was a boy, so I beg your pardon for any text error in the game. Also, White Circus has been my very first game... I programmed the code in Machine Language, I created the graphics, the music and the sounds effects. I assembled it in about 10 months in 1987, using BBK Monitor, not a real and comfortable Assembler tool… It’s normal that White Circus is not perfect and that the playability is not always at the top. I know that it is not a masterpiece but it’s a my creature and I will always love it It’s a great joy for me to have finally the opportunity to share it with all you, Atari fans Ciao P.S. You can find this game and other news also in the nice website of Filippo : http://www.santelloc...i/programmi.htm White Circus.zip
  24. walker7

    Section Header 2

    From the album: The Best Assembly Computer

    Another example of a program's section header. This could be used for all the math routines used in the game (e.g. multiply, divide, random numbers).
  25. restc.bin - - - - - Below is an early XB game, also now known as "Restless I". Thread goes ahead and develops "Restless II", a game written in Assembly and released as a binary for cartridge. Move your ship left and right using the joystick. Shoot by pushing joystick up. 100 CALL CLEAR::CALL SCREEN(2)::CALL MAGNIFY(3) 110 CALL CHAR(64,"01010103070F001B376FDF00D47F1F03808080C0A0D000B8B4DADD0055FEF8C") 120 CALL CHAR(68,"0043AF19193F3F78073B72637339100001C2F42828F4F43AE0DCCEC6CE9C08") 130 CALL CHAR(72,"0103030301010101010100010100000180C0C0C08080800080808080008") 140 CALL CHAR(76,"000000107C3828000703117D39280000000020F8701040E0FCF8F0B01") 150 CALL COLOR(6,5,1)::FOR X=1 TO 20::CALL HCHAR(X,RND*32,76)::NEXT X 160 CALL SPRITE(#1,64,16,170,96,#2,68,16,10,96,2,0,#3,72,10,200,256) 170 CALL JOYST(1,X,Y)::IF X THEN CALL MOTION(#1,0,X*4) 180 IF Y=0 THEN IF RND>.8 THEN CALL MOTION(#2,1,RND*32-16) 190 IF Y THEN CALL POSITION(#1,Y,X)::CALL SPRITE(#3,72,10,154,X,-16,0) 200 CALL POSITION(#3,Y,X)::IF Y>154 THEN CALL DELSPRITE(#3) 210 CALL POSITION(#2,Y,X)::IF Y>154 THEN CALL DELSPRITE(#3)::Y=1::GOTO 230 220 CALL COINC(ALL,X)::IF X=0 THEN 170 ELSE Y=2 230 CALL MOTION(#1,0,0,#2,0,0,#3,0,0)::FOR X=3 TO 16::CALL COLOR(#Y,X)::CALL SOUND(-300,-6,(X*2)-6)::NEXT X 240 CALL PATTERN(#Y,76)::FOR X=3 TO 16 STEP .2::CALL COLOR(#Y,X)::NEXT X::GOTO 160
×
×
  • Create New...