Puppy Linux Discussion Forum

Pizzasgood · Posted: Mon 14 Apr 2008, 18:12 Post_subject:

2.14, 2.14R, and 2.16 all use the 2.6.18.1 kernel. So I think the 2.16 source should work.

VCSkier · Joined: 04 Apr 2008 Posts: 12

A friend of mine has an old laptop with 64MB or RAM, and I'm trying to get a reasonably quick installation running on it. Puppy 3.01 is working, but it's pretty slow, so I was wondering if 2.14R might be alittle quicker. Has anyone tried it on a system like this? Is it intended to be faster or older systems, or simply offer better legacy compatibility?

Also, if I understand correctly, pfix=noram should help speed things up. Will it work with 2.14R? Thanks.

richard.a · Posted: Mon 05 May 2008, 19:38 Post_subject: Sub_title: Yes! You can :)

Your answer in a nutshell is "yes"

Go look here and you will see screencaps of my running 2.15ce as the only system on a Twinhead with 64Mb of slow RAM (probably EDO) and a 266MHz processor and a small swap file on a 2Gb HDD.

That link again... http://micro-hard.homelinux.net/puppy/about.html - go down the page a bit and you'll see I mention the caps are taken from the laptop. I resized all the desktop icons (all the icons in the directory where they are) to 32 pixels square because they are HUGE at the original resolution. I should put up a download for them some time.

FYI I've done a fair bit of exploring with older computers.

I wouldn't recommend you muck around with turning RAM off etc... let the system manage itself - Linux is very good at doing that Smile

Richard in Adelaide

Dougal · Posted: Thu 08 May 2008, 06:07 Post_subject:

jonyo · Joined: 28 Dec 2006 Posts: 2727

ttuuxxx · Posted: Mon 26 May 2008, 19:54 Post_subject: Sub_title: Yes! You can :)

mcewanw · Joined: 16 Aug 2007 Posts: 1523 Location: New Zealand

Since still using old dialup I have to be careful that any sfs files or isos I download are in fact the compatible ones I imagine them to be.

With that in mind, I am seeking clarification on which devx_xxx and which kernal source sfs should be used with Puppy 2.14R?

I'm presuming devx_214.sfs and maybe (as I've read in above posts) Puppy-kernel-source_216.sfs, both of which I see available at www.puppylinux.ca

Are these the correct two development sfs files for 2.14R?

I've actually still to download 2.14R too, but I'm interested in everything I've read about it so far. Might just work the best on an old laptop I have with 128MByte RAM.

Dougal

mcewanw · Joined: 16 Aug 2007 Posts: 1523 Location: New Zealand

Thanks Dougal
Unfortunately, I've since discovered that 214R doesn't detect the PCMCIA 56K "goldcard" dialup modem in my old Dell CPx laptop. Works fine with 2.17.1 or Dingo (and several other puppies).
When using one of these other puppies the modem is detected as being on /dev/ttyS1
But the modem is not detected anywhere by the connect screens supplied in 214R. Is there some utility available in 214R that could help with that?

muggins · Joined: 20 Jan 2006 Posts: 6663 Location: lisbon

I've had a modem that wasn't detected by pup2.16, but which pup1.08 saw as ttyS0. Solution: run modem-wizard in p2.16 & choose ttyS0 anyway & it works. No gaurantee same will work for you, but worth a try.

mcewanw · Joined: 16 Aug 2007 Posts: 1523 Location: New Zealand

capoverde · Posted: Sat 08 Nov 2008, 12:39 Post_subject:

First of all, hearthy thanks to all those who worked at Puppy 2.14R! Puppy 2.14 has been in almost daily use on one of my boxes since its release, working perfectly: thus, a "revisited" version is very welcome to me.

One problem I haven't found posts about: I can't get Qiv to respond to any of the mouse/Kbd commands listed in the terminal's Help menu, other than exiting with <Esc>, <q> or mouse middle key. At first I thought it might be another odd hitch from Xorg, but the same happens with XVesa; I tried 2.14R v1.01, but still no change.

Any hint? Does that happen only to me? Shocked

Thanks in advance.

HW: AMD Athlon XP 1800 on a Biostar M7VIW MoBo, 256MB RAM.

Pizzasgood · Posted: Sat 08 Nov 2008, 21:22 Post_subject:

I haven't used qiv in a long time. Don't remember about 2.14R, but I know that stuff worked in the "real" 2.14.

The image cycling stuff only works if you pass it multiple images when running the command.

I think there was a full-screen option for the 'f' key that works with just one image.

Oh, yeah! I think I remember something about controls only working in full-screen mode.

capoverde · Posted: Sun 09 Nov 2008, 04:28 Post_subject:

Thanks for the hints! At first I felt real dumb for not having tried with a multiple-image selection (all other viewers I've used opened in sequence all images in the same folder automatically): but no, qiv doesn't go to another pic even that way, full-screen or not.

Contrary to what I said, however, it does respond to other key commands (fullscreen, zoom in/out, commands list etc.) so it's probably my fault anyway. I'll try giving it a list of pics from the console (but shouldn't that be the same as with a mouse selection?).

The funny thing is that pressing the <space> key or left-clicking, the yellow line reporting commands does declare 'next image', and there is a screen refresh -- but to the same pic. Mad

Pizzasgood · Posted: Sun 09 Nov 2008, 19:22 Post_subject:

I think you do have to give it them from the commandline. A tip: you can open the commandline and type qiv followed by a space, and then select all the images in ROX-Filer, and then middle-click on the terminal and it will paste the paths to them all. There is a catch though: it doesn't automatically correct things if there are spaces in the paths, so you can only use this with paths that don't have spaces.

Or you can open a terminal in that directory and run one of these:
qiv *
qiv *.jpg
qiv *.jpg *.png
etc.

You could probably make a script that will grab the path from the parameter and use that to run qiv on the entire directory. Something like this: