Nice Pup. Installed nicely onto my EEEPC 1000HG. On the way out it created a savefile ( as you'd expect). On reboot I installed Chromium from PPM. Ran into the usual "running Chrome as root" issue. On exit it prompted me ( again) to create a savefile??. Definitely something not right.

Looks like the savefile isn't being found at boot. How exactly did you install? Where is the save file in relation to the other files? (vmlinuz, initrd.gz, puppy_slacko_5.5.01.sfs)_________________Woof Mailing List | keep the faith |

I installed using the Puppy Universal installer. The savefile resides on a different partition.

Guess that may answer my question- partition isn't mounted until after Puppy boots and therefore the savefile isn't going to be visible. I'll try making a savefile within the Puppy partition and see if it makes any difference.

On Intel NM10 laptop with 1024x600 screen, direct rendering works at 175 fps (glxgears). However, xorgwizard has to be commanded at first boot to get into X (same with PHATslacko).

Did not see VLC, so installed it via PPM/puppy-slacko14 together with ffmpeg. When playing video full-screen, load gets to as high as 85% CPU utilization (only 75% in PHATlacko).

Had to reboot 2x to use adrv (is this correct?).

Thanks, Micko.

Hi raffy,

First, adrive should load on first boot. It must be in the same location as the other puppy files (see example I offered lemmy999 above). Also, xorgwizard is probably to be expected for these machines. I tried to get them going to desktop but I think something is missing. I do not have access to one for tests. All feedback has been from JustGreg, and great his help was too.

Second, I have no idea why cpu usage for VLC is higher in Thin than PHAT, but I do know why it is high for your machine. It's to do with the lack of an accelerated video driver for your machine (see tempestuous' explanantion, mention of lousy MPlayer performance). Also, the cpu is a bit of an underperformer for a newish device.

Not sure scsijon, looked around JWM, nothing in there to change what I mean.
When the mouse moves over a close (X) box, a tiny transparent thing appears which is a pita 'cos it's a bit too small and easy to miss, plus the minimise and maximise glyphs,bitmaps or whatever they are, are a bit too small as well. The mouse arrow is fine.

Not sure scsijon, looked around JWM, nothing in there to change what I mean.
When the mouse moves over a close (X) box, a tiny transparent thing appears which is a pita 'cos it's a bit too small and easy to miss, plus the minimise and maximise glyphs,bitmaps or whatever they are, are a bit too small as well. The mouse arrow is fine.

Sorry, it's 'discussed' in the jwm thread that he has changed the way the mouse 'symbols' now work. Basically, they are now controlled by a component of linux, not a overlay symbol as was with earlier done. It speeds things up and makes code easier to work with, therefore enabling other improvements that have been added. There is no intention to revert.

@Smithy - yeah, the default cursor set in most pups looks a bit odd with the new jwm hover feature for titlebar buttons. If you compile jwm, you can redo the mapping (some like all titlebar buttons to show left_ptr on hover) in the src/cursor.c if I recall that bit.

The other option is to use a different cursor set - Neutral Plus Inverted is one that renders the jwm hovers well and a bit more intuitive in my opinion. NPI is part of lightcursorpack-1.0.pet, which likely will work in ThinSlacko (I made a custom cursor set using mostly NPI with some bits of aerodrop and it works fine in slacko55).

They turn your ThinSlacko-5.5.01-SCSI-XZ.iso into ThinSlacko-5.5.03-XZ.iso, sorry, no GZ just yet. Kernel sources later too (tomorrow), as it's k3.9. We'll see if they fixed the nvidia and other driver bugs eh?

# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
303 frames in 5.0 seconds = 60.405 FPS
300 frames in 5.0 seconds = 59.999 FPS
301 frames in 5.0 seconds = 60.001 FPS
#
I installed Seamonkey 2.17.1 from ppm after updating the slackware
patches repo, couple of other apps too.
It's working well, no problems at all so far.

There is no need to update the patches repo because it is done automatically every 2 days with Updates Manager. Actually, to be more correct, it only updates when you open Updates Manager and it finds that the file is more than 2 days old. It's very quick too, only takes 2 seconds for me.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum