4.3 frozen

Consider 4.3 to now be "frozen". I'm going to do a build then test as thoroughly as possible for a day or two.

There are a few things that I would have liked to put in, but will consider them for 4.3.1. For example:

USB floppy formating (8-bit)
Woo-FF video file converter (trio)

Posted on 16 Sep 2009, 9:55


Posted on 16 Sep 2009, 13:13 by 8-bit
4.3 frozen
I wanted to say that the Pet package I made includes ufiformat and I did not create that or give the author of it credit in my Pet package.
But I do appreciate the thought of including it in a future version.
But I think it would be better off as an addition in the Puppy Package manager. That way, if it is not needed, it does not increase the size of Puppy.
Nuff Said.

Posted on 16 Sep 2009, 13:38 by cthisbear
Keep your wallpaper
I see that you might use oldmickos' wallpaper.
Slightly modified from yours.

When I first booted 4.3.5...
I thought that you might have been sniffing
that towering Cactus plant??? in Penjori.

But I have since tried it a few times,
and I now think that it's different, but
not obnoxious.

Puppy should make you smile and when I see
that wallpaper I have a quiet laugh.
I think of that bike in the desert,
was that 4.1 beta???

From a previous post....
" I would still like Superpup and
the brushed metal of previous release
in the wallpapers. "

" Kick out squiggles and the seagull and
the orange one. "

This would give it more variety.

Puppy 4.3.5, by and large seems pretty good.

And you are probably a bit weary of Puppy again because you are not relaxing at the wheel,
driving to Perth and back.
Getting the gremlins out of the car and you.

Thanks again...........Chris.

Posted on 16 Sep 2009, 20:22 by Mistfire
Released candidates puppy linux
Due to the tentative date of puppy 4.3 release. I suggest to deploy at least 2-3 puppy release candidates to the puppy tester volunteers. If the puppy testers voted best puppy RC in terms of stability, realiability, and performance. Then the chosen RC will become the official puppy release.

Posted on 16 Sep 2009, 23:47 by 8-bit
v43 scsi lockup
Upon further thought on the lockup when trying to boot 4.3 scsi, I came to the conclusion that the problem I was experiencing may be due to the driver for my TekRam SCSI card. It is the dc395x.ko driver.
Since I tried to install it in the regular v4.3 and the PC immediately locked up, I got to thinking that that is why the scsi version is locking up at 'Loading Kernel Drivers needed to access drives'.
The scsi version is loading the same scsi driver at that point and locking up.
Make sense?

Posted on 16 Sep 2009, 24:13 by kirk

I forgot to mention this, might want this for 4.3.1.


It's a little GUI for ntfsclone. It's just a GUI, Puppy already includes all the tools (ntfsclone, split, gzip). It for backing up NTFS partitions. Ntfsclone has worked very well for me, very quick, I've used it to backup and restore Windows 2000 and Vista several times.

Posted on 16 Sep 2009, 24:59 by panzerpuppy
The most important fix / update for 4.3.1
Upgrading to ALSA 1.0.21a will solve many sound-related problems.

A lot of users will be happy ;)

Posted on 17 Sep 2009, 5:18 by RetroTechGuy
Hi Barry,

I just downloaded 4.25, and I'm hoping that some of the operations have a progress indicator (I will try it soon).

I generally like to use the install disk as a live boot, and load the personal workspace from a flash drive.

Under 4.21 (and a couple other versions), when you create these save files, it is often VERY SLOW (especially some of the older machines I play with - in one case, I let it run for around 1/2 hour, before rebooting, thinking it had hung).

This lack of response has the appearance of having crashed or locked the machine. A progress indicator would let the user know that it hasn't crashed or otherwise locked up (i.e. "hang on dude! I'm working as fast as I can..." ;)

My current workaround, is that I created small starter workspace image, and build up from there (did I mention that I set users up with Puppy, when I give them old but otherwise functional computers?...)

Posted on 17 Sep 2009, 23:29 by RetroTechGuy
V4.25 (= 4.3 Beta3)
OK, I launched the latest Puppy on my test bed (AMD K6-500, 256 MB ram), and it works pretty well. Earlier versions would hang for a very long time at the second boot (the merging layers, or whatever the exact message was). Puppy 4.25 sat for about 40 seconds at this stage (instead of minutes, or tens of minutes).

Curiously, 4.25 booted right up and ignored my several older pup_save files -- I expected it to invite me to load one of them, at which time I could convert it to the latest (I have a bunch of these from various versions, since it's my "test bed"... ;)

Does 4.25 scan and know that these are from 4.10, 4.11, 4.12, 4.20, 4.21, 4.76 and then deliberately ignore them? Are they incompatible?

Posted on 18 Sep 2009, 2:15 by BarryK
old pupsaves
The old pupsaves are ignored. You have to rename whichever one you are interested in upgrading, or better yet make a copy of it.

Required name is 'pupsave*.2fs'

...this is explained in the release notes.


...or it will be in a couple of hours from now when I get around to updating that file.

Posted on 18 Sep 2009, 5:33 by RetroTechGuy
Re: old pupsaves
Barry writes: "Required name is 'pupsave*.2fs'"

Ah, that explains it. Sorry, I didn't see that change...

I had expected it to look at all my old files, and let me pick (or not, as the case may be)...

Some of the people that I direct to Puppy want multiple users, and so the pupsave selection widget makes that easy to implement. Nice system!