wine-devel May 2004

wine-devel@winehq.org

124 participants
249 discussions

ARTSD capture and wine
by Háber János 07 May '04

07 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have a little question Wine why not support artsd in full duplex mode? I try to use skype, it's installed sucessfully, because the capture not work. (Playback and capture work with artsd in same time, tested Krec/XMMS/Sim) Cow - -- Fingerprint: EC31 2ABB 041F DA6C AE7C 6B45 7962 5707 C033 1A33 Public Key: http://boci.eminens.hu/boci.asc Key Identifier: 0xC0331A33 Key Server: wwwkeys.eu.pgp.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAm7+6eWJXB8AzGjMRAk3RAJwLkURXMA8YVwb7w6VzCS2nj0x2HACfYrpJ MOoqXIAmRS1/JSdhFTk1A44= =b6qg -----END PGP SIGNATURE-----

1 0

Question about a FIXME
by William Lahti 07 May '04

07 May '04

I read previously that Daylight Savings Time transition dates were a FIXME. If I knew where to implement them, I will look into implementing them myself.

2 1

Log of wine32 build of wine-20040505
by Ivan Leo Murray-Smith 07 May '04

07 May '04

Log is attached. Ivan.

1 0

RE: WNetGetConnection(): Fix for incorrect drive name and remote name and
by Krishna Murthy 07 May '04

07 May '04

Thanks Alexandre, Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard@winehq.org] Sent: Thursday, May 06, 2004 9:00 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: > 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. Well, this still doesn't answer my question, but never mind, I put the patch in. It's not more incorrect than before anyway, so if you prefer to see something that looks more like a valid path that's OK with me. Just be aware that if any real app tries to do something with the results it will fail just as badly as before. -- Alexandre Julliard julliard(a)winehq.org

1 0

RE: WNetGetConnection(): Fix for incorrect drive name and remote name and
by Krishna Murthy 07 May '04

07 May '04

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@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 07 May '04

07 May '04

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 06 May '04

06 May '04

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 06 May '04

06 May '04

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 06 May '04

06 May '04

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 06 May '04

06 May '04

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@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

← Newer
1
...
16
17
18
19
20
21
22
...
25
Older →

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