“wine program.exe” in terminal = fail

[tankmanbrad]

I searched the forums for the following and found no reference to them so this should be a valid query unless someone out there doesnt like me again, lol. Seems a short list of reasons why but Im not sure how to fix them.

After using the mandatory “wine program.exe” in terminal while running an M1/silicon/arm64 mac mini (I DID start this in the Mac OS forum) OS 12.7.5
It is Wine ver. 9.0 assembled by homebrew as per instructions on WINEhq install page. Also followed with uninstall and re install in case it was a case of not knowing if older version of WINE was already installed on this machine.

Im no codey. I searched the Library/application support/ folder for the following that appear to be problematic

ShellExecuteEx
FTSER2K
winedevice.exe
syswow64

winedevice is there, in case explorer is really a prob it is also in there. The rest are not.

Anyway.
I got this reply under the command attempt if ppl need greater detail:

extssdbrad@Exts-Mac-mini ~ % wine program.exe
0048:err:environ:init_peb starting L"C:\\windows\\syswow64\\winedevice.exe" in experimental wow64 mode
0054:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\FTSER2K": c0000142
003c:fixme:service:scmdatabase_autostart_services Auto-start service L"FTSER2K" failed to start: 1114
009c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
009c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
009c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
009c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00a4:fixmeNtUserActivateKeyboardLayout Changing user locale is not supported
00bc:fixmeNtUserActivateKeyboardLayout Changing user locale is not supported
00a4:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY2" display settings returned -2.
00a4:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY2".
Application could not be started, or no application associated with the specifie
d file.
ShellExecuteEx failed: File not found.

I see some ancient posts where the answer is that brew sent a 32bit package? if its command originated from this machine I thought it sends the right one, it has for other 64bit brews/casks I did since then.

Would using Macports help get it done better, or a command that the WINEhq page doesnt show?

[setimes]

ShellExecuteEx is a function in the nt kernel, FTSER2K is a driver, and syswow64 is in the wine prefix, which is why you won't find them in /Library/Application Support/.

Could you be more specific about what "program.exe" exactly is? Is it 32-bit or 64-bit? You mentioned using wine 9.0 so stable would be assumed, but have you tried wine-staging?

[tankmanbrad]

oh dear G
whatta newbie thing on my part. I see how I got confused here...

This is what Im becoming familiar with in Terminal use:

"brew install FORMULA|CASK..."
for an example of how to brew an install of an app and then a series of staggered variables to refine the caps part

so i would have expected
wine [PROGRAM}

... as a command to start up an .exe installed via brew already
not the exe: wine program.exe thing

Im going to guess this is probably installed then and try the terminology similar to the brew command suggestion, not copy/paste the part wine suggests after its 'exe.:' header

delete this whole thread if someone wants