(Topic ID: 284216)

Questions about burning 2732 Eproms for bally -17/-35 at U2 and U6

By T-Tommy

3 years ago


Topic Heartbeat

Topic Stats

  • 28 posts
  • 9 Pinsiders participating
  • Latest reply 3 years ago by barakandl
  • Topic is favorited by 2 Pinsiders

You

Linked Games

No games have been linked to this topic.

    Topic Gallery

    View topic image gallery

    GQ-4X_power_pack.png

    You're currently viewing posts by Pinsider slochar.
    Click here to go back to viewing the entire thread.

    #15 3 years ago
    Quoted from Coyote:

    Be sure to do a verify afterwards - if the chip wasn't getting enough power from the programmer, then a verify would catch any bits that weren't written right.

    Also it can help to double and triple burn, and to catch some counterfeits, I always remove the eprom, wait a minute or so, put it back in with a cleared buffer, read in what's on the new chip, save it and compare it to the original file.

    #21 3 years ago
    Quoted from Tuukka:

    With most programmers, the double or triple burn will not help, because the programmer first reads the eprom location and compares it with the data to be programmed, and skips programming if it is already correct.

    Hmmm interesting. I guess that would explain why it sometimes goes faster.

    #27 3 years ago

    Yes, fc /b fileone.ext filetwo.ext

    You're currently viewing posts by Pinsider slochar.
    Click here to go back to viewing the entire thread.

    Reply

    Wanna join the discussion? Please sign in to reply to this topic.

    Hey there! Welcome to Pinside!

    Donate to Pinside

    Great to see you're enjoying Pinside! Did you know Pinside is able to run without any 3rd-party banners or ads, thanks to the support from our visitors? Please consider a donation to Pinside and get anext to your username to show for it! Or better yet, subscribe to Pinside+!


    This page was printed from https://pinside.com/pinball/forum/topic/questions-about-burning-2732-eproms-for-bally-17-35-at-u2-and-u6?tu=slochar and we tried optimising it for printing. Some page elements may have been deliberately hidden.

    Scan the QR code on the left to jump to the URL this document was printed from.