Cold-Targz-Backup utility for frugal Puppy installs v.5.1

[glene77is]

Linux_CTB_Screen-Shot.jpg

Linux_ColdTarBackup_230116-889.jpg (84.71 KiB) Viewed 732 times

First posted by glene77is »
Monday, January 16, 2023 now with revised source code notes. edit: 240801-0928

... UPDATED Current Version #5.1 dated 230205 is uploaded here :
... This version #5.1 has a custom gtk box_help sub-routine which is more flexible than the original gtkdialog.
... This version #5.1 can use a /CTB_config.sh file to specify alternate tar.gz output targets.
... version 5.1 "CTB" has a "alpha" exe script, a "compact" rendering which is stripped of notes ... much smaller.
... version 4.1 "CTB-SL" has option to scan list of 8 mounted drives sda1 thru sdh1

V#5.1: Download the Cold-Tar-Backup executable BASH script, "run", and read the "Help" page-out.
V#5.1: current file is also available at http://www.GeoCities.WS/glene77is/
V#5.1: On my website, on the "front page" click this label : "Linux Page" for the GC_Linux.html

Suggestion to observe tar messages as a Progress Indicator.
(0) Once you have downloaded, and extracted the several code scripts to a working directory.
(1) Rename "CTB-SL.sh" file to "CTX.sh" and follow these instructions ( to use the Xterm method ).
(2) place the executable file into "/root/my-applications/bin", which is a Puppy System Path location.
(3) From Command Line terminal, carefully enter xterm -e CTX.sh
(4) This proces will call "xterm", which will execute "CTX.sh" , which will show the "TarOpt" code activity inside "CTX.sh" .
You can observe the message output of tar as it cycles through groups of code lines, as a Progress Indicator.

"CTB"
...is our Puppy Backup for Frugal saveDATA
"PUPSTATE"
...controls the program parameters.
"CTB"
...will generate a 'saveDATA.tar.gz' with and your custom name , tagged with "Date-Time-Seconds".
...will generate a standard '.tar.gz' backup
...for saveFOLDER or saveFILE.4fs
...for Official Puppy Frugal Systems.
"CTB"
...will place the generated output file "saveDATA-DTS.tar.gz" "local" to the source data.
..can use a /CTB_config.sh file to specify alternate tar.gz output targets. Read HELP page.
...
...
"CTB-SL v.4.1" has option to scan list of 8 mounted drives sda1 thru sdh1
... to copy the saveDATA.tar.gz into '/CTB_Backup_' . List is user modifiable in source code.
...
"CTB"
... is written only with lots of standard BASH script .
...... We use some common gtk dialog-boxes v.8, and xmessage boxes.
...... Both gtk routines are included in all Official Puppy OS .

"CTB v.5.0"
... has tool-tips on front screen main buttons.
... Run the CTB script and read the "HELP" tagged page.
... Then Open the (KOSHER) Source Code to see how it's done.

"CTB v.5.2"
CTB Version 5 series is available:
This series has Double-Click <buttons> and Embedded-Images.
This has customized and embedded gtkdialog code
for some of the gtkdialog/box_ and a "config file" .

To restore: ''XArchive', will 'Extract all' from
the saveDATA-CTB---tar.gz file. PKunzip also works ok.

Our Design Philosphy is: .
(1) I.T. documented coding,
(2) readable/modular coding,
(3) modifiable coding.

CTB Produces a '.tar.gz' output file.
Very Standard ... just 'tar' into 'gzip' ...
just like in 1975, the UNIX Tape-ARchive.
Not spectacular, but guaranteed !
Produces a '.tar.gz' output file written to the Working Home SubDir
alongside of the "saveDATA" entity. .

Features for Puppy Linux Backup :
(0) "CTB" original "reads" / "writes" from / into the Puppy OS "home" location.
(1) "CTB" creates a 'tar.gz' backup
. . . with filename plus date-time-seconds stamp.
. . . saved in the Source directory, Puppy OS "home" default.
(2) "CTB" automatically selects fast compression.
(3) "CTB" runs OK on 32/64-bit Frugal SaveFOLDER installs ... in EXT2/3/4 hard-drives and Flash-Drives.
(4) "CTB" runs OK on 32/64-bit Frugal SaveFILE.4fs installs
... in EXT2/3/4 hard-drives and Flash-Drives.
(5) "CTB" is controlled by the PUPSTATE file.
(6) "CTB" handles any System home location
... by using Barry Kauler calculation code described in source code .
(7) "CTB-SL" can scan list of 8 mounted hard-drives sda1 thru sdh1
... to copy the saveDATA.tar.gz into subdir CTB_Backup_ .

Our script has been tested successfuly
on our 12 running Official Puppy Linux systems :

From the Puppy F.A.Q for UpupFF+D 20.12 :
https: // github.com /puppylinux-woof-CE/woof-CE
Q: What is an official Puppy Linux distribution ?
A: It must meet two conditions.
1) It must be built using Woof-CE and its build “recipe” should be in woof-distro.
2) It must be endorsed as “official” by the Puppy Master.

NOT Tested on personal Puppyish distros
which may NOT have all required "dependencies" included by their original distro authors.
unofficial derivatives( “puplets” ) are usually remasters (or remasters of remasters,
made and maintained by Puppy Linux enthusiasts, usually targeted for specific purposes.
( quote from https: // puppylinux-woof-ce. github.io )

---

CTB Version 5 series is available:
This has customized and embedded gtkdialog code
for some of the gtkdialog/box_ and a "config file" .

Note: about Puppy Wheezy
DebianDog project started as Light-Wheezy+Porteus-Wheezy.
Wheezy is not Puppy Linux , but is only "Puppyish",
and it has nothing to do with Puppy based on Debian via Woof-CE. .
Wheezy was not generated via Woof-CE and is Not in the List of Official Puppies.
Wheezy presents dependency problems for routines written for Official Puppies.
If you Download DebianDog / Wheezy be ready to learn different package manager
and different System setup in Debian manner and different Dependencies.

...
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
If you have a problem, try using the "private mail" option at the top of Murga page.
If you have a problem, please remember that this is BASH,
....... BASH is not perfect, and BASH has Quirks .
A better language might be Python, Pascal or Fox ( SCO Unix ),
but our projects [ CTB , MGN, B2R, C3C, S2F, et al ] have given us a chance to explore BASH.
.......

.......

[rockedge]

@glene77is Thanks for the chance to try this out! Your timing couldn't be any better.

I have a 111 Gig save Folder from a Bionic64 that is a primary code dev and compiling machine that sports a solid web server for all website dev and configuration before "going live" and are network accessible.

I will assume that this backup will be a decent test of the package's capabilities

[glene77is]

* NEVER "Assume" , always read the "HELP" page and "FAQ" page.
* Always do test runs and examine the results , if you use a network.
* If it is your skill set, then read the source code. My V.2 has good notes.

Rockedge, we hope this long note helps.

You are welcome to "test" CTB, and I am sure you will have friendly comments .
I have uploaded the 'current' v.2. which is much neater,
and the options are better documented in the source code.

Your 111 Gig save Folder (saveDATA) from a Bionic64 sounds like a big load.
"111 G" is a monstrous size to deal with.
All my systems have running/booting saveDATA size as 15M to 200M,
and 1/3 that for the saveDATA.tar.gz.
Tar.Gz compresses below 50% mostly.
I am curious about that "111 G" , but I have my hands full with our projects.
...
To you, my comment is that we have eight versions of Puppy LInux up/running,
and we have gone to great lengths to locate lingering / left-over code
which we purge from the system
which we cull by script frequently by a script "C3C.sh".
Our search for "extra-lingering data" is via common "A" / "B" comparison search.
...
The /root/cache can be culled for some apps, as some apps rebuild each runtime.
For example:
FireFox browser has a 400M extra baggage cache, and IRON browser has similar,
both stashed elsewhere, which we cull by script frequently.
So, that is browser "cache" and "extra" baggage.
Both have a /root subdir ( /root/iron and /root/mozilla ) with ~ 400 M data
and we do a relative link and move these out of the /root system and onto a /hard-drive,
thus reducing the data load inside of the RAM saveDATA entity.
...
Also, we have used "linking" into file.SFS ( like LibreOffice method)
which reduces the saveDATA load.
If you want to see a "real" Squash-File-System, check KNOPPIX ... fantastic !
...
We think that your system is more complex than we imagine,
and we wish you good fortune in your projects.
...
Just a passing comment, pal ... that is all this is.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
If you have a problem, try using the "private mail" option at the top of Murga page.
If you have a problem, please remember that this is BASH, and BASH has Quirks .
A better language might be Python, Pascal or Fox(Unix),
but CTB , MGN, B2R, C3C, S2F, et al, have given a chance to explore BASH.
We are small, and I retired 25 years ago, and may go 'beach-combing' soon
or simply ride my bicycle off into the "sun-set of Time".
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

Rockedge, we hope this long note helps.

.......

Attached is the Front Screen for CTB V.3.1,
which includes an option for a config-file to specify an alternate tar.gz output file subdir.
Always read the "Help" and "Faq" screens.
...

[bigpup]

Not a bad program!

Something to think about.

Downloaded rc.z_CTB-p-220208-0700-sh.zip
Had to UN-compress it.
Had to give it exec permission for it to run.
That is good info to post, where you have the download link.

This is small enough to make it into a pet package for people to download and install.
Forum will allow pet packages as attachments.
Size limit is max 512KiB.

[bigpup]

Where does this place the backup?
I can not find it.

[rockedge]

@glene77is I went through all the build directories for the many packages I've compiled. Knocked the save folder down to 71 G very quickly. Now looking at the many mysql databases and SQL dumps. probably another 20 G I can delete. Need to be careful though since there are quite a few murga forum database conversions in various stages that are hold overs from the project of converting the murga forum software from a very old version to the newest.

[glene77is]

to BigPup,
Thanks for the 'tip'. " "
I like your Proverb:

When I was a kid, I wanted to be older.
This is not what I expected

...
Much info and procedures are explained/described in the "Help" and "FAQ" tabbed files,
accessed by running the CTB application.
...
Inserted these notes, in my main post, per your good 'tip'.
"CTB"
... will place the generated output file "saveDATA.tar.gz" "local" to the source data.
...This note thanks to BigPup.
"CTB"
... must be given "exec" permission to run. All scripts need this.
...This note thanks to BigPup.
...

Building a PET package sounds like a good idea.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

[glene77is]

to rockedge
Great work "sweeping" the file. Better to "sweep" now than "scrub" later !
Researching your apps, data, and keeping things in order will always be a good thing.
.
Some 40 years back, I did a one year long contract gig
on a data-entry/contact-manager/accounting/auditing program,
some 4K pages, on a 'live system' at our university.
Worked from the 'get go'
.
Some 30 years back, I did a contract gig for the "St.Jude / ALSAC" group
for their first Contact Manager program which controlled their fund raising efforts
... 150K foreign names ! , on an IBM PC-AT, using FoxPro.
Great language (with SQL) but minimal PC !
Worked from the 'get go'
.
My obsession with code planning, code organization, code formatting, code documentation (headers/footers)
produced working systems with no interruptions to service.

Worked from the 'get go' is a good motto !

.
Great work on your part !
You can do "before install" / "after install" comparisions to find where applications are storing their extra data.
Some applications will re-write / restore these caches on each start-up. Browsers are good about this.
These floating cache files can be deleted by script in /root/startup or tacked onto /etc/rc.d/shutdown .
The permanent cache can be "moved" to the Hard-Drive and then you can place a "relative link" back in /root where they will be seen and used.
This will minimize your size of the "saveDATA" entity. I do this 'move out' for my Browsers, since they collect some 400MB of permanent working data.
,,,

[bigpup]

will place the generated output file "saveDATA.tar.gz" "local" to the source data.

After reading that statement.
I found the output file it made.

This was for fossapup64save.
Generated a file with this name:
fossapup64save-CTB-220214-0502-32.tar.gz

[bigpup]

Any chance you could add a feature, that would give you the option to choose, where the generated backup file would be placed?

I and many others, like to keep backups in different locations, even different drives, from where the original save is located.

Being able to choose, stored location, would be a nice feature.

[glene77is]

to BigPup
Your useful request has already been done,
but not so obviously.
So, here is some verbage about the CTB semi-automatic method.

CTB-SL v.4.1 is the "Scan-List" version. (note: 230116)

(1) The primary CTB Backup tar.gz is written local, so no doubt that it works.
(2) Copying to foreign repositories is done according a function" CTB_Scan_List()".
(3) Activating the "SCAN" is done by the user clicking on the button "SCAN" top edge of screen.
* Repeated manual selections of faraway target Repositories is not required.
* This approach is a semi-automatic method and reduces 'maintenance' by 'me' for 'users'.

This work-station seeks drives out to "SDH1" , therefore we wrote a "ScanList" function
which can be user selected on a button "SCAN", top edge of screen
and which "seeks" a standard target subdir. If you want it, create it, CTB can find it.
[Unless you are in midst of a server farm, and you should be using Rsync or GRsync instead ! ]
The "Select Box" method was not written; we let the semi-automated "SCAN" function do it.
(1) Backup will default to local only, ( if you do not preselect "SCAN" button ) .
(2)
...(a) Select "Scan" first, then the"BackUp" button changes label to "BackUp + Scan".
...(b) Then Select "BackUp" and it will
......(1) run the "TarOpt" to create the Backup.tar.gz,
......(2) activate the "Scan" to cast the BackUp.tar.gz to the prepared 'targets' via the "Scan-List".

*** "Scan" method is to set a flagfile in /tmp ,
so then when "BACKUP" is clicked,
it will "Scan" a list of possible targets
in a list like "SDA1", "SDA2", "SDB1", "SDC1", etc.
*** "Scan" will look for a subdir named "/CTB_Backup_" and will deposit a copy of the BackUp.tar.gz file.
You only need to create a subdir named "/CTB_Backup_" on a mounted HD ,
like this "/mnt/home/SDC1/CTB_Backup_".
If you examine the function "ScanList" , you will see how simple this approach is.

CTB-SL v.4.1 is written in BASH and seeks only for 'mounted' hard-drives
from our hard-coded list.
CTB-SL v.4.1 does NOT search for all possible mounted drives, everywhere, anywhere, blindly.

We have written systems in FoxPro ( Unix version and Microsoft version, and MacIntosh version ),
which spanned a server-farm for our city government, with many unknown drives.
....... but that is NOT what CTB-SL v.4.1 was designed to do.

* CTB-SL v.4.1 is written to "SCAN" a list hard-drives from a pre-set list like this :
"SDA1", "SDA2", "SDB1", "SDC1", "SDD1", "SDE1" as seen by a work-station.
If one of our hard-drives is un-mounted, then CTB simply does not 'see' that one,
and will skip over (no error).

* The "scan-list" is written into the "function CTB_ScanList()"
which you can alter view in the Source code, and alter as you wish. It is simple.
* Repeated manual selections of faraway target Repositories of "Backup files" is not required.
* Simply follow the simple examples in our written code in "function CTB_ScanList()"
and cast your Backup.tar.gz entity to the prescribed subdir "/CTB_Backup_"..

Need to go check the lovely Setting Sun for this evening
... May not come back too soon !

[glene77is]

To BigPup
Your useful request has already been done,
but not so obviously.

First: ( and indicating our 'design model' )
In the past, 1980 and forward,
we have supported groups of 27 to 152 people,
with high level languages and Transactional SQL
in relational database systems.
So, we prefer to semi-automate any decision making
that the application-users must do.
We tend to Anticipate and Reduce Support requirements.
Therefore, CTB was written to "Scan" for possible Hard-Drives
in order to 'cast' the Backup.Tar.gz files .
This is a very orderly and standardized method of "BackUp".
We do not allow for dis-orderly deposits of "BackUp" data.
Rsync and GRsync are very good at distributing "BackUp" data
but still let the 'application-user' make his own fatal assignments.
[ The "How,When,Where" an 'application-user' handles his
important/critical Backup data is a whole different topic.
... but Not Now. ]

Second: ( attending to your 'suggestion' )
We added a long "tool-tip" to the "BackUp" button.
We could add long "tool-tip" to every button,
but then the usefulness of the "HELP" and "FAQ" page-outs
would be minimized, and the screen could seem "cluttered"
with every mouse move automatically activating a floating "tool-tip"
... jumping up ... possibly initiating a "support call" .

Third: ( regarding our "design model" )
(1) We would prefer to have a "short" "tool-tip" at each button,
and reserve the "long" text information for the Help and Faq page-outs.
(2) The usefulness of the "HELP" and "FAQ" page-outs
is to consolidate the Help and Faq information,
behind a button, on an obviously special window.
This keeps the main screen "clean"
and the application-user can focus on the task.

[b]Fourth:
We are assuming that you have run CTB,
and that you have opened the "Help" and "FAQ" page-outs.
We realize that different countries and regions use language differently.
We will appreciate any comments to the wording and arrangement
of the "Help" and "FAQ" page-outs.

...

CTB_Screens_All-220310-view02.jpg (104.65 KiB) Viewed 1723 times

...
..
...
NOW ...
Need to go check the lovely Rising Sun for this cool crisp morning
... May not come back til noon ! ... may not come back at all ?
The 'old man' in me understands that his 'day' is coming... age 80 ...
so I need to appreciate what has been offered for this day !

[glene77is]

to rockedge

Great work "sweeping" the file. Better to "sweep" now than "scrub" later !
Researching your apps, data, and keeping things in order will always be a good thing.
...
I use CTB to create a DTS stamped saveDATA entity every 1/4 hour, and so that is my panic backup for when I muck up some running code.

[glene77is]

This post may be my last comment on this subject here.
We are in process of 'closing' the shop.
Everybody has other contracts to stay busy.
I have a bicycle to ride --- off into the evening sunset.
Thanks for your help.

Bike_Duo-Riding-in-Forrest-Road_sunset-sml.jpg (17.35 KiB) Viewed 1677 times

[rockedge]

@glene77is

Oh no what happened? Is the project finished?

This is some significant work and works really good. Thanks for sharing it with us

I am running this on 49 GiB save folder Fossapup64-9.5. This is a web server set up to work on phpBB3 forum development and other web based systems. Also for Zoneminder testing of the latest git master branch

Screenshot(64).png (274.18 KiB) Viewed 1660 times

[rockedge]

Glad to report Cold-Tar_Backup worked well backing up a 49 GiB Fossapup64 save folder.
The resulting .tar.gz is now 30 GiB which I transferred to a back up drive.

Screenshot(65).png (111.99 KiB) Viewed 1644 times

The script's logic performed well and did not copy the dynamic socket files produced by Zoneminder since I ran the backup on a live system with a full featured web server running.

[glene77is]

RockEdge,
Sorry, missed your post.
Well, can't go on with this program forever.
Read the Help and FAQ pages.

From the OS system help page:
#(: snapmergepuppy is -u, --update
#(: copy only when the SOURCE file is newer
#(: than the destination file or when the
#(: destination file is missing
#(:
So, if you want a "pristine" copy of old saveDATA into current saveDATA,
snapmergepuppy will NOT do that.
SMP is called with option "-u" which is an "update" (read "merge") .
Snapmergepuppy will "MERGE" it.

The only way to obtain a "pristine" saveDATA is to delete the existing old saveDATA and start again fresh.
I think it is not reasonable to examine every piece of data stored by all your applicacations and delete the extra files.

CTB has the option to SCAN a list of normally named HardDrives ( SDA1, SDB1, SDC1, etc)
looking for a subdir named /mnt/home/CTB_Backup_
into which it will cast your latests saveDATA.
I do backups every 15 minutes or so,
and since they have a DTS in the name,
I can always restore to my 'last working version'.

Backups are so important for historical reference, if lightning strikes ,
and so critical , because your client's money is on the line,
that I have never, as a design criteria, allowed the user at each cubical to decide "where" to put the backup.
I have always, as a design criteria, defined a secure repository for the "saveDATA" backup.
Therefore, you will not find a "picker" or "subdir select" option.

The CTB is FOSS, and you can try your hand at it.
As a passing thought, the Best place would be right before the "TarOpt" code.
The TarOpt process flips the "/root" reference from system level to local level,
and the process needs to be traced (some of my tracing to pin this down is still in the code).
If a new "TargetFileName" is injected at that point (from your "picker" routine) then Tar will not know the difference.
So,"TargetFileName" will be a variable, contents supplied by either original code or by "picker", just a line or so before "TarOpt" .

I am not on my 'last legs', just in need of attending to other things,
like my long distance bicycle adventures.
I would go back to college, but check my credentials on my website,
and then you will understand that I have been there before.

In past decades, I have written several commercial programs of nearly 900,000 lines each, requiring a year or more,
on "live" systems, and they all "worked OK first time". Great!

Personally, analyzing/resolving software allowed me to express and examine the way my mind works
... and I was surrounding that personal effort with the required work for my money.
In that matter, I have been very fortunate to find work which allowed me that kind of opportunity.

So, you wrote "Oh! No! What happened? Is the project finished?"
Ha! "All Good Things" have a limit.
Other talented individuals can pursue the issues further, in this "Free Open Source Software" system.

I think I see the CTB as a good, running program, lots of modularity and documentation,
and staying within certain Design Criteria (which I believe should be considered "stable") .
CTB could be a good tutorial for younger software engineers to study.

I am just moving "on" to other things
( check my website , or ResearchGate.Net) , have done many things, published long papers.
I am not moving "out" ! He has not called me yet.

If you are able to post/reply to any of my posts, then present your ideas.
Rockedge, see you around.

Humor-Squirel-playing-chess.jpg (9.17 KiB) Viewed 1626 times

===

[rockedge]

@glene77is Ahh I know already the routine. I just wanted to say thanks.

My son is a young Computer Engineer in Germany. I've mentioned many of these projects to him.

Good friend of mine went to Veterinarian school at the University of Tennessee in the early 1980's. Back then they offered a Trimester program that had to be ended because it was impossible but he made it. Doctor in 3 years. Is now a leading expert in animal orthopedics as we both hit 60 years old now.

I drove with my Dad in 1968 from San Diego California to Stratford Connecticut in a 1964 VW bus. We had that car since 1966 when my Uncle bought it in Germany and had shipped over to Los Angeles and sold it in 1986 to a young surfer from Bridgeport CT for $180. Many many many miles on that Bully.

My friends as kids used to be impressed that my dad could drive 100 only thing is the speedometer was scaled in Kilometers so 100 was really 60 mph

Definitely see you around! Maybe biking one day traveling the less beaten trail.

[glene77is]

to RockEdge, ( 220412 )
You wrote, "Glad to report Cold-Tar_Backup worked well backing up a 49 GiB Fossapup64 save folder."
CTB should work well, since the backup/Compression is handled by "TAR"
the everlasting Unix Tape Backup program.
I have seen others make use of newer compression routines,
and it made me think ... the newer, tighter routines MIGHT NOT be shipped out with a newer Distro of Puppy
... and then what ?
"TAR" has been around since "Year One" , along with "ZIP" ... for good reason.
...

Linus

Peanuts_Linus_Blue-Blanket_.jpeg (9.32 KiB) Viewed 1547 times

I like "backups"
... remember the Peanuts cartoon ?
... remember Linus' blue blanket ?
Backups make me feel "secure".
....................................................

[rockedge]

On the many Puppy Linux variants and the KLV's and WeeDog's I run, 98% of them have a save folder or /upper_changes directory that are no more than 2 GiB. I have versions that run NO save whatsoever.

The 3 really big systems are used to build ZoneMinder and dev code. This includes local repos. This also includes the many weight files that are results of training object detection/recognition using miles of JPEG and PNG files to train Deep Learning Neural Networks what it is looking at and what it is.

I am not that concerned about the size on these three systems which also run WINE installations and some Windows programs that I use add to the size. One of them has 6 or more browsers built in for web sites and web application testing. Usually there are gigs of caches that get caught up.

In the end though, the 30 Gig Bionic64 save file is not any larger because of any different memory management of the 64 bit OS and is also at a point, disposable and will again leave plenty of room upon deletion

[glene77is]

to RockEdge, (220413)
Thanks for the description of your system.
Video surveillance with many jpg and mpg ,
and Wine and Windows compatibility issues can be a really large endeavor.

Very big and serious application.
Obviously much talent and time have been invested therein !

I appreciate your response.
Makes good sense.
Makes me think outside of my 'box' .
...

Peanuts_Linus_Blue-Blanket_coffee_mug.jpeg (8.31 KiB) Viewed 1245 times

[glene77is]

to rockedge,

Looks like the project was not finished.
When it washed up on he shore of my mind ,
Then I decided to simplify, and move into v.5.12 with Embedded Graphics !
The yellow 'jug' and green 'jug' and the 'exit' graphic are written literally in the source code,
so I was not dependent on the current system (of 21 Puppy OS on this computer)
to have the graphics available. "MGR" has two dozen embedded graphics from which to select.

Main Screen

CTX.sh-main-screen-230205-0900.jpg (42.18 KiB) Viewed 673 times