You said, that it is enough when the viewer is installed to the card. Well, I tested it with ZLauncher: It creates a RAM stub, which is just enough to trick the system - hence no problem. A user having Launcher X and standard T3 launcher reports this problem once the viewer is installed to the card. (Unfortunately, I did not test these launchers.)
I was referring to the standard launcher behavior. When you launch an add that's in the Card catergory, it will be copied to main memory and launched. At that time, it may register itself. When it ends, the application is removed from memory, but the prefs that got setup by that app aren't removed, and that leads to the bad registration entry.
ZLauncher gets around this with its stubs, but that's not standard behavior. The thing that breaks the system is Exchange Manager trying to get the name of the application and not finding it, and then exiting out with an error without cleaning up properly.
-- Ben Combee, DTS technical lead, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
