David, I've been through this issue, with some tragic results that may not apply to your situation. I'll comment anyway, first describing what happened to my machine.
I had OS10.1 ( on partition #1) running and after a while my wonderfully stable machine became incredibly flaky. It actually crashed (kernel panic)! And apps would crash frequently. I used Norton's a couple times and then things completely went to heck. DiskDoctor was in no way up to repairing the disk in fact it seemed that it had probably trashed the directories for good. I salvaged my data (not the bootable OS) with DiskWarrior, best $70 I've spent in some time. After I put things back together I booted OS 9 (on partition #2 - which had never displayed any problems) and 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. OS 10.2 has never crashed, NEVER. Neither have apps such as TextEdit (detractors?) and this system has been run hard... 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. > > (3) there is no way to tell the operating system to not use those particular addresses? The only way I know of is to replace the RAM. > (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 --- David Elmo <[EMAIL PROTECTED]> wrote: > Used Gauge Pro for the first time on my 7600 Powerlogic G3/4 360 MHz > 576MB > RAM (8 by 64) running on 9.0.4 with VM turned off and was surprised > to see > it kept finding faults at various addresses on the memory check on > various > passes. My machine rocks along just fine and nothing shows up on the > presumably more superficial memory check (when enabled) at start up). > So > there is no crisis - still, it is a niggling thing now ... naturally > I want > to put off pulling chips and testing individually as long as possible > so I > thought to pester you folk ... > > david_elmo __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- 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
