Hi--Had a laptop crash but everything was reinstalled o.k. Version 414 installed fine and handheld hotsynced to desktop okay. All data went to desktop, however the next time I opened desktop an error message comes up and says "Palm Desktop Application has a problem and needs to close"....and then it closes. I can see for a few second all my data on the screen before it shuts down, but can't access conduits or anything. Tried uninstalling and reinstalling---same result. Used both the disk and the downloaded software. Again, hotsyncing is not a problem, getting the desktop to remain on is. Need some help on this one. Thanks. Steve ps the Modname on the error message is mfc42.dll
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Desktop error
- Thread starter Romel S
- Start date
Had the same thing happen to me when I upgraded from Windows 98 to Windows XP. My computer guru told me that the upgrade was as if we were trying to give my computer a gender change when we upgraded. There was really no way he could fix this without slicking my computer clean and performing a fresh install of Windows XP. After we did this...no problems thereafter.
Carol
Carol
Mackenziee Rose.
New member
To echo what Carol has written, the first thing to try is a system restore in XP. It seems that an XP crash will damage the MFC42.DLL file and no amount of iddling with it fixes it. If you immediately do a system restore when you first see the problem, that can sometimes fix the error. Other times, it seems to take a complete reinstall of XP. MFC42.DLL is a base Windows file used with both Windows and Internet Explorer so this isn't a problem that's limited to the Palm desktop - I've seen the same error when trying to open any program that has any Visual Basic associated with it.
nature walker
New member
Thanks Jim and Carol. Tried to do it the easy way with reconfig, but had to do a complete clean out and reinstall of XP. It now works fine. Thanks again.
bangerang :)
New member
Similar issue in XP Media Center - (Yeah, I know that Palm doesn't support it - does that mean they know they screwed it up or that they're too lazy?)
Hotsync's are clean, but desktop just crashes on startup after displaying the screen. I note that I have no reference to mfc42.dll anywhere - not even in the file that windows offers to send to Microsoft (Microsoft's systems say that I should "Blame Palm" and even offers a link).
I've been assuming that it's a data issue since I've not used palm desktop but sync/installs have always seemed to work just fine.
Don't ask me to reimage/load the machine - it's brand new and unfortunately has Media Center on it.
Is there any decent alternative to "Palm Desktop" that might be sane with Media Center?
Wholly
Followup:
Suspecting data, I deleted my "profile" directory under palm desktop and was able to navigate all over the application. After a hotsync - BAM - failure. So, my assumption right now is that I have a hotsync conduit that is writing data that palm desktop can't swallow.
(This is from a Treo 650 device) I notice that there are what appears to be two conduits for each data type. Maybe I'll muck around with that - unless someone has better ideas...
Hotsync's are clean, but desktop just crashes on startup after displaying the screen. I note that I have no reference to mfc42.dll anywhere - not even in the file that windows offers to send to Microsoft (Microsoft's systems say that I should "Blame Palm" and even offers a link).
I've been assuming that it's a data issue since I've not used palm desktop but sync/installs have always seemed to work just fine.
Don't ask me to reimage/load the machine - it's brand new and unfortunately has Media Center on it.
Is there any decent alternative to "Palm Desktop" that might be sane with Media Center?
Wholly
Followup:
Suspecting data, I deleted my "profile" directory under palm desktop and was able to navigate all over the application. After a hotsync - BAM - failure. So, my assumption right now is that I have a hotsync conduit that is writing data that palm desktop can't swallow.
(This is from a Treo 650 device) I notice that there are what appears to be two conduits for each data type. Maybe I'll muck around with that - unless someone has better ideas...