you might need to use 'start' to run from a .lnk file, like: wine start "path\to\whatever.lnk" alternatively you can use a unix path with the /unix option: wine start /unix /home/MyName/.local/blah/blah/blah.lnk i think this behavior changed at some point, which caused problems for people ...

(my mistake, the change also adds the brackets at the end, regardless i assume this is working now)

are you doing all this manually? afaik it's (highly) recommended to use winetricks to install the various .net versions, and preferably in a fresh WINEPREFIX. (up to version 4.8 anyway, i don't know about anything later)

i'm not sure about the first part, but i think it's come up before that the wine desktop closes automatically when all programs in it have closed. it's inconvenient but i think opening notepad or something and minimizing it should be a workaround (before you go looking further and modifying the sour...

if nothing else, your second log indicates wine is failing to open anything; the path should probably be in quotes. if you haven't yet you'll probably want to make a backup of (at least) that wineprefix before going further, just in case. (and if you have a backup already don't overwrite it until th...

i'm not 100% sure but it looks like a fix for this was committed recently: https://gitlab.winehq.org/wine/wine/-/commit/354ddcb382f7dffe515fa72a961b5910839b60dc you can try that patch or just removing the "* const" from those six lines manually, or update wine in git if you're using it, or...

well that's certainly odd. unfortunately all i really have is a wild guess that this is some virtual server setup that is causing some unusual problems. which probably isn't much help even if that's the case. you could try getting more verbose output by setting WINEDEBUG but it may be failing before...

it seems that wine overrides that setting for actual drives mounted by the operating system, and i'm not aware of a way to prevent this (short of modifying dlls/kernelbase/volume.c and building wine locally, perhaps) though it should i think be possible to work around by making a drive in winecfg on...

it's possible this is the issue described in the FAQ here: 10.3.3 preloader: Warning: failed to reserve range... first thing to try would be what's suggested there, beyond that more details would help. like this is typically a problem with very old programs that expect some DOS stuff to still be aro...

for anyone wondering or finding this the fix for the issue in winetricks was apparently committed on Dec 15 (...and some further fixes since)

at a guess it may be a graphics problem or those earlier messages may indicate other problems, you are able to run native linux programs with this graphics setup i assume? either way you can get more verbose debug output by setting WINEDEBUG for example: # WINEDEBUG=warn+all winecfg to start with an...

wine will typically output messages to the terminal like that and those can be ignored unless something goes wrong, then they may be helpful with debugging wineboot shouldn't do anything noticeable other than that and possibly a popup dialog or two about installing gecko and mono, so you should be a...

first thing to check would be that you have the 32-bit (i386) package for libodbc installed

if that's not it i'd ask if you're following instructions from somewhere, getting database stuff working can be a pain and it could help to know what it is you've tried so far

i vaguely recall people having similar issues, never did myself but i did find this that has some possible info: https://forum.winehq.org/viewtopic.php?t=32854 in short it seems a 32-bit process may be limited to (slightly less than) 2 gb address space (to be clear, is this a 32-bit program, and are...

hm. unfortunately the one comment there may be right, if the program is attempting to access the card directly by the hardware device rather than through the filesystem it is unlikely to work it's hard to know from just a quick look though. it is checking drives from what i can see; it's a long shot...

in general wine will map any mounted disks to a drive letter when wine starts if there's already a filesystem on it and you have it mounted under /media/ or somewhere you can run winecfg to see if it's there and change the drive letter or possibly other things, or try to add it manually if it's not ...

afaik on ubuntu, like debian, X11 Forwarding is disabled by default so you'll have to enable it yourself if you haven't (it's recommended this be done per host) there is information on this in /usr/share/doc/openssh-client/README.Debian.gz as well as the ssh man page and probably elsewhere in nicer ...

Thank you! Check GetEnvironmentVariable('PROCESSOR_ARCHITEW6432')='AMD64' works fine! One more question - can program get Wine prefix name that is used to run it? I mean if program is located in prefix2 and run by prefix1 (i.e. WINEPREFIX=~\.prefix1 wine home/user/prefix2/drive_c/program) to check ...

It appears that the archives for the mailing lists stopped updating early Tuesday Oct 18. I first noticed this for wine-bugs and checking the others haven't had any more recent posts either. I did check that for wine-bugs there are in fact new bugs that haven't shown up on the archive. (It's possibl...

I know linux has 'taskset' for tying a process to one or more processors, on a typical system anyway. No idea how that interacts with VMs on 400 processors. Seems to me there should be some way to do that one way or another. It's also possible wine wasn't designed with such a system in mind. Seems l...

I *think* this is wineconsole. (of course there's always ways to figure out details about a running process, too.)

yeah, apparently it's intentional: https://bugs.winehq.org/show_bug.cgi?id=50866

an admin(?) explains there that they have fail2ban configured to issue a 24 hour IP ban if you attempt a request that results in a 403 FORBIDDEN

Another option is to use the Linux Steam client and enable Proton which will use wine* to run Windows games that don't have a Linux port.


* a bundled and modified version of wine so don't expect support at winehq

Yeah, I got the same thing when I tried current wine; I don't know how it works for jkfloris. wine staging still works though.

There's a space missing, should be "Program Files (x86)".