I tried it out and I have a pertinent question not having to do with any bug.
How do I set up things to get rid of a lot of gray in the menus and program windows.
I just am not used to a black entry window in geany for instance.

Adding libmad back makes it easier to install alsa-streamtuner. I believe not everybody knows it has been deleted compared to Puppy 431 official.
Yes it was mentioned at the release announcement. Pmusic just doesnt work as well as for example ttuuuxxx compiled alsa-streamtuner.pet

Not big problem when you know but annoying to hunt libmad before you have it saved to hdd.

on rebooting after frugal install, desktop icons reverted to MIME types. Same issue as with Stardust and 'invisible' icons in top tray when blue theme is activated. Freemem app missing, no way to change font for gtk theme. Network connection is cool._________________Spup Frugal HD and USB
Root forever!

re: alsa-streamtuner - libmad needs to be added as a dependency to the package - fixing the dependencies is a big todo list since many packages are missing them ... also pmusic has had significant improvement since 4.2.X and more integrable into the desktop

re: freemem and space - you will find those in Pwidgets (I think?) and they can be turned on or off (alternative is to edit .jwmrc-tray to have them swallowed)

Switching the theme is available in Zigbert's new PCC, but I haven't played with that part much. Yes the terminal and geany are backwards from the traditional setup. Which style is prefered - "backwards", traditional, 4.2.1 style or Barry style?

re: notecase, I had forgotten that I recompiled notecase with text highlighting support (not really much gained there). I can recompile without gtksourceview since geany already has text highlighting and nicoedit was the only other program to use it AFAIK.

re: woof build. I played with woof again last night and it seems to be difficult to use local pets... is there a way to tell woof to use a local repository (a.k.a. a directory full of pets?) it seems silly to upload them so I can download them -- is hiawatha the best answer?_________________Check out my github repositories. I may eventually get around to updating my blogspot.

If builds start with 433, why is yours 431? Is it temporary? Why not pup-4312.sfs if you needed a reference point?

In short, yes it is temporary... thus "Pre" Alpha. I have recompiled almost all of the core software and many of the core libraries that will be needed to update others and needed to confirm non-breakage and hopefully non-regression.

Jemimah has informed me of a fix for abiword browser issue for builds with gtk-2.14+ ... need to make a firefox symlink to defaultbrowser I had tried setting the BROWSER environment variable as documented and required in 2.6 to no avail.... this is great news, since it takes me a whole day to build in 4.2 and I borked up the spell check last time due to the outdated enchant.

That's the answer I was hoping for.
I'll try to test in a closed environment, thus using fully psubdir.
I think in this way there is no confusion possible about the pup-431.sfs with the one I have already._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

regarding the psubdir parameter - I have been using it as long as I can remember without problems... is there any reason that it should not be included by default for a frugal install?_________________Check out my github repositories. I may eventually get around to updating my blogspot.

I would really like to see a patch to woof to allow DOC>DOC and NLS>NLS (their own sfs) instead of having to send them to null (discarded) unless they are explicity put in the pup or devx sfs via the DOC>EXE or NLS>DEV in the config

The really dark themeing should be an option, but not the default. It is much harder to see if your eyesight is a bit poor or aged, and could cause problems for those who are colour blind. On a technical note, the brighter the screen, the more the pupil stops down and the sharper the perceived image. As an optician, I showed both options to a random sample of patients with less than perfect vision, and all could see the 'normal' 4.3.1 more easily._________________Spup Frugal HD and USB
Root forever!

As for the psubdir usage:
I use the Lin'N'Win method and some 20 puppies are in the ntfs partition in their respective directories.
I don't want to use nts, just for the boot only.
So my pupsave files are on a different fat partition.
If I use constantly psubdir I write to ntfs and the pupsave's are separated, which I don't want.
I didn't have a problem to boot without psubdir=. I just to have take care that if same pup-xxx.sfs files are used, the correct one is available in /mnt/home.

Having said that here my experience so far with this pre alpha.

I boot with pfix=ram for a first time.
I never got the questions about keyboard, timezone, locale, and graphic environment (xorg - xvesa)
Don't know if this intended.
When the desktop came up (after the install phase) I was in 800x600 xvesa. Could change to 1024x768. But still xvesa. Didn't try yet to use xorg via xorgwizard (if this still exists)
Then I found out my keyboard was wrong so I had to use the control panel (a nice one) to set my keyboard to Belgium.
From the menu I couldn't start programs like rox, rxvt, seamonkey and much more.
I can go to rox via the home icon, so I can browse the file system.
From rox I could also open a terminal and start seamonkey.
Network configured ok with pwireless2 so I am able to type this now with 4.4 pre alpha.

So not being able to use the menu system is a real show stopper.

The second one is that at shutdown I never got the panel to say yes I want to save to a save file. (even if I booted with psubdir=) This is a long outstanding issue for quite some people as I have read in the forum. I directly get the message: Session not saved.

I know how to create an empty pup save, but this isn't the normal way of operation.

I hope there are solutions for this issue.

EDIT
Well well.
I did ctrl-alt-backspace and typed xorgwizard
I got the msg: keyboard be doesn't match the xorg layout. report to BK.

So I changed to us.
I got the msg: keyboard us doesn't match the xorg layout. report to BK.

So unable to configure xorg apparently.
My Thinkpad R40 has a ATI Radeon 6500 controller.
No support for this one?_________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

The really dark themeing should be an option, but not the default. It is much harder to see if your eyesight is a bit poor or aged, and could cause problems for those who are colour blind. On a technical note, the brighter the screen, the more the pupil stops down and the sharper the perceived image. As an optician, I showed both options to a random sample of patients with less than perfect vision, and all could see the 'normal' 4.3.1 more easily.

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