How to Keep Classic with webOS 2.0 and above

[Arthur Thornton]

With webOS 2.1.0, everything we did up to page 5 or 6 was made pointless...

Through extensive work over the course of weeks, I came up with a good solution, bases on the tests of others with regards to completely separate projects.

Read post 146 (NEW STEPS) to find out what you must now do to get Classic running on a webOS 2.1.0 device.

[comptuter]

Is there a way for us non programmers to do this?

[ToniCipriani]

I would understand this method restores the ROM if you already have the Classic app in your profile (and assuming the OTA update removes the ROM), but what if you create a new profile, and the App Catalog on Pre 2 doesn't even have Classic? Classic is NOT a Doctor bundled program but obtained from the App Catalog (I know there's a way to do it illegally, though...)

[Planesdragon]

Better question: what size is that file? Is it over 200MB? Is it even close?

'cause if it's not, MotionApps needs to... well, make a 2.0 version of classic that includes the darn thing.

[Arthur Thornton]

This isn't actually Classic.

What this does is pull in the ROM that Palm removed from webOS 2.0

It is a very simple drag-and-drop (and run a command) for the PalmOS ROM that is included on all current devices (before the Pre2, that is).

The ROM is about 9.5MB.

[Arthur Thornton]

Originally Posted by ToniCipriani

I would understand this method restores the ROM if you already have the Classic app in your profile (and assuming the OTA update removes the ROM), but what if you create a new profile, and the App Catalog on Pre 2 doesn't even have Classic? Classic is NOT a Doctor bundled program but obtained from the App Catalog (I know there's a way to do it illegally, though...)

This isn't actually Classic, but rather it is the PalmOS ROM.

[Arthur Thornton]

Originally Posted by comptuter

Is there a way for us non programmers to do this?

Not right now.

[Arthur Thornton]

Originally Posted by Planesdragon

Better question: what size is that file? Is it over 200MB? Is it even close?

'cause if it's not, MotionApps needs to... well, make a 2.0 version of classic that includes the darn thing.

9.5-10MB (I posted that 3 posts up just a couple minutes ago)

I agree that MotionApps needs to release a new version of Classic that includes the PalmOS ROM inside the ipk.

[palmdoc2005]

Originally Posted by ToniCipriani

I would understand this method restores the ROM if you already have the Classic app in your profile (and assuming the OTA update removes the ROM), but what if you create a new profile, and the App Catalog on Pre 2 doesn't even have Classic? Classic is NOT a Doctor bundled program but obtained from the App Catalog (I know there's a way to do it illegally, though...)

It's 'downloadable' even if one doesn't have access to the App Catalog using ipk fetcher 2 since it's a 'free' download.

[ToniCipriani]

Originally Posted by arthurthornton

This isn't actually Classic, but rather it is the PalmOS ROM.

That's what I said, no?

My question was, even if you have the ROM, how would it help the if you can't access the app legally, if you have a new profile and new device. I wouldn't put it past HP to remove it from the catalog.

[Arthur Thornton]

Originally Posted by ToniCipriani

That's what I said, no?

My question was, even if you have the ROM, how would it help the if you can't access the app legally, if you have a new profile and new device. I wouldn't put it past HP to remove it from the catalog.

Sorry, I was referring more towards the second half of your post.

And I also mentioned that in my original post. It is indeed required that you have Classic installed on your device or something along those lines. It also requires that you have purchased Classic through MotionApps and that your device is licensed to use it.

I don't expect HP to keep it in the Catalog for long, unless they removed the ROM to free up the 10MB it used and plan to re-release Classic with the PalmOS ROM inside the ipk.

[johncc]

It's probably about time that we heard from HP Palm about what is going on with Classic. Surely some explanantion is warranted. It's not the sort of high-handed behaviour we normally expect from Palm.

Hardbeatz ? Andora? Crazypants?

[Cringer]

Let it die.

[Arthur Thornton]

Originally Posted by Cringer

Let it die.

I don't use Classic, but some people rely on it for their daily work because the PIM support in webOS is poor compared to PalmOS.

I hope that will change in the near future (maybe they're going to use the new Enyo framework as an opportunity to completely rewrite all of their default apps to make them more business-and-consumer oriented).

[johncc]

Originally Posted by Cringer

Let it die.

^

I don't use it either, but if it's as easy as arthurthornton's method suggests, then there's no excuse to not keep it going.

[JKM]

No, please don't let it die !

So, has anyone successfully tried this with a Pre 2 ?

One thing that is missing in the original post:
You have to let MotionApps transfer the license to the new device (tell them the new serial-number).

A question regarding copying the files:
How do I make sure that the owner and group attributes of the files are correct?

[palmdoc2005]

Originally Posted by johncc

^

I don't use it either, but if it's as easy as arthurthornton's method suggests, then there's no excuse to not keep it going.

I agree.

[Arthur Thornton]

Originally Posted by JKM

No, please don't let it die !

So, has anyone successfully tried this with a Pre 2 ?

One thing that is missing in the original post:
You have to let MotionApps transfer the license to the new device (tell them the new serial-number).

A question regarding copying the files:
How do I make sure that the owner and group attributes of the files are correct?

Yes, you will need to contact MotionApps to have them register the new serial number.

And regarding the file permissions, I actually hadn't thought about that.

Let me look into that in a bit and get back to you on what the permissions need to be, though I think that they it should be automatically executable since it is in the USB partition, but I'm not 100% certain of that.

[JKM]

Ok, I just used novacom to have a look at the files on my PrePlus:

localhost:~ jkm$ novacom -t open tty://
root@palm-webos-device:/# cd usr/lib/palmos/
root@palm-webos-device:/usr/lib/palmos# ls -la
drwxr-xr-x    4 root     root         4096 Mar 13  2010 .
drwxr-xr-x   23 root     root        20480 Jun 14 20:17 ..
-rwxr-xr-x    1 root     root          512 Mar 13  2010 .copyclassicapps.sh
-rwxr-xr-x    1 root     root           50 Mar 13  2010 .preferences-default
-rwxr-xr-x    1 root     root         1899 Mar 13  2010 .prepare.sh
-rwxr-xr-x    1 root     root          445 Mar 13  2010 .uprepare.sh
-rwxr-xr-x    1 root     root          440 Mar 13  2010 Read Me.txt
-rwxr-xr-x    1 root     root       409600 Mar 13  2010 classic.rgba
drwxr-xr-x    2 root     root         4096 Mar 13  2010 entlic
-rwxr-xr-x    1 root     root       409600 Mar 13  2010 expired.rgba
drwxr-xr-x    2 root     root         4096 Mar 13  2010 rom0
root@palm-webos-device:/usr/lib/palmos# cd rom0/
root@palm-webos-device:/usr/lib/palmos/rom0# ls -la
drwxr-xr-x    2 root     root         4096 Mar 13  2010 .
drwxr-xr-x    4 root     root         4096 Mar 13  2010 ..
-rwxr-xr-x    1 root     root      9830400 Mar 13  2010 ROM.bin

So owner and group are root. I also noticed that there are more files than just the ROM.bin.
I wonder, what those other files are?

[Arthur Thornton]

Originally Posted by JKM

Ok, I just used novacom to have a look at the files on my PrePlus:

localhost:~ jkm$ novacom -t open tty://
root@palm-webos-device:/# cd usr/lib/palmos/
root@palm-webos-device:/usr/lib/palmos# ls -la
drwxr-xr-x    4 root     root         4096 Mar 13  2010 .
drwxr-xr-x   23 root     root        20480 Jun 14 20:17 ..
-rwxr-xr-x    1 root     root          512 Mar 13  2010 .copyclassicapps.sh
-rwxr-xr-x    1 root     root           50 Mar 13  2010 .preferences-default
-rwxr-xr-x    1 root     root         1899 Mar 13  2010 .prepare.sh
-rwxr-xr-x    1 root     root          445 Mar 13  2010 .uprepare.sh
-rwxr-xr-x    1 root     root          440 Mar 13  2010 Read Me.txt
-rwxr-xr-x    1 root     root       409600 Mar 13  2010 classic.rgba
drwxr-xr-x    2 root     root         4096 Mar 13  2010 entlic
-rwxr-xr-x    1 root     root       409600 Mar 13  2010 expired.rgba
drwxr-xr-x    2 root     root         4096 Mar 13  2010 rom0
root@palm-webos-device:/usr/lib/palmos# cd rom0/
root@palm-webos-device:/usr/lib/palmos/rom0# ls -la
drwxr-xr-x    2 root     root         4096 Mar 13  2010 .
drwxr-xr-x    4 root     root         4096 Mar 13  2010 ..
-rwxr-xr-x    1 root     root      9830400 Mar 13  2010 ROM.bin

So owner and group are root. I also noticed that there are more files than just the ROM.bin.
I wonder, what those other files are?

Alright, it looks like the permissions are 755.

The other files are included in the webOS 2.0 doctor, so it looks like those aren't problematic---yet.