http://bugs.winehq.org/show_bug.cgi?id=4937
Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|wininet |shdocvw
--- Comment #5 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2008-08-07 17:50:12 ---
looks more like a bug in shdocvw (and oleaut32) now
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=4937
--- Comment #4 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2008-08-07 17:49:09 ---
Created an attachment (id=15340)
--> (http://bugs.winehq.org/attachment.cgi?id=15340)
fine graphics with native oleaut32
In current git it starts now fine for me using native shdocvw and oleaut32.
Without builtin shdocvw it just returns to the console after a certain time,
with native shdocvw the main window starts fine, but is all black. Needed
native oleaut32 to get the app functional, see screenshot. Didn't test really
much further
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3077
--- Comment #10 from Ryan May <rmay(a)ou.edu> 2008-08-07 16:37:11 ---
Still present for me on stock Wine 1.1.0 (latest on Gentoo), using the latest
version of Weatherscope (1.6.1). If there's reason to believe this would be
fixed by 1.1.2, I can try to get that installed. Or I can update when a more
recent version is available.
Available at:
http://sdg.mesonet.org/builds/final/win/WeatherScope/WeatherScope-1.6.1.exe
Also, when running, don't forget to use full path, or it will crash. This is
technically a bug in Weatherscope, as it will crash on Windows without the full
path as well. It isn't really noticable on windows since using a link runs with
full path.
Run it using:
wine c:\\Program\ Files\\Weathersoft\\Weatherscope.exe
for the default install options.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6340
Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #13879|application/octet-stream |text/plain
mime type| |
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14699
Summary: DLL loading prolem when injecting into another
process
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hongbo(a)njstar.com
I have observed a DLL loading prolem when injecting into another process.
For example,
In folder C:\DirA\, I have A.exe which is linked to B.dll, and B.dll is linked
to C.dll.
B.dll and C.dll are in same folder as A.exe.
If I run A.exe, B.dll and C.dll will be loaded without problem since they are
in same folder.
Support there is a process running C:\DirX\X.exe, and C:\DirX\ is not the
current folder and
it's not on PATH.
Now I inject B.dll from A.exe into process X.exe, the System will map
C:\DirA\B.dll into process X.exe.
Since B.dll is linked to C.dll, the system will try to load C.dll for process
X.exe. But because C.dll is not in same folder of process X.exe, wine failed to
load C.dll for X.exe. This cause DLL injection to fail.
Wine rror message:
err:module:import_dll Libary C.dll (which is needed by L"C:\\DirA\\B.dll) not
found.
Windows does not have this problem. So I am trying to find a solution.
I think when processing the imports for C:\DirA\B.dll to load C.dll, it should
try C:\DirA\C.dll first,
then form the standard load locations.
I think it should call load_library( "C:\DirA\C.dll ",
LOAD_WITH_ALTERED_SEARCH_PATH)
so C.dll can be loaded into C:\DirX\X.exe process.
I may also look into import_dll where the error occured.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8922
--- Comment #6 from Jaime Rave <jaimerave(a)gmail.com> 2008-08-06 18:47:54 ---
I'm still having this problem in Wine 1.1.2
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3332
--- Comment #13 from Igor Tarasov <tarasov.igor(a)gmail.com> 2008-08-06 16:48:19 ---
Yes, this patch works perfectly! Thank you!
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6936
--- Comment #48 from Wine? Gimme Beer! <furex.furetto+wine(a)gmail.com> 2008-08-06 16:41:51 ---
Guess it depends on your definition of "a lot" :) Fast or slow makes no
difference, at least in my case.
Try putting several big files (e.g. Linux CD images) and leaving it running for
a couple days, you should stumble on it sooner or later. When it starts doing
it, it won't stop anyway, unless it crashes first. Usually I'm not downloading
files with more than some dozens of sources, that might make a difference or
not.
@ Anton, native not necessarily better = a badly written application does not
magically turn into a good one just because it's native. A well-written native
application is expected to offer /some/ advantages over an equivalent
non-native app but - depending on the metric used, the non-native app can still
be better than the good, native one (e.g. set of features)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3332
Lei Zhang <thestig(a)google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #15314|0 |1
is obsolete| |
--- Comment #12 from Lei Zhang <thestig(a)google.com> 2008-08-06 16:04:49 ---
Created an attachment (id=15321)
--> (http://bugs.winehq.org/attachment.cgi?id=15321)
second patch attempt
Thanks for testing it out. This updated patch should fix the space issue.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.