Problem using Wine in fossapup64-9.5

[packwood]

I have used Wine successfully in earlier versions of Puppy. Now it seems all the menu entries have been removed. Apparently the procedure is to run wine from the Terminal for a Windows executable.

I installed Wine from the Quickpet menu, and the 32-bit compatibility package. There did not appear to be any errors.

So I tried to run my selected Windows program, which happens to be 32-bit from terminal by I get the following errors.

Code: Select all

root# wine setup.exe
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /usr/lib64/wine/ntdll.dll.so: file too short
0009:err:environ:run_wineboot failed to start wineboot c00000e5
0009:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting
0009:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\root\\my-documents\\setup.exe" failed, status c0000005

It seems some re-writing of Wine has caused some issues of what used to work flawlessly.

Advice please.

Thanks.

[mikewalsh]

Hallo, @packwood :- (back?) to the kennels....

O-kay. So; you're running this the traditional way, using the 32-bit compat libs SFS. Did you remember to run

Code: Select all

ldconfig

.....from the terminal immediately after loading the SFS, and before you did anything else at all?

Also, installing WINE from quickpet well & truly chucks a spanner in the works. This is 64-bit WINE, which doesn't work at all the same as normal WINE; in fact, I've never used it myself, and I don't know many others who have been successful with it. I'm honestly not sure why Phil B. used one of these WINE64 packages when assembling the repository for Fossapup64.

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

How invested are you in this Fossapup install? Would it hurt to re-install, and start from scratch?

The reason I ask is because we now have access to some WINE AppImages, which simplify this whole business to such an extent it's ridiculous. Or, there are of course the portable versions of WINE.

AFAIK, the WINE Menu Entries have all been bundled up into a separate .pet that you install afterwards. Application Menu entries, however, have always been a case of DIY....

There ARE "options" to be had, y'know?

Mike.

[wizard]

@packwood

wine-portable-3.3_v2.1 works in Fossapup64 on my computers.

wizard

[mikeslr]

As MikeWalsh wrote, you've installed a 64-bit version of wine. As Wizard wrote, wine-portable-3.3_v2.1 works under Fossapup64.
Open Menu>Setup>Puppy Package Manager, then click the Uninstall Button at the top left. Uninstall Wine64.
You can find Wine-portable 3.3_v2.1 packaged as a 'tar.gz' here, https://www.forum.puppylinux.com/viewto ... p=279#p279, together with instructions on what to do with tar.gz. After unpacking the tar.gz, you'll find within a folder named wine-portable. You can place it anywhere EXCEPT within 'Puppy Space'. It belongs on a drive/partition, preferably the same one on which your SaveFile/Folder is located because that partition is automatically mounted on boot-up.

You will need to have the 32-bit compatibility SFS loaded. You can download that using Quickpet. And as MikeWalsh posted, you have to run the ldconfig command, in this case before registering Wine-portable.

If you prefer an installed version of wine, read the instructions of and following this post, https://www.forum.puppylinux.com/viewto ... 776#p63776.

Portable wine comes with its own menus, one in particular is handy --Menu>System>Wine Program Loader-- as it will launch any Installed program. If you use an installed Wine version, you'll want the menu pet you can download from here, viewtopic.php?p=33063&sid=e0b4312601db7 ... 4b5#p33063

[packwood]

Thanks, for these helpful suggestions. The big picture was I was using a version 5 of Puppy and thought it was time I moved up. I have a Windows 11 system but there are a couple of Windows 32-bit programs that I still want to use but refuse to run on Win11 (Oh dear, you say!)

So my requirement was to get Wine running on a more recent version of Puppy and put the whole thing on a USB.

Quite happy to start over, as not much has been invested so far and setting up Puppy the first time really does not take long. Really looking for the best workable Wine solution on Puppy.

Thanks.

[mikewalsh]

@packwood :-

Using the WINE AppImage is really, really easy. You'd want to put this at /mnt/home.....alongside the save-file/folder and Puppy SFSs. It's quite big; you don't really want it in your save.

Then, you create three sym-links into /usr/bin. We can talk you through that.

Once you've configured WINE, it wouldn't be a bad idea to also move the /root/.wine 'prefix' out of root. Again, it can get quite large (here, it's actually .wine32; another sym-link is needed for ease of use). Again, we can talk you through this.

You also don't get a large directory full of 'fake' .dlls at /usr/lib32; these are all contained within the AppImage, so is kept externally anyway.

A few years ago, I put together a script for moving the bulk of WINE to an external location. I may have a look at it, see if I can modify it to work with the AppImage. That way, all you would need to do would be to 'install' the AppImage in /mnt/home, then run the script. Might make things a bit easier for you...it's summat I've been meaning to look at for a while anyway.

Interested?

Mike.

[packwood]

@mikewalsh I think I am going to try the Wine portable option first as it seems less intrusive and maybe an easier to upgrade later(?)

[mikewalsh]

@packwood :-

@mikewalsh I think I am going to try the Wine portable option first as it seems less intrusive and maybe an easier to upgrade later(?)

That's entirely your decision. There's several approaches to WINE, and probably more for us in Puppyland than most get. Whichever way you want to do this, we'll try & get you up-and-running in as pain-free a manner as possible. OK?

There's a few of us who use this stuff on quite a regular basis, so you'll get assistance from more than one direction; t'other Mike and I, especially, have invested quite a bit of time & energy into smoothing out WINE's quirks over this last several years.....and trying to make it as "user-friendly" for Puppians as possible. Others have done the "grunt" work of building WINE itself; we try to make things easier to use.

Mike & I have attempted "upgrading" portable-WINE, and it's not quite as easy as it at first appears. It's a bit beyond both our 'paygrades', if I'm honest, and I think Mike would agree with that. In many cases, however, you don't always gain from using the newest version of WINE.....with Wine it's often a case of one step forwards, two-steps backwards, though in all fairness, the WINE team do a fantastic job; over time, the thing IS steadily improving.

WINE's now up to series 7.....but t'other Mike & I - for instance - both prefer the 3-series WINEs for a lot of things.

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

(You won't see much of me again till around tomorrow midday. It's the time zone thing; there's different members around at different times of the day & night, all depending on where in the world they live. Same as ANY forum, TBH.)

Mike.

[mikeslr]

@mikewalsh I think I am going to try the Wine portable option first as it seems less intrusive and maybe an easier to upgrade later(?)

I've been using Wine-portable 3.3 since 2018 when I cobbled it together using version2013's wine3.3 pet and the portable format structure Shinobar and the Japanese team developed. https://oldforum.puppylinux.com/viewtop ... 45#p989245 back in 2014 https://oldforum.puppylinux.com/viewtop ... 97#p755297. Wine-portable 3.3 has run under every Puppy and AFAIK enable starting every Windows 32-bit program since its publication.

Like you I have --albeit only-- one Windows program which I can no longer run under Windows, itself. It dates from 1998. It runs fine under Wine-portable 3.3.

I've also use Wine AppImages --linked to from here, https://www.forum.puppylinux.com/viewto ... 634#p13634. That thread provides a discussion some details about how to deploy it and a comparison with using portable-wine. Once deployed --and the AppImage's folders are relocted--both methods are easy to set up a 2nd time if you add a 2nd Puppy to your managerie or change your Puppy.

But as to upgrading Wine, itself, that's a horse of a different color.

AFAICT, a Wine AppImage doesn't upgrade. You'll have to find a new version, download it and start from scratch.

Wine-portable is just that, a portable. Anything you install into it's 'false drive_c' will be available if you move or copy it because such installations write to wine-portable's version of Window's registry which move/is copied as well. But AFAIK there's no way to upgrade it. With a new version (when there is one) you have the same situation as having windows on 2 computers. You have to install programs to both.
Portable windows programs are, well, portable. They can be run under any Windows OS and, usually, wine.

I'm not sure you can use Wine (any version) to run a program you installed in Window. Theoretically, you could file browse to it's executable and try to start it. But if its installation involved writing to Windows registry, it will likely need those instructions and they're not part of wine's registry. You'd have to install a such a program into Wine, just as you would have to install it into a new Windows computer.

My recollection is that registering wine-portable will write the files needed for Linux to recognize 'exe' as a file-type to be run under wine-portable, i.e. open the program under wine by Left-Clicking the programs exe. If it doesn't let us know and we'll walk you thru creating that association. It not hard; just not obvious.

I have to run. But there are posts (somewhere ) about how to create menu entries for wine programs not in Wine-portable's drive_c.

Edit: Back for a little while. The post I was looking for were on the old Forum which has been archived. Unfortunately, the process truncated it so it's no longer useful. Hopefully, the link from this post will answer questions you may have about creating Menu access to programs running under Wine. https://www.forum.puppylinux.com/viewto ... 695#p64695

[amethyst]

I'm not sure you can use Wine (any version) to run a program you installed in Window. Theoretically, you could file browse to it's executable and try to start it. But if its installation involved writing to Windows registry, it will likely need those instructions and they're not part of wine's registry. You'd have to install a such a program into Wine, just as you would have to install it into a new Windows computer.

This will depend upon the program but almost all the Windows programs I use were pre-installed with Windows and I just copied over their program folders. They all run in Wine and almost all of them do not show any files in Wine (well, I suppose there may be some entries in the actual Windows registry). Also, if the program has its configuration file in its program folder, it's likely that it will run like a portable application OOTB. Most programs you can configure to save things to a destination of your choice (like backups) so again that specific program will likely run like a portable application. Also - in the past, I've installed some Windows programs using Wine but doing it in a pristine environment (running in RAM for example). In most cases the installation program will give you choice where to install. Again, in these cases the installed programs will mostly run like portable applications from their installed program folders. I have 25 Windows programs I run with Wine (all pre-installed) and only 4 of them insists on creating files under the Wine file structure. I've symlinked those entries to their program folders.

[mouldy]

And dont forget playonlinux. If you can install playonlinux (a front end for WINE), it then can install any version WINE when its almost impossible any other way, meeting dependencies, etc. But it has its quirks too. Nothing concerning WINE is a given. Also if you are having problems, check on the winehq website. Can find hints and workarounds for various windows software. The version of WINE used can matter. For example I need 32bit WINE 6 or newer to run latest Kindle4PC. It just wont run in older versions. So if some program you want, wont run in older version, that doesnt mean it might not work in later version. Usually though you can look on the winehq website and get a clue if there is much chance a particular software will run and what it needs. If there any workarounds, etc.

[packwood]

@mikeslr I have been having a go with Portable Wine today. Downloaded 3.3_v2.1 from http://www.mediafire.com/?mso58025te7mz. I extracted the contents to its own folder on the USB. So now I have a directory wine-portable-3.3_v2 which contains the app wine-portable-3.3_v.2. Now the help file suggests that I should click the executable (app) and a GUI opens, indeed it does.

Screenshot.png (19.87 KiB) Viewed 1877 times

Then "Just click 'OK' to create the wine environment." I was then expecting "After a while, the winecfg GUI opens. Choose the Windows version to simulate. Click 'OK'." But nothing seems to happen.

What am I doing wrong?

[mikewalsh]

@packwood :-

Bearing in mind that I don't use the 'portable' version that much - usually in older, 32-bit Puppies.......its original, intended environment - I believe that even for this WINE package type, in a 64-bit Puppy you still need to install the 32-bit_compat_libs SFS first.

Have you done this? These are 32-bit versions of WINE, so need a 32-bit environment in which to run.

You can find Fossa's 32-bit compatibility SFS here:-

http://distro.ibiblio.org/puppylinux/pe ... ossa64.sfs

Download it. Place it in /mnt/home, then click on it to load it. After it's loaded, this next step is the important bit; you must do this before attempting anything else at all.

Open a terminal, and type in

Code: Select all

ldconfig

.....which is all one word. (That's a small 'L', not a 1'.) Now hit 'Enter'......and wait until the '#' prompt comes back up again. During this short interval, Puppy is setting up a ton of sym-links & other stuff, to give a 'multi-arch' environment. This is needed in order for any 32-bit application to run in a 64-bit Puppy.

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

You should now be able to proceed with installing stuff to WINE. You MAY have to delete the portable & re-extract it again, so it's once more 'pristine'. After configuration - during which time you should get prompts for installing 'Mono' and 'Gecko'; allow these to install - you can then right-click on the 'portable', and select 'Control Panel'. From here, you can choose to install apps, etc. Remember; since this is now within a Windows environment, double-clicks are the order of the day..!

(Normally, I think Fossapup's QuickPet automates all this.....but of course, that installs the wrong kind of WINE. We don't WANT 64-bit WINE....)

Let us know what happens, please.

Mike.

[packwood]

@mikewalsh Great help, that's got my Wine portable working and my Windows executable runs fine apart from I'm missing some standard fonts like "Times New Roman". Googling suggests this can be fixed in Winetricks but I cannot find where it is in the portable version of Wine.

Thanks.

[mikeslr]

Running wine-portable: to open winetricks open a terminal and type --without the quotes-- "wine.sh winetricks".

wine.sh will always be the command to directly start an application under wine-portable [as opposed to any other implementation of wine, where the command is simply 'wine' or IIRC using a Wine.AppImage 'wine32' for 32-bit programs].

Portable-wine locates fonts in .../wine-data/drive_c/windows/Fonts. Any '.ttf' file you drop into that folder will be available to windows programs running under wine-portable. You can flinch ttf fonts from wherever a Windows OS keeps them (I don't recall), download them from the web, or copy them from the folder in /usr/share/fonsts/default.

You can download the Time New Roman ttf font from here, https://fontsnetwork.com/times-new-roman-font/

At one time there was a nice GUI/front-end for winetricks. But it depended on IIRC zenity which apparently was too difficult to maintain. So winetrick now displays a GUI like this:

winetrick's GUI.png (29.92 KiB) Viewed 1853 times

https://howtoforge.com/tutorial/how-to-use-winetricks gives some idea about how to put it to use.

I thought the command you'd want was:

wine.sh winetricks corefonts

But that didn't work. Says cabextract is missing. Frankly, I'm not sure I fully understand how to use winetricks. So, for me at least, the alternate manual approach is just easier.

[mikewalsh]

Simple fix for that, Mike.

Zenity was YAD's ancestor. AFAIK, it still works as intended if you merely create a sym-link from /usr/bin/yad. Open a terminal in /usr/bin. Delete zenity if it exists, then:-

Code: Select all

ln -s ./yad[space]./zenity

Sorted.

Mike.

[packwood]

@mikewalsh

Fixed the font issue manually as suggested by @mikeslr

I ran Winetricks but whenever I tried an option in the GUI the GUI crashed and if fell back to the terminal which then terminated after after 28 seconds. So I followed the instructions to delete zenity and create a sym-link from yad.

However, Winetricks still crashes :

Code: Select all

wine.sh winetricks
wine.sh:ver.20140315
wine.sh:/usr/bin/wine.sh winetricks
wine.sh:PREFIXORG=/mnt/home/wine/wine-portable-3.3_v2.1/wine-portable-3.3_v.2.1/wine-data
wine.sh:WINEPREFIX=/mnt/home/wine/wine-portable-3.3_v2.1/wine-portable-3.3_v.2.1/wine-data
wine.sh:ver.20140315
wine.sh:/mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs/usr/bin/wine.sh winetricks
wine.sh:PREFIXORG=/mnt/home/wine/wine-portable-3.3_v2.1/wine-portable-3.3_v.2.1/wine-data
wine.sh:WINEPREFIX=/mnt/home/wine/wine-portable-3.3_v2.1/wine-portable-3.3_v.2.1/wine-data
wine.sh:/mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs/usr/sbin/winetricks
------------------------------------------------------
Running Wine/winetricks as root is highly discouraged. See https://wiki.winehq.org/FAQ#Should_I_run_Wine_as_root.3F
------------------------------------------------------
Using winetricks 20180217-next - sha256sum: a05e185b4e21a7aab1bd1a66fe20ac4295bdf44cf85a955a4bc1e4cfb86dbf77 with wine-3.3 and WINEARCH=win32
------------------------------------------------------
You are running winetricks-20180217-next, latest upstream is winetricks-20220411!
------------------------------------------------------
------------------------------------------------------
You should update using your distribution's package manager, --self-update, or manually.
------------------------------------------------------

(zenity:32652): Gtk-WARNING **: 19:47:46.020: Error loading icon from file 'yad':
	Couldn’t recognize the image file format for file “yad”
Unknown arg TRUE
Usage: /mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs/usr/sbin/winetricks [options] [command|verb|path-to-verb] ...
Executes given verbs.  Each verb installs an application or changes a setting.

Options:
    --force           Don't check whether packages were already installed
    --gui             Show gui diagnostics even when driven by commandline
    --isolate         Install each app or game in its own bottle (WINEPREFIX)
    --self-update     Update this application to the last version
    --update-rollback Rollback the last self update
-k, --keep_isos       Cache isos (allows later installation without disc)
    --no-clean        Don't delete temp directories (useful during debugging)
-q, --unattended      Don't ask any questions, just install automatically
-r, --ddrescue        Retry hard when caching scratched discs
    --showbroken      Even show verbs that are currently broken in wine
-t  --torify          Run downloads under torify, if available
    --verify          Run (automated) GUI tests for verbs, if available
-v, --verbose         Echo all commands as they are executed
-h, --help            Display this message and exit
-V, --version         Display version and exit

Commands:
list                  list categories
list-all              list all categories and their verbs
apps list             list verbs in category 'applications'
benchmarks list       list verbs in category 'benchmarks'
dlls list             list verbs in category 'dlls'
games list            list verbs in category 'games'
settings list         list verbs in category 'settings'
list-cached           list cached-and-ready-to-install verbs
list-download         list verbs which download automatically
list-manual-download  list verbs which download with some help from the user
list-installed        list already-installed verbs
prefix=foobar         select WINEPREFIX=/root/.local/share/wineprefixes/foobar
wine.sh:28 seconds
umount-FULL: /mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs: target is busy.
umount-FULL: /mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs: target is busy.
umount-FULL: /mnt/+mnt+home+wine+wine-portable-3.3_v2.1+wine-portable-3.3_v.2.1+wine-3.3_v.2.1_7.0.8.6.sfs: target is busy.

[mouldy]

Oh rainy morning and I got to playing with Debian Dog Bookworm. Didnt want to download bunch software so for kicks still had that appimage of WINE5. I cant remember where I got it, but was from a link here on forum. It works great AND INCLUDES THE 32bit LIBRARIES in the appimage! Just wont do current version Kindle. but if whatever you are running doesnt need latest greatest WINE, this is one to try for sure. You know how to use appimages, you have WINE5 without installing anything. Now there are limits to just about anything, it would have to be fairly current version linux. As good as it is, I downloaded an appimage of WINE7 and it flat out sucked. No 32bit library and I couldnt get it to work at all. These are unofficial versions, no official winehq approved appimage. So depends how good the creator of the appimage was.

[mikewalsh]

@packwood :-

Manual installation is so often the best way to do things in Puppy. Remember, Puppy IS, after all, first & foremost a "hobbyist" distro. She positively begs to be tinkered with..!

The sheer amount of modifications I've made in my own highly-customized Puppies would curl your hair. Most of these are, however, NOT arch-specific, so in many cases I've built them up into .pets so's I can quickly & easily "install" them to every occupant of the kennels. In some cases, this includes .pets connecting to Puppy from external partitions, so these consist mostly of sym-links.....

Veteran users of traditional, mainstream 'full' installs turn their noses up at 'our Pup'. To many, she's nowt better than a toy, or 'curiosity' at best. As far as I'm concerned, they can keep their mainstream installs, along with their 'sudo apt-get install' and all the rest of that terminal shit. I came to Puppy to get away from all that crap.

Truth to tell, I can honestly say that I've had more fun this last 8 years or so with Pup than in the whole of the previous 35..!

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

To close, you may be interested in this site:-

PortableApps.com

Many of these Windows portable apps will often run better under WINE in Puppy than regular installs.....and the beauty of them is that they DON'T write their entries to the main WINE Windoze registry. Every single one contains its own, portable, 'mini-registry', thus keeping them entirely separate. You don't install them. You just unpack them, and put them anywhere you like OUTSIDE the /root/.wine directory.....then run 'em from the included .exe file.

Mike.

[packwood]

@mikewalsh

Were you able to advise on the GUI/zenity issue and the crashing of Winetricks?

I know portableapps.com well and use a bunch of them in a folder on a Windows laptop for convenience and the lack of install issues. Now I must try them in Wine.

[mikewalsh]

@packwood :-

Winetricks, no; it's not something I can really help with, I'm sorry to say. I tried it a couple of times nearly a decade ago during my first few Linux months with Ubuntu. It didn't work very well then, and I kinda gave up on the idea of bothering with it any more.

At that time, I was trying to get away from years of Windows GUIs, etc; I needed a challenge, and kinda relished all this technical stuff. Since then, as I age disgracefully (!!), I tend to try and keep things as simple as I can, running portable stuff wherever possible; if I need a .dll, or whatever, I'll hunt it down on the web and manually install it to the correct location by hand.

Fortunately, it's not something I need to do very often....though I do prefer, whenever possible, to fix things myself. I enjoy researching stuff, and like to be able to say, at the end of the day......."It's all my own work".

Mike.

[mikeslr]

Hi again packwood,

If there's a particular program you're interested in which you can't get to run, open a specific thread about it and maybe someone can figure out how.

Winetricks is actually a script, https://raw.githubusercontent.com/Winet ... winetricks, which means a language. Languages require memorizing words and syntax and I have the memory of a sieve. Like a precocious 6 year old, I solve problems through visualization in 4 dimensions. It's a hot day in December when figuring out why a script doesn't do what it's supposed admits to that problem solving technique.

But, having looked at the script --and recalling that yesterday trying to install corefonts using winetricks generated a 'cabextract missing' notice-- this early section of the script may provide a clue.

"# Uses the following non-POSIX system tools:
# - wine is used to execute Win32 apps except on Cygwin.
# - ar, cabextract, unrar, unzip, and 7z are needed by some verbs.
# - aria2c, wget, curl, or fetch is needed for downloading.
# - fuseiso, archivemount (Linux), or hdiutil (macOS) is used to mount .iso images.
# - perl is used for displaying download progress for wget when using zenity
# - pkexec, sudo, or kdesu (gksu/gksudo/kdesudo are deprecated upstream but also still supported)
# are used to mount .iso images if the user cached them with -k option.
# - sha256sum, sha256, or shasum (OSX 10.5 does not support these, 10.6+ is required)
# - torify is used with option "--torify" if sites are blocked in single countries.
# - xdg-open (if present) or open (for OS X) is used to open download pages
# for the user when downloads cannot be fully automated.
# - xz is used by some verbs to decompress tar archives.
# - zenity is needed by the GUI, though it can limp along somewhat with kdialog/xmessage.
#
# On Ubuntu, the following line can be used to install all the prerequisites:
# sudo apt install aria2 binutils cabextract fuseiso p7zip-full policykit-1 tor unrar unzip wine xdg-utils xz-utils zenity

I've highlighted the dependencies I thought most important. I don't think all those programs are built-into wine/wine-portable.

Perhaps the following course could be taken.
1. Backup your Wine-portable folder as this experiment may break it. To back-up a folder, Right-Click it and select 'Duplicate' from the pop-up menu. Give the duplicate a different name. [By the way, I always truncate the folder's name to just 'wine-portable' as that makes it easier to write menu entries which specify the 'full path to an executable'].
If you break the version in use, to use the backup you must first either (a) Setup>Puppy Package Manager>Uninstall>wine-portable-1.0; then register the portable you will be using; or (b) rename the version you will be using so that it will have the name 'registered': deleting or renaming the now broken version'.
2. Serially use winetricks to install the highlighted programs.

[mikewalsh]

@mikeslr :-

That kinda makes sense, now I think about it, Mike.

As you may or may not recall, I have a copy of Photoshop CS2, which I grabbed back in early 2015 when Adobe finally shut the CS2 activation servers down. For about 4 months, you could download every one of the programs in the CS2 suite - Photoshop, InDesign, Lightroom, etc, etc - totally free of charge. They even provided the activation keys (ostensibly for anyone who'd previously registered a copy, and had lost their 'resources'). There was a lot of chatter across the whole tech community about this at the time, so I thought, "Why not?".....and availed myself of the whole suite.

Subsequent testing of the entire suite revealed that, under the state of WINE as it was at that point in time, some of the apps would run, where others wouldn't. Photoshop and InDesign ran virtually OOTB, so I hung onto those two.

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

I followed a tutorial that Jack Wallen over at TechRepublic had posted about the best way for Linux users to get this running under WINE. It wanted zenity, of course - seemingly a standard requirement for many Adobe apps at the time - one or two items I now can't remember......and 'cabextract', which is used by Windows for opening what are known as 'cabinet' files. Seems this is a Windows 'special', effectively a 'tarball' which contains multiple different files specifically for application configuration, but which not only unpacks them but also simultaneously installs them, too.

They might just as well have packed them in the normal way and called them .exe files. But that's Microsoft for ya, always moving the goalposts and finding new & different ways of doing the same thing specifically to lock you in to the Redmond juggernaut. Naturally enough, the 'cabinet' format is copyrighted to Microsoft, so nobody else can freely use it.......and it can only be packed with M$-exclusive tools anyway.

We can unpack & use them, but we can't create them.

For anyone who might be interested, you can find the entire listing of date-specific packages for 'cabextract' at the Ubuntu 'old-releases' site, here. Doesn't matter what the Puppy's age is, you can find a package that would have been current at the time that particular Puppy was built. This ensures that it will work properly with all of that Puppy's dependencies:-

http://old-releases.ubuntu.com/ubuntu/p ... abextract/

For any of the more modern 'buntu-based Pups, you should be able to install direct through the PPM.

Mike.

[packwood]

Hi again packwood,

If there's a particular program you're interested in which you can't get to run, open a specific thread about it and maybe someone can figure out how.

Winetricks is actually a script, https://raw.githubusercontent.com/Winet ... winetricks, which means a language. Languages require memorizing words and syntax and I have the memory of a sieve. Like a precocious 6 year old, I solve problems through visualization in 4 dimensions. It's a hot day in December when figuring out why a script doesn't do what it's supposed admits to that problem solving technique.

I've decided I am going to stay clear of Winetricks and just install fonts manually as required.

Thanks.