http://bugs.winehq.com/show_bug.cgi?id=1187
------- Additional Comments From winebug(a)flonet.net 2003-28-06 07:48 -------
Bug comments restored from Gmane.org:
Wine 20021125 (latest in debian unstable), no windows install.
Remote administrator 2.1 (www.famatech.com) loads a window with selectable
remote machines. The keyboard works on this menu, however when a remote screen
is opened the keyboard stops working (ie doesn't transmit to remote screen).
This used to work a long time ago, say v20001202. There is a simple work
around: by choosing the menu, then clicking options, about or connection info
the keyboard starts working properly.
Radmin reports errors like these:
fixme:ntdll:RtlNtStatusToDosError no mapping for 403a01d8
fixme:winsock:NtStatusToWSAError Status code 403a01d8 converted to DOS error
code 13d
fixme:ntdll:RtlNtStatusToDosError no mapping for 403a1cf0
fixme:winsock:NtStatusToWSAError Status code 403a1cf0 converted to DOS error
code 13d
fixme:ntdll:RtlNtStatusToDosError no mapping for 403a10b0
fixme:winsock:NtStatusToWSAError Status code 403a10b0 converted to DOS error
code 13d
fixme:ntdll:RtlNtStatusToDosError no mapping for 403a20c0
fixme:winsock:NtStatusToWSAError Status code 403a20c0 converted to DOS error
code 13d
fixme:ntdll:RtlNtStatusToDosError no mapping for 403a01d8
fixme:winsock:NtStatusToWSAError Status code 403a01d8 converted to DOS error
code 13d
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2002-12-12
04:25 -------
> fixme:ntdll:RtlNtStatusToDosError no mapping for 403a10b0
> fixme:winsock:NtStatusToWSAError Status code 403a10b0 converted to DOS error
> code 13d
Winsock issue, fixed in CVS already.
No idea with keyboard issue. Try using --debugmsg
+relay,+key,+keyboard,+message,+event,+x11drv,+winsock
------- Additional Comments From coryp <at> petersen-arne.com 2002-12-12 17:58
-------
That produces a lot of output! 100mb for only about a minute. I opened radmin,
connected to a server, tried to use the keyboard than killed the wine server
because my cpu maxes and wine no longer responds to either mouse or keyboard
with all those debug options. 45mb gzipped error log can be found at:
http://www.petersen-arne.com/~cory/wine_debug1.txt.gz
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1124
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:46 -------
Bug comments restored from Gmane.org:
I'm running Wine 20021007 on a Suse-8.0 machine, and want to startup
Bryce-4.0 (which installed properly inclusive Quicktime and Acroreader)
but which fails with:
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel
(0x426bc1d8)->(00000000,00000008)
fixme:win:OpenDesktopA ("screen-saver",1,0,40): stub
fixme:msvcrt:_XcptFilter (-2147483392,0x406d1f7c)semi-stub
wine: Unhandled exception, starting debugger...
err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134679808
512") (2)
What's there going wrong? Is it maybe only the missed screen saver?
But when, how getting one for a pure wine installation, so wine without
some Windows-whatever-release-wherefrom-stuff?
With greeting from Munich ..
------- Additional Comments From buffer0 <at> t-online.de 2002-11-03 16:41 -------
This sort of "bug/error" and exception was caused by the incomplete
installation of Bryce-4.0 (German release). The 'setup' by the CDROM
distribution hadn't a proper run through (spurious!). Well, when
having installed the [MetaStream],[QuickTime 3] and [Acrobat] folders
explicitely in addition after the setup, one obtained a complete
installation.
However, on my Suse-8.0 box/installation, all things had run through
only to the point where some ALSA problems then occured:
Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-slot-1
Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-service-1-3
Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-slot-2
Nov 4 00:00:05 teflon modprobe: modprobe: Can't locate module sound-service-2-3
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-1
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-1-3
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-2
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-2-3
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-1
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-1-3
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-slot-2
Nov 4 00:00:06 teflon modprobe: modprobe: Can't locate module sound-service-2-3
Nov 4 00:00:06 teflon kernel: ALSA
../../../alsa-kernel/core/seq/oss/seq_oss_init.c:212: no device found
AND that's a different bug and story, I'll assume. So I'lll resolve/close
Bug#1124.
What's the main thing with this bug? Well, wine is VERY sensitive on
principle installation dependancies, and can't tell them to us ...
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:22 -------
The resolution shouldn't be fixed.
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:29 -------
Did the installer say that all necessary components were installed, when they
were not? In that case this should be considered an open bug.
------- Additional Comments From johane <at> lysator.liu.se 2002-11-06 02:30 -------
A clicking-error...
------- Additional Comments From buffer0 <at> t-online.de 2002-11-06 10:53 -------
I'm testing wine and Bryce, with the following results:
[0]: The installer hadn't complained. The sole worse things had been with
installing Quicktime where the window-management made trouble:
The installer GUI put its screen on the screen with topmost
priority, resulting that all other related subwindows aren't
visible for the user.
What helped? Some alt-F4 or so under KDE, or some other hot-key
under Enlightenment which allowed to change the window orders ...
[1]: Some hard thing must be wrong the window management!
Bryce-4.0 runs only proper within the Desktop mode!
When trying to run in fullscreen mode the main-top window
can't be accessed. Seems a worse arrangment problem
with X11 window management schemes.
[2]: wine crashes spuriously; '*click*' error/crash. But wine+Bryce crashes
definitely intermediately when selecting under Bryce-help menu the
about menu-entry.
[3]: An important thing for the wine-config file: "crtdll"= "native, builtin"
is a must. Else Bryce-4.0 doesn't come up with its main screen.
[4]: wine+Bryce didn't had crashed yet on rendering. Meaning: All the window,
menu and whatever I/O stuff seem to influencee much too hard the
non-crashing quality of wine - with Bryce-4.0 - or?
So what? The *click+crash* problems are worse. But how fixing (it fast)?
How jumping into the wine and w$dos machinery??
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1123
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:45 -------
Bug comments restored from Gmane.org:
Discovery proceess:
After install of "wine-20021007.i386.rpm" the root ID cannot run wine. Winesetup
documentation says "be user" for wine run-time. OK, login as user, run "wine
winword". Oops, need full directory string. do that, and when I do that, I get a
nasty error, "Cannot create C:\Windows\Desktop". OK, su - root, and ls -l | grep
Desktop" (in C:/Windows directory) to get permission list of "drwxr-xr-x ...
Desktop". Vain attempt of "chmod 777 Desktop" because windows directory has
insufficient permission structure for this situation.
Workaround:
Realizeing that problem can be circumvented if root can run wine, I "cp -R
/home/user/.wine /root" (created by the user ID earlier, above). Now I execute
"wine winword.exe" (in the C:\Program Files\microsoft office directory, and all
works well.(That is until I try to run spelling check, Seems the file directory
linkages do not work.Cannot find the dll where expected.)
Concerns:
1.User ID cannot ever have permissions needed in win98 file structure!
2.Process for finding windows PATH in wine applications is insufficient for the
task.
3.When looking for a file to open (in winword.exe), I get the directory, but
need to type in the <directory name>\*.doc to move to that directory. Typical
Microsoft double click on directory to change directory tries to open directory
file for editing.
Kudo's:
I also ran a doc file with an jpeg image in it. Winword (97) worked very well.
Wine winword.exe saves files OK too.
Michael F. Winthrop
winthrom <at> hotmail.com
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1122
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:45 -------
Bug comments restored from Gmane.org:
Since "cvs up -D 2002-10-30" the game Neverwinter Nights does not longer accept
keyboard inputs in the main game window (it works e.g. in dialogs).
My settings in the config that might be of interest
DXGrab: NO!
Managed: YES!
Desktop: YES!
A cvs diff shows some changes in the hook management for windows - guess the
problem came with this patch.
BTW: assigned it to wine-user, because parts of the changed for the hooks took
place their.
------- Additional Comments From lazytodd <at> hotmail.com 2002-11-13 13:06 -------
*** This bug has been confirmed by popular vote. ***
------- Additional Comments From tony_lambregts <at> telusplanet.net 2002-11-13
15:54 -------
Could you find the exact patch please?
http://www.winehq.org/Docs/wine-devel/cvs-regression.shtml
------- Additional Comments From frick <at> sc-networks.de 2002-11-19 04:50 -------
I just want to let you knwo, that i am working on it - but i usually can not do
more than 3 compile runs on my box per evening; i think i am close to the patch
- but have not found it yet (still surrender it per hour - binary search works
fine for computers; but not humans, because there is this guy named Murphy :))
------- Additional Comments From tony_lambregts <at> telusplanet.net 2002-11-19
10:27 -------
I have had dealings with Murphy myself. However as your time frame narrows
compile time _should_ go down since there are less changes.
I do regression testing on my 300 mhz machine a fair amount and I have a wine
tree and a regression tree. That way I can go from regression testing to an
up-to-date CVS in a matter of minutes.If you do development as well you could
have a development tree as well.
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2002-11-23 12:51
-------
Patch has been submitted to wine-patches on 20021123 which is supposed to fix this.
------- Additional Comments From frick <at> sc-networks.de 2002-11-25 16:41 -------
Well now i can say it definetly - this is the patch:
http://www.winehq.com/hypermail/wine-cvs/2002/10/0469.html
I did an cvs up yesterday and the bug was _not_ gone - assuming the patch
Andreas mentioned was already in this version i used.
------- Additional Comments From hoffmajs <at> gmx.de 2002-11-27 09:21 -------
Yes that patch was the culprit. Are you sure that the fix for it was in the
cvs update you checked? just look at dlls/dinput/dinput_main.c around line 58
the line should read ..."KeyboardCallback, inst, 0 );" instead of
"KeyboardCallback, 0, 0 );".
If its the latter just change the first zero to "inst" and im sure it will
work :)
------- Additional Comments From frick <at> sc-networks.de 2002-12-01 07:51 -------
I guess i checked out the "current version" before your patch made it to my cvs
host or something like that. In the version i "update"ed the lines you mentioned
where in the source. The annotate shows, that the lines made it in the cvs on
20021024.
Long story short: I tested it some minutes ago and i can confirm, that the
problem is gone! Thanx gentleman!
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2002-12-01 08:36
-------
Closing bug.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1121
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:42 -------
Bug comments restored from Gmane.org:
When attempting to invoke the multiplay capabilities in Heroes of Might and
Magic III, I receive the following error message:
"DirectPlay Error:
'Unknown error?'
File: 'C:\Dev\Heroes 3 Exp 2\Remote.cpp'
Line# 1867"
At this point, the builtin version of dplay was being used. I received the same
error when using the native version. The output of "wine --debugmsg
+dplay,+dplayx,warn+all Heroes3.exe" can be found at
http://yotamr.dyndns.org/winelog. The apparently
relevant excerpt from the log
is: trace:dplay:DPLAYX_LibMain (1117782016,0x00000000,0x1)
trace:dplay:DPLAYX_DestructData DPLAYX dll unloaded - destruct called
trace:dplay:DPLAYX_GetThisLobbyHandles Waiting for DPLAYX semaphore
trace:dplay:DPLAYX_GetThisLobbyHandles Through wait
trace:dplay:DPLAYX_IsAppIdLobbied Translated dwAppID == 0 into 0x0806e1b0
trace:dplay:DPLAYX_GetThisLobbyHandles DPLAYX Semaphore released
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2002-11-02 11:24
-------
DirectPlay is known to be problematic sometimes.
Checking out a --debugmsg +relay,+dplay log might be helpful.
------- Additional Comments From yotamr <at> bezeqint.net 2002-11-02 11:42 -------
I have made the compressed wine log available at
http://yotamr.dyndns.org/winelog-with-relay.gz
The file takes up 80 MiB in its uncompressed form.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1189
------- Additional Comments From winebug(a)flonet.net 2003-28-06 07:42 -------
Bug comments restored from Gmane.org:
When starting either Total Commander (http://www.ghisler.com)
SummaSummarum
(best obtained through me), windows that should be in front, are created
behind the main application window.
Total commander, when unregistered, opens a nag-window where the user must
press a certain key. This window is created as tha frontmost window under MS
Windows, but behind the main application window under wine 20021125 (running
Suse 8.1).
SummaSummarum (accounting software) opens a window that lets the user decide
which ledger to open. Like with total Commander, this is created behind the
main window. there is also a very visible screen error, where a non-refreshing
area is created just below the toolbar.
Both programs were created with Delphi.
Please contact me if you want elaboration or to obtain a copy of SummaSummarum
(it is shareware, but the download site is in danish).I will also be happy to
test updates for the prolems.
------- Additional Comments From ping <at> piteraq.dk 2002-12-13 03:25 -------
Created an attachment (id=354)
--> (http://bugs.winehq.com/attachment.cgi?id=354&action=view)
The window from SummaSummarum that should be in front
------- Additional Comments From ping <at> piteraq.dk 2002-12-13 03:26 -------
Created an attachment (id=355)
--> (http://bugs.winehq.com/attachment.cgi?id=355&action=view)
The dark blue and dark grey bars are not shown with wine
------- Additional Comments From ping <at> piteraq.dk 2002-12-13 03:29 -------
*** This bug has been confirmed by popular vote. ***
------- Additional Comments From ping <at> piteraq.dk 2002-12-13 14:53 -------
Errata: I have written that the dark blue and the dark grey bars are not
shown. That is not correct, as they ARE shown, but between them and the
horizontal toolbar, there is some slackspace when used under wine that is not
there under ms windows. Could it be that the window height somehow is reported
less than it actually is ?
------- Additional Comments From michal.seliga <at> visicom.sk 2003-01-29 11:49
-------
There is the same problem in many application (new modal windows are created
behind main window), including many installers. I workarounded it with setting
wine to not use managed mode in wine.conf. Now everything works well. I tried
wine 20030115
so maybe that could lead to something.... (bug in managed mode?)
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1116
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:39 -------
Bug comments restored from Gmane.org:
If you open winrar, navigate by the directory until that you find a .zip file, and
you do doubleclick about the file, it will refresh the listbox and will should the list
of files what are included in the .zip, (almost correct because the icons are
buggy), but the problem is that a new "extra" header have been included in the
"header" control, it has now:
Name | Size | Packet | Type | Modified | CRC32 | Name
^^^^^^ <- this is duplicated!!!
Now if you click in the gold arrow and go back to the last seen folder, it does
refresh the listbox, but the "extra Name" doesn't disappear. It works fine with
comctl32 native.
Regards,
Carlos.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1115
------- Additional Comments From z_god(a)wanadoo.nl 2003-28-06 07:39 -------
Bug comments restored from Gmane.org:
When you run the program, it is NOT usable, it is repainting continually the
screen, and no one control works. It works fine with comctl32 native. The
problem looks like that happen in rebar, because it is giving some ERR messages:
err:rebar:REBAR_AdjustBands Phase 1 failed, x=561, maxx=0, start=0, end=0
err:rebar:REBAR_AdjustBands Phase 1 failed, x=565, maxx=0, start=0, end=0
err:rebar:REBAR_AdjustBands Phase 1 failed, x=565, maxx=0, start=0, end=0
If you add a "return;" to the start of the function REBAR_Layout, the rebar is
painted incorrectly, but the program can be used.
If you don't remove REBAR_Layout and only comment the last line of the
REBAR_Layout function
//REBAR_ForceResize (infoPtr);
Then the rebar are painted better (but no correct) and it is usable.
Regards,
Carlos.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.