'Puppy' Linux Corner.....

Puppy Linux Discussion Corner

------------------------------------------------------------------------------
 
Notice:- New 'Puppy' Forum - this may well become the main Forum before long:-
 
https://puppylinux.rockedge.org/index.php
 
-------------------------------------------------------------------------------

INDEX of items @ 'Puppy Corner'

Page 1, post #3: The save-file/folder explained
Page 1, post #7: Why can't I find Quickpet?
Page 1, posts #10/11: UEFI in Puppy

Page 2, post #20: Desktop link demo
Page 2, post #21: Sym-links in Puppy
Page 2, post #23: ROX-filer's rt-clk file 'action' box
Page 2, post #27: 'Big Buck Bunny' - video short made with Blender

Page 3, post #41: Installing Puppy to USB (from within Puppy) - video

Page 4, posts #48/49: Al's 'demo' of the 'quick'n'dirty' install method
Page 4, post #53: Nick's link to wifi connection using SNS (Simple Network Setup)
Page 4, post #57: Setting-up the new-style firewall

Page 5, post #69: Quick keyboard layout changer
Page 5, post #70: Re-mapping keys in Puppy (xmodmap)
Page 5, post #71: Virtual keyboard (xvkbd) - .pet package
Page 5, post #72: Windows 'Portable Apps' under WINE in Puppy
Page 5, post #73: Running 'Portables' from a USB drive
Page 5, post #74: Full.....or 'frugal'? Pet.....or SFS?

Page 6, post #77: SweetHome3D - package

Page 8, post #112: Nick (link to FatDog64 review)
Page 8, post #113: Link to PulseAudio FF 'fix'
Page 8, post #115: Using AppImages in Puppy
Page 8, post #116: WIRE AppImage for Puppy (a viable Skype replacement)
Page 8, post #120: Nick's XP running in a VM in Tahr 605 (w/'recipe')

Page 11, post #153: File syncing with 'SyncThing'
Page 11, post #155: Comodo's 'AV for Linux' - package
Page 11, post #157: Google Earth for XenialPup - package
Page 11, post #158: Google Earth for Slackos 560 & 570 - package
Page 11, post #162: 6-series Google Earth for Xenialpup/560/570 - package
Page 11, post #163: G.Earth for Racy 5.5 (and link to glibc 'upgrade for Racy)
Page 11, post #164: WebCamoid AppImage - package

Page 12, post #166: GuvcView 'black screen' fix
Page 12, post #167: Omron blood pressure analysis software - package
Page 12, post #168: SimpleScreenRecorder for Racy 5.5 - package
Page 12, post #169: How to 'RecordMyDesktop'
Page 12, post #170: More 64-bit AppImages
Page 12, post #171: Volume control short-cuts
Page 12, post #172: Scrolling tricks with Puppy...
Page 12, post #174: 64-bit Cinelerra 6.0 - package
Page 12, post #175: 32-bit Cinelerra 4.2 - package
Page 12, post #176: 32-bit Cinelerra 5.0 - package
Page 12, post #177: 32-bit final release of Cinelerra (5.1) - package
Page 12, post #180: TeamViewer 12.0.85001 - packages

Page 13, post #182: 'RecordMyDesktop' for all 5- & 6-series Puppies - self-contained .pet package
Page 13, post #184; OpenScad 3D CAD modelling app
Page 13, post #185; Firefox 'Quantum' in Puppy
Page 13, post #186; SoftMaker FreeOffice 2016
Page 13, post #189; Googledrive GUI
Page 13, post #190; Remmina remote desktop control app

Page 14, post#200; Gxine 0.5.95 - complete media player pet for Slacko 570

Page 15, post#211; various recommendations for a modern, easy-to-maintain Pup
Page 15, post#221; Nick's 'Attackpup' desktop!
(Page 15 - various discussions about EFI/UEFI on Puppy)

Page 16 - discussions about 'pen testing')
Page 16, post#230; MPV media player for various Pups
Page 16, posts 237-238; query about VLC in Puppy

Page 17 - discussions about Meltdown/Spectre in Puppy)
Page 17, post#251; Hiding data in plain sight - with Steg

Page 18, post#261;How to enter special Unicode characters into any text with Puppy
Page 18, post#262; Tixati BitTorrent client for Puppy
Page 18, post#264; YAD-based 'StartCenter' GUI for SoftMaker FreeOffice 2016
Page 18, post#265; 32-bit Upup BB 18.05 released (Bionic Beaver)
Page 18, post#270; TUSK (Evernote client) & Digikam 32-bit AppImages for Puppy

Page 19, post#271; WeX, scrox, and Weav (screen-capture w/embedded webcam possibility)
Page 19, post#272; Nimbus-weather AppImage, Electron-based 'Temps' weather app
Page 19, post#273; I-Nex - CPU-Z for Linux!
Page 19, post#279; 'Windows95' 64-bit AppImage in Puppy...

Page 20, post#287; Q.I.V 'slideshow' app (with GUI) - 32/64-bit .pets
Page 20, post#293; YAD-based Brightness/Color temp dual-slider app for desktop PCs
Page 20, post#298; Puppy Chrome 70 package released
Page 20, post#300; PaleMoon 28.1.0 .pet available

Page 21, post#301; Puppy package of SRWare Iron browser, v69 released
Page 21, post#302; Updated packages for Smartmontools/GSmartControl
 
Page 22, post#321; Pale Moon-portable browser
Page 22, post#322; BackSeatDriver, v3.0
Page 22, post#323; Chrome 72 available
Page 22, post#325; BackSeatDriver as AppImage/self-extracting script
Page 22, post#326; FF60esr/Thunderbird 60 portables
 
Page 23, post#331; BackSeatDriver video tutorial
Page 23, post#333; 'Lockstate' - on-screen toggling for your 'lock' keys
Page 23, post#334; SSE-only build of PaleMoon 27.9.4, packaged in portable format with glibc 'tweak'
 
Page 24, post#349; Opera 60 packages
Page 24, post#350; OpenVPN packages from OscarTalks
Page 24, post#352: EasyDD - GUI frontend for 'dd', from the PuppyMaster
Page 24, post#355; Chrome 76 & FF68esr-portable
Page 24, post#357; 'DogRadio'
Page 24, post#359; RacyPup website
Page 24, post#360; Chrome 78 - final 'standard' packages
 
Page 25, post#361; BackSeatDriver update
Page 25, post#364; Opera 65 - SFS & portable
Page 25, post#365; Kodi AppImage - 18.4 'Leia' / LMMS AppImage
Page 25, post#366; 'LeonFlix' AppImage (API now deprecated)
Page 25, post#367; Google-Chrome 'portables'
Page 25, post#368; Vivaldi/Yandex 'portables'
Page 25, post#369; Opera-portable
Page 25, post#370; NVidia driver packages
 
Page 26, post#376; Tipp10! typing tutor/OTPClient Linux desktop 2FA app
Page 26, post#377; Opera68-portable
Page 26, post#379; Opera 68 update/Iron 81 'portables'
Page 26, post#380; SoftMaker's FreeOffice 'TextMaker' - repack as standalone WP
Page 26, post#381; Vivaldi-portable updates / Vokoscreen for Quirky7 'lite'
Page 26, post#382; Opera69-portable
Page 26, post#383; FF78esr 'portables'
Page 26, post#384; Announcement of John Murga's passing away...
Page 26, post#385; Chrome-portable 84/Brave-portable/Yandex-portable update/FreeTube-portable (now defunct)
 
Page 27, post#392; Iron84-portable/Chrome85-portable/Vivaldi3.3-portable/Openshot 2-series for Bionicpup64
Page 27, post#393; Chrome86-portable/Iron85-portable/Edge for Linux-portable (dev-build 001)/AnyDesk 'RoxApps'/Skype4Linux .pet packages
Page 27, post#396: More news about Skype.
 
Page 28, post#414; modified, current Chrome-portable + explanation.
Page 28, post#416; BlueMaxima's project - Flashpoint 'Infinity' - packages
Page 28, post#417; Ungoogled Chromium, LibreWolf.....security/privacy-focused browsers - portables
Page 28, post#418; Updated PaleMoon 'portables' - v28.16.0 (32-, 64-bit)
 
Page 29, post#426; update for Google_Chrome-portable - 87.0.4280.141
Page 29, post#428; details for sym-linking 'portable-browser' profiles from an exterior location
Page 29, post#429; Skype-'portable'!
Page 29, post#430; updated Vivaldi-portables.
Page 29, post#432; updated Chrome-portable - 88.0.4324.96
Page 29, post#433; FreeTube 'portable', resurrected.....independent, Electron-based YouTube client.
Page 29, post#434; Zoom-'portable'- v5.5.2
 
Page 30, post#438; Skype-portable update
Page 30, post#439; updates for Chrome-portable, and Iron-portable.
Page 30, post#440; Zoom-portable - now v5.5.4
Page 30, post#441; Skype-portable update
Page 30, post#443; updated Chrome-portable
Page 30, post#444: Ugraded "glibc_tweak" 32-bit PaleMoon-portable (2.19 → 2.28)
Page 30, post#445; updated Chrome-portable - v89.0.4389.114

Page 30, post#447; updated Zoom-portable; v5.6.1

Page 32, post#466; experimental Chrome AppImage for Puppy.

Page 32, post#467; OpenshotQT & Shotcut video editors, packaged in 'portable' format.

Page 36, post#532; 64-bit compatibilty package for 32-bit Puppies...!

Page 36, post#535; 'Static' builds of ffmpeg, and OpenSSL with current CA-certs.
 
------------------------------------------------------------------------------
 
Evening, everybody.
 
Introduction
 
By way of introduction, let me just say that this is intended to be an on-going discussion thread about all things Puppy-related. It's intended to be the place you can come to for advice (or to give it); to make observations; tell any stories you come across about Puppy; reviews (or queries) about any particular Pups that take your fancy; links to useful information to do with Puppy; relate your own personal experiences with Puppy.....stuff like that.
 
It's also the intention to make this a central repository of information about Puppy in general, here at BC. All are welcome.....from green 'newbies' to seasoned 'veterans'. NO question will be regarded as 'silly'. And bearing in mind just how different Puppy is (even by Linux standards), I fully expect we'll even get questions from some of the 'old-timers'..!
 
Two very important links to start with:-
 
The Murga-Linux Puppy Forum (an invaluable source of Puppy-specific support and software):-
 
http://www.murga-linux.com/puppy/index.php
 
.....and the official Puppy Linux site:-
 
http://puppylinux.com/
 
There's also the 'alternative' Puppy Forum:-
 
http://puppylinux.info/
 
-------------------------------------------------------------------------------
 
Right! I'm going to kick this off with an introduction to one of the more 'familiar' Pups that have recently been released, following some requests in this Forum:-
 
LX Pup
 
This is based on two of the most rock-solid & stable of the current crop of up-to-date Pups; Tahrpup (currently at 6.05) and Slacko (currently 6.3.0.) These are finished off with the LXDE desktop, as also used by the 'minimal' official version of Ubuntu.....Lubuntu. As such, this DE will be familiar to not only regular Linux users, but also easy-to-navigate for Windows 'refugees'. The 'standard' combination of the JWM window manager & the ROX-Filer 'pinboard' make a very powerful combination.....but it does take some getting used to.
 
Both are based on current supported releases; 'Tahrpup' on Ubuntu 14.04 LTS (the Long-Term Support version), and 'Slacko' on the current 14.2 release of Slackware (one of the oldest of Linux distros still under current development.) I'm not familiar with the Slackware support schedule, but Tahrpup has access to the huge Ubuntu repositories, and will be supported until April 2019. Anybody more familiar with Slackware's schedule, feel free to post that information here, please!
 
As Viper has already discovered for himself, Puppy is amazingly fast.....since it runs entirely in RAM in most cases, and is coded to be as fast and lightweight as possible (even on elderly hardware).
 
You can find LXPup here:-
 
http://lx-pup.weebly.com
 
 
Mike. 

Edited by Mike_Walsh, 02 September 2023 - 07:11 PM.
Puppy Linux Corner index update - September 3rd, 2023

Two more links that you may find interesting:-

http://barryk.org/puppylinux/technical/root.htm

This is the 'PuppyMaster' (Barry Kauler, the originator of Puppy), writing about the 'perceived' pitfalls of running as 'root' all the time.....but take note of Pup's intended usage scenario. You may agree, you may not...

http://barryk.org/puppylinux/development/howpuppyworks.html

This is Barry explaining in his blog about the way that Puppy's union- and aufs-layered file system works, for those of you who may be curious about such things. I'll warn you, however, that it does get a wee bit 'technical' at times..! You have been warned... 

Mike. 

Edited by Mike_Walsh, 03 December 2016 - 06:55 PM.

The 'Save-file' and 'Save-folder' explained...

This is one of Puppy's 'secret weapons'.....and the reason why Puppy is so easy to recover, in the event of major 'melt-down'. Both of these contain a full Linux file-system inside them.

The 'save-file' was the first to be developed, and was essentially in the squash file-system format. At boot-time, Puppy, having located the save-file, will decompress the contents of it into RAM, layering it into the union file-system in such a way that it appears, to the user, to be one contiguous, normal Linux file-system. The save-file then remains in the 'dev-save_tmp' folder during your session; at shut down, any incremental changes from your session are written back to the save-file, and the whole thing is re-compressed as part of the shut-down procedure, and saved back to its original location, overwriting the previous one in the process.

The only limitation of the save-file is that it is 'fixed' in size. Utilities exist within Puppy for enlarging it, when it's getting full; it can't, however, be reduced in size. This was the reason for the development of the 'save-folder'; it will expand and/or contract in size like any normal directory, up to the maximum permitted by the partition in which it is installed to.

As long as you keep regular back-up copies of your save-file/folder (literally a copy & paste procedure - no need for special back-up programs), if Pup should throw an irrecoverable 'wobbly', it's a simple matter to replace the save-file/folder from outside of Puppy (again, 'delete', followed by copy/paste), then re-boot Pup. It'll be running in the condition it was in at the time the previous save-file/folder was backed-up. A half-hour job at most.

And, so long as the recommended format of ext3 is used, it's almost foolproof, since this contains the 'lost & found' directory for use with the 'e2fsck' utility, which can be used to confirm the save-file/folder's integrity. Ext2 is supposedly the best format to be used with flash-installed Pups.....but it has a tendency to 'corrupt' rather easily. This has been discovered through years of experience by various Puppy Forum members.

It is, if you like, the Puppy version of Windows' 'System Restore'.....except it's guaranteed 100% reliable, unlike the latter's well-known tendency to 'balk' at the critical moment..!

-----------------------------------------------------------------------------------

This is an over-simplified explanation, I'll own; but it explains the basic points well enough for the layman. A more detailed explanation can be found in the link in the previous post, about the workings of the union layer file-system.

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 06:12 AM.

Hi Mike (almost said hi Barry, lol), first question:

 

And, so long as the recommended format of ext3 is used, it's almost foolproof, since this contains the 'lost & found' directory for use with the 'e2fsck' utility, which can be used to confirm the save-file/folder's integrity. Ext2 is supposedly the best format to be used with flash-installed Pups.....but it has a tendency to 'corrupt' rather easily. This has been discovered through years of experience by various Puppy Forum members.

For the viewers as much as for myself, is there an incompatibility with Ext 4 and Puppy that would preclude it being used? I note that e2fsck is used as part of the GParted activities for manipulating Partitions, albeit Ext 4 is the format I am using all the time?

Cheers and thanks for starting this Topic.

Wizard

I have Puppy tahr6.0CE and tahrPuppy 6.0.5 installed with Lick so I can boot to them or Win 10. I noticed tahr 6.0 has Quickpet

as a package installer but I can't seem to find it in 6.0.5.   Is it there somewhere ?  Enjoy using both distros 

Morning, all.

Hiya, Wiz.....and 'Welcome'. (I almost said 'Welcome to the kennels'.....but that's what we refer to the Puppy Forum as..!)

Now then; as far as I know, the main reason ext3 is used is because the Puppy Universal Installer doesn't support Ext4 for the 'frugal' install. It's quite happy with Ext4 if you want to install Puppy as a traditional, 'full' install.....but then you lose all the advantages of the 'load-on-the-fly' SFS packages, ease of recovery after 'meltdown' (!), etc.

Our Japanese forum member, Shinobar, found this out way back in 2010.....and, as far as I can determine, Puppy is still using the same version of the PUI. Shino considered that it could be construed as a 'bug' within the PUI.....but the general attitude toward such things in Puppyland is that if such things work, and there's no demonstrable security 'issues' known.....leave it alone. Puppy doesn't automatically update stuff on a regular basis anyway, as I'm sure you're aware; people tend to simply install the next, newer version if they want to use more up-to-date stuff.

And in Puppy that's a very quick, simple process. On top of which, the 'frugal' install is by far the most widely-used, since that's the way Pup has been developed to work over the years. 'Full' installs are usually performed by newbies....since there's not much documentation provided to tell you otherwise, I'm afraid. (Something which does need addressing at some point, I suspect.)

Hope that answers your question!

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 05:17 AM.

@Dave46:-

Morning, Dave.

Enjoy using both distros  

Glad to hear you like 'em!

--------------------------------------------------------

"Where's Quickpet? Why can't I find it?"

Ha! This has got to be one of the most widely-asked questions on the Puppy 'Beginner's' sub-Forum in the last couple of years.....and it's all due to the way the updates/upgrades, or 'Service Packs' (as Phil B. has decided to call them!) come through.

Everything's linked in to the PPM (the Puppy Package Manager). The first time you go into this, the initial required action is to update the databases, okay? This not only updates the information Tahrpup holds about the Ubuntu repositories, but it also downloads the 'Service Pack' data, too.....of which 'Quickpet' is one component, along with the 'Bugfix' Menu Entry.

The next time you re-boot, then go into the PPM, you'll be asked if you want to upgrade to the next 'Service Pack' level. This doesn't occur automatically, like with all the 'big' distros (Debian, Ubuntu, Mint, Red Hat, Arch, etc., etc.), because 'Puppians' like to be in full, total control of their system at all times. And the view taken is that with automatically installed 'updates' (like with Windows), you don't know what you're getting.

Hence, the 'manual' aspect to all this.

IF you've installed 6.05 straight off, then I believe the procedure is still the same; update the PPM, re-boot.....and they should be there, automatically. I'm not dead certain about that, because I started with the original Tahr 6.0 back in Nov '14, and progressed up through 6.02 & 6.03 to 6.05, as the 'Service Packs' arrived. Don't expect these to keep on arriving for too much longer, as Phil B. is putting most of his time and efforts into the new XenialPup at the moment. It's unusual for Puplet developers to do this for any length of time, in fact; most Pups tend to remain as a fixed 'snapshot in time' as of the moment they were created & released to the community.

When all's said & done, I always recommend Tahr to newcomers if they want something that's rock-solid and stable; Phil B.'s work is beyond reproach, as he always goes out of his way to ensure that everything just 'works', OOTB. Certainly, it was the first Pup where everything 'just worked' for me.....

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 05:26 AM.

Hi Mike,

Thanks for your detailed explanation !!  I haven't run across the update feature in the Package Manager yet, but I'm going to look for it now.

" automatically installed 'updates' (like with Windows), you don't know what you're getting."   I couldn't agree more.

Windows knows best what you need.  ( sarcasm intended)

Dave

Hi Mike, 

OK, I found it and now have " Quickpet ".  I wanted  Chrome browser and I couldn't get it with the package manager. Now I have it, thanks to your help !!

Dave

Just a quick reminder to anyone wanting to run Puppy on a UEFI booting machine .... you need to disable safeboot in your UEFI settings

Unlike Ubuntu based distros, Puppy is not "recognised" as a "legitimate" OS if safeboot is enabled, so your computer will not boot from it until safeboot is disabled.

Hiya, Gary.

In actual fact, while that is still true to a large extent, it's not 100 % correct any longer.....and even most folks who are 'into' Puppy aren't aware of this.

A few years ago, when JamesBond & Kirk, the developers of FatDog64, were getting the early versions up-and-running, they, along with a few of our more brilliant Forum coders, were trying everything they could to achieve a 'workaround' for the then new UEFI/SecureBoot combo. They spent a long time on this.....but eventually came to the conclusion that there was no 'clever' way round it.

So they bit the bullet.....and forked over the required $99 to obtain a SecureBoot-recognised 'key' for Pup. They were, however, careful not to specify an exact version.....realising that FatDog would evolve way faster than Windows itself would. So the licence merely states 'Puppy' Linux.

JamesBond & Kirk have very kindly 'shared' this licence key with the other development members of the Woof-CE team (who essentially determine the direction Puppy will take these days, after Barry K delegated this authority when he stepped-down to get on with developing 'Quirky')....and it's being used in the current alpha and beta versions of what will soon become the 7th generation of Puppy in the next few months.

So although 'new' Puppy is now 'recognised' by most modern Windows-inflicted machines as being an 'official' OS, by and large Gary R is correct. For the majority of existing Pups, you do need to disable SecureBoot/FastBoot first.

Good catch, Gary. Thanks for reminding everybody of that. 

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 07:44 PM.

Thanks for the update Mike, glad to know that the next generation of Puppies will not need safeboot disabling.

To be honest the only reason I remembered it was because I've just been installing Slacko to a USB drive, and although it would boot on my Mint machine (ex W7 and BIOS booting), it wouldn't boot on my W8.1 (UEFI booting) machine.

So I scratched my head a bit, wondering why a version of Ubuntu that I have on another USB stick would boot on the W8.1 machine, whilst Slacko wouldn't, and then remembered that I hadn't disabled safeboot (because I didn't need to for Ubuntu). Quick change of UEFI settings, and bob's your uncle, problem gone.

Hey, Dave.

Glad to hear you got it sorted. I was a bit worried my instructions might have been a bit out, since I haven't done any updating on Tahr for about 15 months now.....and the old 'grey matter' is not what it was these days!

You may find the version in Quickpet isn't the most recent version of Chrome available. I think it's 43 (44? 45?).....something like that.

If you're on 32-bit Tahr, the very last version of Chrome supported for Linux was 48. One of my colleagues on the Forum, OscarTalks, has this last version in his repo. It's as safe as houses; I've been using it for several months myself. If you want this one, it's available as both .pet and SFS, from here:-

http://smokey01.com/OscarTalks/

However, you still don't have an up-to-date version that way. We've experimented with a couple of the Chromium-based 'clones' in recent months; FlashPeak's SlimJet browser, and the Iron browser from German developers SRWare.

Chromium itself is where all the cutting-edge development work takes place (and the Chromium Projects are sponsored by Google). When this reaches a stable release (usually, I'm afraid, compiled against the newest version of the glibc - the 'C' library), Google take it, re-compile it against a much older version, add their proprietary bits'n'bobs, then release it as Chrome. This ensures compatibility with the largest possible user-base.....further enhancing its popularity.

SlimJet is nearly the perfect replacement, along with a host of privacy-related stuff. However, you can't watch NetFlix on it, since FlashPeak won't code in the necessary h.264 support.....for 'legal' reasons.

Iron, however, will allow you to watch NetFlix.....after we've replaced the WideVine module with its counterpart from Chrome, that is! PepperFlash works fine, YouTube too; Iron is, to my mind, the ideal replacement on 32-bit architecture for anyone who wants to still use 'Chrome'. Your Google a/c will work perfectly with it, just as it does in Chrome.....along with all your extensions, etc.

If you'd like to give it a try, I'll give you the same link as I gave to Viper_Security the other day, for use in LXPupTahr. This is from my MediaFire a/c (and was the newest version, based on Chromium 54, until yesterday.....when Chrome 55 was released):-

https://www.mediafire.com/folder/4r81ytprtusz5/32-bit_'generic&%2339;

Please do heed the advice from Animal in that same thread:-

https://www.bleepingcomputer.com/forums/t/633378/laptop-for-friend-puppy/?p=4131768

What we're doing here (sharing files) is not normally endorsed or even allowed on BC. This is a special exception made for the Linux & Unix section.....largely due to the fact that Linux is fairly much community-driven ( and Puppy even more so than the majority)....and most Linux users tend to be pretty tech-savvy, and, generally speaking, know what they're doing. And in Puppy's case, a huge amount of software is developed by the Forum members themselves.....not by some faceless corporation. So; use at your own risk. Although, in this case, this is my own package, and I'm posting from it right now, so......

As soon as the next version of Iron 'hits the shelves' (which won't be long), the new Puppy package won't be far behind.

And the majority of established Linux users tend to be a lot more respectful of other users.....far more so than in the Windows world, where you tend to just be a speck among the faceless masses..!

Anyway, I would recommend giving it a try. Your decision, of course...

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 01:17 PM.

Hi, Gary.

Yes, I guess I'm extremely lucky that there is literally not a single thing I need Windows for. What few Windows apps I do still use (all graphics apps), in every single case run perfectly under WINE.

What do I need MyCrudSoft for???     Puppy works for me.....and it's a perfectly usable 'daily driver', if people will give it a chance.

Mike. 

Edited by Mike_Walsh, 04 December 2016 - 07:47 PM.

Hi Mike,

Thanks for the links and information !!  

I am using tahr64 so the latest version of Chrome I can find is 32. I tried using the update from Chrome browser and managed to

trash my Chrome install    so I had to uninstall it and re-install with Quickpet.

Can you suggest a basic photo editor for my versions of Puppy?  (tahr64 6.0.1  and tahr64 6.0.5)

I installed Gimp but it is far more than I need.......GTK looks interesting.......is that available ?