Welcome, Guest. Please login or register.

Author Topic: Just got my first A2000! :)  (Read 11875 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline GadgetUK

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show all replies
Re: Just got my first A2000! :)
« on: August 17, 2013, 11:24:22 AM »
Grats on your purchase!!  Looks tidy and minimal acid damage!
 

Offline GadgetUK

  • Jr. Member
  • **
  • Join Date: Mar 2013
  • Posts: 89
    • Show all replies
Re: Just got my first A2000! :)
« Reply #1 on: August 20, 2013, 09:23:36 PM »
Quote from: Oldsmobile_Mike;745493
Well, no love from my A2000 clock yet.  The new LIR batteries arrived (thankfully I ordered two - one arrived DOA!), but the other read a solid 3.6V on the battery itself, and 3.31V at the resistor.  I checked this on my spare A2000 board and noticed there's also about a .3V drop between those two points, so I'm sort of thinking this is normal?

Anyhow, set the clock and left it off overnight, and it's still showing the wrong time.  I'm suspecting my clock chip must be toast, any thoughts?  I'm not really adept enough with soldering to replace the clock chip, wonder if it's time to ship it off to someone else?  *sigh*  Should I check pin 9 for continuity to ground?  Am not 100% positive on which is pin 9, I think it's the top-right when facing the front of the system?

I also tried a variety of "setclock reset" and "setclock save" commands from the shell, just in case it was something in WB that was knackered.

------------------------------------------------------------------

Also, why the bloody he** is OS3.9 so slow?  I don't remember it taking close to 3 minutes to boot up on my old A1200 back in the day, and I sure didn't have an 040 in my A1200!  Icons load at a glacial pace, and all I've got is a fresh install with all the Boing Bags, Visual Prefs, Full Palette (to use the Rebel 16-color palette), FBlit, and BlazeWCP.  I've already removed AmiDock.  Seems like the more patches I put in to try to speed things up the slower it goes, might have to revert back to MagicWB icons, LOL.  :p


Get the schematics out and trace connectivity to each pin on the clock chip from agnus or wherever it's supposed to connect.  It could be the variable cap affected by corrosion as well - you could probably take one from a 500 memory expansion.