Pup214R v1.00 - Puppy Linux 2.14 Revisited, is now available

[Dougal]

I load Pup214R v1.00 with pfix=debug command.
The following message come:
"Could not find kernel image for pfix=debug"

It occured to me that maybe you tried "pfix=debug" and not "puppy pfix=debug" and maybe it has some effect...

If you get it working, look in the output for the line

Code: Select all

PUPMODE=|13|

I think I found the problem and fixed it, but just to make sure...

[pdrito]

Shame on me. !!!

You are absolutly right: I forget to put puppy on the sentence puppy pfix=debug

So,
with the puppy pfix=debug command I found:

PUPMODE is :12: [yes , 12 and not 13. I checked 3 times]
Coping /pup_214R.sfs to tmpfs ...done
/mnt/dev_save2007-12-10-01-13 No such file or directory
etc etc.
e2fsch 1.40.2 (12-Jul-2007)
ext2fs_check_if_mount No such file or directory
etc. etc.

Hope this info are good to you.
And sorry again for my mistake.

pdrito.

[Dougal]

PUPMODE is :12: [yes , 12 and not 13. I checked 3 times]

Oh, now that I think of it, it would actually be 12... So I think we're ok and it's fixed.

[8-bit]

I have to say KUDOs to you on the desktop drive/dev icons and the mount/unmount that is part of them. Compared to Pmount and MUT, it just flat flys in mounting a drive or partition.
My question here is:
Will there be a pet of this addition that can be made available to users of other versions of puppy that would like to add it?
I have pup214r installed (full hard drive install) on an OLD Compaq notebook 133mhz, 1.2gig hard dirve, no eth0, no wifi, no CD drive.
But It is running in 32 megs physical ram!
Just thought you would like to know!

[gerry]

Do we actually need both:

Menu > setup > setup wizards > etc

and

Menu > setup> wizard wizard > etc

since the end result is essentially the same?

Also, Menu > system > Xpdq printer management

gets you to the Xpdq gui, but Printer > Add printer does not do anything. It only works if you come via a setup wizard. A bit of a downer if you try this approach first!

Gerry

[Dougal]

Do we actually need both:

Menu > setup > setup wizards > etc

and

Menu > setup> wizard wizard > etc

since the end result is essentially the same?

I don't understand what you mean... Do you mean having the wizards sub-menu and the WizardWizard?

[ttuuxxx]

Hi i just tried it and i think its excellent, Great job guys, Only problem so far that i've had is when i did a screenshot using mtpaint, I had like 20+mtpaint windows open automtically, i had ezpup3.0 running at the time and that was it, also when you use ezpup 2.17r4 or 3.0 the menus are broken, you only have 2 items in the start menu. And yes i did the fixmenus thing and got some missing folders, other then that i really do like this puppy sorry about the image quality but i used mtpaint to get that and tried to make it smaller with it and it became pretty crappy ttuuxxx

[gerry]

Hi Dougal... yes.

Gerry

[rerwin]

Dougal,
Thanks for clarifying the significance of the "modes:" and "timing:" statements:

The "timing" lines list the modes supported by the screen and in the case of laptops it usually will be only the one, native, mode.
The part of ddcprobe output related to your adapter is the first part of ddcprobe output (that's why when you get only half the output and "edidfail" it means that it couldn't get to your screen).
What I did is make sure that Xmodes (which is normally created by Xvesa -listmodes) has got the 800x600 and 1024x768 modes, thus the user will be offered them, being told "ok with card, maybe NOT ok with screen".

So my Tecra gets described correctly by your fix. However, without a 800x600 timing line, cherriepuppy's 800x600 Portege with the same adapter will not be given the 800x600 option. To condense his posts re my 1024x768 fix:

works on toshiba portege 7010ct except it says that 1024x768 resolution is available but the screen only goes up to 800x600.

ddcprobe shows following:
# ddcprobe
vbe: VESA 2.0 detected.
oem: MagicGraph 256 AV 44K PRELIMINARY
. . .
edid:
edid: 1 0
id: 5081
eisa: TOS5081
serial: 00000000
manufacture: 20 1995
input: analog signal.
screensize: 23 17
gamma: 1.000000
dpms: RGB, no active off, no suspend, no standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@75 Hz (VESA)
#

The absense of a "timing: 800x..." line would prevent the wizard from offering the actual native resolution of that Portege. I expect that laptops considered for Puppy would support at least 800x600. So, the logic to add this line could be conditioned upon there being no higher-resolution "timing:" line.

My problem with what I call the "fill in the gaps" approach is that it must get it right for all affected adapters and screens, an open-ended maintenance issue. The solution I settled on simply takes the default used in the absense of (sufficient) screen information; that is the case here, although with 1024x768 screens, accepting the "8514A" 1024x768 line supplies the correct option. (With the "default" approach, we would not be discussing details of the FITG fix for 10-year-old laptops, conserving energy for the greater-impact stuff.)

BTW, dalderton's Toshiba TE 2000 produces:

oem: Trident CYBER 8820
. . .
timing: 720*400@70Hz (VGA 640*400, IBM)
timing: 640*480@70Hz (VESA)
timing: 800*600@72Hz (VESA)
timing:1024*768@87Hz Interlaced (8514a)
ctiming: 1280*1024@60
ctiming: 1600*1200@60
dtiming: 1024*768@74

telling me that it supports resolutions lower than native. But, for Puppy, I see no need to supply the lower resolutions if ddcprobe omits them.
Richard

[ttuuxxx]

so basically if its really nice, we can't jazzz it up a bit???

[ttuuxxx]

The icons on the desktop was a setting for rox in options, Strange option and really never would I ever find a use for such a option. So that one wasn't 2.14r fault at all, I also found that if you used ultimate icewm the computer would slow down a lot, and that package was made for the 2 series, so then i had 128icewm package laying around and tried that one, And finally yes it work perfectly, other then renaming the start menu buttons but thats ok. excellent work and yes ezpup wasn't made for the 2 series. The xarchiver sometimes gets errors when extracting so i installed xarchive-0.2.8-6.pet and then it worked flawlessly.
ttuuxxx

[ttuuxxx]

ok i have disabled "hotplug" and it has stopped that desktop icon thing. So its either the package fault or hotplug, But just take into account the package has always worked perfect on 3.0 & 3.01.Haven't tried it on other puppy versions sorry:)

[Dougal]

i had ezpup3.0 running at the time and that was it, also when you use ezpup 2.17r4 or 3.0 the menus are broken,

Any problems caused by ezpup should be directed to the ezpup developers.
Besides that, it is likely that packages intended for later versions of Puppy might not work properly.

[Dougal]

Hi Dougal... yes.

Gerry

Well, Barry has both the WizardWizard and all the wizards in the same menu... I just put the separate wizards into a submenu to make it more neat, but if I decide to remove either of the two, some people will obviously think I should have removed the other one... I never use the WizardWizard, but there are others that probably do.

[Dougal]

when i opened any program, It would give a open tab in the taskbar as usual but here's the thing it would put a desktop icon as long as it was open, once i closed the program the icon would disappear.

Those are iconified windows. You can enable/disable using them in the rox settings.

[Dougal]

Rerwin, I'll look into it.

[wjaguar]

sorry about the image quality but i used mtpaint to get that and tried to make it smaller with it and it became pretty crappy ttuuxxx

You shouldn't have converted the screenshot to GIF - for an image like this, PNG would have been both considerably smaller and of much better quality. Converting an RGB image to indexed is lossy in general, and mtPaint's default dithering mode is the fastest one, not the best quality one.

[willhunt]

just lov'n it

[ttuuxxx]

just lov'n it

That looks excellent!!, how did you change the rox buttons, I looked all over for the forward, up, etc rox buttons. Thanks

[willhunt]

Gnome file browser not rox from the gnome.sfs file here
on the forum all the sfs from the VIZ series seem to work
fine in 2.14R