Does it work with 10.3.3? - kyle_skrinak
Anecdotal experience: works fine for my 10.3.3. I'm using version 3.1 of "HotSync Manager" "Conduit Manager" and "Transport Manager" Maybe a conduit conflict? Maybe a bad prefs file?Tuesday, May 11 2004 @ 08:28 AM PDT
Does it work with 10.3.3? - kyle_skrinak
I just upgraded my Palm software to v.4.2.1 (the three managers are at 3.2) and MAL Conduit continues to work just fine (10.3.3)Tuesday, May 11 2004 @ 10:38 AM PDT
Does it work with 10.3.3? - LFransson
I have just synced with it twice (using 10.3.3) and it works fine.Sunday, May 16 2004 @ 10:53 PM PDT
Does it work with 10.3.3? - Edwin-schemer
Works as well as the Linux and Windoze versions on my antique PalmPilotVx, synched via IRDA to my G4 Titanium -- in 10.3.3, of course, and Palm 4.2.1. Sure beats the old terminal based malsync with which I struggled under 10.2.Sunday, May 16 2004 @ 11:28 PM PDT
Does it work with 10.3.3? - Edwin-schemer
Works as well as the Linux and Windoze versions on my antique PalmPilotVx, synched via IRDA to my G4 Titanium -- in 10.3.3, of course, and Palm 4.2.1. Sure beats the old terminal based malsync with which I struggled under 10.2.Sunday, May 16 2004 @ 11:29 PM PDT
Does it work with 10.3.3? - kluzz
I also tried many things listed here. Couldn't get iSync, Palm 5.x, and Palm Desk 4.2.1 to all play nice together.Went back to 1.0.2... and it's all good now.
Wednesday, May 26 2004 @ 04:20 PM PDT
Does it work with 10.3.3? - peterwhite--2008
Don't worry about the unexpected quit. Set up the server etc as instructed and then re-HotSync. The whole process should work fine, and then you'll be OK from then on...Friday, May 28 2004 @ 12:18 PM PDT
Does it work with 10.3.3? - Jack Repenning
Looks to me like it does not:<pre>
Date/Time: 2004-05-10 16:48:18 -0700
OS Version: 10.3.3 (Build 7F44)
Report Version: 2
Command: Conduit Manager
Path: /Applications/Palm/Conduit Manager/Contents/MacOSClassic/Conduit Manager
Version: 3.1 (3.1)
PID: 1162
Thread: 3
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000004
Thread 0:
0 libSystem.B.dylib 0x900075c8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007118 mach_msg + 0x38
2 ...ple.CoreServices.CarbonCore 0x90293474 SwitchContexts + 0x60
3 ...ple.CoreServices.CarbonCore 0x90288c9c YieldToThread + 0x104
4 Conduit Manager 0x0046e708 Yield__7LThreadFPC7LThread + 0x48
5 Conduit Manager 0x0047074c ExecuteSelf__16LYieldAttachmentFlPv + 0x3c
6 Conduit Manager 0x00448658 Execute__11LAttachmentFlPv + 0x58
7 Conduit Manager 0x004482ac ExecuteAttachments__11LAttachableFlPv + 0x6c
8 Conduit Manager 0x00445588 ProcessNextEvent__12LApplicationFv + 0x98
9 Conduit Manager 0x0040a094 0x405000 + 0x5094
10 Conduit Manager 0x00445258 Run__12LApplicationFv + 0xc8
11 Conduit Manager 0x00409bac 0x405000 + 0x4bac
</pre>
Reply to This
Monday, May 10 2004 @ 05:08 PM PDT