wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

closing handle fails
by steve.lustbader＠philips.com 22 Nov '02

22 Nov '02

I open a handle to a com port with m_hPort = ::CreateFile(_T("COM1"),GENERIC_READ | GENERIC_WRITE, 0, 0, OPEN_EXISTING,FILE_FLAG_OVERLAPPED, 0); Later, when I try to close the handle, the call to CloseHandle(m_hPort) gets stuck when CloseHandle calls NtClose. What trace can I provide here to help? -Steve

1 0

Re: wine/ windows/winproc.c windows/winpos.c windo ...
by Greg Turner 22 Nov '02

22 Nov '02

On Friday 22 November 2002 03:22 pm, Alexandre Julliard wrote: > ChangeSet ID: 6371 > 1.154 1.155 +76 -93 wine/controls/menu.c gcc 3.2 isn't happy with this: make[2]: Entering directory `/var/src/wine/dlls/user' gcc -c -I. -I. -I../../include -I../../include -march=athlon -O1 -pipe -mmmx -m3dnow -gstabs -g3 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_USER32_ -D_WINABLE_ -D_REENTRANT -o ../../controls/menu.o ../../controls/menu.c ../../controls/menu.c: In function `MENU_GetBitmapItemSize': ../../controls/menu.c:722: pointers are not permitted as case values ../../controls/menu.c:729: pointers are not permitted as case values ../../controls/menu.c:730: pointers are not permitted as case values ../../controls/menu.c:731: pointers are not permitted as case values ../../controls/menu.c:732: pointers are not permitted as case values ../../controls/menu.c:733: pointers are not permitted as case values ../../controls/menu.c:737: pointers are not permitted as case values ../../controls/menu.c:738: pointers are not permitted as case values ../../controls/menu.c:739: pointers are not permitted as case values ../../controls/menu.c:740: pointers are not permitted as case values ../../controls/menu.c:741: pointers are not permitted as case values ../../controls/menu.c: In function `MENU_DrawBitmapItem': ../../controls/menu.c:778: pointers are not permitted as case values ../../controls/menu.c:793: pointers are not permitted as case values ../../controls/menu.c:796: pointers are not permitted as case values ../../controls/menu.c:799: pointers are not permitted as case values ../../controls/menu.c:802: pointers are not permitted as case values ../../controls/menu.c:805: pointers are not permitted as case values ../../controls/menu.c:808: pointers are not permitted as case values ../../controls/menu.c:809: pointers are not permitted as case values ../../controls/menu.c:810: pointers are not permitted as case values ../../controls/menu.c:811: pointers are not permitted as case values ../../controls/menu.c:812: pointers are not permitted as case values make[2]: *** [../../controls/menu.o] Error 1 make[2]: Leaving directory `/var/src/wine/dlls/user' make[1]: *** [user] Error 2 make[1]: Leaving directory `/var/src/wine/dlls' make: *** [dlls] Error 2 These are DECLARE_HANDLE'ed values. This seems to fix it: Index: controls/menu.c =================================================================== RCS file: /home/wine/wine/controls/menu.c,v retrieving revision 1.155 diff -u -r1.155 menu.c --- controls/menu.c 22 Nov 2002 21:22:16 -0000 1.155 +++ controls/menu.c 22 Nov 2002 22:13:40 -0000 @@ -719,26 +719,26 @@ { switch(LOWORD(id)) { - case HBMMENU_SYSTEM: + case (WORD)HBMMENU_SYSTEM: if (data) { bmp = (HBITMAP)data; break; } /* fall through */ - case HBMMENU_MBAR_RESTORE: - case HBMMENU_MBAR_MINIMIZE: - case HBMMENU_MBAR_MINIMIZE_D: - case HBMMENU_MBAR_CLOSE: - case HBMMENU_MBAR_CLOSE_D: + case (WORD)HBMMENU_MBAR_RESTORE: + case (WORD)HBMMENU_MBAR_MINIMIZE: + case (WORD)HBMMENU_MBAR_MINIMIZE_D: + case (WORD)HBMMENU_MBAR_CLOSE: + case (WORD)HBMMENU_MBAR_CLOSE_D: size->cx = GetSystemMetrics( SM_CXSIZE ); size->cy = GetSystemMetrics( SM_CYSIZE ); return; - case HBMMENU_CALLBACK: - case HBMMENU_POPUP_CLOSE: - case HBMMENU_POPUP_RESTORE: - case HBMMENU_POPUP_MAXIMIZE: - case HBMMENU_POPUP_MINIMIZE: + case (WORD)HBMMENU_CALLBACK: + case (WORD)HBMMENU_POPUP_CLOSE: + case (WORD)HBMMENU_POPUP_RESTORE: + case (WORD)HBMMENU_POPUP_MAXIMIZE: + case (WORD)HBMMENU_POPUP_MINIMIZE: default: FIXME("Magic 0x%08x not implemented\n", id); return; @@ -775,7 +775,7 @@ switch(LOWORD(lpitem->text)) { - case HBMMENU_SYSTEM: + case (WORD)HBMMENU_SYSTEM: if (lpitem->dwItemData) { bmp = (HBITMAP)lpitem->dwItemData; @@ -790,26 +790,26 @@ bm.bmWidth -= bmp_xoffset; } goto got_bitmap; - case HBMMENU_MBAR_RESTORE: + case (WORD)HBMMENU_MBAR_RESTORE: flags = DFCS_CAPTIONRESTORE; break; - case HBMMENU_MBAR_MINIMIZE: + case (WORD)HBMMENU_MBAR_MINIMIZE: flags = DFCS_CAPTIONMIN; break; - case HBMMENU_MBAR_MINIMIZE_D: + case (WORD)HBMMENU_MBAR_MINIMIZE_D: flags = DFCS_CAPTIONMIN | DFCS_INACTIVE; break; - case HBMMENU_MBAR_CLOSE: + case (WORD)HBMMENU_MBAR_CLOSE: flags = DFCS_CAPTIONCLOSE; break; - case HBMMENU_MBAR_CLOSE_D: + case (WORD)HBMMENU_MBAR_CLOSE_D: flags = DFCS_CAPTIONCLOSE | DFCS_INACTIVE; break; - case HBMMENU_CALLBACK: - case HBMMENU_POPUP_CLOSE: - case HBMMENU_POPUP_RESTORE: - case HBMMENU_POPUP_MAXIMIZE: - case HBMMENU_POPUP_MINIMIZE: + case (WORD)HBMMENU_CALLBACK: + case (WORD)HBMMENU_POPUP_CLOSE: + case (WORD)HBMMENU_POPUP_RESTORE: + case (WORD)HBMMENU_POPUP_MAXIMIZE: + case (WORD)HBMMENU_POPUP_MINIMIZE: default: FIXME("Magic 0x%08x not implemented\n", LOWORD(lpitem->text)); return; -- gmt "War is an ugly thing, but not the ugliest of things; the decayed and degraded state of moral and patriotic feeling which thinks that nothing is worth war is much worse. A man who has nothing for which he is willing to fight; nothing he cares about more than his own personal safety; is a miserable creature who has no chance of being free, unless made and kept so by the exertions of better persons than himself." -- John Stuart Mill

1 0

wintab.dll: Copyright & trademark issues.
by Robert North 22 Nov '02

22 Nov '02

As I mentioned in an e-mail a couple of days back, I'm about to start implemening a version of wintab.dll. First I want to ask about legal issues: 1. trademark issues. wintab is a trademark. Does this impact on the ability to implement wintab.dll 2. API header files. Please look at the licence for the API files, avaialable at the following URL: http://www.pointing.com/Wintab/WTKIT126.ZIP Does this allow our use of the headers, in Wine? Does it allow the use of fragments of the headers in Wine? This is not too much of an issue, as I understand it's OK to re-write compatible headers "In your own words". 3. I am in the UK, how does this affect the copyright/trademark issues above? Ok, some background about wintab: wintab.dll is an "open industry standard" API developed by a group of tablet manufacturers, and seems to be currently maintained by the company LCS/Telegraphics. Web page for wintab: http://www.pointing.com/WINTAB.HTM LCS/Telegraphics home: http://www.pointing.com/LCS.HTM I also found this organiation that LCS belongs to interesting: http://www.interop.org/ Many thanks -Rob.

1 0

Re: wine and asyncronous file i/o
by Martin Fuchs 22 Nov '02

22 Nov '02

Thanks, Martin! > EOF conditions are nasty. Seems we got it wrong... Please try the > following patch (it should solve your problem). However I guess it needs > regression testing because it changes overlapped ReadFile() semantics > drastically. If this condition turns out to be right, we may actually be > able to get rid of the special treatment of sockets in > FILE_AsyncReadService(). Yes, the file read routine seems to work now. However the application doesn't run completely yet. But that's another problem, I think... -- Martin Fuchs martin-fuchs(a)gmx.net

1 0

wm_mousehover bug fix.....
by Mike Hearn 22 Nov '02

22 Nov '02

Sorry to kind of spam, it was much easier to fix it than I thought it would be. Hacking wine isn't so hard after all...... input.c line 970 should be: PostMessageA(TrackingList[i].tme.hwndTrack, WM_MOUSEHOVER, get_key_state() , (pos.y << 8) + (pos.x)); I didn't think it was worth sending to wine-patches as it's just a 1 line fix and I didn't do it against wine cvs, but the last tarball release. That solves all my mouse handling issues with the ASV, so I'm a happy person once more. If somebody could apply that patch that'd be fab. thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ

4 3

RFC: console & curses
by Eric Pouech 22 Nov '02

22 Nov '02

I did send a couple of days ago a first patch about the (n)curses backend to wineconsole Alexandre commented a few implementation issues in it, which may change a bit what I started with and how the wineconsole should behave: console creation can be invoked from different contexts: 1/ the program calls AllocConsole 2/ the user starts wine thru wineconsole for his/her (favorite) CUI app (using from command line something like 'wineconsole foo') 3/ (N1) the program forks a child with CREATE_NEW_CONSOLE flags set in CreateProcess 4/ the program doesn't request anything on the other hand, wineconsole is now able to handle two types of backend for the user interface: A/ USER: the one already in place B/ Curses: the new one using (n)curses and a regular term for display (N2) C/ no wineconsole support => by default, the windows input & output streams are hooked to stdin and stdout, but we don't provide full console support - cursor motion, screen reading... now the final question, how to choose between A, B and C. the proposal is to fix the choice with: 1 => A 2 => B 3 => A 4 => C why such a directive proposal ? 4 => C is rather natural and doesn't need further explanation (one day, we could envisage to support it no longer, but that's another story) 1 => A greatly facilitates the console creation (ncurses requires both terminal control and moreover to keep the process group leader running as long as all the children - hooked to the same terminal - are running). Very few programs use AllocConsole (and even use it). The only issue may be with winedbg which may allocate its own console on startup (N3) 2 => B we could easily add 2 => A too (with some wineconsole parameters). Moreover, if the user wants to have the console in a specific xterm, it's doable with xterm -e 'wineconsole blablabla' 3 => A here again it's easier to deal with. if trying to run a curses backend, we should ensure that two different wineconsoles are not currently hooked to the same terminal If you have any comments, speak up now !! A+ N1: 3/ can be seen from various aspects as a specific case of 1/, but implementation could implement it as 2/) N2: one could try running wineconsole USER backend with ttydrv instead of x11drv, but that's out of the scope of this (maybe for Dimi's fun projects list N3: IMO what's missing is that winedbg should check if has inheried a real console. If so, it should detach from it and recreate a new one.

3 16

Re: Rosetta, wine, sound bug?
by Jeff Smith 22 Nov '02

22 Nov '02

>From: Sylvain Petreolle <spetreolle(a)yahoo.fr> > > > bash-2.05a$ wine -debugmsg +winmm,+wave,+dsound Rosetta.exe > > trace:winmm:WINMM_LibMain 0x41630000 0x1 (nil) > > trace:winmm:WINMM_CreateIData Created IData (0x403f0ef8) > > trace:winmm:MMDRV_Install ('wineoss.drv', 'wineoss.drv', mapper=N); > > trace:winmm:MMDRV_Install Got 32 bit func 'auxMessage' > > trace:winmm:MMDRV_Install Got 32 bit func 'mixMessage' > > trace:winmm:MMDRV_Install Got 32 bit func 'midMessage' > > trace:winmm:MMDRV_Install Got 32 bit func 'modMessage' > > trace:winmm:MMDRV_Install Got 32 bit func 'widMessage' > > trace:winmm:MMDRV_Install Got 32 bit func 'wodMessage' > > trace:winmm:MMDRV_GetDescription32 Can't find file wineoss.drv > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Shouldn't happen. > > trace:winmm:MMDRV_Install wineoss.drv => No description I get similar errors with MMDRV_GetDescription32. I assumed they were happening because the actual file wineoss.drv does not exist. Further, I assumed that MMDRV_GetDescription32 tries to get the description from locating the relevant record in the actual file. Please note that I have not had a chance to verify any of this. I have just recently taken an interest in wine's sound libraries, and would be glad to help out where I can. -- Jeff S _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

2 1

Rosetta, wine, winex bug?
by ladies_man＠earthlink.net 22 Nov '02

22 Nov '02

I have a problem with wine, and everyone says that it is a bug, so I suppose that it would have some relevance here. Any help or solutions would be helpful. I have three programs, wine, winex, and Rosetta. When I combine winex with Rosetta sound works fine, but then the display is royally messed up. When I use wine with Rosetta, the sound fails but everything else works beautifully. Computer Information: Make: Dell Inspiron 3800 Laptop Processor: 700mhz Celeron Ram: 128mb Distribution: Gentoo Linux, stage 1, highly optimized and custom compiled. Video Card: ATI Rage Mobility Sound Card: ESS Maestro3 Devices: /dev/mixer /dev/dsp /dev/cdroms/cdrom0 Here is my Wine config file: [Drive C] "Path" = "${HOME}/.wine/fake_windows" "Type" = "hd" "Label" = "MS-DOS" "Filesystem" = "win95" ;;[Drive D] ;;"Path" = "/path/to/drive_d" ;;"Type" = "hd" ;;"Label" = "LABEL" ;;"Filesystem" = "win95" [Drive E] "Path" = "/mnt/cdrom" "Type" = "cdrom" "Label" = "CD-Rom" "Filesystem" = "win95" "Device" = "/dev/cdroms/cdrom0" [Drive F] "Path" = "/tmp" "Type" = "hd" "Label" = "Tmp Drive" "Filesystem" = "win95" [Drive H] "Path" = "${HOME}" "Type" = "network" "Label" = "Home" "Filesystem" = "win95" [Drive Z] "Path" = "/" "Type" = "network" "Label" = "Root" "Filesystem" = "win95" [wine] "Windows" = "c:\\Windows" "System" = "c:\\Windows\\System" "Temp" = "f:\\" "Path" = "c:\\Windows;c:\\Windows\\System;f:\\;h:\\;z:\\" "Profile" = "c:\\Windows\\Profiles\\Administrator" "GraphicsDriver" = "x11drv" ; Wine doesn't pass directory symlinks to Windows programs by default. ; Enabling this may crash some programs that do recursive lookups of a whole ; subdir tree in case of a symlink pointing back to itself. ;"ShowDirSymlinks" = "1" "ShellLinker" = "wineshelllink" # <wineconf> [Version] ; Windows version to imitate (win95,win98,winme,nt351,nt40,win2k,winxp,win20,win30,win31)" }, ;"Windows" = "win98" ; DOS version to imitate ;"DOS" = "6.22" ; Be careful here, wrong DllOverrides settings have the potential ; to pretty much kill your setup. [DllOverrides] "rpcrt4" = "builtin, native" "oleaut32" = "builtin, native" "ole32" = "builtin, native" "commdlg" = "builtin, native" "comdlg32" = "builtin, native" "ver" = "builtin, native" "version" = "builtin, native" "shell" = "builtin, native" "shell32" = "builtin, native" "shfolder" = "builtin, native" "shlwapi" = "builtin, native" "shdocvw" = "builtin, native" "lzexpand" = "builtin, native" "lz32" = "builtin, native" "comctl32" = "builtin, native" "commctrl" = "builtin, native" "advapi32" = "builtin, native" "crtdll" = "builtin, native" "mpr" = "builtin, native" "winspool.drv" = "builtin, native" "ddraw" = "builtin, native" "dinput" = "builtin, native" "dsound" = "builtin, native" "opengl32" = "builtin, native" "msvcrt" = "native, builtin" "msvideo" = "builtin, native" "msvfw32" = "builtin, native" "mcicda.drv" = "builtin, native" "mciseq.drv" = "builtin, native" "mciwave.drv" = "builtin, native" "mciavi.drv" = "native, builtin" "mcianim.drv" = "native, builtin" "msacm.drv" = "builtin, native" "msacm" = "builtin, native" "msacm32" = "builtin, native" "midimap.drv" = "builtin, native" ; you can specify applications too "notepad.exe" = "native, builtin" ; default for all other dlls "*" = "native, builtin" [x11drv] ; Number of colors to allocate from the system palette "AllocSystemColors" = "100" ; Use a private color map "PrivateColorMap" = "N" ; Favor correctness over speed in some graphics operations "PerfectGraphics" = "N" ; Color depth to use on multi-depth screens ;;"ScreenDepth" = "16" ; Name of X11 display to use ;;"Display" = ":0.0" ; Allow the window manager to manage created windows "Managed" = "N" ; Use a desktop window of 640x480 for Wine "Desktop" = "640x480" ; Use XFree86 DGA extension if present ; (make sure /dev/mem is accessible by you !) "UseDGA" = "Y" ; Use XShm extension if present "UseXShm" = "Y" ; Use XVidMode extension if present "UseXVidMode" = "Y" ; Enable DirectX mouse grab "DXGrab" = "N" ; Create the desktop window with a double-buffered visual ; (useful to play OpenGL games) "DesktopDoubleBuffered" = "N" ; Code page used for captions in managed mode ; 0 means default ANSI code page (CP_ACP == 0) "TextCP" = "0" ; Use this if you have more than one port for video on your setup ; (Wine uses for now the first 'input image' it finds). ;; "XVideoPort" = "43" ; Run in synchronous mode (useful for debugging X11 problems) ;;"Synchronous" = "Y" [fonts] ;Read the Fonts topic in the Wine User Guide before adding aliases ;See a couple of examples for russian users below "Resolution" = "96" "Default" = "-adobe-helvetica-" "DefaultFixed" = "fixed" "DefaultSerif" = "-adobe-times-" "DefaultSansSerif" = "-adobe-helvetica-" ;; default TrueType fonts with russian koi8-r encoding ;"Default" = "-monotype-arial-*-*-*--*-*-*-*-*-*-koi8-r" ;"DefaultFixed" = "-monotype-courier new-*-*-*--*-*-*-*-*-*-koi8-r" ;"DefaultSerif" = "-monotype-times new roman-*-*-*--*-*-*-*-*-*-koi8-r" ;"DefaultSansSerif" = "-monotype-arial-*-*-*--*-*-*-*-*-*-koi8-r" ;; default cyrillic bitmap X fonts ;"Default" = "-cronyx-helvetica-" ;"DefaultFixed" = "fixed" ;"DefaultSerif" = "-cronyx-times-" ;"DefaultSansSerif" = "-cronyx-helvetica-" ; the TrueType font dirs you want to make accessible to wine [FontDirs] ;"dir1" = "/usr/X11R6/lib/X11/fonts/TrueType" ;"dir2" = "/usr/share/fonts/truetype" ;"dir3" = "/usr/X11R6/lib/X11/fonts/TT" ;"dir4" = "/usr/share/fonts/TT" [serialports] "Com1" = "/dev/ttyS0" "Com2" = "/dev/ttyS1" "Com3" = "/dev/ttyS2" "Com4" = "/dev/modem" [parallelports] "Lpt1" = "/dev/lp0" [ppdev] ;; key: io-base of the emulated port ;; value : parport-device{,timeout} ;; timeout for auto closing an open device ( not yet implemented) ;"378" = "/dev/parport0" ;"278" = "/dev/parport1" ;"3bc" = "/dev/parport2" [spooler] "FILE:" = "tmp.ps" "LPT1:" = "|lpr" "LPT2:" = "|gs -sDEVICE=bj200 -sOutputFile=/tmp/fred -q -" "LPT3:" = "/dev/lp3" [ports] ;"read" = "0x779,0x379,0x280-0x2a0" ;"write" = "0x779,0x379,0x280-0x2a0" [Debug] ;"RelayExclude" = "RtlEnterCriticalSection;RtlLeaveCriticalSection" ;"RelayInclude" = "user32.CreateWindowA" ;"SnoopExclude" = "RtlEnterCriticalSection;RtlLeaveCriticalSection" ;"SpyExclude" = "WM_SIZE;WM_TIMER;" [registry] ;These are all booleans. Y/y/T/t/1 are true, N/n/F/f/0 are false. ;Defaults are read all, write to Home ; Global registries (stored in /etc) "LoadGlobalRegistryFiles" = "Y" ; Home registries (stored in ~user/.wine/) "LoadHomeRegistryFiles" = "Y" ; Load Windows registries from the Windows directory "LoadWindowsRegistryFiles" = "Y" ; TRY to write all changes to home registries "WritetoHomeRegistryFiles" = "Y" ; Registry periodic save timeout in seconds ; "PeriodicSave" = "600" ; Save only modified keys "SaveOnlyUpdatedKeys" = "Y" [Tweak.Layout] ;; supported styles are 'Win31'(default), 'Win95', 'Win98' ;; this has *nothing* to do with the windows version Wine returns: ;; set the "Windows" value in the [Version] section if you want that. "WineLook" = "Win95" [Console] ;"Drivers" = "tty" ;"XtermProg" = "nxterm" ;"InitialRows" = "25" ;"InitialColumns" = "80" ;"TerminalType" = "nxterm" [Clipboard] "ClearAllSelections" = "0" "PersistentSelection" = "1" ; List of all directories directly contain .AFM files [afmdirs] "1" = "/usr/share/ghostscript/fonts" "2" = "/usr/share/a2ps/afm" "3" = "/usr/share/enscript" "4" = "/usr/X11R6/lib/X11/fonts/Type1" [WinMM] "Drivers" = "wineoss.drv" #"Drivers" = "winearts.drv" "WaveMapper" = "msacm.drv" "MidiMapper" = "midimap.drv" [dsound] ;; HEL only: Number of waveOut fragments ahead to mix in new buffers. ;"HELmargin" = "5" ;; HEL only: Number of waveOut fragments ahead to queue to driver. ;"HELqueue" = "5" ;; Max number of fragments to prebuffer ;"SndQueueMax" = "28" ;; Min number of fragments to prebuffer ;"SndQueueMin" = "12" ;; Kazaa Lite [AppDefaults\\Kazaa.exe\\DllOverrides] "shdocvw" = "native" "shlwapi" = "native" "urlmon" = "native" # </wineconf> Here is the output from the wine command: bash-2.05a$ wine -debugmsg +warn,+winmm,+winoss,+err,+fixme .wine/fake_windows/Program\ Files/The\ Rosetta\ Stone/The\ Rosetta\ Stone/Rosetta.exe trace:winmm:WINMM_LibMain 0x41630000 0x1 (nil) trace:winmm:WINMM_CreateIData Created IData (0x403f10a8) trace:winmm:MMDRV_Install ('wineoss.drv', 'wineoss.drv', mapper=N); trace:winmm:MMDRV_Install Got 32 bit func 'auxMessage' trace:winmm:MMDRV_Install Got 32 bit func 'mixMessage' trace:winmm:MMDRV_Install Got 32 bit func 'midMessage' trace:winmm:MMDRV_Install Got 32 bit func 'modMessage' trace:winmm:MMDRV_Install Got 32 bit func 'widMessage' trace:winmm:MMDRV_Install Got 32 bit func 'wodMessage' trace:winmm:MMDRV_GetDescription32 Can't find file wineoss.drv trace:winmm:MMDRV_Install wineoss.drv => No description trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 6 dev for (wineoss.drv:Aux) trace:winmm:MMDRV_InitPerType Setting min=0 max=6 (ttop=6) for (wineoss.drv:Aux)trace:winmm:MMDRV_InitPerType Aux:Trans[0] -> w ineoss.drv trace:winmm:MMDRV_InitPerType Aux:Trans[1] -> wineoss.drv trace:winmm:MMDRV_InitPerType Aux:Trans[2] -> wineoss.drv trace:winmm:MMDRV_InitPerType Aux:Trans[3] -> wineoss.drv trace:winmm:MMDRV_InitPerType Aux:Trans[4] -> wineoss.drv trace:winmm:MMDRV_InitPerType Aux:Trans[5] -> wineoss.drv trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (wineoss.drv:Mixer) trace:winmm:MMDRV_InitPerType Setting min=0 max=1 (ttop=1) for (wineoss.drv:Mixer) trace:winmm:MMDRV_InitPerType Mixer:Trans[0] -> wineoss.drv trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 0 dev for (wineoss.drv:MidiIn) trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 0 dev for (wineoss.drv:MidiOut) trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (wineoss.drv:WaveIn) trace:winmm:MMDRV_InitPerType Setting min=0 max=1 (ttop=1) for (wineoss.drv:WaveIn) trace:winmm:MMDRV_InitPerType WaveIn:Trans[0] -> wineoss.drv trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (wineoss.drv:WaveOut) trace:winmm:MMDRV_InitPerType Setting min=0 max=1 (ttop=1) for (wineoss.drv:WaveOut) trace:winmm:MMDRV_InitPerType WaveOut:Trans[0] -> wineoss.drv trace:winmm:MMDRV_Install ('wavemapper', 'msacm.drv', mapper=Y); trace:winmm:MMDRV_Install Got 32 bit func 'widMessage' trace:winmm:MMDRV_Install Got 32 bit func 'wodMessage' trace:winmm:MMDRV_GetDescription32 Can't find file msacm.drv trace:winmm:MMDRV_Install msacm.drv => No description trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (wavemapper:WaveIn) trace:winmm:MMDRV_InitPerType Setting min=0 max=0 (ttop=1) for (wavemapper:WaveIn) trace:winmm:MMDRV_InitPerType WaveIn:Trans[-1] -> wavemapper trace:winmm:MMDRV_InitPerType WaveIn:Trans[0] -> wineoss.drv trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (wavemapper:WaveOut) trace:winmm:MMDRV_InitPerType Setting min=0 max=0 (ttop=1) for (wavemapper:WaveOut) trace:winmm:MMDRV_InitPerType WaveOut:Trans[-1] -> wavemapper trace:winmm:MMDRV_InitPerType WaveOut:Trans[0] -> wineoss.drv trace:winmm:MMDRV_Install ('midimapper', 'midimap.drv', mapper=Y); trace:winmm:MMDRV_Install Got 32 bit func 'modMessage' trace:winmm:MMDRV_GetDescription32 Can't find file midimap.drv trace:winmm:MMDRV_Install midimap.drv => No description trace:winmm:MMDRV_InitPerType DRVM_INIT => 00000000 trace:winmm:MMDRV_InitPerType Got 1 dev for (midimapper:MidiOut) trace:winmm:MMDRV_InitPerType Setting min=0 max=0 (ttop=0) for (midimapper:MidiOut) trace:winmm:MMDRV_InitPerType MidiOut:Trans[-1] -> midimapper trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:waveOutGetDevCapsA (0 0x406b22c4 52)! trace:winmm:MMDRV_Message (WaveOut 0 4 0x00000000 0x406b22c4 0x00000034 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=4 usr=0x00000000 p1=0x406b22c4 p2=0x00000034 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutMessage ((nil), 2058, 1080763140, 0) trace:winmm:MMDRV_PhysicalFeatures (0x403f2594, 080a, 406b2304, 00000000) trace:winmm:MMDRV_Message (WaveOut 0 2058 0x00000000 0x406b2304 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=2058 usr=0x00000000 p1=0x406b2304 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open (0x4043334c, 0, Out, 0x40433338, 43630D38, 404330B0, 00030080, 32); trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=22050, nAvgBytesPerSec=44100, nBlockAlign=2, wBitsPerSample=8, cbSize=0 trace:winmm:WAVE_Open cb=43630d38 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b21a0 0x406b2220 0x00030080 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b21a0 p1=0x406b2220 p2=0x00030080 trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=0x8000 trace:winmm:waveOutSetVolume (0000, ffffffff); trace:winmm:MMDRV_Message (WaveOut 0 17 0x00000000 0xffffffff 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=17 usr=0x00000000 p1=0xffffffff p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutClose (0x8000) trace:winmm:MMDRV_Message (WaveOut 0 6 0x406b21c8 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=6 usr=0x406b21c8 p1=0x00000000 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutGetDevCapsA (4294967294 0x406b1f2c 52)! trace:winmm:waveOutGetDevCapsA (0 0x406b2068 52)! trace:winmm:MMDRV_Message (WaveOut 0 4 0x00000000 0x406b2068 0x00000034 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=4 usr=0x00000000 p1=0x406b2068 p2=0x00000034 trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open ((nil), 0, Out, 0x40430808, 00000000, 00000000, 00000001, 32); trace:winmm:WAVE_Open WAVE_FORMAT_QUERY requested ! trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=44100, nAvgBytesPerSec=176400, nBlockAlign=4, wBitsPerSample=16 , cbSize=0 trace:winmm:WAVE_Open cb=00000000 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b1fb4 0x406b2034 0x00000001 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b1fb4 p1=0x406b2034 p2=0x00000001 trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=(nil) trace:winmm:WAVE_Open (0x40430804, 0, Out, 0x40430808, 00000000, 00000000, 00000002, 32); trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=44100, nAvgBytesPerSec=176400, nBlockAlign=4, wBitsPerSample=16 , cbSize=0 trace:winmm:WAVE_Open cb=00000000 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b1fac 0x406b202c 0x00000002 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b1fac p1=0x406b202c p2=0x00000002 trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=0x8000 trace:winmm:waveOutGetVolume (8000, 404307f8); trace:winmm:MMDRV_Message (WaveOut 0 16 0x406b1fd4 0x404307f8 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=16 usr=0x406b1fd4 p1=0x404307f8 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutClose (0x8000) trace:winmm:MMDRV_Message (WaveOut 0 6 0x406b1fd4 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=6 usr=0x406b1fd4 p1=0x00000000 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open (0x40430804, 0, Out, 0x40430808, 00000000, 00000000, 00000002, 32); trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=44100, nAvgBytesPerSec=176400, nBlockAlign=4, wBitsPerSample=16 , cbSize=0 trace:winmm:WAVE_Open cb=00000000 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b2210 0x406b2290 0x00000002 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b2210 p1=0x406b2290 p2=0x00000002 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=0x8000 trace:winmm:waveOutGetVolume (8000, 406b233c); trace:winmm:MMDRV_Message (WaveOut 0 16 0x406b2238 0x406b233c 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=16 usr=0x406b2238 p1=0x406b233c p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutClose (0x8000) trace:winmm:MMDRV_Message (WaveOut 0 6 0x406b2238 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=6 usr=0x406b2238 p1=0x00000000 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:WAVE_Open (0x40430804, 0, Out, 0x40430808, 00000000, 00000000, 00000002, 32); trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=44100, nAvgBytesPerSec=176400, nBlockAlign=4, wBitsPerSample=16 , cbSize=0 trace:winmm:WAVE_Open cb=00000000 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b1ec0 0x406b1f40 0x00000002 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b1ec0 p1=0x406b1f40 p2=0x00000002 trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=0x8000 trace:winmm:waveOutPrepareHeader (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b1ee8 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b1ee8 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b1ee8 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b1ee8 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b1ee8 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b1ee8 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b1ee8 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b1ee8 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:waveOutWrite (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b1ee8 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b1ee8 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b1ee8 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b1ee8 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b1ee8 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b1ee8 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b1ee8 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b1ee8 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutReset (0x8000); trace:winmm:MMDRV_Message (WaveOut 0 12 0x406b1ee8 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=12 usr=0x406b1ee8 p1=0x00000000 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b1ee8 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b1ee8 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b1ee8 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b1ee8 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b1ee8 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b1ee8 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b1ee8 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b1ee8 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutClose (0x8000) trace:winmm:MMDRV_Message (WaveOut 0 6 0x406b1ee8 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=6 usr=0x406b1ee8 p1=0x00000000 p2=0x00000000 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:WAVE_Open (0x40430804, 0, Out, 0x40430808, 00000000, 00000000, 00000002, 32); trace:winmm:WAVE_Open wFormatTag=1, nChannels=2, nSamplesPerSec=44100, nAvgBytesPerSec=176400, nBlockAlign=4, wBitsPerSample=16 , cbSize=0 trace:winmm:WAVE_Open cb=00000000 trace:winmm:MMDRV_Open Setting mmdIndex to 0 trace:winmm:MMDRV_Message (WaveOut 0 5 0x406b22b8 0x406b2338 0x00000002 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=5 usr=0x406b22b8 p1=0x406b2338 p2=0x00000002 trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WAVE_Open => 0 hWave=0x8000 trace:winmm:waveOutPrepareHeader (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b22e0 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b22e0 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b22e0 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b22e0 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b22e0 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b22e0 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutPrepareHeader (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 7 0x406b22e0 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=7 usr=0x406b22e0 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x2 (nil) trace:winmm:waveOutWrite (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b22e0 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b22e0 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b22e0 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b22e0 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b22e0 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b22e0 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutWrite (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 9 0x406b22e0 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=9 usr=0x406b22e0 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutReset (0x8000); trace:winmm:MMDRV_Message (WaveOut 0 12 0x406b22e0 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=12 usr=0x406b22e0 p1=0x00000000 p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x40430824, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b22e0 0x40430824 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b22e0 p1=0x40430824 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x404308b8, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b22e0 0x404308b8 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b22e0 p1=0x404308b8 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x4043094c, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b22e0 0x4043094c 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b22e0 p1=0x4043094c p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutUnprepareHeader (0x8000, 0x404309e0, 32); trace:winmm:MMDRV_Message (WaveOut 0 8 0x406b22e0 0x404309e0 0x00000020 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=8 usr=0x406b22e0 p1=0x404309e0 p2=0x00000020 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutClose (0x8000) trace:winmm:MMDRV_Message (WaveOut 0 6 0x406b22e0 0x00000000 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=6 usr=0x406b22e0 p1=0x00000000 p2=0x00000000 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x3 (nil) trace:winmm:waveOutSetVolume (0000, ffffffff); trace:winmm:MMDRV_Message (WaveOut 0 17 0x00000000 0xffffffff 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=17 usr=0x00000000 p1=0xffffffff p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:waveOutSetVolume (0000, ffffffff); trace:winmm:MMDRV_Message (WaveOut 0 17 0x00000000 0xffffffff 0x00000000 Y)! trace:winmm:MMDRV_Message Calling message(dev=0 msg=17 usr=0x00000000 p1=0xffffffff p2=0x00000000 trace:winmm:MMDRV_Message => 0 trace:winmm:WINMM_LibMain 0x41630000 0x0 0x1 bash-2.05a$ Now I have no clue what the problem is, many people have been working on this and none of them can figure it out. Both winex 20020807 and the 2.2.1 version have used the oss.drv's and they work. If anyone can help solve this problem I would greatly appreciate it, and if it is a bug, I hope you can fix it quickly. -- ---------------------------------- E-Mail: ladies_man(a)earthlink.net Date: 20-Nov-2002 Time: 15:54:44 This message was sent by XFMail ---------------------------------- -- ---------------------------------- E-Mail: ladies_man(a)earthlink.net Date: 20-Nov-2002 Time: 15:59:39 This message was sent by XFMail ----------------------------------

4 7

winspool.drv again
by Dimitrie O. Paun 22 Nov '02

22 Nov '02

Alexandre, The winspool.drv issue is a lot more serious than the in-tree execution. This one screws things up badly for the PuTTY build system. Should we modify winebuild to try to link with winspool.drv, and if that fails with winspool.dll when -lwinspool is given? (or the other way around, I don't know) I'd really appreciate help on this one, so I can send the patch out. -- Dimi.

4 4

Wine and IrDA via Virtual Com Port
by Ryan Reading 22 Nov '02

22 Nov '02

Hi all, This is my first time on this list. I've been playing around with Wine with quite a bit of success, but I've ran into a problem when trying to get an old program that uses IR to work correctly. I've already post on comp.emulators.ms-windows.wine and they referred my problem here. Here is the info that I have... For the record, I am running Wine 20021031. The program is based on the commercial Greenleaf Comm++ libraries. It is designed to be utilized in Windows on top of a *virtual* Com port running IrDA. The software itself knows nothing of IrDA, it's the *virtual* Com port's responsibility to provide that. Apparently it uses IrCOMM and TinyTP, but I'm just learning exactly what that means. I setup Linux to run IrDA through /dev/ttyS0 (the physical IR serial device) on /dev/ircomm0 (the IrDA device). I set "Com4" = "/dev/ircomm0". in the wine config file. I run the software with "--debugmsg +comm,+file" and look at the output. The software gets to a point where it performs some basic Serial port setup (SetupComm(), GetCommState(), SetCommState(), etc) and then I get the following... <snip> trace:file:Writefile 192 0x420b1190 14 0x4230a200 0x430a1530 trace:file:Writefile Overlapped not specified or invalid event flag <-- this is the interesting line trace:ClearCommError handle 0xc0 cbInQue = 0 cbOutQue = 0 ... last line repeated until timeout </snip> ( big apologies for not having a larger dump ) The pointer to the OVERLAPPED structure in this function is not set to NULL, but the hEvent member of that struct is set to ZERO (0), which seems to be the problem. I don't know why that member variable is set to ZERO (0), but that obviously keeps me from actually writing anything to the IR port. So my question involves how to approach this problem. I actually modified the Wine code to "overlook" the bad hEvent variable in WriteFile(), ReadFile(), and GetOverlappedResult() just for kicks to see what would happen. When I do that, it actually sends stuff over the IR connection and processes more ( additional ReadFile[Ex](), WriteFile[Ex](), GetOverlappedResult() calls ), but obviously the handshaking doesn't complete correctly since I'm ignoring the error checking. Could my problem be in the way IrDA is setup ( i.e. what is the correct way to emulate a Windows *virtual* COM port running IrDA in Wine )?? Any advice or information on this problem would be really appreciated. Thanks. -- Ryan

2 1

Debugging mouse messages
by Mike Hearn 22 Nov '02

22 Nov '02

Hi, After setting up my dual crossover/winehq (last tarball release) installation, I tried doing some traces on IE with the adobe svg plugin. I can't figure out why I am getting this: trace:msg:MSG_peek_message got type 5 msg 113 hwnd 0 wp 8 lp 41380d58 trace:cursor:X11DRV_GetCursorPos pointer at (661,442) trace:msg:MSG_peek_message got type 5 msg 2a1 hwnd 10042 wp 0 lp 0 trace:msg:GetKeyState key (0x12) -> 0 trace:msg:WINPROC_CallProc32ATo32W func 0x413e9024 (hwnd=00010039,msg=WM_USER+000b,wp=00000000,lp=00000000) over and over again when the mouse is not moving. It appears that IE (the constant polling for the cursor position occurs when showing a 404 screen too) has different mouse behaviour to other apps, for instance in WebFerret the X11DRIV_GetCursorPos function is only called when the mouse actually moves. In IE, it's called seemingly on a timer (i'd guess every .25 or .5 seconds) even when the cursor is over a toolbar (though not the address bar oddly). I'm also confused by the reference to WINPROC_CallProc32ATo32W, is this normal? Google says it's used as part of 32bit<->16bit thunking, but there is no 16bit code here as far as I'm aware. Any ideas? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ

2 3

Re: Screenshots
by Brian Vincent 22 Nov '02

22 Nov '02

I've been meaning to put something together for a few days here.. > shots to Brian isn't the best way to go about it as nobody knows who has > sent what. Have you actually got any yet Brian? First, take a look at: http://www.theshell.com/~vinn/ss Quite a few folks have sent stuff in. Now, after looking at so many screenshots and trying to evaluate them for content I've realized a few things.. 1) We're absolutely going to have to insist on 800x600 resolution. Thanks for all the ones so far, but really the only usable ones are the 800x600. (There are exceptions, such as Mike's Quicktime one that can be resized nicely.) 2) Screenshots of an application doing something are the way to go. For instance, the one Mike just sent me showing Adobe's SVG plug-in in IE is WAY cool. Unfortunately it's not usable because of the resolution. Even a pull-down menu being pulled down is enough. 3) Cluttered desktops suck. You don't need to have 3 terminal windows, Mozilla, and everything else in the background. For the most part I think the screenshots have followed that rule closely. Okay, here's the deal.. Thomas Wickline volunteered to do screenshots of these apps: Office 2000 and everything in it lotus notes Quicken Quick Books visio Carlos Lozano did shots for the "gold" list apps. I'm going to ask him for some more here in the future.. (unbeknowst to him) The following would be nice to see: any game the exact same screenshot Mike Hearn sent of IE/SVG except at 800x600 Adobe Photoshop Anything else is fair game. I'll put screenshots on that URL above, so check there before doing any. -brian

6 5

Interesting control samples
by Mehmet YASAR 22 Nov '02

22 Nov '02

Hi, I just found http://www.codejock.com/, they seems to provide a Toolkit to enhance any app (giving Microsoft's new UI look), the most interesting for Wine is that you can download 40 basic samples of different controls. Few notes : - A quick test shows that Wine can't launch any exe. - No source code is included I thought it may be a good test case ... Here is the list of samples included in XTSetupSamples_1931.exe : AccelDemo.exe BrowseDialog.exe BrowseEdit.exe Button.exe CaptionBar.exe CheckListBox.exe ColorPicker.exe CommonControls.exe CoolMenu.exe DockingDemo.exe EditListBox.exe FlatCombo.exe FlatHeader.exe FlatTabCtrl.exe FlatTabView.exe GUI_Explorer.exe GUI_Outlook.exe GUI_VisualStudio.exe GUI_WinZip.exe HexEdit.exe HyperLink.exe ListCtrl.exe MaskEdit.exe MDITabWindows.exe MultiFrameDocking.exe OutlookBar.exe Pager.exe PrintPreview.exe SearchOptions.exe SplitterWindow.exe StatusBar.exe TabbedView.exe TabCtrlBar.exe TabCtrl.exe TipOfTheDay.exe TipWindow.exe TrayIconDemo.exe TrayIconDlg.exe TreeCtrl.exe WindowPos.exe Mehmet

1 0

winewrapper
by Dimitrie O. Paun 22 Nov '02

22 Nov '02

Folks, Another problem developing Winelibs app while using your Wine tree. Say you have the following: -- a Winelib app you're working on -- a Wine tree you're working on -- you compile wine out-of-tree Now, say you build your myapp.exe.so OK, and you now want to create a symlink myapp -> winewrapper so you can start your Winelib app. Problem is that winewrapper resides in the source tree, and there is no way for it to figure out where the build tree is, and it needs that. Possible solution: -- have winewrapper somehow in the Wine build tree. One way to do that is to rename winewrapper to winewrapper.in, and generate winewrapper at build time -- link to the winewrapper in the build tree -- modify winewrapper slightly so that it looks where is resides, and if it's in the wine tree, is should try to use that to run the app. Alexandre, what do you say? -- Dimi.

4 13

Re: wine/tools wineinstall
by Dustin Navea 22 Nov '02

22 Nov '02

On Thu, 2002-11-21 at 17:46, Alexandre Julliard wrote: > ChangeSet ID: 6362 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2002/11/21 17:46:06 > > Modified files: > tools : wineinstall > > Log message: > Matthew Davison <m.davison(a)virgin.net> > Remove obsolete --enable-opengl. > > Patch: http://cvs.winehq.com/patch.py?id=6362 > > Old revision New revision Changes Path > 1.47 1.48 +1 -1 wine/tools/wineinstall > > > I'm not totally sure that this should be done as my wine install comes with opengl disabled due to relying on libpthread for thread safety. If we remove the --enable-opengl from wineinstall FLC's will not know how to enable it... -Dustin

2 1

__int64
by Dimitrie O. Paun 22 Nov '02

22 Nov '02

Hmm, Another header problem. When compiling Putty with Wine's headers, I get this errors: In file included from /home/dimi/dev/wine/wine.src/include/msvcrt/wchar.h:12, from wcwidth.c:9: /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:42: parse error before "__int64" /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:42: warning: no semicolon at end of struct or union /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:44: parse error before '}' token /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:60: parse error before "__int64" ... Reason is that __int64 is not defined. Now, this happens when I compile a file that has only one include: #include <wchar.h> As a quick hack, I've added this: typedef long long __int64; to include/msvcrt/sys/types.h, but it doesn't look like the right fix. We define __int64 in here: include/basetsd.h:#define __int64 long long but why a define and not a typedef? Should we include this file from one of the msvcrt header files? I really don't like doing that, but than again, I don't know much about the organization of our headers, or most importantly, the way MS does it... -- Dimi.

4 7

PuTTY update
by Dimitrie O. Paun 21 Nov '02

21 Nov '02

Folks, Here's a quick status update on PuTTY as a Winelib app: 1. It compiles, links, and runs perfectly (Yay!) 2. I've talked to the PuTTY folks, and they agreed to add Winelib as one of their targets in their build process (provided I do the patch :)) 3. I've modified they Makefile-generation Perl scrip to do just that. What is missing: 1. The winspool issue I've sent earlier is bugging me. They link against -lwinspool, we require -lwinspool.drv This is very awkward to implement, and my patch would become a lot more intrusive (and maybe unacceptable). We need to fix this on our end, so we're compatible. 2. The winewrapper thing I've just sent out. I can't send them a bunch (they generate like 7 apps) of silly wrapper scrips, that'd be ridiculous. Help in resolving these issues would be greatly appreciated. I'd like to send them the patch sooner rather than later, so that (1) they don't change their mind, and (2) I don't forget what I was doing! :) -- Dimi.

2 2

Seperating winelibs from main wine ( was "Winelib support" )
by Mark Hannessen 21 Nov '02

21 Nov '02

Mmmm.. Doesn't sound like a basic windows app. I do not know any windows program that uses putty and there are plenty linux/unix alternatives. but it might be usefull to some people. ( i don't know anyone ) perhaps it is time to seperate all the winelib progs from the main wine package and create a winelib package. just how knows what people in the future might write. paint / control panel / media player / calculator / etc... comments please Mark Hannessen On Thursday 21 November 2002 10:50, wine-devel-request(a)winehq.com wrote: > Hi folks, > > I'm one of the Wine (http://www.winehq.org) developers, > and I just managed to build Putty under Winelib. That > is, Putty now runs as a native Linux application. > > The interesting part is that I've managed to do so with > virtually no changes to the source code, just a few > changes to the makefile.cyg file. > > Now, my question to you: are you interested in supporting > Putty under Wine, as a Winelib app? If so, I can clean up > my changes, and send you a patch for the build system to > incorporate in your tree.

7 13

[Fwd: Re: Wine developers want Pegasus Mail as a 'Gold' app]
by Rick Romero 21 Nov '02

21 Nov '02

I contacted David Harris, author of Pegasus Mail, and here's what he had to say. I am totally lost when it comes to the windowing stuff, I'm not sure what's X and what's Windows. Hopefully that can help a little.. I know the patches thread was really self-explanatory, but was centered on the app being iconified. I don't know that this is really any different, but it just seems more of a 'hiding the taskbar' and not iconifying the app. Or am I just stubborn/thick-headed? (well, I am :) The "Setup Wizard" was something I thought would be good to have, but at this point, I think David would have to remove the actual file open code from Pegasus for it to work. HTH. Rick -----Forwarded Message----- From: David Harris <David.Harris(a)pmail.gen.nz> To: Rick Romero <rick(a)valeoinc.com> Subject: Re: Wine developers want Pegasus Mail as a 'Gold' app Date: 22 Nov 2002 10:52:12 +1300 On 21 Nov 2002 at 11:59, Rick Romero wrote: > I apologize for the direct email, I had hoped that a Win-PM list posting > would be sufficient, but it unfortunately hasn't been. Alas, I don't read any of the public lists any more - with more than 300 messages a day to deal with just on the local accounts, I simply don't have time. > But let me get right down the the issues. I was hoping you could give > me some insight into the workings of Pegasus Mail so that the Wine guys > could easily implement any Windows API's that you might be using, that > are missing from Wine. Please consider my mailbox open at any time of the day for this - both yourself and any Wine developer who would like to contact me directly. Given that I simply don't have the resources to produce my own Linux version of Pegasus Mail at this stage, Wine assumes considerable importance for me, so any collaboration offers clear mutual benefits. > The first, critical issue, has to do with hiding the taskbar entry. > The option: "Hide the Pegasus Mail taskbar entry when minimized" which > is on by default, causes Wine to not refresh the window after > minimizing, or changing virtual desktops. A one-line fix for Wine DOES > exist, (Essentially, the flag WS_VISIBLE is not checked within Wine) but > I was hoping you could give us a little more info on what flag you may > set on that checkbox, or if it's just a flag at all, or a quick couple > lines of code.. It's not as clean or tidy as a couple of lines of code - there are some messages involved, but overall it's pretty simple. When Pegasus Mail gets a WM_SIZE message with wParam set to SIZE_MINIMIZED, it simply calls ShowWindow (hWndFrame, SW_HIDE); where "hWndFrame" is the main WinPMail frame window. There's a little other cruft in there as well, but nothing that would affect this. Under Windows, the effect of this is to remove the application from the taskbar. That's really all there is to it. The preferences checkbox merely sets a preference field which is queried later when the application is actually minimized - it has no other immediate function when it is checked. > The second issue is just for user convienance. We've found that Pmail > checks for a physical winsock.dll (wsock32.dll for Wine), and if that > exists, it enables TCP/IP. What still doesn't occur though, is the > Internet Setup Wizard. A fresh install, with wsock32.dll existing, (We > assume) should start the Wizard upon startup. That doesn't happen, > Pegasus works just fine, but doesn't start the wizard for the new user. > Are there any other checks you make to start that wizard up? Looking through the code, it appears to me that the following conditions need to be true before the Internet Setup Wizard will run: 1: It must be the first time the program has ever run for this user (i.e, there needs to have been no PMAIL.INI file present in the mailbox when the program started). 2: The commandline -Z (flags) switch must not have bit 0 set (i.e, it cannot have "1" as one of its bit members) - this disables TCP/IP altogether. 3: The User's POP3 server, POP3 username and POP3 password must all be zero-length (i.e, not yet defined) internally. 4: The bit member 0x20000 must not be set in the -Z (flags) commandline switch (this bit simply disables the setup wizard). 5: The program must be able to locate WSOCK32.DLL in any of the usual places where LoadLibrary would look (the Windows System directory, the Windows directory, the path, the current directory). Note that the check in step 5 is unintentionally quite extensive - the file not only has to be present, but Pegasus Mail actually has to be able to open it for reading (this is because I have a general-purpose file existence checking routine that attempts to make sure that the file not only exists, but can be opened, and I use that as part of the process of searching for a DLL). Aside from (all) that, I can't see anything else in there that might cause the setup wizard not to run. -- If there were some reliable way that I could determine that I was running under Wine, I would be *happy* to add code to the program that gave it specific behaviours in that environment - all you need to do is tell me what behaviours you need modified, and how I can detect Wine. Cheers! -- David -- ------------------ David Harris -+- Pegasus Mail ---------------------- Box 5451, Dunedin, New Zealand | e-mail: David.Harris(a)pmail.gen.nz Phone: +64 3 453-6880 | Fax: +64 3 453-6612 Real newspaper headlines from U.S. papers: MAN HELD OVER GIANT L.A. BRUSH FIRE -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

1 0

Minor AIM bug
by Dustin Navea 21 Nov '02

21 Nov '02

Hey now that I got AIM running, (have to copy from a windows install and force wine to use that winver) I noticed 2 small bugs.. Both are related to comctl32 AFAICT... 1) When going to sign on, the controls think that the left mouse button is pushed always, and so when you move the mouse over the screen name it selects it, that is more of a feature IMO, as it makes it easier to switch screen names 2) When resizing the chat windows, there is a significant amount of lag moving the controls, like you resize the window, but the controls all move a lot slower than the window does, hard to describe but if anyone wants a screenshot I can post one somewhere... -Dustin

1 0

PostMessage and NULL HWND's
by steve.lustbader＠philips.com 21 Nov '02

21 Nov '02

PostMessage fails if you pass in NULL as the HWND argument. According to the MSDN, a NULL HWND means "The function behaves like a call to PostThreadMessage with the dwThreadId parameter set to the identifier of the current thread." Currently, PostMessage tries to get the thread id of the hwnd, which of course fails since it's NULL in this case, and of course the error is Invalid Window Handle. It seems like a simple fix is a test if hwnd is NULL and calling PostThreadMessage with the right thread ID, but I don't know how to get the current thread's ID. Any ideas/suggestions? -Steve

2 1

RE: Adding -lc when linking?
by Patrik Stridvall 21 Nov '02

21 Nov '02

> Gerald Pfeifer <pfeifer(a)dbai.tuwien.ac.at> writes: > > > How should this be solved (in a portable way)? > > Adding -lc seems the right way. In fact I committed that fix last > night ;-) Yes I noticed. :-) However, it doesn't seem to be the 100% correct fix. DLLs using pthreads like the ones depending on OpenGL needs to link with -lc_r instead of -lc on FreeBSD. ---8<--- gcc -shared -Wl,-Bsymbolic,-z,defs d3d8.spec.o basetexture.o cubetexture.o d3d8_main.o device.o directx.o indexbuffer.o resource.o surface.o swapchain.o texture.o vertexbuffer.o volume.o volumetexture.o d3d8.dll.dbg.o -o d3d8.dll.so -L../../dlls -L../../library -lwine -L../../ole -lwine_uuid -L/usr/X11R6/lib -lSM -lICE -lXxf86dga -lXxf86vm -lXv -lXext -lX11 -lGL -lGLU -lm -lc /usr/lib/libgcc.a(_eh.o): In function `__empty': _eh.o(.text+0x9e): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(_eh.o): In function `__get_eh_info': _eh.o(.text+0xec): undefined reference to `pthread_key_create' _eh.o(.text+0x1b9): undefined reference to `pthread_getspecific' _eh.o(.text+0x1d8): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(frame.o)(.text+0x44b): undefined reference to `pthread_mutex_lock' /usr/lib/libgcc.a(frame.o)(.text+0x492): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info': frame.o(.text+0x8d9): undefined reference to `pthread_mutex_lock' frame.o(.text+0x900): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info_table': frame.o(.text+0x969): undefined reference to `pthread_mutex_lock' frame.o(.text+0x990): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__deregister_frame_info': frame.o(.text+0x9dc): undefined reference to `pthread_mutex_lock' frame.o(.text+0xa27): undefined reference to `pthread_mutex_unlock' frame.o(.text+0xa4d): undefined reference to `pthread_mutex_unlock' *** Error code 1

3 2

Re: COM Enhancement patch
by John K. Hohm 21 Nov '02

21 Nov '02

> Well, I was hoping some of the COM experts would comment on that. If > I understand it right you are avoiding writing some thunking routines > for older interfaces, at the cost of an extra pointer access in every > function. I'm not convinced it's a good trade-off, but I'd like to > hear other opinions. I might not exactly be an expert, but I don't like the extra work being done everywhere with the extra pointer. If writing the thunk functions is really so cumbersome, perhaps a macro for generating the thunk functions is in order.

3 2

re: RFC: console & curses
by Dan Kegel 21 Nov '02

21 Nov '02

Eric wrote: > N2: one could try running wineconsole USER backend with ttydrv instead > of x11drv, but that's out of the scope of this (maybe for Dimi's fun > projects list ttydrv is not as far out as all that. I use ttydrv now to run commandline windows programs that output to stdout. I *cannot* use the current Debian wine, because *it uses curses*. Curses renders commandline windows programs useless. Imagine a program that outputs two lines of text. With Wine switching to the alternate text screen on entry, and switching back on exit, *you never see those lines of text, ever*. And with those escape characters gunking up the output, you certainly can't pipe the output of wine running that console program to a file and get anything sensible. Please help make wine safe for running commandline programs from the unix shell - let us select 'ttydrv, no curses' easily somehow! I'm tired of having a separate .wine directory for console programs, and I'm tired of debian's wine (and possibly also the main tree) breaking commandline programs so badly. - Dan

3 4

winspool
by Dimitrie O. Paun 21 Nov '02

21 Nov '02

Folks, On windows people link to winspool as such: -lwinspool In Wine, we need to do: -lwinspool.drv Obviously, this causes problems. Should we create a winspool -> winspool.drv link in dlls/? -- Dimi.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel