need thacrips help with linux

[cryofreeze666]

1) used sudo apt install playonlinux

2) searched all tabs for wine 4.0.4, nothing, even typed in search window, nothing.  ended up using snap to download (using ubuntu)

3) found imgburn and it's being difficult. it has me browsing files, but install is obviously not the correct file. tried every folder in the install file with exact same error that wine crashed.

 

i really don't want to reload 7 or 10 just so i can image burn another debian based o.s.  i also don't want to turn a thumb drive into a hard drive, cause i'm still trying to figure out what o.s. i like best.  so far ubuntu is ok, but it seems to have a foul temperment when it comes to loading gaming platforms.   

[ThaCrip]

Sorry, I have not been active on here in a little while as I just noticed your post here on Oct 24th 2024, so I am over 3 weeks late.

but I am personally using Wine v6.0.1 (32-bit) for my ImgBurn setup currently and I have no issues on Mint 21.2-Xfce, which is based on Ubuntu 22.04 LTS. my two other computers are using Mint 22.0-Xfce which is based on Ubuntu 24.04 LTS and ImgBurn starts up on those okay to.

but once you got PlayOnLinux installed, you install the Wine you want from PlayOnLinux's "Tools > Manage Wine versions" screen. the one I am using would be listed on 'Wine versions (x86)' tab and on the left hand side you scroll down and select whatever Wine version you want to use and then highlight it and then in the center area will be a ">" click it and it should download and install.

NOTE: I generally avoid Snap or Flatpak stuff (in fact, Snap is disabled by default on Mint but Flatpak is possible to use). what I am using is the standard software installs.

p.s. I also play some games on Linux through Lutris using the current GE 8-26 (from Feb 2024) runner or even the newer 'UMU-Proton9.0-3.2' (from Oct 15th 2024). I even played around with 'Heroic Games Launcher' a bit and that works to. on Lutris I installed it with a standard ".deb" file where as Heroic Games Launcher I used the '.AppImage' file.

[ThaCrip]

On 10/1/2024 at 6:28 PM, cryofreeze666 said:

i really don't want to reload 7 or 10 just so i can image burn another debian based o.s.

I suggest using Ventoy (i.e. ventoy.net or https://github.com/ventoy/Ventoy/releases ; currently you would download "ventoy-1.0.99-linux.tar.gz" for use on Linux) as with that you can create a multi-boot USB stick that still functions like a regular USB stick but also can boot ISO's directly. because once Ventoy is setup on it, you just copy your Linux/Windows ISO's to the root of the USB stick (basically just copy the ISO file to the USB stick from file manager). then to boot to it, you boot to a USB stick like usual, select the ISO from the Ventoy menu and then proceed to use/install Windows or Linux like you normally would.

p.s. for those who don't like Windows 11, you have the option to stick with Windows 10 past the Oct 2025 end-of-support date 'if' you use the 'IoT Enterprise LTSC 2021' version of Windows 10 (it's basically '21H2' where as standard Win10 is '22H2' but it's pretty much the same) which is supported until Jan 2032 etc. I am using that version of Windows 10 in a virtual machine on my main Linux PC and as a bonus it does not have the junk in it like the regular version does like no Microsoft Store and the start menu is nice and clean. also, it's possible to use a updated version of Windows 7, which will have security updates to October 2024 ('Simplix' which is about a 800MB file), but I heard the ones that came in October 2024 are the very last ones from Microsoft (but for the general average person Jan 2020 was the end-of-support date for Windows 7 but it was still possible to get updates afterwards through other means), so it's probably not worth using Windows 7 at this point short of very limited use situations. but Firefox ESR is still officially supported on Windows 7 until March 2025 I think as that was extended not long ago. but I did use that (Simplix) to create a updated ISO to August 2024 not long ago as the official Win7 SP1 64-bit ISO was 3.1GB but after updating that with the newest updates along with bundling DirectX/dotNET/VisualC++ stuff with it, the ISO was now 4.5GB which is what I used to install Win7 on a old computer I have for potential use of old games/software that does not work on newer Windows etc and that computer cannot run any Windows newer than Windows 7 and on that old computer gaming is not a option because the driver Linux supports on it is too old for modern standards so for gaming, Win7 is the only option on that backup computer of mine (my main PC I can play my games on Linux through Lutris and no obvious issues). but on that same PC I have Linux Mint 22.0-Xfce installed on it for general usage and ImgBurn works fine on that (although to get PlayOnLinux to start up on Mint 22 I had to install a additional thing (i.e. "apt install python3-pyasyncore") for it to start up. but since you are using a different distro it's possible you might not need to do that for PlayOnLinux to start since in your screenshot it's working as on Mint 22 the main PlayOnLinux interface simply refuses to start up until I issued that from terminal. I upgraded from Mint 21 to 22 and even from a clean install a while ago it still reacts the same way).

 

On 10/1/2024 at 6:28 PM, cryofreeze666 said:

3) found imgburn and it's being difficult. it has me browsing files, but install is obviously not the correct file. tried every folder in the install file with exact same error that wine crashed.

I use the "SetupImgBurn_2.5.8.0.exe" directly already on hard drive. I typically do my stuff from that PlayOnLinux's 'Configure' icon as it allows a bit more manual control over things vs trying it from the 'Install' option on the main PlayOnLinux screen. but I would imagine the 'Install' will be okay to but I never use it personally.

also, the system installed Wine should work if you prefer to use that I suspect. I just prefer PlayOnLinux since it keeps a separate Wine prefix solely for ImgBurn use (which is stored in a different location..."~/.PlayOnLinux/wineprefix/" my ImgBurn wine prefix (v6.0.1 (32-bit)) here is 4xxMB in size). but if you use the system installed Wine (which stores it's default prefix at "~/.wine") you will have to tweak it so the "ImgBurn.exe" is specifically designed to run in Windows XP mode as that's critical as Wine has defaulted to Windows 7 for a while (like on Wine v8.x and a fair amount before this) and in recent memory (I think on the current Wine v9.x series) now defaults to Windows 10 and ImgBurn will hang/not-work if you don't have Wine set to WindowsXP mode for the ImgBurn.exe specifically. this way you could leave the default wine prefix to it's usual Windows 10 mode but for ImgBurn specifically it would use Windows XP. but if I recall correctly each time you ran a program that uses default it would probably be always re-writing data to that when switching etc which is why I suggest just creating one solely for use with ImgBurn as then you don't have to worry about that stuff since it will stay completely separate and less likely to act up if you have multiple programs running from default "~/.wine" location.

optionally... if you want, you can install the latest Wine from official Wine website (i.e. https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu ; follow the instructions for your specific Ubuntu version!) as I got mine installed but I don't even currently have a prefix created with it (since it wastes 1-2GB of storage space and I prefer to have separate stuff for most of my programs etc) as I am currently using the 'development' version which the newest is currently v9.20 as this gets updated roughly once a month where as the current 'stable' version would be v9.0. generally for the average person I would probably stick with the 'stable' which seems about one major release every year, usually around January. this will generally be newer than if you stick to the stuff in the Ubuntu repositories.

so bottom line... I would suggest sticking with PlayOnLinux for ImgBurn since it stays separate from any potential system installed Wine stuff.

p.s. if i recall correctly... say you got the more standard system installed Wine installed, once PlayOnLinux is installed, if you try to remove the system installed Wine etc, I think this will screw up PlayOnLinux. I don't remember the precise detail off the top of my head but I am pretty sure it's something along these lines. but if this happens it's still fixable as that's partially why I have not bothered to mess with my system installed Wine much even though I pretty much don't use it as PlayOnLinux uses it's own stuff and so does Lutris etc.