Jump to content

JR>

Members
  • Posts

    563
  • Joined

  • Last visited

Posts posted by JR>

  1. 3 hours ago, tep392 said:

    I tried it out after verifying the voltages were all good.  The drive will spin for a couple seconds after I power it up, as expected. But when I try to access the drive, nothing happens and I get a 138 - Device Timeout.  It seems that the control board isn't communicating with my Atari.

    Are you sure it's set as d1:? Have you tried booting from a different drive and see if it responds as a different drive number?

     

  2. 5 hours ago, TZJB said:

    I just found out that you can easily use a 2764 to replace a 2732 by duplicating the 4KB data into the upper bank. Then connect pins 1,2,26,27 & 28 together and orientate into the socket with pin 3 to pin 1 of the socket and the corresponding pin 26 to the socket pin 24 which is VCC 5V. All the other pins then line up with the correct signals. You do need enough room for the overhang but I just tried it successfully with a US Doubler.

     

    image.thumb.png.de31447ed797611c38396d655543c523.png

    I've always liked this diagram that shows just how pin compatible all of the 27xxx EPROMs are: 

     

    2532 Eprom Pinout

     

     

    • Like 1
    • Thanks 1
  3. 3 hours ago, zzip said:

    I swear I tried both and both triggered the update,  but maybe refind was shuffling the menu order on me?

    Or maybe there just happened to be a valid update when you tried....lol. At any rate I think one is a recovery partition that will always trigger the update and the other is the active one.

  4. On 1/3/2023 at 6:59 AM, zzip said:

    Those instructions are using rEFInd instead of Grub2.    I'd actually prefer to use rEFInd, however whenever I boot Atari OS with it it triggers "update mode" and the VCS will download and reinstall the latest update everytime you boot it through the menu.

     

    What my instructions do is provide a way to boot AtariOS through grub without triggering that issue.    If/when I can find a way to do the same with rEFInd, I'd probably switch.  rEFInd likes to autodetect the bootable OSes available rather than you providing the list and special parameters

    I installed refind and it came up with multiple bootable instances of AtariOS. One of the instances would trigger a reinstall, but the other doesn't. I just removed that instance from the refind menu.

  5. 12 minutes ago, Justin Payne said:

    How good are these things at diagnosing issues? 

     

    Seems to do a pretty good job.  I just picked one up recently and tested several 8 bits that seemed perfectly functional.  It identified problems with several of them that I would probably never have noticed without it.  The long burn in tests are especially good in finding faults that are intermittent.

    • Like 1
  6. On 11/8/2020 at 9:54 AM, MrFish said:

    Haha... ok, glad I alerted you in the appropriate season.

     

    Thanks for the board pictures and ROM dump, btw.

     

    Well, so far rooting about has not yet yielded the manual.  Searching my email does reveal that I should have a photocopied manual somewhere. Apparently Rory McMahon was kind enough to send this to me way back in 2005.  We also discussed the disks.  He was going to check and see if he had them in with his boxed Amdek III, but it doesn't look like either of us ever followed up on that.

     

    Back to rooting.....coming across all kinds of stuff I'd forgotten about!

    • Like 1
×
×
  • Create New...