- place jwm/rox into an external SFS file, so the desktop can easily be changed by another and builders can build alternate desktops much strongers. See this thread

- woof settings so builders can build a barebone easily. Because right now we all have hard time at removing packages and testing what dependencies are needed.

- gtkdialog for all the old scripts. See Carolina pupsaveconfig as an example

- Beware all puppy scripts can fit into a 1024x768 screen because right now many are not even readable. So if a user have a video driver problem and downgrade to 1024x768, at least he could setup his system again. (this have been a show stopper for _many_ people)

- Beware many alert popup have colors hardly readable on notebooks, like black on purple etc. Set a nice and good looking gtkdialog alert popups, all the same look and feel all over the puppy so it is easy to recognize.

- improve and simplify the video card selector with something like jockey on Ubuntu: if your video driver is there, go on with it. If your video driver is not there start with the best resolution useable, then launch later puppy-jockey to detect an additional driver on internet repository, then popup offer to download and install.

please re-code iwlwifi.ucode to allow Intel 5100-1 device to use WPA-PSK encryption-it is capable in XPsp3. I do not know if NDISwrapper will enable the function. That, and RA2850 RTL9192SU devices similarly. Please advise.

i am new to linux and lupu and here is a report of what confused me. i fixed it now this is just so it can be changed in the official version

Startmount cannot be started from PupControl - it needs to be called with its full path /usr/local/Startmount/Startmount to function correctly. which startmount is /usr/bin/startmount which is a copy of Startmount but note that a symlink would not work either. it would be cleanest to comment line 349 in PupControl-bin and change the action path or a launch script could be made

quickpet links lupu_devx_528.sfs but the highest version available is lupu_devx_525.sfs

getflash doesnt work - the broken link to adobe.com causes the error message "Unable to contact the server, please check your internet connection". there is a package flash_install-0.1 in PPM which succeeded; otherwise, changing the link to 11.2 fixed getflash and apparently 11.2 is the last version

I'm seriously curious why VLC is not the default mediaplayer in Wary, Slacko, and Precise. Instead we get these clunky mplayer apps that have two simultaneous gui's by default until things get cleared up in Preferences. How much larger is VLC that versions can't adopt it as default player?

VLC version 1.1.7 pet works great with the portion of QT that is built in to Puppy, been using it as main media player for two years now.
Couldn't get the midifile plugin to work, but everything else I have thrown at it works.

VLC version 1.1.7 pet works great with the portion of QT that is built in to Puppy, been using it as main media player for two years now.
Couldn't get the midifile plugin to work, but everything else I have thrown at it works.

Yes, I do use this VLC 1.1.7 also. It has been already available in LazY Puppy 528-4 and meanwhile I've set this as the default Video Player in my LazY Puppy (XineDVD and Gnome-MPlayer are removed). For Audio I do use the Aqualung Player because of its XML based music database._________________LazY Puppy Home
The new LazY Puppy Information Centre

1.) make sure Puppies fit on a CD-R(W)
2.) Settle on one default Video and Audio, VLC for vids, I'm not sure what is the better Audio, I've only experienced alsa-mixers.
4.) Jeez, these browsers are getting bloated... any ideas? 120Mb mem at fresh start?

If I'm not mistaken, Puppy has already done this many times and those distro versions are already available.

I am not suggesting that Puppy LInux need not advance. Rather, that for older PCs and "CDs vs DVDs" Puppy has already addressed those needs.

The technology changes is what Barry had in mind when he began investigating RasPi and etc.

Most all x86 (especially 32bit x86) has already been done. PC manufacturers switched to x86 64bit PC/laptops/etc in 2006+. Several Puppy developers, for past several years, are now looking at 64bit x86.

ARM manufacturer are becoming 64bit. Handheld and video of processors have already started the 64bit migration as is already seen and will be seen, more, at 2014 CES.

With the older x86 technology, PUPPY LInux has done an incredibly great job of providing needed coverage and addressing fundamental needs.

I am hoping the next releases continue to do what some developers has been doing more and more of; namely, documenting what are the tested platforms and the minimum platforms their distro are targeted for as they bring forth newer distros addressing newer hardware needs that users and Linux industry presents. Thus, a user now see, on the front end, the base expected environment for the PUP as well as any dependencies and exceptions which usually accompany that Opening Post's documentation (you know, the open thread of the distro or packages).

This documentation, though very subtle and so very minor, is a real benefit to any community user/testers who come to Puppy Linux for a desktop/LAN/WAN solution._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

I have a small, but in my view, important suggestion to make. I run PP 5.7.1., and when ever I load, or unload an SFS file, at the subsequent reboot, my desktop will be filled with all the icons of all default applications in their respective position like it was the first time I booted Puppy, but they are placed along with the icons I placed there myself, so it effectively becomes a messy affair.
Now, jpeps has made an terrific little utility for this which backs up and restores the desktop.

This has been a true lifesaver for me. What I want though, is for this procedure to take place automatically. The best thing of course is for this bug not to occur at all anymore, but if that turns out to be too complicated, then I want a smart Puppy which understands that under certain conditions a desktop restore at bootup is required.

Save the script with a unique name (in /usr/sbin or /usr/local/bin) and execute/call this script from somewhere in /usr/bin/xwin (make sure it is executed before X is starting) and change the following in script /usr/local/bin/desktop-restore at line 34

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