rc46

Hi Aviator,

What I do is copy my PRC and PDB files into
\Palm Pre\ClassicApps\Palm\Launcher\

Make sure the free utility program FileZ.prc is one of those .PRC files.

Start classic and then start up FileZ. Navigate to the virtual SD card called
"internal" and change directory to \palm\launcher
Select all the files in that directory (put a check mark next to them) except filez then select menu -> move and select 'Palm Card" as the destination

This will move all of your PDB and PRC files into the Palm ROM. This will allow them to run in a much more stable enviroment. Make sure you use a program like "BackupBuddyVFS.prc" to make a backup of your Palm ROM in case you ever have to recover from a full erase for hard reset.

Hope it helps!

__________________
Pilot 1000 -> Pilot 5000 ->Palm Pilot Professional -> HP 620LX -> TRG Pro -> Palm V -> Palm Vx -> Palm M505 -> Palm i705 -> Palm Tungsten|T -> Samsung i500 -> Treo 600->Treo 650 -> Treo 600-> Treo 700p ->Centro ->Treo 800w + Redfly C8n -> Palm Pre (Because Palm is Back!!
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
)

bdhu2001

Because I've changed from one version to the next, I have more than one install folder in classic. If you're installing a file that has other pdb files with it, I go to:ClassicApps, palm, Launcher, install.

If you're installing a program that just has one file with it, go to: ClassicApps, install. With the current update, I don't think you need to use anything except the first one. Make sure you don't have any files even text, in the ClassicApps, install folder.

Aviator

Thnkyou RC46, but to do the above do I need fileZ? Or can I use their rom updater prc?

Krayze

I know classic has it's issues, but til ePocrates, Er suite and the like are available native to the pre or webOS.. then I'll use em any way I can =)

photoframd

MotionApps created their own Blue Screen nightmare. As part of the install of the Classic App and the ROMupdater, they added two readme.txt files. These files are causing the Blue Screens. Just delete them. More info here:

blog.photoframd.com/2009/06/28/solution-to-motionapps-blue-screen-of-death-on-the-palm-pre/

Aviator

Excellent job, the link above.
Got to where Epocrates is autoupdating.
Interestingly, Epocrates "autoupdate" is not classic certified.
What a sorry *** company that Palm picked.

palmdoc2005

Motionapps now say the issue has been fixed with WebOS 1.04 update. Can anyone confirm?
MotionApps: Classic v1.1 release is now complete

__________________

To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

bitmage

With 1.0.4 I can now place files in ClassicApps/Install and Classic will install them, without the old rom updater app, and without a blue screen.

Classic overall is much more stable after 1.0.4.

__________________
Palm IIIx-->Palm Vx-->Kyocera 6035-->Kyocera 7135-->Treo 650-->Treo 700p-->Pre

jfscars48

I had waited and waited for Classic since day on. I wanted to be able to HotSync. The day they announced HotSync(this week) I bought it. I followed instructions on installation but it does NOT work. I filled out a ticket with MotionApps and they came back telling me to follow the instructions. I wrote back telling them I think i did. They wrote back and told me not to email them again. Nice group of people!! If anyone would be willing to walk me through the installation I would be happy to pay them. It's not that I really need this app-I WANT it.