[Solved] Proteus v09 very slow?

[nickh]

Hi,
I have been an intermittent user of Slax-Remix v8 when working on the road. Because of a few issues with it I thought I'd try Proteus v09 as I know some things were fixed when Remix went to v9.

I renamed the boot and slax folders on my USB stick then copied over the boot and porteus folders folders from the iso. The PC (Dell E6400 laptop) boots up but is deathly slow. With KDE, from beginning to initialise the desktop to the desktop completing loading is about 2 minutes. It is less than 5 seconds with Remix v8. Opening a folder, like double-clicking on home, takes minutes. Click Logout -> long wait -> shutdown -> PC off takes minutes.

Do you know if there is anything I can do to make it usable?

FWIW LXDE boots much faster but has the same problems opening folders and with other general operations like application launching.

Nick

[fanthom]

please post output of psinfo on pastebin.com.
is there any process which is eating your CPU? open console and run 'top' application.
are you saving changes? please try 'Always Fresh' mode.

waiting on a report

[nickh]

OK. It might be a couple of days as I am just off travelling.

Posted after 1 day 19 hours 40 minutes 25 seconds:
Here we go:
psinfo.txt at pastebin.com as requested.

top has nothing over 1% all the time.

I've tried Always Fresh and it works fine. The problems appear with the KDE and LXDE modes.

I've tried deleting the changes folder (having booted from another o/s) and restarting but it was the same.

The only thing possibly odd with my set up is the hdd is encrypted and not recognisable in Slax, Remix or Proteus, presumably because it has a non-standard format. I am not trying to use it at all and Slax and Remix both operate correctly.

[fanthom]

@nickh
"I've tried Always Fresh and it works fine."
that's exactly what i thought
now please read known bugs section:
http://forum.porteus.org/viewtopic.php?f=41&t=176

btw: in 1.0 you will be forced to use save.dat on MS filesystem anyway
please add [Solved]

[nickh]

Thanks for the quick answer. I'm afraid that from the known bug report there is no way I could have identified my symptoms to that report.

I have it fixed now but even that was not totally straightforward. Putting changes= lead Porteus to find the old changes directory. I deleted that and put changes=slaxsave.dat and it worked. I am now about to move it to the porteus directory

[Ahau]

Good to hear!

with slaxsave.dat in your porteus directory, you'll just need your APPEND line to read: changes=/porteus/slaxsave.dat