223258 - Cannot install Address Book Palm Sync -- Error loading Conduit Manager

Status: RESOLVED DUPLICATE of bug 182573

(MailNews Core Graveyard :: Palm Sync, defect)

Description

[M Mapes]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007

After [Address Book Palm Sync Install], I get the usual "Do you want to
continue". I choose Yes. Then I get 

--------------------------------------
Mozilla Address Book Palm Sync Install
--------------------------------------
Error in loading the Conduit Manager while installing the Mozilla Address Book
Palm Sync Conduit

OK
--------------------------------------

I tried adding the following registry entry, as recommended on
http://mozilla.org/releases/mozilla1.5/installation-extras.html#extras_palm

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\palm.exe]
"Path"="C:\\Program Files\\Handspring"

But this didnt' help. Is it that I'm using a Handspring? Is it Windows 2000? Is
it that I have a non-default file location? What's up?

Thanks.


Reproducible: Always

Steps to Reproduce:
1. Start > Programs > Mozilla > Palm Tools > Address Book Palm Sync Install
2. (to "Do you want to continue") click YES
3. Error occurs

Actual Results:  
Dialog box appears with error message "Error in loading the Conduit Manager
while installing the Mozilla Address Book Palm Sync Conduit"

Expected Results:  
Installed the palm sync feature

I'm using Win 2K. Using a Handspring. Palm Desktop software v4.01. Tried with
hot sync manager open, and with it closed, and got same results.

Comment 1

[JLB]

I think this is a duplicate. Bug 182573 comment #7 gives a workaround that I
have tested on W2K and WXP.

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to comment #1)
> I think this is a duplicate. Bug 182573 comment #7 gives a workaround that I
> have tested on W2K and WXP.

JBL's report is the charm - the above worked per reporter 

duping to bug 182573 


*** This bug has been marked as a duplicate of 182573 ***