- Wine-Devel - list.winehq.org

Re: problem with native dll's.
by Alexandre Julliard April 23, 2001

April 23, 2001

Rein Klazes <rklazes(a)xs4all.nl> writes: > Since the cvs commits early this week or the last (I could be more > precise but that will take a while) I have noticed a problem with some > native dlls. > If I start one app that uses such a dll and then another using the > same dll may crash. If this second app is started as the first process > it runs fine. Most likely my shared sections fix: 2001-04-13 Alexandre Julliard <julliard(a)winehq.com> * server/file.c, server/mapping.c, server/object.h: Repaired shared PE data sections. The fix itself should be OK, but it probably reveals other bugs that were hidden by the fact that the sections were not shared properly before. For instance if a dll stores window handles in the shared area it will break since window handles are not shared yet (working on it...) In your case it doesn't seem to be window handles though, so it may be worth investigating a bit more. -- Alexandre Julliard julliard(a)winehq.com

4 3

Re: Virtual memory under Win95
by Alexandre Julliard April 23, 2001

April 23, 2001

"Dmitry Timoshkov" <dmitry(a)sloboda.ru> writes: > Perhaps applications which use assumptions about Win95 virtual memory > management should be considered as broken? Or it is worth to support them? What should be considered broken is the memory management of Win95 ;-) But yes, we should probably forget about making this kind of things work, we cannot possibly support the Win95 memory model 100% right anyway. Especially since the app works with -winver nt40, I think that's a reasonable work-around. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Msvcrt fixes
by Andreas Mohr April 23, 2001

April 23, 2001

On Mon, Apr 23, 2001 at 12:27:58AM -0700, François Gouget wrote: > Btw, the Linux localtime documentation sucks. It's even worse than > the MS one!!! Err, fix it ? ;-) Really, what is an Open Source programmer supposed to do when he realizes that something sucks ? Food for thought, -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.germany.net/100-30936/

3 3

Virtual memory under Win95
by Dmitry Timoshkov April 23, 2001

April 23, 2001

Hello all. Could anybody with access to a Win95 machine run this simple program and report the result? void test(void) { HANDLE hMapping; void *p; MEMORY_BASIC_INFORMATION info; DWORD dwRet; hMapping = CreateFileMappingA(INVALID_HANDLE_VALUE, NULL, PAGE_READWRITE | SEC_RESERVE, 0, 0x0400f000, NULL); printf("hMapping = %04x\n", hMapping); p = MapViewOfFile(hMapping, FILE_MAP_READ ,0, 0, 0x00010000); printf("p = %p\n", p); UnmapViewOfFile(p); dwRet = VirtualQuery(p, &info, sizeof(info)); printf("VirtualQuery(%p) ret=0x%lx\n" "BaseAddress = %p\n" "AllocationBase = %p\n" "AllocationProtect = 0x%08lx\n" "RegionSize = 0x%08x\n" "State = %08lx\n" "Protect = %08lx\n" "Type = %08lx\n", p, dwRet, info.BaseAddress, info.AllocationBase, info.AllocationProtect, info.RegionSize, info.State, info.Protect, info.Type); } Thanks in advance.

4 6

Re: Virtual memory under Win95
by Alexandre Julliard April 23, 2001

April 23, 2001

"Dmitry Timoshkov" <dmitry(a)sloboda.ru> writes: > From http://msdn.microsoft.com/library/psdk/winbase/filemap_79wn.htm > > --- cut --- > "To fully close a file-mapping object, an application must unmap all mapped views > of the file-mapping object by calling UnmapViewOfFile, and close the file-mapping > object handle by calling CloseHandle. The order in which these functions are called > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > does not matter. The call to UnmapViewOfFile is necessary because mapped views of > ^^^^^^^^^^^^^^^ > a file-mapping object maintain internal open handles to the object, and a file-mapping > object will not close until all open handles to it are closed." > --- cut --- > > My patch is WRONG. MSDN says that until both CloseHandle and UnmapViewOfFile are called > the file-mapping object still exists. This is wrong for NT but true for Win9x. Why do you say it's wrong for NT? It seems perfectly correct: the mapping object exists as long as you have a handle to it, or some view of it is mapped (which keeps a handle internally, just like we do under Wine). Do not confuse the file mapping object with mapped views; the doc only talks about the mapping object. Specific views of the object are unmapped by UnmapViewOfFile (at least under NT), even if this may not cause the mapping object to be deleted. This doesn't contradict the doc at all. -- Alexandre Julliard julliard(a)winehq.com

3 2

DDraw,DGA bug?
by wine＠henkis.net April 22, 2001

April 22, 2001

Hello, I seem to have a problem running Direct Draw under wine, when changing screens is a game i get to keep the old screen and the new screen is being drawed under the old screen. (Seen it by manualy changing resolution). It worked ok earlier, with a a month or so older version of wine. Anyone knows anything about this? Regards Henrik

2 1

problems while using yahoo! messenger
by K.Shyam April 22, 2001

April 22, 2001

hello; i am getting the following error message while running yahoo messenger using linux. can someone help me.i am new to wine as such and it might take some time for me to understand how it exactly works... thank you K.Shyam fixme:win32:DeviceIo_MMDEVLDR (5,(nil),0,0x40394dbc,4,0x405a6ab8,(nil)): stub fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device NWLINK fixme:debug:FlushInstructionCache (0xffffffff,0x42aa1ee8,0x0000000d): stub fixme:debug:FlushInstructionCache (0xffffffff,0x42aa1e00,0x0000000d): stub fixme:debug:FlushInstructionCache (0xffffffff,0x42aa1d10,0x0000000d): stub fixme:accel:CreateAcceleratorTableA should check that the accelerator descriptions are valid, return NULL and SetLastError() if not. fixme:debug:FlushInstructionCache (0xffffffff,0x42aa1b18,0x0000000d): stub err:shell:IShellFolder_fnBindToObject can't bind to a file this is my config file : WINE REGISTRY Version 2 ;; All keys relative to \\Machine\\Software\\Wine\\Wine\\Config ;; ;; MS-DOS drives configuration ;; ;; Each section has the following format: ;; [Drive X] ;; Path=xxx (Unix path for drive root) ;; Type=xxx (supported types are 'floppy', 'hd', 'cdrom' and 'network') ;; Label=xxx (drive label, at most 11 characters) ;; Serial=xxx (serial number, 8 characters hexadecimal number) ;; Filesystem=xxx (supported types are 'msdos'/'dos'/'fat', 'win95'/'vfat', 'unix') ;; This is the FS Wine is supposed to emulate on a certain ;; directory structure. ;; Recommended: ;; - "win95" for ext2fs, VFAT and FAT32 ;; - "msdos" for FAT16 (ugly, upgrading to VFAT driver strongly recommended) ;; DON'T use "unix" unless you intend to port programs using Winelib ! ;; Device=/dev/xx (only if you want to allow raw device access) ;; [Drive A] "Path" = "/mnt/floppy" "Type" = "floppy" "Label" = "Floppy 0" "Device" = "/dev/fd0" [Drive C] "Path" = "/win" "Type" = "hd" "Label" = "MS-DOS 0" "Filesystem" = "win95" [Drive D] "Path" = "/mnt/cdrom" "Type" = "cdrom" "Label" = "CD-ROM 0" "Filesystem" = "win95" "Device" = "/dev/cdrom" [Drive E] "Path" = "/tmp" "Type" = "hd" "Label" = "Tmp Drive" "Filesystem" = "win95" [Drive F] "Path" = "/" "Type" = "network" "Label" = "Root" "Filesystem" = "win95" [Drive G] "Path" = "${HOME}" "Type" = "network" "Label" = "Home" "Filesystem" = "win95" [wine] "Windows" = "C:\\windows" "System" = "C:\\windows\\system" "Path" = "C:\\windows;C:\\windows\\system;E:\\;G:\\" "Profile" = "C:\\windows" "Temp" = "E:\\" "GraphicsDriver" = "x11drv" "ShellLinker" = "wineshelllink" # <wineconf> [DllDefaults] "EXTRA_LD_LIBRARY_PATH" = "${HOME}/wine/cvs/lib" "DefaultLoadOrder" = "native, builtin, elfdll, so" [DllOverrides] "kernel32" = "builtin" "gdi32" = "builtin" "user32" = "builtin" "krnl386" = "builtin" "kernel" = "builtin" "gdi" = "builtin" "user" = "builtin" "toolhelp" = "builtin" "comdlg32" = "elfdll, builtin, native" "commdlg" = "elfdll, builtin, native" "version" = "elfdll, builtin, native" "ver" = "elfdll, builtin, native" "shell32" = "builtin, native" "shell" = "builtin, native" "lz32" = "builtin, native" "lzexpand" = "builtin, native" "commctrl" = "builtin, native" "comctl32" = "builtin, native" "wsock32" = "builtin" "winsock" = "builtin" "advapi32" = "builtin, native" "crtdll" = "builtin, native" "ntdll" = "builtin, native" "mpr" = "builtin, native" "winspool" = "builtin, native" "winspool.drv" = "builtin, native" "ddraw" = "builtin, native" "dinput" = "builtin, native" "dsound" = "builtin, native" "winmm" = "builtin" "w32skrnl" = "builtin" "msvfw32" = "builtin" "mmsystem" = "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" "midimap.drv" = "builtin, native" "w32skrnl" = "builtin" "wnaspi32" = "builtin" "wow32" = "builtin" "system" = "builtin" "display" = "builtin" "wprocs" = "builtin" "wineps" = "builtin" "icmp" = "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" = "Y" ; Run Wine windows in desktop. Contains "N" or something like "800x600". ; Note Wine currently supports this option only on command line. ; So this option has currently no effect. Hope this will change. "Desktop" = "N" ; Use XFree86 DGA extension if present "UseDGA" = "Y" ; Use XShm extension if present "UseXShm" = "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" [fonts] ;Read documentation/fonts before adding aliases "Resolution" = "96" "Default" = "-adobe-times-" [serialports] "Com1" = "/dev/ttyS0" "Com2" = "/dev/ttyS1" "Com3" = "/dev/modem,38400" "Com4" = "/dev/modem" [parallelports] "Lpt1" = "/dev/lp0" [spooler] "LPT1:" = "|lpr" "LPT2:" = "|gs -sDEVICE=bj200 -sOutputFile=/tmp/fred -q -" "LPT3:" = "/dev/lp3" [ports] ;read=0x779,0x379,0x280-0x2a0 ;write=0x779,0x379,0x280-0x2a0 [spy] "Exclude" = "WM_SIZE;WM_TIMER;" [registry] ; Paths must be given in /dir/dir/file.reg format. ; Wine will not understand dos file names here... ;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" ; Use new file format "UseNewFormat" = "Y" ; Registry periodic save timeout in seconds ; PeriodicSave=600 ; Save only modified keys "SaveOnlyUpdatedKeys" = "Y" [Tweak.Layout] ;; WineLook=xxx (supported styles are 'Win31'(default), 'Win95', 'Win98') "WineLook" = "Win95" [programs] "Default" = "" "Startup" = "" [Console] ;Drivers=tty ;XtermProg=nxterm ;InitialRows=25 ;InitialColumns=80 ;TerminalType=nxterm [Clipboard] "ClearAllSelections" = "0" "PersistentSelection" = "1" # </wineconf>

1 0

notes2paper
by Ralf Schwarzmaier April 21, 2001

April 21, 2001

after the last configuration change, i've become an error message, but i don't kno what to do with it, this message sad nothing to me ;-))) thank you bye ralf fixme:mpr:WNetGetUserA ((null), 0x2aa100dc, 0x408d6d38): mostly stub err:listview:LISTVIEW_WindowProc unknown msg be10 wp=04500001 lp=00000450 err:listview:LISTVIEW_WindowProc unknown msg b029 wp=00000000 lp=00000000 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=04500002 lp=00000450 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=04500001 lp=00000450 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=06880001 lp=00000688 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=06880002 lp=00000688 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=06880001 lp=00000688 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=07a80001 lp=000007a8 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=07a80002 lp=000007a8 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=07a80001 lp=000007a8 fixme:system:SystemParametersInfo16 Unknown option 4104. fixme:treeview:TREEVIEW_WindowProc Unknown msg be10 wp=0ab40001 lp=00000ab4 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=0cf00001 lp=00000cf0 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=0cf00002 lp=00000cf0 err:listview:LISTVIEW_WindowProc unknown msg be10 wp=0cf00001 lp=00000cf0 fixme:heap:HeapCreate Shared Heap requested, returning system heap. fixme:crtdll:CRTDLL___dllonexit stub fixme:crtdll:CRTDLL___dllonexit stub fixme:mpr:WNetGetUserA ((null), 0x2a1eb560, 0x408d66fc): mostly stub fixme:mpr:WNetGetUserA ((null), 0x2a34789c, 0x408d6754): mostly stub fixme:system:SystemParametersInfo16 Unknown option 4104. err:statusbar:StatusWindowProc unknown msg be10 wp=1a7c0001 lp=00001a7c err:statusbar:StatusWindowProc unknown msg be10 wp=1b980001 lp=00001b98 fixme:string:GetLocaleInfoA 'SENGLANGUAGE' is not defined for your language (0007). Please define it in dlls/kernel/nls/YourLanguage.nls and submit patch for inclusion into the next Wine release. fixme:toolhelp:CreateToolhelp32Snapshot flags 1 not implemented FATAL: No handler for Win32 routine kernel32.Heap32ListFirst (called from 0x6c252073) fixme:toolhelp:CreateToolhelp32Snapshot flags 1 not implemented FATAL: No handler for Win32 routine kernel32.Heap32ListFirst (called from 0x6c252073) fixme:toolhelp:CreateToolhelp32Snapshot flags 1 not implemented FATAL: No handler for Win32 routine kernel32.Heap32ListFirst (called from 0x6c252073) fixme:toolhelp:CreateToolhelp32Snapshot flags 1 not implemented FATAL: No handler for Win32 routine kernel32.Heap32ListFirst (called from 0x6c252073) fixme:heap:HeapDestroy attempt to destroy system heap, returning TRUE!

1 0

Notes2Paper with wine
by ralf schwarzmaier April 21, 2001

April 21, 2001

hi @ll i have an problem with notes2paper under wine .... i need this for some databases of Notes. my lotus notes client runs perfect, but the additional programm notes2paper not, i can install notes2paper without any problems, direct in wine, but when i start it, it crash with non error message. what can i do, or what are teh parameters for an development debuging log ? thank you bye ralf

1 0

GDB remote debugging for wine
by Ove Kaaven April 21, 2001

April 21, 2001

As we all know, gdb isn't very compatible with wine, since gdb makes so many assumptions about the operating environment that isn't true in wine. But lately it occurred to me that perhaps it's possible to use gdb's remote debugging features to solve these issues. So recently, I've been secretly experimenting with writing gdb-server code in the wineserver. It goes something like this... ./configure --enable-remote-gdb [...blah...] $ wine stuff gdb socket ready at: target remote localhost:1234 $ gdb wine (gdb) target remote localhost:1234 and you're currently able to look at registers, backtrace, list all the threads, change thread, and read process memory... neato. But its usefulness might be quite limited since gdb doesn't know about the dynamically-loaded dlls so it doesn't automatically load their symbols... does anyone have ideas on how to solve that? It doesn't appear that the standard remote protocol have a command to tell gdb, and I don't know how gdb ordinarily does it. I've pondered making wine generate a file full of "add-symbol-file" commands or something that could be executed by gdb, but I don't know how to do that cleanly... preferably hacks for loading symbols should be transparent to the developer, and new symbols loaded automatically after new dlls are loaded. Hmm...

2 1