https://bugs.winehq.org/show_bug.cgi?id=47643
Bug ID: 47643 Summary: Windows Registry no longer supporting Path Key Product: Wine Version: 4.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: shagooserver@gmail.com Distribution: ---
Certainly, 1 year ago modifying HKEY_CURRENT_USER>Environment by adding a Path key caused Wine to follow that path when looking for a exe file. It appears this is no longer the case as the exact same modification to the Windows registry results in a file not found message.
https://bugs.winehq.org/show_bug.cgi?id=47643
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Still works for me. Although you don't add a 'Key', you add a string value. Need more information, what exactly are you doing?
https://bugs.winehq.org/show_bug.cgi?id=47643
--- Comment #2 from Scott shagooserver@gmail.com --- I think this is splitting hairs unnecessarily and I believe your assertion is incorrect, if I understand the situation correctly the PATH container is a (sub) key which contains a string value "whatever it is". A bit like folders and files.
Anyway, to the crux of your question. I am using wine to run a Windows non GUI program, in this particular case the program is eac3to. I have a basic launcher script that opens a CLI window in the Wine prefix with a Z: prompt. The path directs Wine to look in the folder where the exe file is located, which is what paths do except in this case it is not.
I hope this is sufficient though I would be happy to provide any further information you might require.
https://bugs.winehq.org/show_bug.cgi?id=47643
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- It's a string value under the Environment key. If you made it a subkey it's not going to work. Please show us the exact contents of your Environment key (you can export it with regedit).
https://bugs.winehq.org/show_bug.cgi?id=47643
--- Comment #4 from Scott shagooserver@gmail.com --- Created attachment 65098 --> https://bugs.winehq.org/attachment.cgi?id=65098 Copy of windows registry
https://bugs.winehq.org/show_bug.cgi?id=47643
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Thanks. Now please show the exact command you are running, the exact error you get, and the exact path to the file you are trying to run.
https://bugs.winehq.org/show_bug.cgi?id=47643
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47643
--- Comment #6 from Scott shagooserver@gmail.com --- OK, shoot me. I do not know how or why, as I have done absolutely nothing, but it now works as expected, or in other words correctly. The path command does work. My apologies for wasting everybody's time.
For the vengeful types please take heart in the fact that I feel like a complete fucking idiot who stands about 3mm tall...
https://bugs.winehq.org/show_bug.cgi?id=47643
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- No worries, I'm glad it works now.
https://bugs.winehq.org/show_bug.cgi?id=47643
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Ken Sharp imwellcushtymelike@gmail.com --- Closing bugs marked as invalid.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla