Jump to content

Great Hierophant

Members
  • Posts

    1,684
  • Joined

  • Last visited

3 Followers

Contact / Social Media

Profile Information

  • Custom Status
    Scribbler
  • Gender
    Male
  • Location
    Massachusetts

Recent Profile Visitors

15,831 profile views

Great Hierophant's Achievements

Stargunner

Stargunner (7/9)

696

Reputation

  1. A friend of mine noted that both Choplifter! (1982)(Broderbund Software)(US)[a][!].atx and Choplifter! (1982)(Broderbund Software)(US)[a2][!].atx in the a8preservation archive replace the copy-protection check at $067D with a JMP past it. In other words, these are cracked disks. Should they have the [!] label attached to them, which I understand to mean a pristine dump of original media? Now if these images were made from a budget re-release disk, that might explain why they were cracked. Companies were known to do budget re-releases and eliminate copy protection which was not cost-effective to replicate. Can anyone shed more light on the subject?
  2. My friends found a copy of Chuck Benton's version of Sierra's Frogger for the Atari 8-bit machines while trying to redump the PC version. Sierra did not mark their labels with the version of the software they contained in the early years and they bought up as many disk only options as they could find back in 2014. Unfortunately they were unable to find the PC version in their copies but found many copies of John Harris' version (which is already in the archive) and one copy of the Benton version. I have attached the Kryoflux dump Frogger-Atari-Benton.7zof the Benton version and an ATX image made from it. It works with my 48KiB 400 and SDrive Max and Altirra.Frogger-Atari-Benton.7z Frogger_Sierra_Chuck_Benton.atx
  3. Replacing my Pokey fixed my issue and it should fix the OP's.
  4. My replacement POKEY came from Best Electronics today and fixed my problem. Now I get Memo Pad or a BASIC prompt in 2 seconds or disks start loading instantly from my SDrive MAX (and successfully too).
  5. I replaced the PIA with the 68B21 and all of the other generic logic chips (with the exception of the LS02 on the CPU board) and no change resulted in the blue screen. I await my POKEY from Best Electronics in the hopes of a fix.
  6. You may be able to get to the Ready prompt in BASIC or show the Memo Pad if you press the Break key when you see the blue cursor. Have you tried a cartridge game?
  7. This sounds like the problem I'm having with my 400, did you try pressing the Break key when you see the cursor or hold the Start key down as you boot and hear a buzz?
  8. It does use a Synertek 6520, and if I knew about Best's IC list, I'd have gone with them and got the Pokey there as well.
  9. I have ordered a 68B21 off Jameco to try to see if the PIA is the problem, but if it is not, has anyone a spare POKEY they can sell to me?
  10. Timestamp here shows the system booting to memo pad and you can see the speaker is not connected. What happens with the keyboard removed? Nothing, I just see the blue screen with the cursor.
  11. My BASIC Cartridge came today but will not show the READY prompt until I press the Break Key. I learned from Adrian Black's channel that the speaker need not be connected for the system to boot to Memo Pad. I also do not hear the stuttering sound that should be heard for 2 seconds until the Atari Computer - Memo Pad text appears. That stuttering sound is generated by Pokey, not the speaker.
  12. I've swapped the CPU with one from an Apple IIe, tried booting without Pokey and without PIA and both and no change in behavior. System still booted.
  13. SIO Internal Chip Data In 3 14 POKEY Data In 24 Data Out 5 13 POKEY Data Out 28 Command 7 12 PIA CB2 19 I traced the pinouts of the three signal wires the SIO uses to communicate with the SDrive Max and checked continuity from the pins on the chips to the pins on the adapter board inside the SDrive Max where the SIO pins connect. All are good. I observe that as virtually every cassette program I loaded works, and the cassette recorder uses Data In and Data Out but not Command, then that would suggest that the Pokey is not the problem chip (thank god if it is not). I've reseated every other chip in the system and still no signs that the system is receiving whatever disk data the SDrive Max is trying to send.
×
×
  • Create New...