I don't think I have the eye-sight to run this CE; black text on dark-gray background or dark-yellow text on gray background .

Booted with pkeys as usual, no cigar, had to manually set my keyboard layout.

Right-click on desktop to open the menu - I miss it .

Sorry, but I was faster helping out my colleague on his Vista machine (which I had never previously run) than I was finding my way around in this CE-puplet (and I have tried quite a few of these puppies) .

Thank you.
I wasn't sure it followed the one of the newer 4.xx puppies._________________Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch

There seems to be an influx of oldies into the Puppy Forum these days who complain that the theme is too dark for their aging visual perception abilities. Since I'm rapidly becoming an "oldie" myself, I do understand what they mean. Maybe a default theme should be lighter (call it "Old but Experienced"?) and another for those with more cat-like vision. (Call it "Dark but Interesting"?)

On another topic, yesterday I had the task of installing drivers for printing and scanning into 4.4Alpha. (for a Brother DCP7030 all-in-one). Basically it worked for me by doing the following:

1. Go to http://packages.debian.org and select the 'testing' repo.
2. Install DPKG from there using Puppy Package manager.
3. Go to http://solutions.brother.com and download the relevant drivers.
4. Install the drivers as per the online guide at Brother.

The thing is, Puppy 4 series comes out-of-the-box with 'dpkg-deb' but not 'dpkg' which is necessary if you need to use 'dpkg' from the command-line for any reason - as is certainly the case if you are trying to install certain types of DEB packages such as the above-mentioned Brother drivers to take an example.

It is necessary to use the command-line here because on occasions you need to pass command-line parameters to dpkg e.g. 'dpkg -i force-all'

It is also often useful to be able to easily install debs into puppy in situations where there is no easily available native Puppy alternative.

What this adds up to then, is that there now appears to be a need for DPKG to be included in Puppy in addition to DPKG-DEB (already included).

To make this easier for newbies (as well as the more experienced)
a pet package for DPKG appears to be in order. (lol, a dotpet for a Debian DEB for DPKG).

The resultant pet will not be of any significant size and will also contain blank files placed in /var/lib/dpkg called 'status' and 'available'.

If there is any interest or demand for this, I could build this dotpet from the existing DEB. Let me know and I'll make it. Ideal for 4.4CE I reckon._________________Life is too short to spend it in front of a computer

I have been using petget to install debs for a while - would petget not install them? What advantage is dpkg over petget's deb support?
I have also made a patch to install txz packages and our own new similar xz compressed pet called pxt...all that is left is rpm and there was a thread on that too

mtpaint was from svn... wjaguar has made many improvements and mtpaint now also supports theming... but needs testing_________________Check out my github repositories. I may eventually get around to updating my blogspot.

Downloaded local DEBs will often install fine directly via Puppy Package manager. This is accomplished via dpkg-deb - a different package from dpkg itself.

But, if a situation arises where you need to install a locally downloaded DEB from the command line (as opposed to clicking on the DEB file and then letting Puppy PM take care of things) - then DPKG also needs to be installed. An example of this situation could arise if you have, say, printer drivers to install that require a forced install for some reason.

The drivers(s) for my Brother printer/scanner will not install in any other way other than by issuing a command line such as:

dpkg -i force-install 'name of driver' for example

Puppy by default only contains dpkg-deb - an executable that (not surprisingly) does not accept the command-line parameters from dpkg.

It's a relatively uncommon situation to come across having said that, but could be worth its weight in gold if you're struggling with installing stuff from the massive Debian repos as is necessary on occasions.

The size/usefulness trade-off would be favourable, since the basic dpkg executable is small. Only other things to be included in the dotpet would be two blank files that hold installed package data. (apt-get is not needed in this case in order to be able get this to work well enough to accomplish the required package installation). As always, dependencies are another matter though._________________Life is too short to spend it in front of a computer

-i Install the package
-l List of installed packages
-C Configure an unpackaged package
-F depends Ignore dependency problems
-P Purge all files of a package
-r Remove all but the configuration files for a package
-u Unpack a package, but don't configure it_________________Check out my github repositories. I may eventually get around to updating my blogspot.

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