Using Winetricks to tell your wine64 to run a 32 bit package

[Grey]

how to tell it to use the 32 bit instead of wanting to go right for the 64

You have both versions at your disposal. Let's look at the example of the Wine build from Kron4ek. Versions 3-8 can be found there.
There are two files there (in Fossapup):

wine_folder.gif (16.69 KiB) Viewed 795 times

Next, you need to read the manual, sections 3.5.3 and 3.5.4 (& maybe 3.5.2): https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH

In Russian (with obscene language and shouting ) I could explain everything to you pretty quickly But in this case, it is better to read the manual.

[Lordsyke]

how to tell it to use the 32 bit instead of wanting to go right for the 64

You have both versions at your disposal. Let's look at the example of the Wine build from Kron4ek. Versions 3-8 can be found there.
There are two files there (in Fossapup):
wine_folder.gif

Next, you need to read the manual, sections 3.5.3 and 3.5.4 (& maybe 3.5.2): https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH

In Russian (with obscene language and shouting ) I could explain everything to you pretty quickly But in this case, it is better to read the manual.

So I need to reverse engineer some kinda of code to put into my terminal, to tell my Fossapup to switch on the 32 arch ONLY every time Firestorm viewer is on? Someone told me to just get VanillaDPup but I'm still not 100% sure this will fix my problem, but the thing is I do AI Generated art or am getting into this and I need to install the Automatic, and nobody knows what codes to use for Fossa, I bet Pip and whatever else is needed is already in Vanilla, Or it knows how to install or "get" these packages. So if VanillaDPup can do this or do this much easier and install the Automatic thingy I would like to just upgrade the Kernel to that! and for only 100mb more it shouldn't make any difference in speed with my 16gb ddr3 and should boot of the ram perfectly. and also I wish to if doing this set up a dual boot menu for Batocera.linux, Unless you think it's better to just have an alt desktop with certain things switched off for retro emulation functions and what not.

[Grey]

So I need

As one big fan of retro games and emulation to another, I can only advise one thing.
Try 99 options and the hundredth will work

[mikeslr]

Lordsyke, the problem you encounter with firestorm-viewer is that it is primarily a 64-bit application but requires 32-bit libraries to provide (some) sound functions. To be fully functional you need an operating system which is Multi-Arch: that is capable of running both 64-bit and 32-bit applications, contains the necessary libraries for both, or --if not already present-- will install those libraries in the locations where the application expects them to be and the operating system allows them to be used. Fossapup64's work-around use of a 32-bit compatibility SFS does not meet those requirements.

"I would like to just upgrade the Kernel". The kernel is just one component of an operating system, an important component. I think of it as the 'engine and chassis' of LInux. It both powers the system and is the platform upon which applications are built. With Puppys kernels are somewhat interchangeable. Even if you could* swap the kernel used by VanillaDpup into Fossapup64 that would not make Fossapup64 a Multi-arch system. VanillaDpup's Multi-Arch capabilities are provided by other components of VanillaDpup's system: I think the contents of puppy_vanilladpup_xxx.sfs.

"I do AI Generated art or am getting into this and I need to install the Automatic, and nobody knows what codes to use for Fossa, I bet Pip and whatever else is needed is already in Vanilla, Or it knows how to install or "get" these packages." Very likely. VanillaDpup much more closely adheres to debian Linux than other Puppys which only used some debian Linux components. And unlike Fossapup64, VanillaDpup's package managers --apt and synaptic-- are the native debian packages managers. To find out how to install or configure applications the documentation relating to debian can be used (doesn't have to be translated to Puppy). And google searches for 'how to' and 'problems' with 'debian' included with the other search terms will be particularly productive.

Still, VanillaDpup is not a 'cut-down' version of debian. It does have some Puppy components. dimkr has 'locked' out the installation of some files to prevent the system 'as a whole' from breaking. Accordingly, I suggest two things:

(1) While setting up your system --installing the applications you want-- operate under PupMode 13. Ask how if you need instructions. Under PupMode13 files are NOT immediately and automatically installed into your SaveFolder. Rather they are held in a special location in RAM until you execute a Save. But you can still test the effect of what will happen by their installation: whether they provide a functioning application, if not why not, and whether they will break some other application. After 'installing' --but before you Save-- you can Menu>Exit>Restart-x (AKA Graphical Server). That causes Puppys to re-catalog what then constitutes its entire system. Under PupMode 13 anything 'installed' but not Saved will be deleted on shutdown/reboot returning you to your system before such 'install'.
(2) Take careful note of what's taking place during an install noting any failures or problems. Don't hesitate to ask for advice if there are any.
-=-=-=-=-
* After the publication of Fossapup64-9.5 debian and Ubuntu implemented a structure change regarding where files can be located. It's known as the 'user-merge' Rule. Kernels complying with the 'user-merge' rule can not be swap with those which don't; and vice-versa.

[Lordsyke]

One question about VanillaDPup before I make the jump to this, how close in speed is this to tge FossaPup64?

[Lordsyke]

Yeah so if I change to VanillaDPup will I lose any speed at all when loading from the ram?

[bigpup]

Actually it may be a little faster.

[dimkr]

After 'installing' --but before you Save-- you can Menu>Exit>Restart-x (AKA Graphical Server). That causes Puppys to re-catalog what then constitutes its entire system.

No need to, the menu is updated automatically when you install or remove applications. (fixmenusd is a daemon that triggers fixmenus when .desktop files are added, removed or modified)

And Vanilla Dpup should be much faster than Fossapup unless your computer doesn't have enough RAM so Puppy can't run from RAM. It includes various optimizations for low CPU and RAM consumption (some come at the cost of bigger size), fast boot time, PipeWire and drivers for GPU acceleration that are not included in 'official' Puppy releases.

[mikeslr]

"No need to, the menu is updated automatically when you install or remove applications. (fixmenusd is a daemon that triggers fixmenus when .desktop files are added, removed or modified)".
True for VanillaDpup and when what you install is an application containing a desktop file. The procedure I suggested is worth remembering for other Puppys and when exploring the installation of other things. I use it all the time so that I don't have to remember when and when not to.

[Lordsyke]

Okay, so here's what I'm going to do, I'm going to back up any important files to my SSHD drive, and change the kernel to Vanilla, I'm going to read through that guys instructions again on some text or code file that I think someone else said is in this day and age highly useless.