Pup214R v1.01 uploaded

News, happenings
Message
Author
User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#91 Post by Pizzasgood »

2.14, 2.14R, and 2.16 all use the 2.6.18.1 kernel. So I think the 2.16 source should work.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

VCSkier
Posts: 12
Joined: Fri 04 Apr 2008, 18:36

#92 Post by VCSkier »

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.

User avatar
richard.a
Posts: 513
Joined: Tue 15 Aug 2006, 08:00
Location: Adelaide, South Australia

#93 Post by richard.a »

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 :)

Richard in Adelaide
[i]Have you noticed editing is always needed for the inevitable typos that weren't there when you hit the "post" button?[/i]

[img]http://micro-hard.dreamhosters.com/416434.png[/img]

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

#94 Post by Dougal »

VCSkier wrote:Also, if I understand correctly, pfix=noram should help speed things up. Will it work with 2.14R? Thanks.
When you boot 2.14R you have the info about the boot options. The right parameter is pfix=noramsfs, but it is irrelevant in your friend's case, as the sfs isn't loaded anyway with 64MB of ram.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

jonyo

#95 Post by jonyo »

richard.a wrote:Twinhead with 64Mb of slow RAM (probably EDO) and a 266MHz processor and a small swap file on a 2Gb HDD.
Luuv to read your stuff & what you're working on. I've also felt that original icons tend to be HUGE, take up alot of space & I still haven't sorted out a quick easy way to resize. :? :cry:

Btw, what size swap file?

User avatar
ttuuxxx
Posts: 11171
Joined: Sat 05 May 2007, 10:00
Location: Ontario Canada,Sydney Australia
Contact:

#96 Post by ttuuxxx »

jonyo wrote:
richard.a wrote:Twinhead with 64Mb of slow RAM (probably EDO) and a 266MHz processor and a small swap file on a 2Gb HDD.
Luuv to read your stuff & what you're working on. I've also felt that original icons tend to be HUGE, take up alot of space & I still haven't sorted out a quick easy way to resize. :? :cry:

Btw, what size swap file?
tell you what, since your fellow Canuck like myself I'll give ya a hand. :)
I don't have 2.14r installed but if you tar up the icons and send them to me, I'll resize them and optimize them, But I need to know what size your looking for, like (16x16, 24x24, 48x48) <-- puppy defaults
and the size you want??
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

which devx_xxx and kernel_source sfs to use with 2.14R

#97 Post by mcewanw »

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.

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

Re: which devx_xxx and kernel_source sfs to use with 2.14R

#98 Post by Dougal »

mcewanw wrote: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?
Yes, assuming that the kernel sources are for 2.6.18.1 (you will also have yo rename the sfs to 214...).
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

214R doesn't detect my modem

#99 Post by mcewanw »

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
Posts: 6724
Joined: Fri 20 Jan 2006, 10:44
Location: hobart

#100 Post by muggins »

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
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

#101 Post by mcewanw »

muggins wrote: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.
Actually, modem-wizard appears by default in 214R, so I had already tried what you suggest, but alas, no go...

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#102 Post by capoverde »

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? :shock: Thanks in advance.

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

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#103 Post by Pizzasgood »

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.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#104 Post by capoverde »

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. :x

User avatar
Pizzasgood
Posts: 6183
Joined: Wed 04 May 2005, 20:28
Location: Knoxville, TN, USA

#105 Post by Pizzasgood »

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:

Code: Select all

#!/bin/sh
DIR="$(getdir "$1")"
exec qiv "$1" "$DIR/*"
Name it something like "qiv_all", set it executable, and place it in /usr/local/bin. Then change the run-action on images to use qiv_all rather than qiv, and I believe it should work. You may have to full-screen it, not sure. If you do, you could modify the script to be like this:

Code: Select all

#!/bin/sh
DIR="$(getdir "$1")"
exec qiv -f "$1" "$DIR/*"
You can hardcode any other options you like in the same manner.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]

User avatar
Dougal
Posts: 2502
Joined: Wed 19 Oct 2005, 13:06
Location: Hell more grotesque than any medieval woodcut

#106 Post by Dougal »

The best way to view all the images in the directory is probably to try the right F-button (F1 or F2) for GqView (while you're viewing the image with qiv).
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#107 Post by capoverde »

Pizzasgood's way works OK -- finally! Thank you (some day maybe I'll grasp the difference between this and a standard mouse selection of many image files).

Oddly, Dougal's way doesn't work (thanks all the same) -- the commands menu appears with F1, but GQview doesn't start with any other F-key and if one dares hit one of the number keys, as qiv's menu seems to suggest, two black tabs clog the picture and freeze the viewer! Found no other way out than <Ctrl+Alt+Bcksp> and restart X.

Following the same menu's hints, GQView starts from the commandline with

# qiv-command 1 <filename>

or from the main menu of course; but it behaves unpleasantly (e.g., when switching to a new picture it loses the previous settings) which makes me prefer plain-vanilla qiv.

It's fine to have a pic viewer instead of MTPaint started when clicking an image file; it would be ideal if it could go on to view all other pics in the same folder without too much fuss...

User avatar
T_Hobbit
Posts: 400
Joined: Sat 27 May 2006, 10:50
Location: Portugal - Lisbon

#108 Post by T_Hobbit »

Is this Puppy still actual for old specs? Any update to come?

Or better be for another Pup?
T_Hobbit
:idea: Rebuilding old DOS Machine for Wing Commander Privateer and Puppy :!: Old spare parts to give away - anyone interested :?:

User avatar
J-Bob
Posts: 282
Joined: Sun 10 Feb 2008, 00:58
Location: Canada
Contact:

#109 Post by J-Bob »

T_Hobbit wrote:Is this Puppy still actual for old specs? Any update to come?

Or better be for another Pup?
It was supposed to be the base for the Puppy Phoenix CE version, but it got abandoned, but i don't know what it's version number would have been.

Puppy 2.20 (But that was Puppy 3.00, so that would not really work)
Puppy 2.14.1 (Might be a good name)
PuppyPhoenix (Could have possibly worked)

it was one of the three puppies for the current ce project.
It included Phoenix, Lassie, and Dingo.
Phoenix and Lassie were basically abandoned
Lassie is currently being revived under the Puppy Linux 3.02CE project which I'm leading with help from Tronkel and Evil20071.

I might work with Ecomoney and tronkel after i finish 3.02CE to possibly revive Phoenix.

Then I'll put those skills into a possible revival of the Puppy 1.xx series.
But that might not be as easily done as it sounds, and it sounds quite tough to begin with.

So basically the one that is fully living still is Dingo, and WhoDo is coordinating that.

And Lassie is revived, but was dead for a few months.

But phoenix might get a later revival, Possibly by me an Ecomoney, or other people in the community.

disciple
Posts: 6984
Joined: Sun 21 May 2006, 01:46
Location: Auckland, New Zealand

#110 Post by disciple »

Then I'll put those skills into a possible revival of the Puppy 1.xx series.
You need to be absolutely certain you really want to and can do that before you do it. I only migrated from 1.x as my everyday system a couple of months ago, but I can tell you it will be an awful lot of work to get a 1.x up to date with a lot of programs like abiword and a decent CD burning app etc. And there are so many major differences between 1.x and later versions that to maintain it you would essentially be maintaining a separate distro.
Personally I think we need as many people as possible to focus on the core puppy :(
Do you know a good gtkdialog program? Please post a link here

Classic Puppy quotes

ROOT FOREVER
GTK2 FOREVER

Post Reply