Jump to content

DjayBee

Members
  • Content Count

    420
  • Joined

  • Last visited

Community Reputation

565 Excellent

1 Follower

About DjayBee

  • Rank
    Moonsweeper

Profile Information

  • Gender
    Male
  • Location
    Stuttgart, Germany

Recent Profile Visitors

9,171 profile views
  1. Omit the slashes completely. Since you parse all colons anyway, they make no sense. And it becomes easier on the Atari's side.
  2. You might have a look at MKRELO which is part of the ABC Compiler. You compile your program twice, each time for a different target address. MKRELO then compares both files and creates a relocatable file. I never tried it myself, but from the description in the manual this sounds completely independent from ABC itself. Manual at MrFish's website: Chapter 5.2 Generating relocatable code
  3. Hi vitoco, downloading the file gives only an error 500.
  4. I am an unconcerned watcher of this drama from the grandstand of not owning a U1MB. ANd I have to admit that this is better than Netflix. But I do not get the reason why you insist on accessing replicated/mirrored/whatever-one-wants-to-call-it memory locations instead of the base ones, which seem not to cause any problems with both buggy and bugfree hardware.
  5. I guess that you mean the scoreboard shows only the copyright. This happens if the copy protection fails. The image is OK. Please verify that you have the "D: patch" disabled.
  6. This is both cool and useful, just like being able to mount a disk image using HTTP(S). I only said that browsing huge collections this way might be cool but is not useful.
  7. I believe that the fun in this idea vanishes, as soon as you really try to browse through the list from the Atari - memorywise and perfomancewise.
  8. Why not post here an ATR of it? Perhaps we can crack it without the original disk. I am astonished that it cannot be copied with a Happy drive. All other titles by Alpha Systems have a not that sophisticated protection (duplicate sectors IIRC).
  9. I found a method which works on all OSs. The RAM test writes only $00 and $FF and the paddles use only $00-$E4. The below code allows $00 and $FF to be written to PADDL0 which passes the RAM test on XL/XE. All other values are replaced with 60 which passes the protection. @DrVenkman If someone documents the behaviour of the Paperclip dongle, we might be able to construct something similar. But then it seems that custom devices cannot overlay PIA's address range at $D30x. { "name": "Keyword-1 Dongle", "variables": { "val": "int" }, "memory_layers": { "PADDL0": { "name": "POKEY Paddle 0", "address": "$200", "size": "$100", "control":[ { "address": "$270", "size": 1, "mode": "r", "variable": "val" }, { "address": "$270", "size": 1, "mode": "w", "script": [ "if (($value == 0) || ($value == $FF))", "val = $value;", "else", "val = 60;" ] } ] } } } End of thread-hijacking - back to useful stuff
  10. Thanks for your help. Since Keywriter needs BASIC, it did not work as designed and I ended up with different implementations for XL/XE and 400/800. For XLs and XEs I added to your cart-code "enable-BASIC using PORTB and JMP ($BFFE)". Therefore booting has to be done without BASIC. For 400/800 I could only get my version to work. keywriter1.zip
  11. Yes, but it is only capable of returning weird joystick positions (like up and down at the same time). It depends on what Paperclip needs. The only program which uses a different sort of dongle I analyzed so far is Keywriter-1 from Amazon Systems. It verifies that PADDLE(0) is between 40 and 80. The below code works for OS-B, but fails for XL-OS because of the memory test during reset. I have not found out how to check a certain memory location to detect "after boot" from inside the device script. { "name": "Keywriter-1 Dongle", "memory_layers": { "POT0": { "name": "POKEY Paddle 0", "address": "$200", "size": "$100", "control":[ { "address": "$270", "size": 1, "mode": "r", "data": 60 } ] } } } Keywriter-1 (1982)(Amazon Systems)(GB)[BASIC][req dongle].atr
  12. Great idea! I was looking for a way to emulate a resistor-based dongle and gave it a try, but fail miserrably. Unfortunately I cannot find the additional examples in the help file, only an 8k cart and an 810 drive. This is what I try: Mclaneinc pointed me in the right direction. This is the error message I receive: Error on line 9: Control item was not an object.
  13. LOL, wouldn't do that. Nice typo - could not resist.
  14. I found a bug in the latest version which pads GBs to images. Fixed script incl. a version for Enhanced Density attached. atx-200105.zip
  15. You have too many nice friends for anybody to understand which post or link you are talking about. A little help from your side would be a real improvement in communication for everybody following this thread.
×
×
  • Create New...