Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

54 Excellent

About atarixle

  • Rank

Contact / Social Media

Profile Information

  • Gender
  • Location

Recent Profile Visitors

8,688 profile views
  1. You can find my Fuijiama-related photos on my Fujiama 2019 Homepage (see my signature).
  2. My example is doing things to more than one scan-line, and it's ment to be work in Graphics 0. I just wanted to show, how I defined the Constants, e.g. in __asm__("sta %w", WSYNC); I am not that kind of super-programmer (in fact, I am a pro in BASIC and Turbo-BASIC), so I don't even know why I use __asm__() instead of asm() Oh, btw, I call the DLI like this: // initialize DLI POKEW(0x0200, (int)DLI); // VSDLST ... POKE the address of the function DLI() into 0x0200 POKE(0xd40e, 0xc0); // NMIEN ... turn on DLI which is a quick and dirty PEEK-and-POKE, the way I use to do it in BASIC, instead of using a C-like style by using pre-defined functions.
  3. Just a moment, let me check out my DLI (which I created last year) ... it looks like this: #define FONTBASE_HW 0xd409 #define FNT 148 #define WSYNC 0xd40a #define VSDLST 0x0200 #define NMIEN 0xd40e #define GPRIOR 0xd01b void DLI() { __asm__("pha"); __asm__("lda #%b", (unsigned char)FNT); __asm__("sta %w", WSYNC); // WSYNC __asm__("sta %w", FONTBASE_HW); // FONTBASE Hardware-Register von 756 __asm__("lda #192"); // Graphics 11 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #64"); // Graphics 9 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #192"); // Graphics 11 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #64"); // Graphics 9 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #192"); // Graphics 11 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #64"); // Graphics 9 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #192"); // Graphics 11 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("sta %w", WSYNC); // WSYNC __asm__("lda #64"); // Graphics 9 __asm__("sta %w", GPRIOR); // HW-Register von 623 __asm__("pla"); __asm__("rti"); } This one works for me, I hope it helps you create your DLI.
  4. I once owned a Rat-like mouse, advertised for the C64 - it was likely the same product as the Rat itself, as it just emulated Joystick-controls. So it kinda worked on the Atari. When I tried to use it, I thought, that there had to be "speed" register, but it wasn't, which made this all pretty useless. The Atari-ST-Mouse itself sends raw movement-signals to the Atari, so it has to "emulate" the ST-Mouse-Controller (which is built into the ST). Simple mouse-drivers read the data a 1000 times a second, so it wont run in VBI (I guess, other drivers do a better job), but for that it's pretty real-time and 50fps/60fps capable. My BOSS-X-GUI can make use of the ST-mouse.
  5. You can convert it to KPN, a format I made back in 1992. It just represents the commands PLOT, DRAWTO, and FILL (and some others for very simple animations) in a stuffed file.
  6. I really like the gfx on the screenshots ... sadly I am not a gamer at all
  7. is it licenced in a way that I can integrate it into BOSS-X?
  8. What I actually do with my Atari is programming BOSS-X, so I can start the few Games I play via double-click instead of swapping disks. The second thing I do is still discovering capabilities of the Atari machines - after 28 years of owning one I am not nearly half aware of what I can do just with Turbo-BASIC.
  9. We will move into a bigger flat - just for setting up an Atari Workspace that includes a cassette drive just for watching Bad Apple HD on the real machine.
  10. I am still working with Colleen - where 'working' means to play simple games (Joystick only games) and watch Demos (e.g. SillyPack 18). A very big downside for me is that Colleen cannot write onto ATRs if they are stored on the external SD-Card. But it still is a cool thing to quickly show things to people on your mobile instead of a Laptop or the real machine.
  11. Ok, I found my old COPY2ATR.TUR program. In line 200 it's OPEN #%1,6,%0,"H4:*.*" ... so I get the directory using star dot star. BUT as the H: device gives back a filename format other than *:FILENAMEEXT 000, so my program has to handle filenames different. Instead of converting *:FILENAMEEXT 000 to FILENAME.EXT, I use the untouched filename for opening the source file (from H: to D:). And this is what MyDUP cannot handle.
  12. g2 check this out ... I am not 100% sure right now, but I think I do wildcard copies on 800Win using just a single * ... (COPY2ATR.TUR). In case of 800Win, the H: device gives back long filenames with the dot in the middle - something MyDUP cannot handle at all if it just handles a 12345678123 sheme internally.
  13. The H: device has nothing to do with MyDOS. So the MyDUP relies completely on MyDOS when it comes to Syntax-Things, which causes both of these errors. But you can always workaround this with software especially written for one emulator's H: device (where Atari800's H: device has to be handled different than the one on Atari800Win or Altirra). When I wrote my COPY2ATR.TUR, which copies all files from H4: to D: ) for Atari800Win, it worked only on Atari800Win. It didn't even work in Atari800DOS if I remember right.
  14. I have multiple MyDOS 16MB Volumes in use, either ATR-Images for emulator or SIO2xx use, or as a KMK-IDE2-Partition. My 1MB RD is driven perfectly by the internal, auto-configured MyDOS-RD-Driver (as D9: ). MyDOS can write only 720 Sectors onto DOS2.5-Disks, but it can read all files on DOS2.5-Disks with 1040 Sectors. So if you want to fill your 16MB drive, just copy them from any DOS2.5-Source. Beware that MyDOS can only 64 files per directory, but you can creat theoreticly an infinite amount of sub-directories (only limited by the size of the volume). COPYFNF.TUR (on my BOSS-X-Disk) is a Turbo-BASIC-Program that can copy files and folders from one MyDOS-Volume to another MyDOS-Volume (or another sub-directory) directly or using the RAM-Disk as a temporary buffer. To get files of any size off the MyDOS-Drive (like from MyDOS to any other) you have to define what "any other" is. I always use an emulator's H: drive. As H: is a completely separate emulator-DOS (H: is not D:), it has nothing to do with MyDOS, SpartaDOS or DOS2.5. So it not always can handle MyDOS-subdirectories. Some emulators do not even translate filenames (you literary can use large filenames for H: disks on Atari800Win). Some H: devices (Altirra I think) also support sub-directories - but I never really tried that.
  15. A yeah, thank you 1000 times for this Mac Version of Atari800. Do you think you will merge Atari800 4.0.0 with Atari800MacX anytime soon?
  • Create New...