Jump to content

sanny

Members
  • Posts

    713
  • Joined

  • Last visited

Everything posted by sanny

  1. I also like the attract mode (now... back then I didn't like it, C64 friends inspired)
  2. @pcrow, how about a Mac/65 file analyzer. Or is it covered by the basicanalyzer?
  3. You could do this with the atari800 emulator. You have to compile your own version with special settings, though.
  4. I think you don't need a plot. Just a more complete example of what is possible. Like @ivop suggested.
  5. Joseph, can't you start to release anything only after there are no known bugs. I don't remember a release announcement of you without "but there is a bug here and there..." 😞
  6. Thanks. Where did you find the disk image?
  7. You need to exclude the leading "lib". So to link with libfoo.a use -lfoo
  8. If you are at the gdb prompt after the SIGSEGV, type "bt" (for backtrace) to see the call history. If you don't see anything sensible (just '??' etc), compile the program with debug information and without optimizations (with gcc: '-ggdb -O0').
  9. Doesn't this miss a "NEXT"? Two opening "FOR"s and only one "NEXT"? But it seems to work somehow
  10. And what do you have configured as "CompileCommand"? I don't know WUDSN, but it appears it could be an user settable configuration. Still a bug if you could enter things there that cause it to crash...
  11. How did you convert that to PDF? With this font..
  12. Hi, I was reading the OS/A+ manual where they speak about an Apple version and the Atari version. Did the Apple version really exist? I haven't found a disk image of it. regards, chris
  13. You don't delay in your loop. You should give pokey some time to play the new frequency....
  14. I think also some Atari arcade machines used the Pokey.
  15. > Only after looking at the resulting hex, and comparing it with the 6502 instruction code, did I figure out that it was no longer compiling code that would work on a 6502. How did you come to that conclusion? What are the command line arguments to ca65? What do you mean with "hex" file?
  16. This will make cc65 runtime internal tables inconsistent. Just close() it instead, like an open()ed fd.
  17. > I've been told it should have been on #6 Who told you that? cc65 is using the next available IOCB.
  18. There is no atarisyseq.h in the cc65 distribution. The file to use is atari.h.
×
×
  • Create New...