Closed
Bug 374151
Opened 18 years ago
Closed 17 years ago
Palmsync crashed during Hotsync on Vista
Categories
(MailNews Core Graveyard :: Palm Sync, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: evers, Assigned: Bienvenu)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2 Build Identifier: 1.5.0.10 (20070221) Palmsync appears to install correctly under Windows Vista Home Basic, but when I try to access it, either by changing the settings or Hotsyncing, Hotsync crashes. Hotsync works for syncing to Palm Contact. Reproducible: Always Steps to Reproduce: 1. Install Palmsync 2. Enable Hotsync to Thunderbird Address Book 3. Hotsync Crash or 1. Install Palmsync 2. Attempt Hotsync 3. Hotsync Crash Actual Results: Hotsync Crash Expected Results: Successful Hotsync
Comment 1•18 years ago
|
||
David Bienvenu, what is the documented status TB 1.5 with regard to vista support? Reporter, what PDA and version of HSM?
Assignee: mscott → bienvenu
Component: Address Book → MailNews: Palm Sync
Product: Thunderbird → Core
QA Contact: address-book → vseerror
Summary: Palmsync crashed Hotsync upon access → Palmsync crashed during Hotsync
Version: unspecified → 1.8 Branch
Assignee | ||
Comment 2•18 years ago
|
||
2.0 is the release we support on Vista - 1.5 is not. That doesn't mean it won't work on Vista, but 2.0 is where we did the work to make sure we're correctly registered as the default e-mail client, etc. The same is true for Firefox re 2.0 and Vista support.
Comment 3•17 years ago
|
||
David Evers, Does palmsync work for you if you use Thunderbird v2 and palmsync for TB2 that I emailed you about? Results? As for Palm, follow http://www.palm.com/us/support/windowsvista/ and the instructions for palm desktop at http://tamspalm.tamoggemon.com/2006/06/15/the-state-of-palm-desktop-in-vista-beta-2/ namely "I can open Palm desktop in Vista if βUser Account Controlβ is turned on. If UAC is turned off, Palm hangs at the splash screen. This is very frustrating. I much prefer to work with UAC turned off because I experience far few problems with other applications." Not related to palmsync, ... tHere is also a blog at http://blog.palm.com/palm/2007/05/palm_desktop_on.html and an alternative for palm application install on vista cited at http://www.brighthand.com/default.asp?newsID=13011
Comment 4•17 years ago
|
||
I forgot to cite http://forums.palm.com/palm/board/message?board.id=software&message.id=15450
Comment 5•17 years ago
|
||
Dave, Which palmsync did you use at that time with Thunderbird 1.5? Did you ever get to try Thunderbird version 2 + Palmsync for TB2? xref bug 422494 which is also VISTA, but is an install problem, not a crasher - PalmSync (v. 2.0.0 beta) will not install into new Palm Desktop 6.2 with HotSync Manager 7.0.2
Comment 6•17 years ago
|
||
David Evers, I realize you arent' using TB and palmsync, but one important question - it will really help to know *how* you knew palmsync installed correctly ... did you get the dialog box message that said installation of conduit complete? --------- Reporter, no longer has TB or palm. And perhaps invalid b/c installed using TB 1.5 - but we don't know if the problem would have shown itself by using TB 2.x. So Leaving open for now and setting tickler CLOSEME 2008-08-08 xref: Bug 422494 - PalmSync (v. 2.0.0 beta) will not install into new Palm Desktop 6.2 with HotSync Manager 7.0.2
Summary: Palmsync crashed during Hotsync → Palmsync crashed during Hotsync on Vista
Whiteboard: CLOSEME 2008-08-08
Comment 7•17 years ago
|
||
change of heart - closing incomplete as we don't aren't going to test 1.5, and we don't have reporter's results with 2.0. but setting dependent to bug 434745 in case this gets reopened because we might have avoided this problem if palmsyncinstall error checking/feedback were better.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Depends on: 434745
Resolution: --- → INCOMPLETE
Whiteboard: CLOSEME 2008-08-08
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•