July 2002 - Wine-Devel - list.winehq.org

Re: The filedlg95 behaviour

by Ann and Jason Edmeades

This leads to an interesting question. The MSDN states (edited for w2k behaviour but others are teh same): Initial Dir: Pointer to a null terminated string that can specify the initial directory. The algorithm for selecting the initial directory varies on different platforms. Windows 2000: ------------- If lpstrFile contains a path, that path is the initial directory. Otherwise, lpstrInitialDir specifies the initial directory. If lpstrInitialDir is NULL and the current directory contains any files of the specified filter types, the initial directory is the current directory. Otherwise, if the application has used an Open or Save As dialog box in the past, the path most recently used is selected as the initial directory. However, if an application is not run for a long time, its saved selected path will be discarded. *****> Otherwise, the initial directory is the personal files directory of the current user. Otherwise, the initial directory is the Desktop folder. Questions... Windows has the 'personal files' directory set to My Documents - That is why when doing this patch I implemented it that way. If you are saying you would prefer the home directory to be this, then why dont we make the Personal Files registry key always point to the users home directory? We either have complete compatibility eg. files go in ~ which is the Unix methodology, but windows apps looking in \My Documents directly would work, or we can try to slightly unix-ify the windows way and use ~ as the My Documents directory. I'm not convinced a patch should be submitted unless this is addressed. I have no problems assuming my change is not 100% correct, but we dont want a bounce of patches where someone tries to swap it back later to fix a specific unix app. BTW It is not a registry key directly which changes the behaviour, moreover which version of windows is trying to be emulated by Wine at that time. Regards, Jason

July 6, 2002

Re: wine/ dlls/dsound/dsound_main.c dlls/x11drv/x1 ...

by Steven Edwards

> There may be a few, but I guess most of them have > been fixed > already. The remaining calls to 16-bit functions are > mostly in cases > where there is simply no 32-bit counterpart > available. The one I am most interested in ATM is WinExec16. shellexc calls it as part of the DDE support and I am wondering if CreateProcess can be used instead. Thanks Steven __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com

July 6, 2002

Re: ShellExecute placeholder patch

by Eric Pouech

> I would be happy to try that. Do you happen to know an app that uses > that function? My comfort level increases greatly if I can try changes > out on something :-) I used to test ShellExecute with Windows Media Player calling Internet Explorer for displaying an URL ("radio" button for example) A+

July 6, 2002

Re: The filedlg95 behavior

by Duane Clark

Andriy Palamarchuk wrote: > > I think this is a correct behavior of the file > dialog. If an application is started with an icon > what's the sense of having e.g. starting directory for > Word it's binary directory? Well, I guess I have (almost) never started a wine app by clicking an icon. Perhaps I am atypical. > On other hand I agree with you that default directory > value should be set not to C:\My Documents, but to the > home directory. We currently map the user home > directory to one of the drive letters. You can submit > a patch to the default Wine registry to point the > default document directory to the home directory > drive. I don't see an easy way to do that, as the registry seems to be rather picky. If I stick "~" in the registry, it comes up in C:\windows\desktop. How it came up with that I don't know. Trying "HOME" (the label in config) comes up in "My Computer". For that matter, so does "D:". Only a precise entry, like "D:\\" works for me, so I don't know of an automatic way to tell the registry where home is.

July 6, 2002

Re: The filedlg95 behavior

by Andriy Palamarchuk

--- Duane Clark <dclark(a)akamail.com> wrote: > I was hoping to perhaps provoke discussion of the > new behavior of the > file dialog. Prior to this patch: > > http://www.winehq.com/hypermail/wine-cvs/2002/06/0028.html > > the default behavior was to start the open file > dialog in the current > directory. After the patch, the default behavior is > to start in the > C:\My Documents directory, though this can be > changed with a registry key. [skipped] I think this is a correct behavior of the file dialog. If an application is started with an icon what's the sense of having e.g. starting directory for Word it's binary directory? On other hand I agree with you that default directory value should be set not to C:\My Documents, but to the home directory. We currently map the user home directory to one of the drive letters. You can submit a patch to the default Wine registry to point the default document directory to the home directory drive. Andriy __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com

July 6, 2002

Re: wine/ dlls/dsound/dsound_main.c dlls/x11drv/x1 ...

by Alexandre Julliard

Steven Edwards <steven_ed4153(a)yahoo.com> writes: > With this patch I can now build dsound on Mingw if I > import ntdll. Are there going to be other places like > this where the A/W function can be used rather then > the 16? There may be a few, but I guess most of them have been fixed already. The remaining calls to 16-bit functions are mostly in cases where there is simply no 32-bit counterpart available. -- Alexandre Julliard julliard(a)winehq.com

July 6, 2002

Re: warcraft 3

by Rizsanyi Zsolt

On Friday 05 July 2002 18:34, Bobby Bingham wrote: > On Fri, Jul 05, 2002 at 10:10:46AM +0200, Rizsanyi Zsolt wrote: > > On Friday 05 July 2002 01:53, Bobby Bingham wrote: > > > After buying Warcraft 3, and reading on the mailing list that the beta > > > had worked under wine, I decided to try the final version under wine. > > > It installed fine, but won't run. Or rather, when I try to run it, it > > > prints this out, and just sits there: > > > > > > fixme:cdrom:CDROM_GetIdeInterface CD-ROM device with major ID 11 not > > > supported > > > fixme:cdrom:CDROM_GetIdeInterface CD-ROM device with major ID 11 > > > not supported > > > > You have an scsi cdrom drive. My code works just with the ide cdrom > > drives. > > it's actually an ide cdrom, using the ide-scsi emulation for cdrecord and > cdrdao. if i turn off the scsi emulation, these messages go away, but it > still doesn't work. If you have windows NT or win2000 installed on the same machine, it would be nice if you could send me the export of the registry keys under LocalMachine/HARDWARE/DEVICEMAP/Scsi Thanks Zsolt Rizsanyi

July 6, 2002

Re: ShellExecute placeholder patch

by Duane Clark

Eric Pouech wrote: > Duane Clark a écrit : > >>As the comment to ShellExecute states, there can be placeholders in >>commandlines retrieved from the registry. For example, MS Installer has >>this string: > > [snip] > Hi Duane, > > It would be better IMO to merge actually ShellExecute and ShellExecuteEx > Most of what you need is already in ShellExecute but not in > ShellExecuteEx > (of course, ShellExecute should call ShellExecuteEx, but this isn't done > yet) I would be happy to try that. Do you happen to know an app that uses that function? My comfort level increases greatly if I can try changes out on something :-)

July 5, 2002

Re: Floppy handling Fix

by Alexandre Julliard

Keith Matthews <keith_m(a)sweeney.demon.co.uk> writes: > 1 - Fix incorrect reporting of no media in floppy drive as > permissions problem. > 2 - Provide partial workaround for very long delays (c. 40 sec per > lookup, about 7 minutes to set up file browser) on lookups to > floppy drive not physically present (e.g. laptop with floppy or > CD setup) I'm not sure why you are trying to duplicate the kernel permission checks, this is clearly wrong. You should simply do an open and check errno to find out what went wrong. Also there's no point in having a DRIVE_NO_MEDIA flag since this is a temporary condition. For the case of open succeeding with no floppy drive, I think you could handle it by checking if the subsequent read() fails. -- Alexandre Julliard julliard(a)winehq.com

July 5, 2002

The filedlg95 behavior

by Duane Clark

I was hoping to perhaps provoke discussion of the new behavior of the file dialog. Prior to this patch: http://www.winehq.com/hypermail/wine-cvs/2002/06/0028.html the default behavior was to start the open file dialog in the current directory. After the patch, the default behavior is to start in the C:\My Documents directory, though this can be changed with a registry key. While this is the default behavior on Windows, I am not sure that wine should copy this behavior so precisely. I personally think that the old behavior was better. I would think that very few Linux users would actually use the C:\My Documents directory. But perhaps my own preferences are coloring my views. I think the command line oriented nature of Linux would call for a occasional differences in behavior. Duane

July 5, 2002