Warning for Palm Pre users: WebOS 1.03 update breaks Classic
Doctors beware. If you have the Palm Pre, you are likely using Classic to run your legacy Palm OS medical apps. The recent WebOS 1.03 update somehow breaks the Classic emulator and users in this forum have reported problems launching Classic.
However forums are ever so helpful that someone has found a temporary fix. Bitmage posted:
Ok, here’s the fix I have found. Unfortunately I deleted my Classic install before trying this, but hopefully that’s not necessary.
Connect the Pre to a PC in USB mode.
Backup anything you need from the ClassicApps folder.
Delete the ClassicApps folder.
Disconnect and Classic should now work.
Classic will recreate the ClassicApps folder, but there is a new structure:
PALM
+–Launcher
InstallAnything you want to be visible when in the emulator must be placed in PALM\Launcher.
If you put files in the Install folder, you will get the blue screen at startup. I’m not sure what the correct process for installing apps is now.
Under the Preferences of the Classic app, there are new options for emulator speed and sound. Sound still does not seem to work, and I’d be leery of activating the background alarms option right now.
Classic is made up of two pieces internally, a javascript bit that launches and handles some setup, and a background native part that does the emulation. Palm’s update brought over the background part without updating the javascript front end. I suspect that it got accidentally rolled into the update, but I don’t know.
This should get you running again until a real fix appears.
|
About the author, Alan: Alan Teh is a Malaysian Physician who specialises in Hematology-Oncology & Stem cell Transplantation. He has been using Palm PDAs since 1997 and is absolutely reliant on them. His current PDA is a Palm Pre and is a strong advocate of the webOS platform, Palm's latest operating system. Caught the blogging bug in 2004 and has been addicted ever since… |
Thanks, i had the same issue, this worked just fine to correct the “Blue screen” problem. BTW>.I’m using eWallet with Classic, works fine