wine-devel February 2004

wine-devel@winehq.org

132 participants
261 discussions

Re: VarRound implementation
by Fabian Cenedese 20 Feb '04

20 Feb '04

>Without a test how can you know if this implementation produces the correct values? What about variant type conversions? It seems silly to send a patch without testing it... I just saw that I submitted a patch with some debug code in it. I guess I'll have to send it again anyway :) bye Fabi

1 0

Re: VarRound implementation
by chmorgan＠charter.net 20 Feb '04

20 Feb '04

Without a test how can you know if this implementation produces the correct values? What about variant type conversions? It seems silly to send a patch without testing it... Chris > > From: Fabian Cenedese <Cenedese(a)indel.ch> > Date: 2004/02/19 Thu AM 08:20:21 EST > To: wine-patches(a)winehq.org > Subject: VarRound implementation > > Hi > > This is the implementation of the Variant Round function. I tried to also create a test > function. But I didn't manage to. > > > > Changelog: > Fabian Cenedese <Cenedese(a)indel.ch> > Implementation of Variant Round function. > > Index: wine/dlls/oleaut32/oleaut32.spec > =================================================================== > RCS file: /home/wine/wine/dlls/oleaut32/oleaut32.spec,v > retrieving revision 1.64 > diff -u -r1.64 oleaut32.spec > --- wine/dlls/oleaut32/oleaut32.spec 21 Jan 2004 22:24:08 -0000 1.64 > +++ wine/dlls/oleaut32/oleaut32.spec 19 Feb 2004 13:09:04 -0000 > @@ -170,7 +170,7 @@ > 172 stdcall VarInt(ptr ptr) > 173 stdcall VarNeg(ptr ptr) > 174 stdcall VarNot(ptr ptr) > -175 stub VarRound # stdcall (ptr long ptr) > +175 stdcall VarRound(ptr long ptr) > 176 stdcall VarCmp(ptr ptr long long) > 177 stdcall VarDecAdd(ptr ptr ptr) > 178 stdcall VarDecDiv(ptr ptr ptr) > Index: wine/dlls/oleaut32/variant.c > =================================================================== > RCS file: /home/wine/wine/dlls/oleaut32/variant.c,v > retrieving revision 1.87 > diff -u -r1.87 variant.c > --- wine/dlls/oleaut32/variant.c 17 Feb 2004 20:25:41 -0000 1.87 > +++ wine/dlls/oleaut32/variant.c 19 Feb 2004 13:09:04 -0000 > @@ -3437,6 +3437,94 @@ > return hRet; > } > + > +/********************************************************************** > + * VarRound [OLEAUT32.175] > + * > + * Perform a round operation on a variant. > + * > + * PARAMS > + * pVarIn [I] Source variant > + * deci [I] Number of decimals to round to > + * pVarOut [O] Destination for converted value > + * > + * RETURNS > + * Success: S_OK. pVarOut contains the converted value. > + * Failure: An HRESULT error code indicating the error. > + * > + * NOTES > + * - Floating point values are rounded to the desired number of decimals. > + * - Negative values are rounded nearer to zero (and not bigger in absolute). > + * - Some integer types are just copied to the return variable. > + * - Some other integer types are not handled and fail. > + */ > +HRESULT WINAPI VarRound(LPVARIANT pVarIn, int deci, LPVARIANT pVarOut) > +{ > + HRESULT hRet = S_OK; > + > +wine_dbg_printf("FABI: VARIANT: VarRound1\n"); > + > + TRACE("(%p->(%s%s),%d)\n", pVarIn, debugstr_VT(pVarIn), debugstr_VF(pVarIn), deci); > + > + switch (V_VT(pVarIn)) > + { > + /* cases that fail on windows */ > + case VT_I1: > + case VT_UI2: > + case VT_UI4: > + hRet = DISP_E_BADVARTYPE; > + break; > + > + /* cases just copying in to out */ > + case VT_UI1: > + V_VT(pVarOut) = V_VT(pVarIn); > + V_UI1(pVarOut) = V_UI1(pVarIn); > + break; > + case VT_I2: > + V_VT(pVarOut) = V_VT(pVarIn); > + V_I2(pVarOut) = V_I2(pVarIn); > + break; > + case VT_I4: > + V_VT(pVarOut) = V_VT(pVarIn); > + V_I4(pVarOut) = V_I4(pVarIn); > + break; > + > + /* cases we need to do math */ > + case VT_R4: > + if (V_R4(pVarIn)>0) { > + V_R4(pVarOut)=floor(V_R4(pVarIn)*pow(10, deci))/pow(10, deci); > + } else { > + V_R4(pVarOut)=ceil(V_R4(pVarIn)*pow(10, deci))/pow(10, deci); > + } > + V_VT(pVarOut) = V_VT(pVarIn); > + break; > + > + case VT_R8: > + if (V_R8(pVarIn)>0) { > + V_R8(pVarOut)=floor(V_R8(pVarIn)*pow(10, deci))/pow(10, deci); > + } else { > + V_R8(pVarOut)=ceil(V_R8(pVarIn)*pow(10, deci))/pow(10, deci); > + } > + V_VT(pVarOut) = V_VT(pVarIn); > + break; > + > + /* cases we don't know yet */ > + default: > + FIXME("Not yet implemented, V_VT(pVarIn) = 0x%X, deci = %d\n", > + V_VT(pVarIn) & VT_TYPEMASK, deci); > + hRet = DISP_E_BADVARTYPE; > + } > + > + if (FAILED(hRet)) > + V_VT(pVarOut) = VT_EMPTY; > + > + TRACE("returning 0x%08lx (%s%s),%f\n", hRet, debugstr_VT(pVarOut), > + debugstr_VF(pVarOut), V_VT(pVarOut) == VT_R4 ? V_R4(pVarOut):-1); > + > + return hRet; > +} > + > + > /********************************************************************** > * VarMod [OLEAUT32.154] > * > > > > >

2 1

Re: Setup .inf files
by Shachar Shemesh 20 Feb '04

20 Feb '04

Chris Morgan wrote: >The best documentation I've found thus far for inf files, >http://www.leeos.com/infdoc.html#Top, doesn't have anything about running >programs from inside of an inf file. If this is possible it would probably >make more sense to have the inf file register the dlls. > > The way to have an INF run a file is by registering it with (if I recall correctly - it has been over four years now) RunOnceEx/Setup in the registry. For those who don't follow - RunOnceEx/Setup is a list of programs to run, executed synchroniously (i.e. - one does not start until the previous one exits), and displaying a small window showing where we are along the process). This brings up a small window with the list of tasks to carry out immediatly after the INF processing is done. There are two problems with this approach: 1. While RunOnceEx/Setup is being processed after each login, the mechanism that runs it after INF processing has always been a mystery to me. I have found no method, other than running an INF, of triggering a processing of RunOnceEx/Setup. 2. Wine(boot) does not currently handle that at all. We currently rely on some helper application that does that for us, that usually gets installed as part of the IE installation. The combination of 1+2 means that it'll probably take some time for Wine's INF processing to work like Windows on this one. -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/

3 4

wine using xp from a dual boot machine?
by r00d00 20 Feb '04

20 Feb '04

Hi I'm in the process of moving over to Linux, I've recently set my machine up dual boot with my old XP Pro and my lovely new Gentoo. However it would be really useful to be able to still access my windows apps in Linux, can I set up wine to use the already installed and configured windows xp setup in this machine. So again in case it doesn't make sense - I want to use the XP files and folders that are already on the machine that would be used when I boot into XP but I want to use them with wine in Linux. Is this possible? I tried it a bit but got very mixed results: I could run things like notepad, but could run bigger apps like word. Is there somethings I should be aware of, or settings maybe I haven't considered important? Many thanks for any help. My config file if it's of any use. ====================================================== WINE REGISTRY Version 2 ;; All keys relative to \\Machine\\Software\\Wine\\Wine\\Config ;; If you think it is necessary to show others your complete config for a ;; bug report, filter out empty lines and comments with ;; grep -v "^;" ~/.wine/config | grep '.' ;; ;; 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) ;; ;; NOTICE: Uncomment and modify the drives you want to use. ;;[Drive A] ;;"Path" = "/mnt/fd0" ;;"Type" = "floppy" ;;"Label" = "Floppy" ;;"Filesystem" = "win95" ;;"Serial" = "87654321" ;;"Device" = "/dev/fd0" [Drive C] "Path" = "/C" ;;"/home/webdev/.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" [Drive F] "Path" = "/tmp" "Type" = "hd" "Label" = "Tmp Drive" "Filesystem" = "win95" [Drive H] "Path" = "/H" "Type" = "hd" "Label" = "H" "Filesystem" = "win95" [Drive Z] "Path" = "/home/webdev/" "Type" = "network" "Label" = "Root" "Filesystem" = "win95" [wine] "Windows" = "c:\\WINDOWS" "System" = "c:\\WINDOWS\\system" ;;"System32" = "c:\\WINDOWS\system32" "Temp" = "f:\\" "Path" = "c:\\WINDOWS;c:\\WINDOWS\\system;c:\\WINDOWS\\system32;f:\\;h:\\;z:\\" "Profile" = "c:\\Documents and Settings\\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" = "winxp" ; 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" [AppDefaults\\msimn.exe\\DllOverrides] ; For ie6 "*comctl32" = "builtin" ; For Outlook97 "mapi" = "native, builtin" "mapi32" = "native, builtin" ; Native dlls needed for various parts of the install "ole32" = "native, builtin" "compobj" = "native, builtin" "ole2" = "native, builtin" "ole2nls" = "native, builtin" "ole2conv" = "native, builtin" "ole2prox" = "native, builtin" "ole2thk" = "native, builtin" "storage" = "native, builtin" "olepro32" = "native, builtin" "rpcrt4" = "native, builtin" "oleaut32" = "native, builtin" "msvcrt" = "native, builtin" "wininet" = "native, builtin" ; for the ie runonce "setupapi" = "native, builtin" "devenum" = "native, builtin" "quartz" = "native, builtin" "urlmon" = "native" "shdocvw" = "native, builtin" "jscript" = "native, builtin" "wintrust" = "native, builtin" "shlwapi" = "native, builtin" "secur32" = "native, builtin" "crypt32" = "native, builtin" "ddraw" = "native, builtin" ; allow launching user.exe (for Remedy) "*user.exe" = "native,builtin" ; default for all other dlls "*" = "builtin, native" [AppDefaults\\IEXPLORE.EXE\\DllOverrides] ; For ie6 "*comctl32" = "builtin" ; For Outlook97 "mapi" = "native, builtin" "mapi32" = "native, builtin" ; Native dlls needed for various parts of the install "ole32" = "native, builtin" "compobj" = "native, builtin" "ole2" = "native, builtin" "ole2nls" = "native, builtin" "ole2conv" = "native, builtin" "ole2prox" = "native, builtin" "ole2thk" = "native, builtin" "storage" = "native, builtin" "olepro32" = "native, builtin" "rpcrt4" = "native, builtin" "oleaut32" = "native, builtin" "msvcrt" = "native, builtin" "wininet" = "native, builtin" ; for the ie runonce "setupapi" = "native, builtin" "devenum" = "native, builtin" "quartz" = "native, builtin" "urlmon" = "native" "shdocvw" = "native, builtin" "jscript" = "native, builtin" "wintrust" = "native, builtin" "shlwapi" = "native, builtin" "secur32" = "native, builtin" "crypt32" = "native, builtin" "ddraw" = "native, builtin" ; allow launching user.exe (for Remedy) "*user.exe" = "native,builtin" ; default for all other dlls "*" = "builtin, native" [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" = "Y" ; 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" ; Use a desktop window of 640x480 for Wine "Desktop" = "1024x768" ; 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" ;; sample AppDefaults entries ;[AppDefaults\\iexplore.exe\\DllOverrides] ;"shlwapi" = "native" ;"rpcrt4" = "native" ;"ole32" = "native" ;"shdocvw" = "native" ;"wininet" = "native" ;"shfolder" = "native" ;"shell32" = "native" ;"shell" = "native" ;"comctl32" = "native" ; ;[AppDefaults\\setup.exe\\x11drv] ;"Desktop" = "800x600" ; ;[AppDefaults\\sol.exe\\Version] ;"Windows" = "nt40" ; ;; Some games (Quake 2, UT) refuse to accept emulated dsound devices. ;; You can add an AppDefault entry like this for such cases. ;[AppDefaults\\pickygame.exe\\dsound] ;"EmulDriver" = "N" ;; Kazaa Lite [AppDefaults\\KazaaLite.kpp\\DllOverrides] "*" = "builtin, native, so" ;"shdoclc" = "native" "shdocvw" = "native" "shlwapi" = "native" "commctrl" = "native" ;"comdlg32" = "native" "oleaut32" = "native" "ole32" = "native" ;[AppDefaults\\_INS5576._MP\\x11drv] ;"Desktop" = "640x480" # </wineconf>

1 0

[WINE] Weird windows systems
by Joshua Hudson 19 Feb '04

19 Feb '04

There are two weird windows cases that might be not be of much value but quite interesting. I have specs. 1) LFN on Windows 3.1 This actually can happen (Winver=3.1, Dosver=7.0). This should be supported LFN on Windows 2000, XP I have verified, the DOS 7 LFN interface works on 2000 and XP Perhaps this should be made to work on wine nt4 mode. 2) Win 3.1 running PE executables Fundamentally weird, but I have specs (OH, and the files required to do this were released by Microsoft for free redistribution) _________________________________________________________________ Click, drag and drop. My MSN is the simple way to design your homepage. http://click.atdmt.com/AVE/go/onm00200364ave/direct/01/

1 0

Re: PATCH wine/controls/button.c paint_button() : "style" range checking
by Alexandre Julliard 19 Feb '04

19 Feb '04

Vincent Pelletier <subdino2004(a)yahoo.fr> writes: > Checks for out-of-range value in "style" (paint_button function): > must be style<MAX_BTN_TYPE or memory violation (reading unpredictable > btyes) occurs, and as it's then used as a function address that could > lead to random code execution. If you really want an assertion you should use assert(), at least then it can be compiled out. And if it's a condition that can legitimately happen, then it has to be handled properly, just adding an ERR doesn't improve anything. In this case I guess it's conceivable that the app would change the style to an invalid one, so it needs to be handled. -- Alexandre Julliard julliard(a)winehq.org

3 3

Re: need some info about Wine
by Brian Vincent 19 Feb '04

19 Feb '04

> [1] did the application like IVR (commercial software for linux) will work > on this Wine for linux. > [2] similarly Automatic call distributor could be executed on linux. Good luck getting any Windows telephony software working, especially an ACD platform. Have you seen http://www.asterisk.org ? > [3] could you please tell me the full dependencies for Wine and the > installation guide for Wine & the configuration info to execute the > application. Please read the documentation at http://www.winehq.org Specifically, http://www.winehq.org/site/docs/wine-user/index > Kindly reply me soon , otherwise I will have to develop on my own efforts. Does that mean you're volunteering to develop the tapi32 DLL? -brian

1 0

Re: [documentation] running.sgml
by Dimitrie O. Paun 19 Feb '04

19 Feb '04

On Wed, 18 Feb 2004, Brian Vincent wrote: > + files you might want to consider using Winefile. This Winelib > + application comes with Wine and can be found in /usr/local/bin. I'm not sure it's wise to hardcode /usr/local/bin into the documentation, it may not be installed there... -- Dimi.

1 0

Re: PATCH: programs/winetest/gui.c fix
by Dimitrie O. Paun 19 Feb '04

19 Feb '04

On Thu, 19 Feb 2004, Gerald Pfeifer wrote: > - default: > + default: ; Oh, just remove it altogether... -- Dimi.

1 0

Re: How do you completely remove wine and start over?
by Ivan Leo Murray-Smith 19 Feb '04

19 Feb '04

Sorry wrong list. Didn't click the stop button fast enought. Ivan.

1 0

Re: How do you completely remove wine and start over?
by Ivan Leo Murray-Smith 19 Feb '04

19 Feb '04

> Do I still need it? No, wineinstall is only needed if installing from the source code. Ivan.

1 0

the lord of the code
by Ivan Leo Murray-Smith 19 Feb '04

19 Feb '04

http://www.geekculture.com/joyoftech/joyarchives/533.html Ivan.

1 0

Win Api Monitor
by Fabian Cenedese 19 Feb '04

19 Feb '04

Hi For figuring out what my program does on Windows I was looking for an Api Monitor, kinda the Windows counterpart of +relay. So I came across this page. It didn't quite help me but it's maybe useful for others. Just be sure to set a process filter or your computer will stop responding as it's overflowed with messages (as happened with me :) http://www.rohitab.com/apimonitor/ bye Fabi

1 0

Re: scanf problem
by Ivan Leo Murray-Smith 19 Feb '04

19 Feb '04

> Try the following patch (compiles, but not tested - I don't use msvcrt). Thanks for the patch, it works perfectly, send it to wine-patches. Ivan.

2 1

What's with command.com / cmd.exe
by Boaz Harrosh 19 Feb '04

19 Feb '04

Some programs, mostly installations also others, look for command.com or cmd.exe to spun commands and batch files. This fails in current wine installation. I know they are not suppose to do that they should use an API, but they do. (What is the API for that and is it supported by wine?) I have soft linked wineconsol.exe.so to \windows\command\command.com in win98 mode. (%systemdir%\cmd.exe in WinNT/XP) And it works OK. (did not yet try WinNT mode). 1) Is this the way to do it? Or are there hidden problems that can arise. (I guess what the application is doing is eventually CreatProcess on command.com/cmd.exe). If so how are we with command-line/Internal-commands compatibility with command.com or cmd.exe? 2) If 1. than should that be done in the regular Install/winecfg session? Or each user to himself. Where are these files in the different windows versions? (By the way same problem in cxoffice) Free Life Boaz

1 0

legal problem for using DLL's
by Erik Dekeyser 19 Feb '04

19 Feb '04

Dear WINE Developers, Briefly with Bricscad IntelliCAD we have an almost-clone of AutoCAD and we are very successfull in selling it to large corporations under a Coporate License Agreement. Several of our Corporate clients want to start with implementing LINUX in their organization. For their engineering departments they need an AutoCAD alternative that is 100% compatible with it and that can be learned by an AutoCAD user in less then 3 hours. BricsCad has invested a lot in making our version of IntelliCAD a stable, relaible and performant CAD software, that is so close to AutoCAD. We have it now ready in a beta version on LINUX. The products name will be BricsCad for Linux and will use WINE. BricsCad for Linux vs AutoCAD is comparable to what Open Office is vs MS Office. We will support three versions: Red Hat, Suse and Java Desktop. Press release is ready. OUR PROBLEM: We are wondering if we can distribute the Microsoft DLL's with the application without infringing the copyright of Microsoft. The alternative is rewrite some of them, but that would require a couple of months of development and postponing the release of the software. I guess we are not the only ones with this problem? Looking forward to your point of view Erik De Keyser CEO BricsCad www.bricscad.com

6 5

Can't compile crosstest
by Jakob Eriksson 19 Feb '04

19 Feb '04

I have noticed I can't compile the crosstests, how can I make it compile? ------------------------- cc1: warning: -fPIC ignored for target (all code is position independent) ../../../tools/make_ctests capture.c dsound.c propset.c >testlist.c || rm -f testlist.c i586-mingw32msvc-gcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o testlist.cross.o testlist.c cc1: warning: -fPIC ignored for target (all code is position independent) i586-mingw32msvc-gcc capture.cross.o dsound.cross.o propset.cross.o testlist.cross.o -o dsound_crosstest.exe -ldsound -luser32 -lkernel32 -ldxguid -luuid -lm propset.cross.o(.text+0xc40): In function `propset_private_tests': /home/jakov/src/wine/dlls/dsound/tests/propset.c:100: undefined reference to `CLSID_DirectSound8' propset.cross.o(.text+0xda0):/home/jakov/src/wine/dlls/dsound/tests/propset.c:120: undefined reference to `CLSID_DirectSoundCapture8' propset.cross.o(.text+0xe50):/home/jakov/src/wine/dlls/dsound/tests/propset.c:130: undefined reference to `CLSID_DirectSoundFullDuplex' propset.cross.o(.text+0xf00):/home/jakov/src/wine/dlls/dsound/tests/propset.c:140: undefined reference to `CLSID_DirectSoundPrivate' propset.cross.o(.text+0xfba):/home/jakov/src/wine/dlls/dsound/tests/propset.c:151: undefined reference to `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x1076):/home/jakov/src/wine/dlls/dsound/tests/propset.c:159: undefined reference to `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x1132):/home/jakov/src/wine/dlls/dsound/tests/propset.c:167: undefined reference to `DSPROPSETID_DirectSoundDevice' propset.cross.o(.text+0x123b):/home/jakov/src/wine/dlls/dsound/tests/propset.c:183: undefined reference to `DSPROPSETID_DirectSoundDevice' make[3]: *** [dsound_crosstest.exe] Error 1 make[3]: Leaving directory `/home/jakov/src/wine/dlls/dsound/tests' make[2]: *** [tests/__crosstest__] Error 2 make[2]: Leaving directory `/home/jakov/src/wine/dlls/dsound' make[1]: *** [dsound/__crosstest__] Error 2 make[1]: Leaving directory `/home/jakov/src/wine/dlls' make: *** [dlls/__crosstest__] Error 2 jakov@dmlive:~/src/wine$

2 1

need some info about Wine
by pooja barmola 19 Feb '04

19 Feb '04

Hello sir , myself is working on linux platform. I want to execute the applications that run on windows , to be executed on linux platform. [1] did the application like IVR (commercial software for linux) will work on this Wine for linux. [2] similarly Automatic call distributor could be executed on linux. [3] could you please tell me the full dependencies for Wine and the installation guide for Wine & the configuration info to execute the application. Kindly reply me soon , otherwise I will have to develop on my own efforts. Thanking you Pooja

1 0

About automatic configuration
by Robert van Herk 18 Feb '04

18 Feb '04

Hi... As I'm working (a bit) on winecfg, I noticed the following line on the todo list Wine installation process should install and configure wine But of course, winecfg also needs some automatic probing of at least disks, since there is a "Autodetect me" button in Winecfg for that. Also, Chris Morgan made a cool feature that autodetects your sound system. I was thinking to write a DLL that would export some functions to autodetect stuff... That DLL could then be called from both the installation (or directly after the installation) to auto-setup both sound and harddisks, and could later on be used from winecfg if something ever changes. Plz give me your opinion on my idea. Is this about what was meant by the remark in the todo-list? Would there be any standards to follow for this kind of functionality? Or should I just hack around a bit? Or is something completely different intended / needed? Grtz, Robert

1 0

scanf problem
by Ivan Leo Murray-Smith 18 Feb '04

18 Feb '04

Apparently there is a problem with wine's scanf. this code #include <stdio.h> int main() { int a; printf ("Type a number\n"); scanf ("%d", &a); printf ("You've entered %d\n", a); return 0; } works as expected on linux, but on wine returns [ivan@localhost ivan]$ wine test.exe Type a number 5 You've entered 1076166144 [ivan@localhost ivan]$ Dimi thinks it's a bug and asked me to fwd this to wine-devel, a very similar program that has the same problem works on windows, I can't test this one because I do't currently have access to a windows box, but unless I've some badly bugged header or something like that, this is a bug. a msvcrt.dll trace follows [ivan@localhost ivan]$ wine test.exe --debugmsg +msvcrt trace:msvcrt:DllMain (0x407d0000, DLL_PROCESS_ATTACH, 0x1) pid(8), tid(9), tls(0) trace:msvcrt:msvcrt_init_mt_locks initializing mtlocks trace:msvcrt:msvcrt_init_io :handles (0x14)(0x24)(0x2c) trace:msvcrt:msvcrt_init_console :Opening console handles warn:msvcrt:msvcrt_init_console :Console handle Initialisation FAILED! trace:msvcrt:msvcrt_init_args got 'test.exe', wide = L"test.exe" argc=1 trace:msvcrt:MSVCRT_setlocale (0 C) trace:msvcrt:_lock (19) trace:msvcrt:_lock (17) trace:msvcrt:_lock : creating lock #19 trace:msvcrt:_unlock (17) trace:msvcrt:_unlock (19) trace:msvcrt:DllMain finished process init trace:msvcrt:MSVCRT___set_app_type (1) Console application trace:msvcrt:__getmainargs (0x403000,0x403004,0x407bff10,-1,0x407bff14). trace:msvcrt:_lock (9) trace:msvcrt:_lock (17) trace:msvcrt:_lock : creating lock #9 trace:msvcrt:_unlock (17) trace:msvcrt:_unlock (9) trace:msvcrt:MSVCRT_atexit (0x4013b0) trace:msvcrt:_onexit (0x4013b0) trace:msvcrt:_lock (13) trace:msvcrt:_lock (17) trace:msvcrt:_lock : creating lock #13 trace:msvcrt:_unlock (17) trace:msvcrt:_onexit expanding table trace:msvcrt:_unlock (13) Type a number warn:msvcrt:MSVCRT_fscanf 0x408068e0 ("%d"): semi-stub trace:msvcrt:_read :fd (0) handle (0x14) buf (0x40363f18) len (512) 5 trace:msvcrt:_read :EOF trace:msvcrt:_read "5\n" trace:msvcrt:MSVCRT_fscanf returning 1 You've entered 1076166144 trace:msvcrt:MSVCRT__cexit (void) trace:msvcrt:DllMain (0x407d0000, DLL_PROCESS_DETACH, 0x1) pid(8), tid(9), tls(0) trace:msvcrt:msvcrt_free_mt_locks : uninitializing all mtlocks trace:msvcrt:_fcloseall :closed (0) handles trace:msvcrt:_close :fd (0) handle (0x14) trace:msvcrt:msvcrt_free_fd :fd (0) freed trace:msvcrt:_close :ok trace:msvcrt:_close :fd (1) handle (0x24) trace:msvcrt:msvcrt_free_fd :fd (1) freed trace:msvcrt:_close :ok trace:msvcrt:_close :fd (2) handle (0x2c) trace:msvcrt:msvcrt_free_fd :fd (2) freed trace:msvcrt:_close :ok trace:msvcrt:msvcrt_free_console :Closing console handles trace:msvcrt:DllMain finished process free [ivan@localhost ivan]$ Ivan.

4 3

wine/controls/button.c (get_button_text) : potential memory leak
by Vincent Pelletier 18 Feb '04

18 Feb '04

In get_button_text, the returned handle must be freed by caller (-> memory leak if it forgots about it). That could be solved using something like : /* BEGIN */ /* in button.c */ inline static void get_button_text(HWND hwnd, WCHAR *out, INT max_len) { INT len = MIN(GetWindowTextLengthW( hwnd ), max_len); GetWindowTextW( hwnd, buffer, len + 1 ); } /* everywhere needed */ #define MAX_BUTTON_TEXT_LEN 255 /* just as an example */ caller_func(HWND hwnd) { WCHAR button_text[MAX_BUTTON_TEXT_LEN]; /* can also be dynamicaly allocated of course */ get_button_text(hwnd, button_text, MAX_BUTTON_TEXT_LEN); /* do something with gathered string */ } /* END */ So, why wouldn't I do it myself ? Because I'm getting lost in sources :). I only crawl wine code for only 48 hours now... So about 5 hours of effective crawling. Vincent Pelletier

1 0

Re: Dll separation - Winedos from kernel32
by Eric Pouech 18 Feb '04

18 Feb '04

Steven Edwards a écrit : > Hello, > This was from a totaly foolish attempt at building winedos on Mingw. I > was hoping we could create a ntvdm for ReactOS. I guess we are not > planning on totaly rewritting winedos to deal with Erics new filesystem > stuff right? So we could just move this call here. this is already taken care of in one of the patches I sent A+

1 0

Fixing the SysParametersInfoW->A crosscall
by Justin Chevrier 18 Feb '04

18 Feb '04

Just a note that i'm working on correcting the SysParametersInfoW -> SysParametersInfoA crosscall, so that there's no duplicated effort I thought i'd send a message to wine-devel. I hope to have a patch in the next couple of days. Justin Chevrier _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

1 0

WINE plugins
by KappaM KappaM 18 Feb '04

18 Feb '04

Hi, I have an application and a Netscape plugin that run in Windows. That plugin is correctly loaded by either Netscape or my application. Now I need to "port" these modules on Linux. To do so I recompiled my application with the WineLib environment, I modified/added the interface function of my plugin and alse recompiled it with the WineLib environment. Every thing works fine if the plugin is loaded by my application. The problem arises when I try to load the plugin by Linux-Mozilla, as the plugin is not recognized. I think that the problem is due to the fact that the wine environment is not active, is it correct? Is it possible to load the wine environment to work only with the plugin (not with an application)? Do you have any suggestions to make my WinePlugin loadable by Linux Mozilla ? Thanks in advance Katia _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

2 1

headers: define SPI_* values introduced in XP
by Kevin Koltzau 18 Feb '04

18 Feb '04

Changelog Define SPI_* values introduced in XP

1 0

← Newer
1
2
3
4
5
6
7
...
11
Older →

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 February 2004