OS 10.6 appears to have corrupted Microtek 9800XL with TMA scanner
Here is the crash report. Microtek has sent me upgraded drivers, etc.... but they say it is an issue with OS 10.6 (10.6.8) that has corrupted their drivers so any time I try to scan, it crashes. However, it had been working for quite a whle with 10.6.8.
Process: ScanWizard Pro 7 [735]
Path: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7
Identifier: com.microtek.SW_Pro
Version: 7.75 (7.75)
Code Type: PPC (Translated)
Parent Process: launchd [100]
Date/Time: 2012-03-12 13:11:32.750 -0400
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 113847 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 154 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 8AC3A1C2-A477-4934-A180-893776DFD4AA
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000001e4c2042
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0xffff1259 __longcopy + 89
1 libSystem.B.dylib 0xffff0876 __memcpy + 214
2 ??? 0x7f8f21ce 0 + 2140086734
3 libSystem.B.dylib 0x8014cea4 memmove + 0
4 ??? 0xbfff96c0 0 + 3221198528
5 ??? 0x3a100557 0 + 974128471
Thread 1:
0 libSystem.B.dylib 0x80142afa mach_msg_trap + 10
1 libSystem.B.dylib 0x80143267 mach_msg + 68
2 com.microtek.SW_Pro 0xb819440f CallPPCFunctionAtAddressInt + 206231
3 libSystem.B.dylib 0x80170259 _pthread_start + 345
4 libSystem.B.dylib 0x801700de thread_start + 34
Thread 2:
0 com.microtek.SW_Pro 0xb815acc0 spin_lock_wrapper + 90152
1 com.microtek.SW_Pro 0xb8179c5b CallPPCFunctionAtAddressInt + 97763
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 3:
0 com.microtek.SW_Pro 0xb815a8ff spin_lock_wrapper + 89191
1 com.microtek.SW_Pro 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 4:
0 com.microtek.SW_Pro 0xb815aa8b spin_lock_wrapper + 89587
1 com.microtek.SW_Pro 0xb818c3eb CallPPCFunctionAtAddressInt + 173427
2 com.microtek.SW_Pro 0xb818eeec CallPPCFunctionAtAddressInt + 184436
3 com.microtek.SW_Pro 0xb80e88cb 0xb8000000 + 952523
4 ??? 0x8af50296 0 + 2331312790
Thread 5:
0 com.microtek.SW_Pro 0xb815a8ff spin_lock_wrapper + 89191
1 com.microtek.SW_Pro 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 6:
0 com.microtek.SW_Pro 0xb815a8ff spin_lock_wrapper + 89191
1 com.microtek.SW_Pro 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 7:
0 com.microtek.SW_Pro 0xb815a8ff spin_lock_wrapper + 89191
1 com.microtek.SW_Pro 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 8:
0 com.microtek.SW_Pro 0xb815a8ff spin_lock_wrapper + 89191
1 com.microtek.SW_Pro 0xb8176e5d CallPPCFunctionAtAddressInt + 85989
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145397 spin_lock_wrapper + 1791
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 9: com.apple.CFSocket.private
0 com.microtek.SW_Pro 0xb815ac81 spin_lock_wrapper + 90089
1 com.microtek.SW_Pro 0xb816ad6f CallPPCFunctionAtAddressInt + 36599
2 com.microtek.SW_Pro 0xb80c6b13 0xb8000000 + 813843
3 com.microtek.SW_Pro 0xb80c0037 0xb8000000 + 786487
4 com.microtek.SW_Pro 0xb80dd8e8 0xb8000000 + 907496
5 com.microtek.SW_Pro 0xb8145c1d spin_lock_wrapper + 3973
6 com.microtek.SW_Pro 0xb801ceb7 0xb8000000 + 118455
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00038000 ebx: 0x00000000 ecx: 0xffdfffc6 edx: 0x00040000
edi: 0x1e489e40 esi: 0x1e489e42 ebp: 0xbfff869c esp: 0xbfff8690
ss: 0x0000001f efl: 0x00010206 eip: 0xffff1259 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x1e4c2042
Binary Images:
0x80000000 - 0x8005dff7 com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x8007d000 - 0x800e7fe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x80142000 - 0x802e9ff7 libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
0x8036b000 - 0x804e6fe7 com.apple.CoreFoundation 6.6.6 (550.44) <F88C95CD-1264-782D-A1F5-204739847E93> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x805de000 - 0x805ecfe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
0x805f1000 - 0x805fdff7 libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
0x80601000 - 0x80647ff7 libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
0x80654000 - 0x807d6fe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <D5980817-6D19-9636-51C3-E82BAE26776B> /usr/lib/libicucore.A.dylib
0x80838000 - 0x808e5fe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
0x808f9000 - 0x808fcfe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <39AC3185-E633-68AA-7CD6-1230E7F1CEF4> /usr/lib/dyld
0xb8000000 - 0xb81defff +com.microtek.SW_Pro 7.75 (7.75) <CC0F32CD-4587-7C83-03D0-9CFE28A58FB6> /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
Translated Code Information:
objc[735]: garbage collection is ON
Rosetta Version: 22.27
Args: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 -psn_0_274499
Exception: EXC_BAD_ACCESS (0x0001)
Thread 0: (0xb0220d74, 0xb815a8ff)
0x98c91aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x98c90190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c91abc ctr: 0x98b0d600
r00: 0xffffffda r01: 0xf0284dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b80c0dc r06: 0x00000020 r07: 0x00000000
r08: 0x3b80c0dc r09: 0x00000000 r10: 0x3b80c0dc r11: 0xa0cb6698
r12: 0x98b0d600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0cbc7cc r22: 0xa0cbc7c0 r23: 0xa0cbc7c8
r24: 0x00000310 r25: 0x9ebe7dee r26: 0xa0cbc50c r27: 0x00000040
r28: 0x0000000f r29: 0x223340dc r30: 0xa0cbc7a0 r31: 0x98c919b4
Thread 1: (0xb0324d74, 0xb815a8ff)
0x98c91aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x98c90190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c91abc ctr: 0x98b0d600
r00: 0xffffffda r01: 0xf0386dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9aabca r06: 0x00000020 r07: 0x00000000
r08: 0x3b9aabca r09: 0x00000000 r10: 0x3b9aabca r11: 0xa0cb6698
r12: 0x98b0d600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0cbc7cc r22: 0xa0cbc7c0 r23: 0xa0cbc7c8
r24: 0x00000310 r25: 0x9eede323 r26: 0xa0cbc50c r27: 0x00000040
r28: 0x0000000f r29: 0x224d2bca r30: 0xa0cbc7a0 r31: 0x98c919b4
Thread 2: (0xb011c84c, 0xb815aa8b)
0x9097531c: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFRunLoopModeIsEmpty + 160
0x909799c8: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFRunLoopRun + 2396
0x9097ac18: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRunSpecific + 656
0x9097ae78: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFRunLoopRun + 72
0x90abf46c: /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv : TSystemNotificationTask::SystemNotificationTaskProc(void*) + 556
0x9064b988: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _PrivateMPEntryPoint + 100
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98b0dcc4 ctr: 0x98b0d590
r00: 0xffffffe1 r01: 0xf0203060 r02: 0xa01053f4 r03: 0xf020317c
r04: 0x07000006 r05: 0x00000000 r06: 0x00000800 r07: 0x0000802f
r08: 0x00000000 r09: 0x00000000 r10: 0x00000000 r11: 0xa0cb6194
r12: 0x98b0d590 r13: 0x00000000 r14: 0x7fffffff r15: 0xffffffff
r16: 0x00000301 r17: 0x5567b288 r18: 0xa0cbd6d0 r19: 0x90a2eba8
r20: 0xa0104a3c r21: 0xf020317c r22: 0xf020317c r23: 0x00000000
r24: 0x00000800 r25: 0x0000802f r26: 0x00000000 r27: 0x00000000
r28: 0x07000006 r29: 0x07000006 r30: 0x00000000 r31: 0x90979074
Thread 3: (0xb03a6d74, 0xb815a8ff)
0x98c91aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x98c90190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c91abc ctr: 0x98b0d600
r00: 0xffffffda r01: 0xf0407dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9899b9 r06: 0x00000020 r07: 0x00000000
r08: 0x3b9899b9 r09: 0x00000000 r10: 0x3b9899b9 r11: 0xa0cb6698
r12: 0x98b0d600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0cbc7cc r22: 0xa0cbc7c0 r23: 0xa0cbc7c8
r24: 0x00000310 r25: 0x9bbec6b6 r26: 0xa0cbc50c r27: 0x00000040
r28: 0x0000000f r29: 0x224b19b9 r30: 0xa0cbc7a0 r31: 0x98c919b4
Thread 4: (0xb0428bcc, 0xb815ac81)
0x9098644c: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFSocketManager + 796
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9098654c ctr: 0x98b6e258
r00: 0x0000005d r01: 0xf040fa90 r02: 0xa00f6138 r03: 0x00000020
r04: 0x1e274c70 r05: 0x1e257d30 r06: 0x00000000 r07: 0x00000000
r08: 0x000000f0 r09: 0xa0106b80 r10: 0xa0f470b4 r11: 0xa00f1448
r12: 0x98b6e258 r13: 0xa0104a3c r14: 0x1e257d30 r15: 0x00000000
r16: 0xa0106138 r17: 0x1e274c70 r18: 0x1e274be0 r19: 0x90a2fd2c
r20: 0x00000000 r21: 0x1e274c80 r22: 0xf0407e60 r23: 0xa01051b8
r24: 0x00000001 r25: 0x1fb03c90 r26: 0x00000020 r27: 0x1fb03bcc
r28: 0x1fb03b50 r29: 0x1fb02d00 r30: 0x00000000 r31: 0x90986138
Thread 5: (0xb02a2d74, 0xb815a8ff)
0x98c91aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x98c90190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c91abc ctr: 0x98b0d600
r00: 0xffffffda r01: 0xf0305dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9a759c r06: 0x00000020 r07: 0x00000000
r08: 0x3b9a759c r09: 0x00000000 r10: 0x3b9a759c r11: 0xa0cb6698
r12: 0x98b0d600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0cbc7cc r22: 0xa0cbc7c0 r23: 0xa0cbc7c8
r24: 0x00000310 r25: 0x9bbe4025 r26: 0xa0cbc50c r27: 0x00000040
r28: 0x0000000f r29: 0x224cf59c r30: 0xa0cbc7a0 r31: 0x98c919b4
Thread 6: Crashed (0xbfff8690, 0xffff1259)
0x9099689c: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFStringChangeSizeMultiple + 944
0x909a4a20: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : _CFStringFindAndReplace + 516
0x00014830: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : UpdateNavEditFileName(NavCBRec*, bool) + 676
0x0001166c: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : myCustomEventProc(long, NavCBRec*, void*) + 480
0x97ad42b8: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : _SendStartEvent + 256
0x97ad4680: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSNavSavePanel sendCBEvent:withData:] + 860
0x97ad5fb4: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSNavSavePanel willBecomeVisibleNotification:] + 108
0x995db17c: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation : __nsnote_callback + 360
0x9094f790: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : ___CFXNotificationPost + 840
0x90950e98: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation : __CFXNotificationPostNotification + 752
0x995db370: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation : -[NSNotificationCenter postNotificationName:object:userInfo:] + 92
0x97a11350: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 792
0x97acf5b4: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSNavSavePanel _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 512
0x97485370: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 652
0x97488004: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector :contextInfo:] + 744
0x97488588: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSApplication runModalForWindow:] + 132
0x977edc68: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSSavePanel runModal] + 360
0x97ad0478: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : -[NSNavSavePanel run] + 120
0x97ad3d28: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit : __NSNavDialogRun + 228
0x963d5108: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices : _NavPutFile + 176
0x00010820: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : Navi_GetSaveFile(STNLYHeader*, short*, IEFM_ShowUI*, long) + 536
0x00016d34: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : StartScanCallBackProc(long, long) + 136
0x007a80a0: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : AIMStartScanCallbackProc(long, long) + 192
0x0081be18: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : HandleScanButtonClick() + 760
0x00819410: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : HandlePreviewWindowClick(EventRecord*, Point) + 1004
0x00808194: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : DoContentClick(OpaqueWindowPtr*, EventRecord*) + 180
0x00807974: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : HandleMouseDown(EventRecord*) + 956
0x00805a10: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : WMEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1712
0x971b44ec: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1524
0x971b4ea8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 456
0x971b51e8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _SendEventToEventTarget + 72
0x971b06a4: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1084
0x971b4924: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2604
0x971b4ea8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 456
0x971b51e8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _SendEventToEventTarget + 72
0x971b0d18: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _ToolboxEventDispatcher + 88
0x971ce9fc: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _GetOrPeekEvent + 584
0x971ced2c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _GetNextEventMatchingMask + 448
0x971cefb4: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _WNEInternal + 180
0x971cf1a8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox : _WaitNextEvent + 76
0x00016e70: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : GetNExtEventCallBackProc(short, EventRecord*, unsigned long, OpaqueRgnHandle*, long) + 88
0x007a6ff0: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : AIMEventLoop() + 248
0x007a729c: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : acquireDoShowUI(AcquireRecord*, short, short, short*, ShowUI*) + 388
0x007a5084: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : acquireDoStart(AcquireRecord*) + 644
0x007a45a4: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : MAINENTRY(short, AcquireRecord*, long*, short*) + 532
0x007a437c: /Library/Frameworks/MicrotekScanWizardPro.framework/Versions/A/MicrotekScanWiza rdPro : _ScannerServiceEntry + 68
0x00015e24: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : _main + 712
0x00002d64: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : __start + 760
0x00002a68: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : start + 48
0xc8f7ffbf: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x90996afc ctr: 0x98b0ed40
r00: 0x90996afc r01: 0xbfff96c0 r02: 0x00000000 r03: 0x1e289e09
r04: 0x1e289e0b r05: 0xfffffffd r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x42242024 r10: 0x00000020 r11: 0xa00f1514
r12: 0x98b0ed40 r13: 0x00000000 r14: 0x20000000 r15: 0xbfff9728
r16: 0x00000001 r17: 0x00000020 r18: 0x1e289e01 r19: 0xfffffffe
r20: 0x0000000a r21: 0x1e289e01 r22: 0xfffffffd r23: 0x00000001
r24: 0x00000000 r25: 0x03af9cd0 r26: 0xbfff9840 r27: 0x0000000a
r28: 0x00000005 r29: 0x00000007 r30: 0x00000020 r31: 0x909964f8
Thread 7: (0xb009ad38, 0xb815acc0)
0x98c904b8: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
0x98c8fe9c: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 308
0x98c9002c: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 372
0x98c90168: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c90480 ctr: 0x98b512d8
r00: 0x0000016b r01: 0xf0080bb0 r02: 0x00000002 r03: 0x00000004
r04: 0x00000000 r05: 0x00000000 r06: 0xf0080d0c r07: 0x00000001
r08: 0xf0080d28 r09: 0x00000000 r10: 0x00000002 r11: 0xa0cb5530
r12: 0x98b512d8 r13: 0x10624dd3 r14: 0x98cdfb04 r15: 0xf0080c0c
r16: 0xf0080c8c r17: 0xa0cd03dc r18: 0xf0080d28 r19: 0xa0cca588
r20: 0xa0ccb588 r21: 0xf0080d0c r22: 0xa0cca508 r23: 0xa0cca488
r24: 0xa0cd03dc r25: 0x00000000 r26: 0xa0cbc62c r27: 0x00000000
r28: 0xa0cbc604 r29: 0xa0cbc33c r30: 0xf0080d28 r31: 0x98c903dc
Thread 8: (0xb019ed74, 0xb815a8ff)
0x98c91aa4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x98c90190: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x98badf08: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /Applications/ScanWizard Pro 7/ScanWizard Pro 7.app/Contents/MacOS/ScanWizard Pro 7 : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x98c91abc ctr: 0x98b0d600
r00: 0xffffffda r01: 0xf0182dc0 r02: 0x00000000 r03: 0x00002703
r04: 0x00000040 r05: 0x3b9aa563 r06: 0x00000020 r07: 0x00000000
r08: 0x3b9aa563 r09: 0x00000000 r10: 0x3b9aa563 r11: 0xa0cb6698
r12: 0x98b0d600 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0cbc7cc r22: 0xa0cbc7c0 r23: 0xa0cbc7c8
r24: 0x00000310 r25: 0x9edc8faa r26: 0xa0cbc50c r27: 0x00000040
r28: 0x0000000f r29: 0x224d2563 r30: 0xa0cbc7a0 r31: 0x98c919b4
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 6 GB, SMC 1.25f4
Graphics: ATI Radeon HD 2600 XT, ATI Radeon HD 2600, PCIe, 256 MB
Memory Module: global_name
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: ATI Radeon HD 2600, sppci_displaycontroller, Slot-1
Serial ATA Device: WDC WD3200AAJS-41VWA0, 298.09 GB
Parallel ATA Device: OPTIARC DVD RW AD-7170A
USB Device: Portable USB 3.0 Drive, 0x18a5, 0x022e, 0xfd200000 / 8
USB Device: FreeAgent GoFlex, 0x0bc2 (Seagate LLC), 0x5031, 0xfd100000 / 3
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd500000 / 2
USB Device: Vendor-Specific Device, 0x05da (Microtek International Inc.), 0x20de, 0xfd510000 / 9
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd540000 / 4
USB Device: Hub in Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x1003, 0xfd542000 / 6
USB Device: Apple Pro Keyboard, 0x05ac (Apple Inc.), 0x020b, 0xfd542300 / 7
USB Device: Desktop USB Drive, 0x18a5, 0x0216, 0xfd541000 / 5
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x5d200000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec
It's highly unlikely that OS X has "corrupted their drivers." Sounds like some hot air to get you off their backs so they don't have to explain the problem to you.
Meanwhile I suggest you try VueScan. It does not require the MicroTek drivers (they can be removed.) VueScan supports your scanner model.
Similar Messages
-
After loading the latest Aperture 3 update, aperture will not load and it appears to have corrupted 10.6.7. and now appears to be missing from the computer and my administrator status has changed to standard. Update Software says I need to do update to 10.6.7 which I can't do because administrator privileges are gone. I didn't back-up with Time Machine ,BAD, but I have all files backed-up on another hard drive. Should I just reformat and start over? Any ideas or help would be appreciated.
PROBLEM SOLVED! For me at least!
Apple Support gave me the clue - I had run Migration Assistant, and it had obligingly replaced a system file (/Library/Frameworks/PluginManager.framework/Versions/B/PluginManager) with the equivalent from my old system.
I reinstalled 10.6.7 using the DVD supplied and all is well.
The moral is - don't use Migration Assistant.
Along the way Apple Support provided me with a link to download Combo update 10.6.7: this could not be installed on my iMac.
Hope this helps. -
CS4 Bridge appears to have corrupted my IPhoto 09 library !
I have MAC mini 10.6.8 Iphoto 09 and recently installed Adobe PS8 including CS4 bridge.
I accessed teh briedge and browsed to my master IPhoto library.
Now when I try and access the libraray through IPhoto I have at least the last year's photo missing.
I have no backup and these are irreplaceable.
LeeI accessed teh briedge and browsed to my master IPhoto library.
Don't know how you did that, bridge can't view the content of the library by default, it only shows the icon for library??
Now when I try and access the libraray through IPhoto I have at least the last year's photo missing.
If you have deleted files using Bridge they should still be in the trash, maybe you messed with the folders in the library and did move the year folder to an other location.
I have no backup and these are irreplaceable.
I'm sorry to hear that, don't think you should be in panic right now, there is still a lot to investigate, just don't empty the trash and try to investigate further.
For instance use the finder and select the iPhoto library, Then use right mouse click and from the menu choose show package content. Navigate through the files and find either the folder called Masters (or originals, believe they changed the name once)
Inhere should be different folders for each year containing a lot of subfolders. Copy (Copy, don't remove!) these folders to a new folder outside the iPhoto library and point bridge to this new main folder. Then in bridge go to the menu View and choose show items from subfolders and let Bridge cache. Then see what has been left of your files.
Also open the trash (click on on the icon in the Dock) and see if there is a folder with the year called or other files you recognize. Just drag them out of the trash to a new location.
In general, it is not a question of if your HD is going to die but when, they all die, some sooner then to be expected. Also the human factor is by far from trusted so always, (always!!!) make a back up of important files!!
And don't try to mix iPhoto and Elements/Bridge without learning more about this way of working, iPhoto uses a library with hidden files and creates a lot of spin off with different versions, thumbs sizes etc. they are by default not developed to work together -
Please HELP! iTunes Appears to have corrupted all my music Files.?
My music plays like its badly corrupted, skips, jumps, sounds like a scratched CD... it's not a hardware problem because I can still play sounds in other programs... but not in iTunes where ALL my music is.
What should I do?
Thank you so much to anyone who is able to helpActually I am running iTunes 6....
okay, we'd better check through the usual suspects. (with a 6.0.x, it's less likely to be a problem with an itunes plugin than with itunes 7.0.x)
iTunes and QuickTime for Windows: Songs and other audio don't play correctly -
XPJ file appears to be corrupt -- have exhausted all known fixes
Hello all,
Before I forget, here's the rundown on our system:
RoboHelp 8, version 8.0.2.208 (all patches up-to-date, to our knowledge); RoboHTML used exclusively
Microsoft Visual SourceSafe 2005, version 8.0.50727.42
Windows XP
Three help projects
Two on VSS; third does not work right from VSS, so we update it separately
One of the two on VSS appears to be corrupt (see below) -- RoboHelp hangs when trying to launch the XPJ file
All other help projects are fine
Four help authors
Background of the problem:
On Tuesday late afternoon, one of our authors was in the help project in question and had several topics checked out when our network went down. She closed the help project with the files still checked out, and when the network came back up, she went back in, got the expected messages about "files are checked out, do you want to replace them with the version from source control or keep them checked out and use your local copy." Since she didn't want to lose her changes, I instructed her to keep them checked out, and then check them back in when everything came up. However, when she tried to check them back in, RoboHelp hung. This was late in the day, so she closed down RH manually and resolved to deal with it in the morning.
The next morning, one of our other authors, who gets in very early, was able to get into the help project just fine and work in it all day. This second author was not aware that the problems from the previous day continued. I was also able to get into the help project at this time. The first author then tried to get into the help project, but wasn't able to get in at all. The second author needed to get into the checked out files to make changes, so I instructed the first author on how to go into VSS and check those files in directly from there, without having to get into RH. At this point, I assumed the problem resided only with the first author's instance of the project, but I didn't think that checking in some topics would exacerbate the problem. (Maybe it did.) I figured, at most, we might need to pull down the help project from the network to her C drive again to fix the problem.
A little while later, the third author and I both tried to get into the help project and were not able to. At this point, only the second author, who had gotten into the project early in the morning, was in the help project and was not having any problems. At the end of the day yesterday, she saved and checked in all of her files. However, this morning, she came in and now she is not able to get into the help project, either.
Troubleshooting attempted:
The error dialog that displays when you shut down an app manually indicates that the app has hung. (No kidding, but thought I'd better say I looked at it.) The actual error reports, of course, were incomprehensible.
Attempted to launch XPJ without source control: Made a copy of the help project to a different location and deleted the vssver2.scc files in the copy. Tried to launch XPJ and it hung.
Attempted to rebuild the XPJ and CPD files: Backed up the help project on C drive, deleted CPD file, renamed XPJ file, and then double-clicked the HHP file. Had to copy and paste the path to the RoboHTML.exe file in the Locate Program dialog box. Received an error that the HHP file is corrupt. Then opened RoboHelp and tried launching the HHP file from the Starter window. Received messages about making various APJ and FPJ files writable. Thought this was a good sign, so I clicked OK on all of them, and then RH hung again.
Pulled down a new version in source control to my C drive, but RH still hangs when launching XPJ. This problem appears to be with the version in source control as well.
At this point, we're afraid our only course of action is to get our IT department to revert the entire help project in source control to the version that existed before the network went down on Tuesday and then pull that version to our C drives. However, we will lose some work from late Tuesday and yesterday. Is there anything else we should try before doing this?
Thank you in advance for your help. I apologize for the novel, but I figured I better be thorough.
Thanks,
LisaFirst, check that the cpd, ldb and pss files aren't included in source control.
With Robohelp closed, ensure that there isn't an ldb file in your project directory - this should only exist while Robohelp is open but sometimes gets left behind when Robohelp crashes.
If you any of the above existe in the specified locations, delete them (and the cpd on the c drive for good measure) and try to open the project again.
If you want to test the project outside source control, there is an additional step which you don't mention, so I'll put it here in case you didn't do it and want to try again. As well as deleting the .scc files, you also need to manually edit the xpj file. Open it in Notepad and delete everything between the <miscproperties> tags. (If you only see <miscproperties/> don't do anything to the file. This can cause other issues, but I won't go into them right now. It might be relevent to the 3rd project you mentioned depending on what 'doesn't work right' means.)
See how that goes,
Amber -
Error message "iTunes has detected an iPod that appears to be corrupted"
Everything used to work just fine until recently. On my Windows XP Home SP3 laptop, with iTunes (version 9.0.2.25) already open, I connect my 5th Generation iPod Nano and get the following message in iTunes:
"iTunes has detected an iPod that appears to be corrupted. You may need to restore this iPod before it can be used with iTunes. You may also try disconnecting and reconnecting the iPod."
If I plug the iPod into the computer without first starting iTunes, the Windows ‘Auto Play’ message comes up immediately then disappears and then the following message appears:
"Your iPod needs to be formatted for use with Windows. Would you like to run iTunes to restore your iPod Now?"
Otherwise, the iPod functions normally when not connected in iTunes. I can play the music, videos, and record videos with no problems.
The troubleshooting steps I took were:
I performed a reset of the Nano by first sliding the hold switch on/off a few cycles, leaving switch off (no orange showing), then pressed and held the Menu + Select button until the Apple logo appeared. Then I tried it in iTunes again; no such luck, same error. I then did a reset again, this time with the iPod connected to an AC power source; still no luck. I tried the reset numerous times and it didn’t help.
Next, I ran the diagnostics by pressing and holding the Menu + Select buttons immediately followed by the Select + Reverse buttons. I stepped through all the diagnostics tests and all tests passed as far as I could tell (there was no errors reported).
After this, I tried it in iTunes again and still no luck.
I even tried the iPod on my Windows Vista Home Premium (32 bit) machine and it behaved the same way. The version of iTunes on that machine was at an earlier version when I first tried it there. I then upgraded iTunes to the latest version but that didn’t help either.
I can sync my iPod Touch and 2nd gen Nano without any problems.
Sorry about be long winded about this but I am wondering if anyone else may have other suggestions. I want to try and avoid a restore if possible because I have some videos I recorded that I would like to get off the iPod. I’m not concerned about my music files as I have them always backed up but didn’t get the videos off yet.I am having this same problem with my brand new Mac Pro. It seems to be tied to the computer awaking from sleep (no I am not leaving the iPod connected while sleep... I am referring to waking the computer from sleep and then connecting iPod as opposed to restarting the computer and then connecting the iPod). In other words, if you are getting this error message, try ejecting the iPod, restart your computer, then connect the iPod and see if the error message goes away. For me it does, but I only get one shot at it, if I eject the iPod and then reconnect it, the error message returns. This happens on both iPods I have. I have rebooted (hold menu-select) and gone to disc mode (hold select-play) and the error message remains. The only way it goes away is to reboot the computer, then I get one shot at hooking up an iPod.
I NEVER had nor get this error message when I connect to the Windows PC that I started with. Perhaps the iPod does not like moving from PC to Mac? -
Creative Cloud update fails with "the download appears to be corrupted" when tried through our company's firewall, but succeeds if the computer is taken outside the firewall. The IT guys have opened up the ports and URL's specified in the Adobe documentation. I have also captured the network traffic of both the failed and successful downloads for IT to examine (using Little Snitch), however they can find nothing to account for the problem. Adobe just seems to "give up and die" after about 2-3 minutes. Why is this? How can I or IT fix this?
Can I send the above log files to someone familiar with these issues for examination?Hi Gveo,
Please follow the article: Creative Cloud Help | About Creative Cloud Packager which will help you to get your issue fixed.
Thanks,
Ratandeep Arora -
Ipod that appears to be corrupted?
I have a 30GB Ipod(not new, had for awhile and never had problems.) and When i plug it in to my computer(windows XP) and open itunes (latest version) it say this:
Itunes has detected an Ipod that appears to be corrupted. You may need restore this Ipod before using it with Itunes. You may also try disconnecting and reconnecting the Ipod.
Now I have done what is has told me to do over and over again but this still comes up!
please help.
fifth Genration iPod Windows XPI have been doign a little bit of digging and i solve it ! FOR WINDOWS
Ipod must be plugged in
go my computer icon and right click it and click on mange.
click on Disk mangement.
find you disk that you Ipod is on (the size is a little bit smaller then what you ipod hold ex. 30GB would be 27.8 GB)
right click the disk
click on change drive letter and paths
change the letter to aletter that is not been used for any of other disk!
that should work!
yay! i helped myself ! -
ITunes has detecetd a iPod that appears to be corrupted message - DESPERATE
We have several iPods in th family. 2 iPod Classics, 1 4GB nano. All woking fine until recently. Now when each one is connected we get the same message:
+"iTunes has detecetd a iPod that appears to be corrupted. You may need to restore it...."+
I have restored all three iPods and updated their software many tens of times in different sequences.
I have followed all the help forum suggestions and more. Have reinstalled iTunes many times. (before and after registry clean ups.) Have even removed regitry settings for USB upper and lower limits. Have re-installed all USB drivers on teh wintel machine. Have deleted the iPod updater files to force an update to latest iPod s/w version through itunes. Have cleaned registry with some tools I have. Have tried other USB ports. I know the iPods are OK because we have tested them on our MacBook Pro.
It doesn't matter what I do on this windows XP box - The same message always ends up reappearing.
I can't find anything on teh support or forum sites that gives any clue to this.
*Is there anyone out there who has experienced this?*
*I've run out of ideas*Needed a new iPod
-
ITunes had detected an iPod that appears to be corrupted
My brand new 80GB iPod just arrived, I plugged it in with USBbut when iTunes opens, I get the following error:
"iTunes had detected an iPod that appears to be corrupted. You may need to restore this iPod before it can be used with iTunes. You may also try disconnecting and reconnecting the iPod."
I tried to restore but i get a new error every time:
"There was a problem downloading the iPod software for the iPod "iPod". The requested resource was not found."
My firewall isn't blocking iTunes so that isn't the problem, I also tried to reboot and reconnected the iPod multiple times. Also Windows doesn't seem to recognize the iPod as no new drive appear under My Computer. I already erased my Temp-folder but that didn't help either.
Help!Have you tried:
Going to C:\documents and setting\<username>\application data\apple computer\iTunes\
and deleting the "Ipod software updates" folder then connecting the iPod to iTunes. I should ask you do download a software update from the apple servers. Furthermore, if if the iPod still isn't showing up I'd change the drive letter on the iPod.
You can do that by going to the my computer icon, right clicking it and selecting manage. From there select disk management. You should see the iPod in there. What you should do from there is right click the iPod and select "Change drive letter and paths." Change the drive letter to Q. I find that Q is out of the way and is rarely used by the OS for assigning a letter to a network device.
I'd like to see how that goes. -
I am getting an 'iTunes has detected an iPod that appears to be corrupted" message from my 80GB iPod Classic. It plays music fine and has 2.5 GB of space left. I get the message on multiple PC's and USB ports. I have tried resetting it and using Disk Mode. Any advice?
In my Computer folder
Right Click the iPod
Select properties->tools->error check
tick both fix filesystem error and surface scan.
Press OK
May take about 2 hours to complete.
PS: dont be in a hurry to disconnect your iPod, as future recurrence will come, as the HD is almost full, do back up your iTunes library, before your iPod HD gives the dreaded fatal Red X sign.
Good Luck! -
"Itunes has detected an iPod that appears to be corrupted" - Ipod Classic
I recently noticed little tiny jumps or skips appearing in songs on my 80GB ipod classic, so decided to restore it. Having done this I got the following message:
"Itunes has detected an iPod that appears to be corrupted. You may need to restore this iPod before it can be used with iTunes. You may also try disconnecting and reconnecting the iPod."
Reconnecting it just brings up the same message. I have Itunes 9.0 and have noticed others here describing problems between the latest versions of Itunes and their iPods.
Is anyone else experiencing similar problems to mine, or do I just have a faulty iPod? Sadly it's out of warranty, but it is just over 2 years old so I'll be pretty disgusted if it's already broken, as I've looked after it very well.
Any advice much appreciated - thank you!Ok, I updated Itunes to 9.03, and so far it seems to have rectified the problem i.e. I'm no longer getting ipod corrupted message, and I can transfer all my songs onto it as normal. Whether it will solve the little ticks I'm hearing in songs throughout my library on the iPod, I've yet to see.
Sorry and good luck to those having similar problem that cannot find such an easy solution. -
Error-Itunes has detected an ipod that appears to be corrupted
When I connect the ipod to the computer it says "Itunes has detected an ipod that appears to be corrupted. You may need to restore the ipod before it can be used with itunes. You may also try disconnecting and reconnecting again." I disconnected and reconnected many times, I have restarted, check for updates, and finally restored my ipod. It has deleted everything off of my ipod then I get a do not disconnect message that never goes away. What should I do please advise?
Bummer! Have you tried resetting the ipod while it's plugged into the PC?
The thing with the hold switch and the buttons on the ipod.
You mentioned restarting, but I'm not sure what you restarted - itunes, I guess? -
BRAND NEW iPod not "recognized" by itunes and "appears to be corrupted"????
I recently purchased an 80gb ipod classic and when I came home to connect it to my computer, itunes opened and the following message appeared:
iTunes has detected an iPod that appears to be corrupted. You may need to restore this ipod before it can be used with iTunes. You may also try disconnecting and reconnecting the iPod
I just got this, and had never even turned it on, so how can it already be corrupted? I tried disconnecting and then reconnecting the ipod, to no avail. I then restored the ipod, again still message. I even quit iTunes and then reopened it, and still it says the same thing.
Here is a screenshot of what I'm seeing:
http://img81.imageshack.us/img81/9031/picture1ul6.png
Any idea on what's going on? This is really annoying/frustrating considering it's brand new.
ughh
Message was edited by: Robert Young10Thanks, I ended up getting the newest version of iTunes (I had 7, just not 7.7 or whatever that little insignificant update was) and then tried again. This time, itunes itserlf wouldn't even open because that version of itunes only worked with Mac OS X 10.4.10, and I had 10.4.4
I did a software update for my OS, which I HATE doing because of all the glitches and possible problems associated with updates but restarted the computer.
After doing Opaldad's helpful tip, I connected the ipod and restored it. After that, its working perfectly.
Thanks for the help
and to anyone who has this in the future, make sure you have the current version of itunes and your OS
Now, just have to wait for my 14 gb of music to upload -
This XML file does not appear to have any style information associated with
Hi All,
I have IDOC to XML file scenario.
In SXMB_MONI, it showed the message processed successfully (checkered flag).
I open the payload in the target, I'm able to see the XML format without error.
then I checked in RWB the overall status is successful.
But when I checked the detail (message content) I got the following message:
"This XML file does not appear to have any style information associated with it".
So physical file created is like corrupted.
If using XML marker to open the file it show warning "Invalid Unicode Sequence".
The thing is when rerun the whole interface again, which is mean the same idoc send from the source, the file created successfully. Sometimes need to rerun twice or more than that to get the file.
Anyone has idea on what is wrong here?
Thanks,
Victor.Hi Baskar,
Thanks for your reply.
It's PI 7.0.
Overall status is successful but when I go to RWB to check the message content i got the error message above.
Target system is only normal FTPS server.
XML file is created as well but it's showing error when we open it.
The weird thing is without fixing anything if we rerun the same interface with same set of data sometimes the error is gone by itself.
Thanks,
Victor.
Maybe you are looking for
-
Is there really a Cisco VPN client for Linux? _Really?_
Hello folks, I've finally after almost experiencing a brain aneurysm by trying to think too hard got my Cisco 881-SEC-K9 router properly configured for a multipoint IPSec VPN tunnel to my Amazon Virtual Private Cloud, so that hurdl
-
I am using BI NW04s and using RRMX via the SAP GUI 7.0. My problem is that BEx will not start. SP13 is meant to fix the problem and there is a note (1018928) that details how to fix it for other SPs....however this does not seem to work. Any ideas? T
-
BO on top of SAP BI 7.0 - MDDataSetBW.GetCellData
Hi, We have created a Universe (BO 3.0) on top of a BI 7.0 Query. We got the below error when we tried to execute the query from Web I: A database error occured. The database error text is: Error in MDDataSetBW.GetCellData. See RFC trace file or SAP
-
Colors not displaying in WEB GUI
Hi, In WEB GUI, I am unable to see the colors in my ALV Grid when the fields are in editable mode where as in SAP GUI am able to. There is no problem when the fields are in non-editable mode. Can you help me out to view the colors in my ALV Grid for
-
I believe XSLT support in 10.6.7 is still 1.0, correct?
Even though the 2.0 got the recommended status a while ago, have Safari and frameworks caught up?