[Sav]

Hi, I'm a newbie of the mac platforms.
I got an I-mac dv with a g3 500 cpu and os X 10.2.6 fully up-to-date.
My hd makes a strange sound (like a scratch) when I try to load the screensaver.prefpane or Iphoto. The applications don't start and I got the message "the application ... was closed without consequences..."
When I do a prebinding update, the operation stops with this message: "bus error", after doing the same strange noise.
I removed and reinstalled Iphoto, but I got the same problem.
I don't know if the crash log of he screensaver engine can help:



Date/Time: 2003-07-07 17:45:19 +0200
OS Version: 10.2.6 (Build 6L60)
Host: Computer-di-Sav.local.

Command: ScreenSaverEngine
PID: 3174

Exception: EXC_BAD_ACCESS (0x0001)
Code[0]: 0x0000000aCode[1]: 0x90a16c60

Thread 0 Crashed:
#0 0x8fe0f400 in relocate_symbol_pointers_in_library_image
#1 0x8fe10f8c in relocate_modules_being_linked
#2 0x8fe106b0 in link_in_need_modules
#3 0x8fe121a4 in _dyld_link_module
#4 0x90016ac8 in NSLinkModule
#5 0x90689238 in objc_loadModule
#6 0x97e40904 in _NSBundleLoadCode
#7 0x97e398b0 in -[NSBundle load]
#8 0x97e41be4 in -[NSBundle principalClass]
#9 0x000058bc in 0x58bc
#10 0x0000506c in 0x506c
#11 0x97dfab58 in _nsNotificationCenterCallBack
#12 0x901684d0 in _postNotification
#13 0x90165be4 in _CFNotificationCenterPostLocalNotification
#14 0x9318a720 in -[NSApplication _sendFinishLaunchingNotification]
#15 0x93161624 in _requiredAEEventHandler
#16 0x91b56570 in _Z20aeDispatchAppleEventPK6AEDescPS_mPh
#17 0x91b590cc in _Z25dispatchEventAndSendReplyPK6AEDescPS_
#18 0x91b56478 in aeProcessAppleEvent
#19 0x96a83778 in AEProcessAppleEvent
#20 0x9308e0a8 in _DPSNextEvent
#21 0x930a0158 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
#22 0x000072b8 in 0x72b8
#23 0x930b1d88 in -[NSApplication run]
#24 0x00004678 in 0x4678
#25 0x00004328 in 0x4328
#26 0x000041a8 in 0x41a8

PPC Thread State:
srr0: 0x8fe0f400 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x8fe0f2ec ctr: 0x8fe31a4c mq: 0x00000000
r0: 0x000031bc r1: 0xbfffd480 r2: 0x00000000 r3: 0x90a0cc08
r4: 0x8fe4b404 r5: 0x8fe4b400 r6: 0x90a0c8f8 r7: 0x90a0c5e8
r8: 0x000000c4 r9: 0x001f6e05 r10: 0x0000005f r11: 0x90a16c5f
r12: 0x90a90728 r13: 0x00000000 r14: 0x00000000 r15: 0x8fe4b3fc
r16: 0x8fe4b404 r17: 0x8fe4b400 r18: 0x8fe4841c r19: 0x8fe4850c
r20: 0x90a0b19c r21: 0x8fe4e33c r22: 0x90a13aa4 r23: 0x90a0c5e8
r24: 0x909a06a8 r25: 0x90a06088 r26: 0x001f6e05 r27: 0x909a06a8
r28: 0x8fe4e33c r29: 0x001f6e05 r30: 0x8fe4e644 r31: 0x8fe0f2ec

**********

Bye

Sav

[pat++]

Repair the disk. Either boot from the CD and use Disk Utility, or boot in single user mode, and use :

fsck -y

until it does not report any errors.
(Repairing permissions is a good idea too).

If the disk makes a weird noise, it may be an hardware issue... you may need to replace it...

[Sav]

I used fsck -y but withou any report.
Is it normal?

[pat++]

Originally posted by Sav:
I used fsck -y but withou any report.
Is it normal?

You have to boot in single user mode (restart and hold command-S during startup). You'll get a back screen. Then only, try fsck -y