I recently crashed my lifedrive after I installed a demo comy of slovoed Eng to eng Dictionary basically the files refused to hotsync so i tried to sync to the card and the LD went into a reset loop did a complete erase and tried to reinstall from my desktop backup with no luck tried twice both times went into a reset loop even after i deleted all ref to slovoed files from the backup copy and with a new SD card. It just wouldnt budge and became a unstable mess
So had to hard reset delete backup and conduits and unistall and reinstall palm desktop
so there I am a new copy of desktop a clean Ld I do a basic sync and wham
Microsoft Visual c++ Runtime Library
Runtime error
c;\programfiles\palmone\hotsync
Application has required a runtime to terminate in an unusual manner please consult the application support team
So I say great an Install glitch I Unistall, delete all old palm folders and general housekeeping apart I reinstall palm desktop from disk same error
this is where I got real P******* off felt like calling palm one and giving them a piece of my mind
Checked all my runtime DLL libraries they r all fine
so i go online and search to see if any solutions and bingo someone else is having the same prob too but no solution
headhunter69 C++ Runtime Library May 26, 2005
When ever I Open and run Hot Synch, I get a error message
Microsoft Visual c++ Runtime Library
Runtime error
c;\programfiles\palmone\hotsnych
Application has required a runtime to terminatte in an unusaul manor pleas consult the application support team
Reply | Forward | Report Abuse | Print
dmspeer same thing with T5 (?) Jun 1, 2005
receiving the error message also after hotsync...
error 6025, which m$ site says is a programming
error in the hotsync module
"CAUSE
This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.
The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description. "
would palmone make a programming error?????? hahaha