Thanks Scott, really appreciate your experience. Yes, I do a lot of editing and stuff and you make me want to more urgently weed the faulty chips out (if indeed they are faulty). I ran TechTool Pro 2 memory tests and nothing was reported as faulty but it is very old software (2.03r1). Gauge PRO turns up faults and is very definite about it.
Actually, I had 8 matching 64s when I got this machine but put in a 128 into A1. First thing I will do is put the original 64 back and run the test again. If faults still appear, I will go do the methodical ... (yawn). How I am tempted to go buy 8 x 128 brand new FPMs! (Anyone who has done this with a PowerLogic G3 (mine is 360 MHz) with OS 9.. (mine is 9.04 but 9.1 will do) is welcome to tell me the brand and where to buy). Guess the cost may make it tempting to go to real G4? Still would like to hear from anyone who knows how the memory addressing system works in relation to the memory bays. In relation to A1, A2 ... B1, B2 ... how do the hexadecimal numbers that mark the addresses apportion to the bays (obviously depends on how big the chips are ... but the addressing must start somewhere and finish somewhere ...) > From: scott granlund <[EMAIL PROTECTED]> > Subject: Re: Memory addresses and faults > In-Reply-To: <[EMAIL PROTECTED]> > > David, I've been through this issue, snip > I ... ran Gauge Pro. It showed the > memory address problems you describe. I located and replaced the bad > chip and all has been well ever since. snip > My theory: > OS 9 and the usual usage (e-mail, web-surf, light PhotoShop etc.) never > writes up to the ends of your available RAM. OS 10 will use everything > available. With OS 9, I never made it up to the 500+M mark where I had > a problem but OS 10 used that space and the bad addressing trashed the > drives partition #1 directory. > >> My questions: >> >> (1) How do I identify the chips from the memory addresses given. An >> example:notice comes up that says there is a memory error "at address >> $0D7C62F4.Expected $56801FF4 but read $56821FF4" > > Boot the machine on 1 RAM chip and check it out, or do two at a time > and then swap them in their slots. The area the OS uses, you've > noticed, doesn't get checked. Crappy process but repeat till you have a > culprit, and have done them all. > > >> (2) Gauge Pro seems not to issue a report, I have been >> shift+command+4 snapping the "faults" as they are reported >> but can't keep doing this and having so many pics. Is there an >> easier way of getting a list of faults from Gauge Pro. > > I'm all ???s here. Sure, try TechTool. I think idea #1 wiil get you > there though. snip >> (4) Is Gauge Pro reporting real faults? > > I believe it is! I also think that if you intend to do any intensive > editing you should get the bad RAM chip out of there or suffer some > sort of data corruption! > > Hope that was of some use, > > Scott -- PCI-PowerMacs is sponsored by <http://lowendmac.com/> and... Small Dog Electronics http://www.smalldog.com | Refurbished Drives | -- Sonnet & PowerLogix Upgrades - start at $169 | & CDRWs on Sale! | Support Low End Mac <http://lowendmac.com/lists/support.html> PCI-PowerMacs list info: <http://lowendmac.com/lists/pci-powermacs.shtml> --> AOL users, remove "mailto:"; Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive:<http://www.mail-archive.com/pci-powermacs%40mail.maclaunch.com/> Using a Mac? Free email & more at Applelinks! http://www.applelinks.com
