WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: PPI installed applications not opening after reboot.  (Read 2425 times)

Offline nbt384

  • Newbie
  • *
  • Posts: 17
PPI installed applications not opening after reboot.
« on: January 02, 2010, 01:42:08 PM »
Hey all.

I am using an HP Compaq Presario F500 laptop.

I followed all the instructions in installing TC to Hard Drive (setting the boot arguments as per the article in the wiki - without max_loop=255).

When I install PPI compatible applications (eg. Opera, Seamonkey, mupen64) they either just refuse to open after reinstall or don't even work in the first place (I just click them (either on the lower bar or on the click-menu, wait for ages and nothing happens).

This problem doesn't happen when I set up a PPR installation.

Does nobody else have this problem?

Cudos to the team on what is otherwise a great distribution (under PPR).

My regrets if this has already been covered in an earlier post.

Offline ^thehatsrule^

  • Administrator
  • Hero Member
  • *****
  • Posts: 1726
Re: PPI installed applications not opening after reboot.
« Reply #1 on: January 02, 2010, 01:56:25 PM »
What are your boot parameters?

Check out the "core concepts" page on the main site for more info.

Offline nbt384

  • Newbie
  • *
  • Posts: 17
Re: PPI installed applications not opening after reboot.
« Reply #2 on: January 02, 2010, 01:57:42 PM »
local=sda1 tce=sda1 home=sda1 opt=sda1

Offline nbt384

  • Newbie
  • *
  • Posts: 17
Re: PPI installed applications not opening after reboot.
« Reply #3 on: January 02, 2010, 01:58:32 PM »
and also quiet

Offline nbt384

  • Newbie
  • *
  • Posts: 17
Re: PPI installed applications not opening after reboot.
« Reply #4 on: January 02, 2010, 02:03:16 PM »
I can remove the local=sda1 parameter and it works fine, however I really want to have a PPI installation.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: PPI installed applications not opening after reboot.
« Reply #5 on: January 02, 2010, 04:49:38 PM »
Set (touch) the copy2fs.flg in the directory where you have your extensions.
Then the extensions will be copied into your persistent /usr/local instead of being mounted.
10+ Years Contributing to Linux Open Source Projects.