- Wine-Devel - list.winehq.org

Re: Wine and industrial communication like OPC
by Rickard Svensson Sept. 8, 2004

Sept. 8, 2004

> > > > Now I also got some questions from your answers: > > > > * Did I understand correctly. Wine doesn't have a built in support for DCom, to be abel to use Dcom I have to add the DCom support from Windows 98 to the Linux system? > > And the problem with that is the MS License, it stops me from distribute those XXX.dll with a Linux product (hardware and software in this case.) > > It doesn't stop you, basically the license says "you must have a Windows > license to use this code". Because it's technically a part of Windows, see? Yyyy! I hate license issues! I can see that for many people this wouldn't be an issue, because they probably have some old Win 98 CD/Licens somewhere (if they even care). But for a company that would like to send it as part of an embedded computer with Linux I can se a lot of problems. > However a Windows license is quite cheap relative to $3000-$4000 for the > APIs so maybe this isn't a problem. But that was per development project, not per system we want to use OPC in. > You could even buy copies of Windows 98 off ebay or something for > ultra-cheap living. The license can be for any version of Windows AFAIK. That could perhaps be an idea.... What does AFAIK stand for? > The difficulty may be that nobody has tested network DCOM servers on > Wine as far as I know, even using Microsofts implementation. So you'd be > doing some pioneering work :) That is good ;-) In the industry we are a lot of people who really question the total madness of letting the OPC standard be that depended on Windows, when it is supposed to be a "free" organization. My hope if I can get this to work is to publish a site on the net so all who want to use Linux in the industrial computing can do that quite easy... But then we have the license issues to :-( > - Wines own, builtin code. This is incomplete and cannot do what you want. > > - Microsofts DCOM implementation > > Wine *does* have support for MSRPC, and I think it's wire compatible > with Windows these days and capable of making simple RPCs. However the > RPC runtime (rpcrt4.dll) is just the first layer of DCOM, all the rest > don't work right yet. Ok, now I understand, and also why I got confused before. And there is a lot of work needed to make DCom to work in Wine? Is someone working on it or is it something that not is that important in other cases? Thanks a lot Mike for you answer! /Rickard -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

5 4

Re: Fix bin2res Help Text
by Dimitrie O. Paun Sept. 7, 2004

Sept. 7, 2004

On Mon, Sep 06, 2004 at 02:37:05AM +0100, Robert Shearman wrote: > " /* BINRES idb_std_small.bmp */\n" > - " {}\n" > + " IDB_STD_SMALL BITMAP idb_std_small.bmp\n" > + " /* {\n" > + " } */\n" What's wrong with the current help. I thought BINRES is the marker... -- Dimi.

1 0

More winecfg todos
by Mike Hearn Sept. 7, 2004

Sept. 7, 2004

On Thu, 29 Jul 2004 23:19:11 -0500, Alexandre Julliard wrote: > Log message: > James Hawkins <truiken(a)gmail.com> > Under the Drives tab, remove the 'Windows Drive' section. You probably want to increase the size of the drive mappings list so it fills the tab, currently there is just a lot of empty space at the top of the pane now you removed the old stuff. Also we should kill the autodetect button. This is done by wineprefixcreate these days, or should be. Other things are: - Drive editing seems broken. The list box only updates the second time I hit edit. err:winecfg:applyDriveChanges unable to set volume label for devicename of 'H:\', label of '' - Browse in the "Add/Edit drive" dialog is a WRITEME - Build system isn't right: I did a cvs update but the res files weren't recreated properly. I had to do a make clean to get the gui updates. - "Add Application" has poor usability: we always use a file browser dialog box even though the most common use case is just "foo.exe", ie the user knows the name and doesn't care about the location. Worse we start in the c:\windows\desktop folder for some reason, meaning users might accidentally select a .lnk file! Ditto for Libraries tab. - The Add/Remove application buttons are *way* too big! - Obviously, once audio autodetection has been moved into the drivers we need to kill the audio tab. - Libraries tab just has generally poor usability, actually. The first item in the radio group is "Builtin" meaning that's the one users are most likely to select, it should be "builtin, native" followed by "native, builtin" - We ask the user to understand a magic * symbol to set the default - what is up with that? - There are no helpful default entries in the drop down box for setting a DLL override, and when you add one the tree does not expand so to actually *set* it you have to expand the tree then select the new override. - We have way too many (eg, more than zero) tree controls in this app. - Drive mappings list is really unclear, there's no separation between the "Drive X:" label and the unix path its mapped to. Basically I'd recommend reading the GNOME HIG: http://developer.gnome.org/projects/gup/hig/ it's a very informative read. Obviously we have to use Win32 UI conventions at least at first, but there's a lot of generically good advice there. Well worth reading for anybody who is going to work on winecfg. thanks -mike

4 4

Re: Create DLL stub files in c:\windows\system
by Hans Leidekker Sept. 7, 2004

Sept. 7, 2004

On Saturday 4 September 2004 14:25, Mike Hearn wrote: > Make apps that search for the DLL files directly happy by creating empty > files for each shipped library There are applications (eDonkey is one of them IIRC) that call LoadLibray() themselves on a number of DLLs. Could be that they do their own linking as part of some anti-debugging technique, I don't know, but it's perfectly legal for application to do that anyway. For these apps having empty DLL files will not be enough. I actually was able to fool the app by putting MinGW cross compiled Wine DLLs in the system directory until it needed kernel32.dll, which doesn't compile. I had to resort to a native win2k kernel32.dll to get it past this but this may still be a good alternative to your empty DLL files. -Hans

8 17

Re: windos: fix EXTENDED COUNTRY INFORMATION
by Vincent Béron Sept. 7, 2004

Sept. 7, 2004

Le mar 07/09/2004 à 06:10, Markus Amsler a écrit : [snip] > *** wine/dlls/winedos/int21.c Tue Aug 24 17:45:23 2004 > --- wine-20040615/dlls/winedos/int21.c Fri Aug 6 11:57:04 2004 > *************** > *** 2116,2123 **** > static void INT21_ExtendedCountryInformation( CONTEXT86 *context ) > { > BYTE *dataptr = CTX_SEG_OFF_TO_LIN( context, context->SegEs, context->Edi ); > ! BYTE buffsize = CX_reg (context); > ! > TRACE( "GET EXTENDED COUNTRY INFORMATION, subfunction %02x\n", > AL_reg(context) ); Please send your patches in diff unified (diff -u) format. Vincent

1 0

Re: Wine Developer Cheatsheet, v1
by Rolf Kalbermatter Sept. 7, 2004

Sept. 7, 2004

"Diego 'Flameeyes' =?ISO-8859-1?Q?Petten=F2?=" wrote: >I have only a doubt: > >> - Is it possible to implement the ANSI version by converting to unicode >> then calling the wide version, rather than duplicate it? > >How can I convert an ansi string to a unicode one and reverse? So I can redo >the patch with the calls :) Typically you use MultiByteToWideChar() for any input strings and then WideCharToMultiByte() for possible output strings. You can look at shlwapi/path.c and other files in there to see how this is usually done. Depending on the place where you do it, it might be preferable to use dynamically allocated buffers instead of using stack space as Wine is already using quite a lot of stack. Principle: WCHAR *textW; INT countW = MultiByteToWideChar(CP_ACP, 0, textA, -1, NULL, 0); if((textW = HeapAlloc(GetProcessHeap(), 0, countW * sizeof(WCHAR)))) { MultiByteToWideChar(CP_ACP, 0, textA, -1, textW, countW); /* Do the Widechar call */ HeapFree(GetProcessHeap(), 0, textW); } Rolf Kalbermatter

4 4

RE: iostream and msvcrt?
by Scott Snell Sept. 7, 2004

Sept. 7, 2004

Hi Dimi, Thanks for helping out. I made the changes you suggested to the gcc-mingw.mak file for STLPort. When I go make it does a: wineg++ -I../stlport -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -mno-cygwin -O2 -D_STLP_USE_DYNAMIC_LIB dll_main.cpp -c -o ../lib/obj/MINGW32/ReleaseD/dll_main.o which throws up a world of errors, such as: In file included from ../stlport/cstdlib:25, from ../stlport/stl/debug/_debug.c:160, from ../stlport/stl/debug/_debug.h:418, from ../stlport/utility:40, from dll_main.cpp:35: /usr/include/c++/3.3.2/cstdlib:97: error: `div' not declared /usr/include/c++/3.3.2/cstdlib:102: error: `ldiv' not declared /usr/include/c++/3.3.2/cstdlib: In function `ldiv_t std::div(long int, long int)': I'm sure its something simple but I'm still not comfortable around gcc/winegcc. thanks, Scott. > -----Original Message----- > From: Dimitrie O. Paun [SMTP:dpaun(a)rogers.com] > > On Wed, Aug 18, 2004 at 11:32:33AM +0300, Boaz Harrosh wrote: > > > > > Better go with gcc-mingw.mak, as threading and OS is more Windows than > > Linux. See if they have a -nocygwin variant. > > Yes, it should work with the gcc-mingw.mak by changing > gcc -> winegcc > g++ -> wineg++ > > > >adding a path pointing to /include/wine/MSVCRT. > > > > > No, you shouldn't need that. You just need to make sure you pass > the -mno-cygwin flag to winegcc/wineg++. > > -- > Dimi.

3 2

Re: PathSearchAndQualify and other shlwapi fixes
by Robert Shearman Sept. 7, 2004

Sept. 7, 2004

Diego 'Flameeyes' Pettenò wrote: >Ok thanks to Mike and Rofl I was able to clean the patch up (at least I hope >so :) > >ChangeLog: >- Write partially PathSearchAndQualify (there is a FIXME) with A->W call >[dlls/shlwapi/path.c] >- Add to PathCreateFromUrl support for file:/// urls (with 3 '/' ) >[dlls/shlwapi/path.c] >- Add to UrlCanonicalize the URL_FILE_USE_PATHURL flag's support. >[dlls/shlwapi/url.c] >- Add to UrlIs support for URLIS_DIRECTORY and URLIS_FILEURL flags >[dlls/shlwapi/url.c] >- Fixes UrlCreateFromPath [dlls/shlwapi/url.c] > > One patch for each atomic change please. It makes it easier to review and more likely to get the changes into CVS. Rob

1 0

Using winelib in python module
by Nikolay A. Liber Sept. 7, 2004

Sept. 7, 2004

Hi All Have anybody tried to use winelib in python modules? I need to make python bindings to some propritary DLL that available as a binary only. I made shared library that simply dynamicaly loads that DLL using winelib mono hack. It works perfectly when I link it with simple C test program but crashes when I load in python module. Just a call to SharedWineInit() causes python to crash Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1075433600 (LWP 2477)] server_init_process () at ../../include/winnt.h:1543 1543 __asm__(".byte 0x64\n\tmovl (0x18),%0" : "=r" (teb)); (gdb) bt #0 server_init_process () at ../../include/winnt.h:1543 #1 0x40497ca7 in thread_init () at thread.c:141 #2 0xbfffc588 in ?? () #3 0x40039500 in dlerror () from /lib/tls/libdl.so.2 #4 0x00000000 in ?? () #5 0xbfffd830 in ?? () #6 0xbfffc588 in ?? () #7 0x404b6140 in forcedWinVersion () from /usr/local/lib/wine/ntdll.dll.so #8 0x4003af54 in ?? () from /lib/tls/libdl.so.2 #9 0x00001f98 in ?? () #10 0x00000000 in ?? () #11 0x00000000 in ?? () #12 0x404b7000 in ?? () #13 0x00001f98 in ?? () #14 0x4003003b in pthread_rwlockattr_setkind_np () from /lib/tls/libpthread.so.0 #15 0x400390b0 in dlsym () from /lib/tls/libdl.so.2 #16 0x4003af54 in ?? () from /lib/tls/libdl.so.2 #17 0xbfffd830 in ?? () #18 0xbfffd830 in ?? () #19 0xbfffc5f8 in ?? () #20 0x40039096 in dlsym () from /lib/tls/libdl.so.2 #21 0x0817fd70 in ?? () #22 0x404b4820 in __JCR_LIST__ () from /usr/local/lib/wine/ntdll.dll.so #23 0xbfffd830 in ?? () #24 0xbfffd820 in ?? () #25 0xbfffc5f8 in ?? () #26 0x40480e48 in __wine_process_init (argc=-1995430796, argv=0xe804245c) at loader.c:2036 Previous frame inner to this frame (corrupt stack?) (gdb) If there are any ways to initialize winelib from python module may be other than mono hack? Please answer by mail fw(a)tehn.ru Thank you

2 1

Re: Wine and industrial communication like OPC
by Rickard Svensson Sept. 7, 2004

Sept. 7, 2004

----- Original Message ----- From: Juan Lang <juan_lang(a)yahoo.com> Date: Sun, 5 Sep 2004 21:59:37 -0700 (PDT) To: riq(a)mail.com Subject: Re: Wine and industrial communication like OPC > > * We want to make a OPC server, because other > > computers want to get information from our system. > > Is there a problem in make a DCOM server, is it the > > "no user can acsas port under 1024 on a Linux > > system" problem. > > It's a problem for lots of reasons. They add up to > this: this is unimplemented in Wine, and probably > won't be implemented any time soon. To bad, I ges that it wil take same time to inplement all the parts of DCom in Wine ;( > > * What I have heard I thought DCom uset RPC??? But > > Juan Lang wrote that Wine doesn't have support for > > RPC > > Did I? I certainly didn't mean it. But you'd need to > install the DCOM98 update to have any chance of > success at it for now, at least if I read the code > right. You wrote: < Date: Thu, 2 Sep 2004 08:27:49 -0700 (PDT) < From: Juan Lang <juan_lang(a)yahoo.com> < This method would allow us to act as a CIFS (TCP port 445) client. < Acting as an SMB (TCP port 139) client isn't handled by the CIFS < module, it's done by the SMBFS module. Not sure what Steve's < plans are here. < Anyway, any of you guys interested in seeing RPC work under Wine < (Greg, you still lurking around here?) might want to play around < with this if you have time. I might myself once I land somewhere < for a while, but no promises. But perhaps I grabd that out of contens, you ment in this case. Thanks a lot Juan for you answer! /Rickard -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm

1 0