http://bugs.winehq.com/show_bug.cgi?id=1361
------- Additional Comments From mike(a)theoretic.com 2003-04-09 04:32 -------
Note the "," mark between +wave and +dsound - not very intuitive I know.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1361>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1376
------- Additional Comments From mike(a)theoretic.com 2003-04-09 04:21 -------
Do you have stdole32.tlb? Try installing DCOM98, that may help
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1376>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1375
------- Additional Comments From mike(a)theoretic.com 2003-04-09 04:20 -------
Hi, what mime type is the test program? I get application/executable, but your
description says source code?
If you could provide a compiled binary of the program as well that'd be useful.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1375>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1361
------- Additional Comments From gregsurbey(a)hotmail.com 2003-04-08 22:06 -------
I built the wine CVS on 04/07/2003 and did the following:
[gsurbey@02f2847 Half-Life]$ pwd
/usr/share/wine-c/Program Files/Half-Life
[gsurbey@02f2847 Half-Life]$ wine --debugmsg +wave +dsound hl.exe >& trace
[gsurbey@02f2847 Half-Life]$ cat trace
wine: cannot find '+dsound'
I don't know why it can't find dsound... so I tried
wine --debugmsg +wave hl.exe >& trace
and I've included the output in the attached file, but I'm not sure if this
output will help you since there's no dsound loaded...
then I did a "make uninstall" of the cvs tree and did a "./tools/wineinstall"
for wine-20010510 and got the same exact dsound not found message. BUT sound in
wine-20010510 works fine in half-life and starcraft. The "HardwareAcceleration"
= "Emulation" option in my ~/.wine/config changed nothing, probablly since the
dsound isn't being loaded to begin with.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1361>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1376
Summary: InstallShield 6 hangs after Wizard setup.
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: klevin(a)eskimo.com
While trying to install an app that uses InstallShield 6 (Watchtower Library
2001), the installation process hangs after the "Wizard setup" window closes.
The following message appear on the console:
fixme:seh:check_resource_write Broken app is writing to the resource data,
enabling work-around
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})
))))cannot set text "InstallShield Wizard" of other process window (nil)
fixme:ole:_copy_arg argument was coerced in-place (0x3 -> 0xb); source data has
been modified!!!
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{00000000-0000-0000-0000-000000000000})
fixme:ole:_xread Read only 0 of 4 bytes from 0x48.
fixme:ole:_StubReaderThread Failed with hres 80004005
This appears on a build done from an uptodate cvs checkout (April 8 2003). The
install was being done to a fake-windows directory tree.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1376>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1375
------- Additional Comments From felipewd(a)elipse.com.br 2003-04-08 16:22 -------
Created an attachment (id=450)
Text to try and paste it in the "About 1" program.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1375>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1375
------- Additional Comments From felipewd(a)elipse.com.br 2003-04-08 16:20 -------
Created an attachment (id=449)
.tar.gz that contains the "About 1" source code (example program)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1375>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1375
Summary: Pasting a large text on a dialog doesn't have any effect
Product: Wine
Version: 20030115
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: felipewd(a)elipse.com.br
Please see the attached source file coded by Cesar Mello (mello(a)elipse.com.br)
and the attached text file.
Trying to paste (Ctrl+V) the context the text file on the "About 1" about
dialog doesn't have any effects.
This looks critical, because the user isn't able to paste big stuff on a
dialog, preventing important programs to work correctly (like our script editor,
for example).
Does anyone have an idea about this?
Felipe
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1375>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1374
Summary: Worllcraft/hammer 3D view not visible
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: dan(a)malin.co.uk
In Valve worlcraft/hammer v3.4, The 3D camera view is a blank window, the
graphics either isnt renedered or is not visible.
The following messgae appears in the console when a file is opened:
err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 0x3008e!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1374>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1373
Summary: ODBC connection failure
Product: Wine
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.com
ReportedBy: tim.ruehsen(a)openmediasystem.de
With wine-20030317 (got it as rpm and srpm from SuSE) the calls to MFC
DBase.Open(...) fails while it is working fine with SuSE wine-20020812 (rpm).
I am using unixODBC 2.2.2 with mySQL 3.23.52 drivers.
The application source is under control of my collegue and written with VC++/MFC.
We made lots of tests, but did not get these lines working (with the newer wine
version):
CDatabase DBase;
char buf[128];
try {
// This fails and a DB exception is thrown
sprintf(buf,"ODBC;DSN=%.100s",DefaultConnect);
DBase.Open(NULL,FALSE,FALSE,_T(buf),FALSE);
}
e->m_strError gives something like (from german) 'Failed to connect to host'.
As strace shows, there is a connection, some data exchange and after that a
connection shutdown.
After removing wine-20030317 and re-installion of wine-20020812 everything works
well (again).
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1373>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.