http://bugs.winehq.org/show_bug.cgi?id=7763
Summary: Loader does not set working directory to the directory
program is installed in when app is executed with
BINFMT_MISC
Product: Wine
Version: unspecified
Platform: Other
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: wine-loader
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Speeddymon(a)gmail.com
Easy to reproduce if you have a registration code for WinRAR..
Download an eval copy of WinRAR and install it.
Insert your registration code in WinRAR to make it registered.
Make sure BINFMT_MISC is setup properly so you can run WinRAR by running
./WinRAR.exe
Make a symlink to ~/.wine/drive_c/Program\ Files\WinRAR\WinRAR.exe under your
/usr/bin
CD to the WinRAR directory and type the name of your symlink to WinRAR.exe on
the command line. It will open and be registered.
Exit WinRAR
CD to any other directory (~ is where I went to test)
On the command line type the name of your symlink to WinRAR.exe
It will come up and show evlauation copy even though the key has been inserted!
To get around this for now I just made a shell script in /usr/bin instead of a
symlink, that does CD and then runs winrar.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7760
thestig(a)google.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |download
------- Additional Comments From thestig(a)google.com 2007-16-03 10:56 -------
Can you describe the strange behavior? Do you know what the proper behavior on
Windows is?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7761
thestig(a)google.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |download, Installer
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7712
------- Additional Comments From mikolaj.zalewski(a)gmail.com 2007-16-03 10:53 -------
Could you find in the logs if it registers the class "WeatherScopeAlert" with
RegisterClass[Ex]W or RegisterClass[Ex]A? If it registers the class with
RegisterClassW and then calls DefWindowProcA so that would explain why
WINPROC_CallProcAtoW was called.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7712
------- Additional Comments From rmay(a)ou.edu 2007-16-03 10:49 -------
I should probably add that CallWindowProcA _is_ indeed called by
SendMessageTimoutA, but when it looks up the procedure for the function, it
fails to find an A version, so it resorts to calling the W using
WINPROC_CallProcAtoW.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7712
------- Additional Comments From rmay(a)ou.edu 2007-16-03 10:34 -------
Thinking about this more and looking at traces, this seems odd to me (though I'm
welcome to be told I'm wrong). Here's the call pattern:
CreateWindowExA
SendMessageA
WINPROC_CallProcAtoW *******
DefWindowProcA
DEFWND_SetTextA
Why would a cross-call (A-to-W) be needed when it in the end calls more SetTextA?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1266
------- Additional Comments From pmcnett(a)pm-sc.com 2007-16-03 10:32 -------
I believe this and bug 1265 still persist, but that the patch at some point
stopped working, although the fix is still the same (IIRC adding a
MsgWaitForMultipleObjectsEx() call).
To be honest I stopped using WINE a couple years ago (because I replaced my need
for Visual FoxPro with open source development environments), so while I'm glad
these bugs are getting some attention, I regret I can't be of much help anymore.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7762
Summary: Error using FileCreateShortcut cmd in AutoHotkey script
Product: Wine
Version: 0.9.31.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mike.clarkson(a)baesystems.com
Can anyone help me with how to create a windows shortcut in wine? I
want to create windows shortcuts on a Linux box that windows clients
can then access. I'm trying to use wine to allow me to create the
shortcut on the Linux box. I'm using the wine-0.9.31 version of wine
on Fedora Core 5. I've tried two approaches, both fail.
I've tried using an autohotkey script. This script runs in wine and
creates a shortcut, but the shortcut has no target, and wine returns
the below fixme error. This script works fine on a windows box.
Here is the script:
#NoEnv ; Recommended for performance and compatibility with future
AutoHotkey releases.
SendMode Input ; Recommended for new scripts due to its superior
speed and reliability.
; %1% (argument #1) - shortcut target (include the full absolute
path)
; %2% (argument #2) - name of the shortcut, include the .lnk
extension
; check to make sure that the correct # of parameters were passed
in
if %0% < 2
{
MsgBox This script requires 2 parameters but received %0%.
ExitApp
}
FileCreateShortcut, %1%, %2%
Here is the error:
Z:\home\mike>"C:\Program Files\AutoHotkey\AutoHotkey.exe"
create_shortcut.ahk "Z:\home\mike\test.txt" "shortcut_test.txt.lnk"
Z:\home\mike>fixme:system:SystemParametersInfoW Unimplemented
action: 8192 (SPI_GETFOREGROUNDLOCKTIMEOUT)
My other approach was to use VBScript to create a shortcut. See
Bugzilla Bug 7659 on http://bugs.winehq.org/
If there are other methods for creating a shortcut that work in wine,
please let me know.
Thanks for any help
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.