- Wine-Devel - list.winehq.org

RE: WNetGetConnection(): Fix for incorrect drive name and remote name and
by Krishna Murthy May 7, 2004

May 7, 2004

We have used the attached sample to test this. The patch I have sent earlier had two fixes; Fix-1 (wide character string) and Fix-2 (Remote Path Name). Basically we have Team Developer product which generates the runtime win32 applications. These generated application are behaving differently on Win32 and Wine. Please find attached the sample win32 application that demonstrates the behavior of WNetGetConnection API. 1. The sample has hard coded the network drive name as "N:\" for this demonstration. Please map a new network drive named "N:\" before running this sample program. 2. In Wine, apply the fix-1 (wide character issue) before applying fix-2 to see the different behavior. 3. Invoke Menu item Test->GetRemotePath Thanks, Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard(a)winehq.org] Sent: Thursday, May 06, 2004 11:57 AM To: Krishna Murthy Cc: wine-devel(a)winehq.org Subject: Re: WNetGetConnection(): Fix for incorrect drive name and remote name and Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > We did some analysis and come to conclusion that QueryDosDevice is a > better choice than GetVolumeInformation. What sort of analysis? Do you have an app that needs that, and if so why is returning a Unix path better? What does the app do with it? -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: Nuke winedefault.reg references
by Alexandre Julliard May 7, 2004

May 7, 2004

Vincent Béron <vberon(a)mecano.gme.usherb.ca> writes: > Changelog: > Remove remaining references to winedefault.reg and replace them by > wine.inf. I don't think we want to document the rundll32 thing; if users have to know about this we are doing something wrong. What we should do is document winecfg and wineprefixcreate, but it may be best to wait for them to actually work... -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: Destroy a window used for testing on exit of the metafile test
by Alexandre Julliard May 6, 2004

May 6, 2004

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > the main reason of the XRender error on dlls/gdi/tests/metafile.c exit > is fixed now. Anyway, I think it's a good programming practice to free > resources on a program exit. Not really, resources are going to be freed automatically anyway, and that's something that needs to be tested too. As shown by the XRender error, that test is exercising some interesting code paths, so I think it's much better to keep it the way it is. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Only child windows receive WM_SHOWWINDOW in DestroyWindow() under Windows
by Alexandre Julliard May 6, 2004

May 6, 2004

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > it's an old patch synchronized with current CVS. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Only child windows receive WM_SHOWWINDOW in DestroyWindow() under Windows. It's not merged properly, you now have two ShowWindow calls, and WINPOS_ActivateOtherWindow will never be called. -- Alexandre Julliard julliard(a)winehq.org

1 0

Filesystem bug
by Steven Edwards May 6, 2004

May 6, 2004

Hello, I noticed this when I was playing around with DCOM and IE installers today. If you run the dcom9x or ie setup programs and pass the /C /T:path flags Wine is creating the destination directory twice. Here is a example wine dcom95.exe /C /T:C:\temp will extract the files to C:\temp\temp rather than C:\temp like it should I just double checked this with ie6setup to make sure it wasnt user error and it really is doing it. wine ie6setup.exe /C /T:C:\tp1 dumps the files in C:\tp1\tp1 Thanks Steven __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

1 0

RE: WNetGetConnection(): Fix for incorrect drive name and remote name and
by Krishna Murthy May 6, 2004

May 6, 2004

We did some analysis and come to conclusion that QueryDosDevice is a better choice than GetVolumeInformation. As you indicated, since network path of the wine's network drive is not pointing to a real network path, neither of them going to return the remote path of the network drive. Since 'QueryDosDevice' retrieves a local path for the network drive (from wine config file), this will be a better choice than GetVolumeInformation. Please find attached diff taken with diff -u Thanks, Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard(a)winehq.org] Sent: Wednesday, May 05, 2004 12:05 PM To: Krishna Murthy Cc: wine-devel(a)winehq.org Subject: Re: WNetGetConnection(): Fix for incorrect drive name and remote name and Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > - Long Description: > 1. WNetGetConnectionA calls WNetGetConnectionW without converting > single character string "drive name" to wide character string. Fix is > to convert the single character string "drive name" to wide character > before calling WNetGetConnectionW. > 2. WNetGetConnectionW() returns drive's label instead of remote name. > Fix is to call QueryDosDeviceW instead of GetVolumeInformationW It's not clear to me that QueryDosDeviceW is a better choice, neither of them is going to return a valid remote name anyway. What does your app need to do with the remote name? And BTW please send diff -u patches. -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: Resend: Fix toolbar getstyle
by Mike Hearn May 6, 2004

May 6, 2004

On Thu, 2004-05-06 at 13:57 +0200, BELLENGE Maxime FTRD/DMI/REN wrote: > As I got no comments on this patch and it is not applied, I resend it. http://source.winehq.org/source/dlls/comctl32/toolbar.c#L3488 It looks like it has already been applied :) thanks -mike

2 2

Re: Vertical font problem
by paolo inzaghi May 6, 2004

May 6, 2004

In attachment the zip file containing the Visual Studio project. Regards, Paolo >From: Shachar Shemesh <wine-devel(a)shemesh.biz> >To: paolo inzaghi <winedev(a)hotmail.com> >CC: wine-devel(a)winehq.org >Subject: Re: Vertical font problem >Date: Wed, 05 May 2004 20:02:34 +0300 > >paolo inzaghi wrote: > >>Hi, >>I'm porting a Windows application to Wine and I found 2 problems. >>For simplicity I wrote a simple Window application (attached to the mail) >>that use two TextOut to write the strings "Horizontal" and "Vertical". >>The text is written horizontally and vertically, setting the lfEscapement >>field of the LOGFONT structure respectively to 0 and 900. >>The application, compiled with MSVC 7.0, works fine in Windows, but it has >>two problems when it is executed inside with wine-20040408 environment. >> >>First problem: >>after the application starts, the two strings are not shown. >>To see the strings in Linux, I force the sending of a WM_PAINT message >>when the user right click the mouse. >>By the way, if you minimize and then restore the application, the strings >>disappear. >> >>Second problem: >>even when shown, the vertical text is not correctly shown. A large amount >>of space is left between the string characters. >>Note that the problem arise every time you set the lfEscapement to >>something different from 0. >>If I use 3600 to show the "Horizontal" string, it also is badly shown (in >>theory 3600 should be equivalent to 0). >> >>Please, could you help me ? >> >>Regards >>Paolo >> >Can you send the project with the zip file? I don't feel like running >precompiled binaries in this day and age. > > Shachar > >-- >Shachar Shemesh >Lingnu Open Source Consulting >http://www.lingnu.com/ > _________________________________________________________________ Invia allegati fino a 20MB con Hotmail Extra Storage! Provalo! http://join.msn.com/?pgmarket=it-it&page=hotmail/es

1 0

Help Porting Application To Linux
by MIKEL CARRASCO May 6, 2004

May 6, 2004

Hi all, A few weeks ago we sent the following message to the Wine newsgroup at Usenet and we were told that it was better to send it here, so here it goes: We are trying to port an application from Windows to Linux. This application is clearly divided in two parts: the first one is the graphic interface, which makes an intensive use of COM, MFC, databases and other MS Windows technologies; the second is the application's "kernel" (nothing to do with the Linux kernel), which carries out all the processing. This "kernel" has been created using mostly plain C. The project needs to be done quite quickly so we've been thinking of using Wine to speed up the process of porting. Thus, we would run the graphic interface using Wine, while we would compile our application's kernel in Linux and it would run as a normal Linux process. In fact we have already managed to run the GUI using wine and it seems to work (more or less). We have compiled most of the kernel too. The main problem we are facing is communication between the GUI and the kernel. Under Windows we do so by means of shared memory (CreateFileMapping, ...) and we don't know very well how to do it in Linux. We have done some tests with Winelib and it seems like we are getting something. However, later on we need our kernel to run as a real time task by means of RTAI, and we don't know if that is even possible with Wine/Winelib. Anybody knows if such a thing is possible? If that's not feasible, I guess we will have to go look how Wineserver works, so we can make our own XXXFileMapping functions to call them from our application's kernel and let us have access to Wineserver's services. But we don't know wether this is posible or if it would be a good solution to our problem. Another possible solution we've been thinking of is to tweak the Wineserver, so it does the file mapping the way we want (place in memory, format, etc.) and we can read/write it from our application's kernel using plain C functions. Can anybody help us, please? Which one do you think would be the best solution? Thank you very much for your help. ______________________________________ Mikel Carrasco I + D Software. Fagor Automation S. Coop. P. O. Box 144 E-20500 Mondragón-Arrasate Spain Tel. ++34 943 71 92 00 Fax. ++34 943 79 17 12 www.fagorautomation.com * Este mensaje y los documentos que, en su caso, lleve anexos, pueden contener información confidencial. Por ello, se informa a quien lo reciba por error que la información contenida en el mismo es reservada y su uso no autorizado está prohibido legalmente, por lo que en tal caso le rogamos que nos lo comunique por la misma vía , se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato. * Mezu honek eta txertatuta eraman ditzakeen dokumentuek informazio konfidentziala izan dezakete. Hori dela eta, nahi gabe hartzen duenari jakinarazten zaio bertako informazioa erreserbatua dela eta baimenik gabe erabiltzea legez debekatuta dagoela; horregatik, bide beretik guri jakinarazteko eskatzen diogu, eta aldi berean mezuaren kopiarik ez egiteko, beste pertsona bati ez emateko eta berehala ezabatzeko erregutzen diogu." * This message together with any documents attached may contain confidential information. You are informed that if you should receive it by mistake, the information it contains is reserved and its use is not authorized. It is legally prohibited. If you have received this message by mistake, please let us know as soon as possible by e-mail. Do not make any copies of the message, nor send it or give it to anybody else. Please delete it right away.

4 3

Re: Thanks :)
by Julliard May 5, 2004

May 5, 2004

1 0