Xenialpup CE 7.5 / 25 Nov 2017

[Ledster]

Sorry I've been a bit slow coming back on this - been doing some experimenting.
Briefly:-
1st
started xenial without the save file. Tried cups - no problems.
2nd
added devx. Tried cups - no problems.
3rd
I have and like a program called Pysol which needs python-tk for which I have pet, so installed that. Tried cups - FAILED!
4th
Started again with 1st as above
5th
as 2nd above
6th
installed python-tk-2.7.11.2 and its deps from ppm. Cups still OK! and Pysol is good.

Looks like it could be a python version problem. The pet works fine in Tahrpup - all versions.

So problem solved - my fault all the time!

@bigpup
probably not relevant, but the printer is a Canon Pixma MG7550.

Thanks to everyone for the ideas

Ledster

[bigpup]

Xenialpup 7.5 CE to the 8gb ssd

i put it on a flash stick booted it up. so i formatted the the 8gb ssd ect in GParted.

Formatted it to what format?
Is it only one partition?
If yes.
Did you flag the partition boot?

How did you do the install?
Did you use the Puppy Universal Installer?
Did you do a frugal or full install?

Strongly suggest do a frugal!!

so i tried installing it again with a boot loader and when i select it on the list i still got the same thing.

What boot loader did you install?
How did you do the install?

Strongly recommend using Grub4dos Bootloader config running from the booted USB to install a boot loader.
Select the SDD as the device to install to.
Check search only within this device.
All other default choices are good. Nothing else but:
OK.
OK.
OK.
done.

[april]

it just booted to a black screen with a blinking white line in the top left side

Not finding your drive

[hamoudoudou]

Xenialpup CE 7.5 / 25 Nov 2017 miss wireless, regarding several complaints from people. Firmware easy to install. Why remove wireless to add bluetooth ? One is everyday usage, the other cutting edge
Perhaps Xenialpup is a Puppy indoor, for testing new technologies, much more advanced than Wi-Fi, in our Labradories in USa or Canada...
Laboratories ! If that is true, please confirm, Artfulpup will be a replacement for people needing only to use their laptop for what they bought it.

First SOS, denied ?

[hamoudoudou]

firmware xenialpup 26mb Artfulpup 56mb
My iwlwifi drivers were removed by ?
I you want to remove libs, remove those that are unused. Useless; as 3D
Better, keep xenialpup as you like, we will use Puppy strecth or Xenialdog; and let you quiet, building your Xenialpup for Linux students.

I play Puppy with ethernet in winter, i don't really need wireless. But nowadays an OS witout wireless is simply to trash, excepted for an hundred linux guys who only practice programming as hobby, in a closet.
For logical , remove ethernet is the clever choice, regarding Mbs and functionalities, laptops are a lot more popular than fixed computers (for office tasks mainly societies). Even for industrial usage, laptops are preferred, then data are downloaded in the central system end of day. same for business men. Music player ? at home you have you equipment better quality than from your computer. Jukeboxes are for listening music when traveling, mainly.

[watchdog]

You can use artfulpup's fdrv.sfs in xenialpup: just rename it...

[hamoudoudou]

Renaming zdrive is not enough, kernels are different. Who could think all of 200.000 downloaders can do that ? Do you imagine they are all linux geeks ? half of them are testing Puppy first time and come form windows. They are not windowsians, there are common people having never programmed anything. They will give up. Sure they are millions.
Remove wireless, what an idea ! A laptop then looks like an electric car that you must keep plugged. Sure tires will have a long life. And you can sell your laptop battery.

Musher0 is learning how to create Puppies; His version xenialpup includes wireless and connect to both wlan0 wlan1 (antenna). his zdrive is 31mb sized, that is not a lot if you consider that thousands of downloaders will be able to use their laptops without having to keep stuck to the wall socket to surf the web.

[bigpup]

hamoudoudou,

Xenialpup 7.5 the 32bit version got released with some of the WIFI drivers missing.
This was by mistake.
However, it was not a lot of them. Only a small number of ones for a specific wifi hardware.
This will added them:
http://distro.ibiblio.org/puppylinux/pu ... nial32.pet

You have not stated what your wifi hardware specifically is.

So, what specifically is it?????

[rustypup]

Hello - first of all, well done to whoever is behind Xenialpup 7.5, it's really great - I love it.

I have found one strange thing though - the pmcputemp thing in the system tray looks to be reading the wrong sensor, possibly my graphics card. PSI shows one of the sensors for cpu with "radeon" label next to it?! Not too bothered but still interested to know what's going on with it. (See screenshot).

Otherwise all good. Got my Focusrite Saffire 6 USB 2.0 audio interface running well - audio and MIDI ins and outs both working in Renoise via Jack. I did have to find the .deb for an older version of qjackctl though as the one from the repositories would freeze everything except the mouse pointer.

Also, RedshiftGUI works - it wouldn't work on this PC under Tahr64.

System specs:
CPU - AMD FX-6300
MOBO - ASUS M5A97 LE R2.0
GPU - XFX Radeon HD7770
RAM - 8GB 1866mhz

[snayak]

Dear All,

I tried to install xenial 32 7.5 on my AMD Athlon XP 2000+ machine which is with 512MB RAM. It failed to boot. It hangs at "Recognising media devices... optical input". It is not being "done". Nothing happens after this!

I am using precise 571 on my machine now.
My hope was to able to use newer browsers and other softwares.
Is there a way out with xenial? Any other successor to precise?

Sincerely,
Srinivas Nayak

[mikeslr]

Dear All,

I tried to install xenial 32 7.5 on my AMD Athlon XP 2000+ machine which is with 512MB RAM. It failed to boot. It hangs at "Recognising media devices... optical input". It is not being "done". Nothing happens after this!

I am using precise 571 on my machine now.
My hope was to able to use newer browsers and other softwares.
Is there a way out with xenial? Any other successor to precise?

Sincerely,
Srinivas Nayak

The AMD Athlon XP 2000+ can access (at least) 1 Gb RAM. Recommend a RAM upgrade whatever else you do. http://www.pc-specs.com/cpu/AMD/Athlon_ ... atible_RAM

Add 2 Gbs of Swap. --Won't help xenial to boot, but will help once you get anything to desktop.

Tahrpup was created after Precise and before Xenialpup. I think the recommended minimum RAM is 768, but you can download and test for free.

Any of the Slackos up thru 6.3, but especially 5.7 and X-Slacko 4.4: See for example, http://www.murga-linux.com/puppy/viewto ... 213#727213

Palemoon web-browser by Watchdog, http://murga-linux.com/puppy/viewtopic. ... 676#973676

And try some of the older DebianDogs, for example Mintpup which accesses the Trusty Tahr repos. See this thread: http://www.murga-linux.com/puppy/viewto ... 904#881904

mikesLr

[bigpup]

I tried to install xenial 32 7.5 on my AMD Athlon XP 2000+ machine which is with 512MB RAM. It failed to boot. It hangs at "Recognising media devices... optical input". It is not being "done". Nothing happens after this!

You are trying to boot from what storage device?????
Installed xenialpup how to this device?????
Sure you got a good download of the xenialpup iso?

Usually trying a fresh new download of the iso and a fresh new install on the storage device can maybe fix this issue.

[sindi]

In 2012 someone in Germany found the solution and posted it under 'Recognizing media devices .... optical input
failed'. They removed the script that checks for optical media. Something to do with country setting - it is buggy.
The optical drive still worked.

http://www.murga-linux.com/puppy/viewtopic.php?p=77788

[OscarTalks]

I compiled VLC 2.2.8 from source in Xenial Puppy 7.5 (32bit)
Seems to be working well with no errors in my brief tests.
Users may wish to take the usual precautions and give it a test.
Lua has been added but apart from that it is just built against all the native packages.
For more details read here:-
http://murga-linux.com/puppy/viewtopic.php?t=112798
Package is uploaded here:-
https://yadi.sk/d/nxx9TP2i3HcXB5?force_show=1

[paulh177]

I grabbed xenialpup-7.5-uefi.iso (32bit) from NLUUG today, and installed it on my old AOA150 (Atom powered 1GB) as a FRUGAL install.

A clean install , creating a new xenialpupsave on first shutdown, seems to work fine, if a touch sluggish.

I've been running PRECISE 5,6,1 successfully on this machine for years and have tweaked it + added/upgraded packages a great deal, so obviously my desire is to retain that savefile (4GB 3fs) and simply have Xenial upgrade the savefile and carry on where I left off.

I had to rename the precisesave to xenialpupsave for xenial to recognise it.

PROBLEM:

Upgrade appears to go thru OK until Xenial tries to start X, whereupon (after "Patch mode 38 to resolution 1024x600 is complete" is displayed), the next error message (repeated twice) is:

"VESA BIOS extensions not detected"

and we are dropped back to the console with the usual informational/error message about running xwin (which just forces the same errors) and running xorgwizard (which doesn't run, appearing to be waiting for input)

I remember having similar problems years ago when the first Ubuntu pups were in beta, but I can't remember how it was resolved.

[paulh177]

Ok ... xerrs.log from the above situation:

Code: Select all

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-97-generic i686 Ubuntu
Current Operating System: Linux 172017 4.4.95 #1 SMP Mon Nov 13 17:15:42 GMT 2017 i686
Kernel command line: PDEV=sda1 psubdir=xenial nosmp acpi=force pfix=noram
Build Date: 13 October 2017  01:57:05PM
xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.33.6
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 24 21:58:47 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) module ABI major version (11) doesn't match the server's version (20)
(EE) module ABI major version (11) doesn't match the server's version (20)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Warning: Only changing the first 5 of 12 buttons.
/usr/local/apps/ROX-Filer/ROX-Filer: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /usr/lib/libicuuc.so.55)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
/usr/bin/jwm
jwm: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /usr/lib/libicuuc.so.55)
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

I noted the libstdc++ error and had a poke about in /usr/lib

libstdc++.so.6 was linked to libstdc++.so.6.0.16 but there was also a libstdc++.so.6.0.21 which wasn't linked to anything.

I unlinked so.6.0.16 and linked so.6.0.21 to libstdc++.so.6 instead.

Lo and behold, X started.

Unfortunately, my desktop looked like the attached screenshot, and xerrs.log looks like this (after I ctrl-alt-bkspc'd out)

Code: Select all

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-97-generic i686 Ubuntu
Current Operating System: Linux 172017 4.4.95 #1 SMP Mon Nov 13 17:15:42 GMT 2017 i686
Kernel command line: PDEV=sda1 psubdir=xenial nosmp acpi=force pfix=noram
Build Date: 13 October 2017  01:57:05PM
xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.33.6
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 24 22:15:08 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) module ABI major version (11) doesn't match the server's version (20)
(EE) module ABI major version (11) doesn't match the server's version (20)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Warning: Only changing the first 5 of 12 buttons.

** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-show-details.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-show-hidden.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-select.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-mount.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-mounted.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-symlink.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/rox-xattr.png'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
/usr/bin/jwm
JWM: warning: /root/.jwm/jwmrc-theme[8]: invalid tag in Active: Text
JWM: warning: /root/.jwm/jwmrc-theme[9]: invalid tag in Active: Title
JWM: warning: /root/.jwm/jwmrc-theme[12]: invalid tag in WindowStyle: Inactive
JWM: warning: /root/.jwm/jwmrc-theme[21]: invalid tag in TaskListStyle: ActiveForeground
JWM: warning: /root/.jwm/jwmrc-theme[22]: invalid tag in TaskListStyle: ActiveBackground
JWM: warning: /root/.jwm/jwmrc-theme[40]: invalid tag in PagerStyle: ActiveForeground
JWM: warning: /root/.jwm/jwmrc-theme[41]: invalid tag in PagerStyle: ActiveBackground
JWM: warning: /root/.jwm/jwmrc-theme[55]: invalid tag in MenuStyle: ActiveForeground
JWM: warning: /root/.jwm/jwmrc-theme[56]: invalid tag in MenuStyle: ActiveBackground

** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/dirs.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/images/application.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/ROX-Filer/.DirIcon'

acpi daemon stopped.

** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/share/icons/quickpet.png'

/usr/sbin/delayedrun: line 199: /root/Startup/autostart: is a directory

** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/root/.icons/ROX/MIME/application-x-generic.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/multimedia48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/root/.icons/ROX/MIME/application-x-shellscript.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/pet48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/email48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/spread48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/Connect/.DirIcon'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/date48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/help48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/drive48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/www48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/word48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/edit48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/draw48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/configuration48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/chat48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/lib/X11/pixmaps/paint48.png'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/Xlock/.DirIcon'
** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/Trash/.DirIcon'

/usr/local/apps/Trash/AppInfo.xml:1: parser error : Start tag expected, '<' not found
¼ÛÛEšKºÆ¹ÖÕ	¢dlŸ ½Æé·~ûM‡©ZÛÙ¶C?Ò¸·ž}b™2
^

** (ROX-Filer:13634): WARNING **: Couldn't recognize the image file format for file '/usr/local/apps/PupZip/.DirIcon'

/usr/sbin/delayedrun: line 199: /root/Startup/disabled: is a directory
acpi daemon started.
/sbin/pup_event_frontend_d: .: line 101: can't open '/etc/rc.d/functions4puppy4'
killall: pmcputemp: no process killed
vm.swappiness = 10
-> Red  1.000, Green  1.000, Blue  1.000
<- Red  0.900, Green  0.900, Blue  0.900
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 44 requests (44 known processed) with 0 events remaining.
ROX-Filer: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
retrovol: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
clipit: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
firewallstatus: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 79 requests (79 known processed) with 0 events remaining.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 8284 requests (8284 known processed) with 5 events remaining.
ROX-Filer: Fatal IO error 0 (Success) on X server :0.
/usr/bin/xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

(ROX-Filer:13789): Gtk-WARNING **: cannot open display: :0
(ROX-Filer:13793): Gtk-WARNING **: cannot open display: :0

[paulh177]

I've received a PM from a forum member offering the suggestion that one should not attempt to upgrade even though it is possible to do so.

I disagree, for the reason I bothered to add to the thread in the first place:

I think a series of software releases should allow users to upgrade between releases in a smooth and manageable manner, and indeed Puppy (which I have been using since v2.11, possibly a bit earlier) had always offered a savefile upgrade automatically (without the faff of having to rename a file too).

If it's decided that each release should stand alone and reject the idea of a simple upgrade path between version, then that needs to be explicitly stated by the Community Developers.

There's a debate to be had here, but it's for the Community to have it publicly.

[mikeslr]

Hi All,

Basically what I told paulh177 was "That something could be done doesn't mean it should be done" and "it is far easier to get new versions of applications, created to run under Xenialpup, running under Xenialpup than to try to get older versions of applications created for Precise to run under Xenialpup.

Linux is all about having choices. Call me lazy. I prefer "easy". It is possible to drop a 2017 Ford Engine into a 2002 Ford, and then spend hours making all necessary adjustments to get the two to work together. But the final result isn't likely to work either as well as a 2002 Ford or a 2017 Ford. And my time is valuable --even if I spend it on leisure activities. I might feel otherwise if, as part of my leisure activities, I enjoyed building hot-rods.

Looking at paulh177's initial log revealed several mismatches in 'core' applications -- the foundation of any system. Having solved one (perhaps all) of them he's now confronted by problems in the next level of systems built on top of that core. I don't doubt that those problems can also be overcome. Ultimately, however, the purpose of a computer operating system is to run applications. I have serious doubts whether applications created for Precise will run either as well under Xenialpup as they did under Precise or as well as applications which were created to run under Xenialpup.

But as I've discovered sometimes older applications built when fewer computing resources were the norm run better than either alternative: less demanding than the newer versions but operating in an environment better than the old.

People do build hot-rods. Well, they used to and enjoyed doing so. paulh177 has proposed an interesting area for exploration. I have every reason to believe that he has a far greater understanding of 'the nuts and bolts' than I. So I would encourage anyone who shares a similar interest to help him. It's not a challenge I would find "easy".

Full Disclosure: As paulh177's computer ran well under Precise, I suggested alternative Puppies which might run better on an older computer. Same reason: What's the easy way to obtain a system which matches well the hardware you have.

mikesLr

[Moat]

The problem is - and always has been - that Linux is a constantly moving, evolving target.

From what I've always understood, upgrading point releases within a given base OS (i.e. - Precise 5.6.1 to Precise 5.7.1) is generally safe. But upgrading from one base to another (i.e. - Precise to Trusty Tahr, for example) is not a good idea, and will likely be fraught with issues. A big jump, as in this case, all of the way from Precise to Xenial... even more so.

From what (little!) I understand, the base operating system's libraries upon which a particular release is built are constantly being further developed/updated by devs all over the world - but often with no regard to supporting the function/compatibility of applications which ran fine on older libs - say from an earlier release (i.e. - regressions). With Ubuntu releases, for instance, each "family"/name (i.e. - Precise, Tahr, Artful, Xenial, etc) are likely each based on many quite different versions of underlying libraries - and in order for applications to work properly, they have to be individually modified/re-built/re-compiled against the libraries of the particular release "family" they're aimed at.

That's why an application pulled from Precise's repository quite likely won't run properly on Tahr, or Vivid, or Xenial, or Bionic, or... (and vice-versa) - not to mention the possibility that installing old applications could pull in old/obsolete libs (as dependencies) that conflict with the native, built-in libs of the newer-base OS - breaking other areas/functions of the system (I believe that's why Snaps/Flatpacks/Appimages/etc. are gaining popularity, as they contain all of their own lib versions, using them independently of the base OS's libraries - but they're therefore huge in comparison - by not utilizing those already-in-place components).

The repositories of each release family are not simply copied/pasted from the former release's repo into the new - each application has to be installed and tested in the new release... if any issues surface, they are identified and modified/re-built/re-compiled until they work properly - and only then added to the new release's repository. I think that's how it's done, anyway... lots of testing and fixing!!

Bottom line - just as mikeslr eludes to... it's quite likely many/most older apps (Precise) won't work in Xenial without a lot of work/tail-chasing... even if at all. The Xenial repos and our wonderful forum member's Xenial-specific app builds are the way to go, if the update to Xenial is worth it to you, Paul - or necessary. Unfortunate, but...

At least that's how I understand things... but I'm no Linux guru, either! All just AFAIK, IMHO, YMMV, etc...

Bob

[bigpup]

I've been running PRECISE 5,6,1 successfully on this machine for years and have tweaked it + added/upgraded packages a great deal, so obviously my desire is to retain that savefile (4GB 3fs) and simply have Xenial upgrade the savefile and carry on where I left off.

I had to rename the precisesave to xenialpupsave for xenial to recognise it.

I am sorry you have probably broken your save file.

At no time is it recommended to use a save from one named version or Puppy with a different named version of Puppy.

I repeat, AT NO TIME!!!!!!

Saves are always specific to the named Puppy version they were originally made for.

There is also no way to make a program, compiled to work in a specific named Puppy version, so it will work in every possible version of Puppy.
Some programs will work OK in many different Puppies. Some are very much Puppy version specific.
There is not set way of making a program work on everything.

That is why each named Puppy version has it's own specific repository of programs and pet packages.

If you have any saved data (pictures, forms, videos, etc...) in the save you want to keep. That data is probably OK.
Copy it from the save to a safe place.

You need to delete the save and start over with a fresh one made for Xenialpup.


There is a chance the save will still work with Precise if you name it back to what it was for Precise.