wine-devel

wine-devel@winehq.org

9 participants
84458 discussions

Re: AFM files no longer required
by Alexandre Julliard 25 May '01

25 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > I actually gave quite a bit of thought to the large file issue before > submitting it, and I would agree with you if there were any functional > code in the file. Because it's entirely data, and it's heavily > interdependent, I really think that one file is better. I disagree. If the data is so interdependent that you cannot split the file, you are doing something wrong IMO. And in fact splitting it will help enforce a clean data structure, which is a major advantage. > From a build point of view, gcc has no problem at all with the file. In > fact it compiles much faster than many of Wine's functional files. I know some older versions of gcc had problems with large data structures, using exponential memory to compile them or something like that. > If a > target compiler (does Wine build with anything other than gcc?) does have > a problem with it, I will yield to necessity. Until that happens, how- > ever, I believe that the practical benefit of maintainability outweighs > stylistic concerns. (After all, it's not like anyone will ever need to > read all the way through the file to understand it, as is the case with > functional code.) You may not need to read every single line, but you still need to go through it if you want to understand the structure (this is how I noticed it was too large...). So please consider splitting it. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: AFM files no longer required
by Ian Pilcher 25 May '01

25 May '01

Forgot to cc wine-devel. Alexandre Julliard wrote: > > You should really split it into separate files, a 40,000 lines file is > a bit too much. Also all this data must be constant and in a read-only > section, it's eating 400k of data space right now. I actually gave quite a bit of thought to the large file issue before submitting it, and I would agree with you if there were any functional code in the file. Because it's entirely data, and it's heavily interdependent, I really think that one file is better. (As the person most likely be tweaking the data in the near future, I can tell you that having a single file to edit, albeit a long one, will be heck of a lot easier than having 39 separate files, and isn't that really the point?) >From a build point of view, gcc has no problem at all with the file. In fact it compiles much faster than many of Wine's functional files. If a target compiler (does Wine build with anything other than gcc?) does have a problem with it, I will yield to necessity. Until that happens, how- ever, I believe that the practical benefit of maintainability outweighs stylistic concerns. (After all, it's not like anyone will ever need to read all the way through the file to understand it, as is the case with functional code.) I would like to make the data constant, but that would require major surgery to afm.c, which is more than I can take on at this point. Keep in mind that the same amount of memory is being used currently; it's just dynamically allocated as the AFM files are read in. > > I'm guessing that you have a script to generate all this; could you > please consider submitting it? This way other people can make changes > too. > I have attached the two programs I use to generate agl.c. I have always intended to submit them, but didn't know where in the source tree to put them. -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Re: Small fixes in controls/menu.c
by gerard patel 25 May '01

25 May '01

At 03:42 AM 22/05/2001 +0200, you wrote: >In attachement WIN.3_11 you can see listing generated under windows 3.11. >( Borland WinSight ) (If you want get a listing generated under win98/95 - no >problem , but I'll have to format&reinstall ,because this copy of windows >stopped functioning about 6 months ago ) >WINE_SETWINPOS ,WINE_NCALC- under wine with first and second version of >patch. >I think WINE_NCALC is more similar to WIN.3_11 . There is nothing looking like a SetWindowPos call between WM_INITMENU and WM_INITPOPUPMENU, yes. But as Alexandre Julliard was pointing, it does not mean that something like calling NC_HandleNCCalcSize is done. >I'm wondering why menu->Height == 0. I'll investigate it. height = 0 because at some point the menu has been changed; this is a Wine flag to signal that the menu dimensions have to be calculated again. The problem with my test app without my original patch is that the menu sizes are not calculated at this point so the mouse clicks are ignored Btw, I have downloaded several of the availables app on your web site and I don't see anything wrong with menus; IIRC I have tried 7.5 for Win3.11, and trial versions 8 and 9 (32 bits). Is it with the main menu that you see this problem ? Gerard

2 1

Re: Unused OPTIONS variable in configure.in
by Alexandre Julliard 25 May '01

25 May '01

Fran=E7ois Gouget <fgouget(a)codeweavers.com> writes: > I noticed that OPTIONS is not used anymore in 'configure.in'. I > believe it may have been used to store the --enable-* stuff at one ti= me > but AFAIU this is now stored in 'config.h'. So I propose to remove it > altogether. Or is it set as a side effect of some standard autoconf > macro on some exotic system? It's here so that you can specify extra flags that configure doesn't know about, by doing OPTIONS=3D-Dfoo ./configure. This can be useful in some cases. --=20 Alexandre Julliard julliard(a)winehq.com

1 0

Re: AFM files no longer required
by Alexandre Julliard 25 May '01

25 May '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > I decided to put all of the data into dlls/wineps/agl.c, since changing > the glyph list data without regenerating the font metrics data would > cause things to break in extremely bizarre ways. (Well, it will once I > actually use the glyph names.) You should really split it into separate files, a 40,000 lines file is a bit too much. Also all this data must be constant and in a read-only section, it's eating 400k of data space right now. I'm guessing that you have a script to generate all this; could you please consider submitting it? This way other people can make changes too. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Strange Wine Problems
by r.maurizzi＠gvs.it 25 May '01

25 May '01

That's the same kernel problem that plagues Lotus Notes (If I've understood correctly the message in German ;-) Lotus Notes will die with the same problem if you use a SuSE 7.0 with SuSE kernel 2.2.18 (Mandrake kernels have the same problem, according to other people here) If you compile the kernel yourself starting from ftp.kernel.org's sources, all is well (at least for Notes). I didn't try SuSE Kernels 2.2.19 / 2.4.2 however. Ciao, Roberto.

1 0

Re: PATCH: mirc dcc send
by Dmitry Timoshkov 25 May '01

25 May '01

"Marcus Meissner" <marcus(a)jet.franken.de> wrote: > + /* This might be a DOS device we do not handle yet ... */ > + FIXME("(%) not detected as DOS device!\n",devname); ^^^ Seems a typo to me.

1 0

Strange Wine Problems
by Josef.Wegner＠t-online.de 25 May '01

25 May '01

Hi, I have some strange errors with wine the last few weeks. Everytime I try to start an application (mainly Ultima Online and Baldur's Gate) wine crashes (stops) with this errors: >wine client.exe For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8071580: read : Die Ressource ist zur Zeit nicht verfügbar fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403938fc,00000138,3):stub fixme:pthread_kill_other_threads_np For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8067660: read : Die Ressource ist zur Zeit nicht verfügbar Beendet Protocol error:0x8075258: read : Die Ressource ist zur Zeit nicht verfügbar I don't know what the problem is. My first thought was that I have problems with my sound drivers (Alsa 0.5.11) , so I tried the kernel emu10k1 driver and after that I loaded no sound module. All with the same result. The only other thing I did with my linux installation was upgrading to a 2.2.18 kernel. My system specs: Latest wine cvs SuSE Linux 7.0 All updates from Suse.com (new glibc 2.1.3) Kernel 2.2.18 (SMP) Alsa 0.5.11 KDE 2.1.1 Xfree86 4.0.3 (Ximera on) Dual PIII 500Mhz 384 MB Ram Adaptec AIC-7880 Ultra SCSI host adapter Matrox G400 Max Dualhead SoundBlaster Live! Value Regards -Josef Wegner

1 0

Re: More wine beginner questions
by Alexandre Julliard 23 May '01

23 May '01

Francois Gouget <fgouget(a)free.fr> writes: > So according to the dll separation rules we must not make msvcrt > depend on an API not exported by a regular windows dll. But in the case > of ntdll I'm not sure. Can we use native ntdll in Wine? I don't think so > since it also exports things like 'wine_dbgstr_[aw]n?'. So maybe we can > bend the rules a little and export _vsnwprintf anyway. A better solution would be to put the *wprintf functions inside libwine_unicode. -- Alexandre Julliard julliard(a)winehq.com

1 0

More wine beginner questions
by Mike Bond 23 May '01

23 May '01

I was just perusing through msvcrt and noticed that in wcs.c there is an implementation of _vsnwprintf, which also exists, verbatim, in it's entirety, in ntdll/wcstring.c. Unless I am misunderstanding the .spec files there appears to be a method of "forward"ing a symbol to an external implementation, such as: @ forward -noimport wcslen ntdll.wcslen Is there any particular reason this was not done for _vsnwprintf as well? There is even a comment in the wcs.c copy saying to mirror any fixes in the ntdll copy. Also, on perhaps a style note, I've noticed some implementations are prefixed by the dll name in all caps, such as MSVCRT_vfprintf, and some are not, such as _wmkdir. Is this just personal style or is there more to these differences? -- TTFN MikeB

2 1

Configuration/Announce
by eric pouech 23 May '01

23 May '01

with today's CVS commit (for those who stay up to date with the latest developments), you'll have to modify your Wine configuration to reflect the changes. First of all, your Wine configuration file now needs a WinMM section containing the following: [WinMM] "Drivers" = "wineoss.drv" "WaveMapper" = "msacm.drv" "MidiMapper" = "midimap.drv" Not adding this will print the following message > You didn't setup properly the config file for the Wine multimedia modules. > Will use the hard-coded setup, but this will disapear soon. > Please add a WinMM section to your Wine config file. Note that the above configuration will be shortly required, so don't wait before setting your configuration up Next, you have also to add a key to your registry. To do so, create a sample file (let's call it foo) containing the following text: [HKEY_LOCAL_USER\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap] 989041554 "AutoScheme"=dword:00000000 "CurrentInstrument"="#0" "UseScheme"=dword:00000000 then goto the <wine>/programs/regapi and compile the program the run: regapi setValue < foo that's it Not applying the key in the registry will result in various errors in MIDIMAP_ functions (mainly if Wine is set up to use a native Windows system) Maintainers are welcome to update theirs packages accordingly (default values are in documentation/samples/config & winedefault.reg) Detailed information is available in documentation/multimedia.sgml. A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

3 3

Re: Configuration/Announce
by Alexandre Julliard 22 May '01

22 May '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > First of all, your Wine configuration file now needs a WinMM section > containing the following: > [WinMM] > "Drivers" = "wineoss.drv" > "WaveMapper" = "msacm.drv" > "MidiMapper" = "midimap.drv" > > Not adding this will print the following message > > You didn't setup properly the config file for the Wine multimedia modules. > > Will use the hard-coded setup, but this will disapear soon. > > Please add a WinMM section to your Wine config file. > Note that the above configuration will be shortly required, so don't > wait before setting your configuration up Please keep the defaults. There is no reason to force people to update their configuration file when there are workable defaults that we can use. Ideally Wine should behave reasonably even with an empty configuration file; this is not entirely possible because things like paths don't have reasonable defaults, but forcing people to specify things that we could guess is not user-friendly. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Small clean up
by Francois Gouget 22 May '01

22 May '01

On Tue, 22 May 2001, Dmitry Timoshkov wrote: > Hello. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Small clean up. > > diff -u cvs/wine/dlls/kernel/comm.c wine/dlls/kernel/comm.c > --- cvs/wine/dlls/kernel/comm.c Sun Apr 22 07:54:54 2001 > +++ wine/dlls/kernel/comm.c Thu May 17 14:21:58 2001 > @@ -535,7 +535,7 @@ > return IE_HARDWARE; > } else { > unknown[port] = SEGPTR_ALLOC(40); > - bzero(unknown[port],40); > + memset(unknown[port], 0, 40); > COM[port].fd = fd; > COM[port].commerror = 0; > COM[port].eventmask = 0; Checking for other instances of this problem I found one in 'misc/comm.c'. But CVS claims that: cvs server: misc/comm.c is a new entry, no comparison available Yet I'm pretty sure I did not create such a file. But when a file is deleted CVS should not give me such a message. Is it because I made changes to these files (probably traces) that CVS did not dare delete them? But shouldn't it say 'was removed, no comparison available'? I also have this message for: cvs server: dlls/ddraw/ddraw/dga.c is a new entry, no comparison available cvs server: dlls/ddraw/ddraw/x11.c is a new entry, no comparison available cvs server: dlls/winspool/winspool.spec is a new entry, no comparison available cvs server: misc/comm.c is a new entry, no comparison available -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Broadcast message : fin du monde dans cinq minutes, repentez vous !

2 1

Re: Anybody know int-31?
by Alexandre Julliard 22 May '01

22 May '01

Bob Goodwin <goodie1(a)pacbell.net> writes: > When calling the save/restore handler function, the only parameter > passed is a byte in AL to indicate whether to save the current context > or restore a saved context. My question is, are there multiple copies of > the save/restore function or at least multiple entry points? It seems > that this would be the only way of having multiple unique context saves. No, the app is supposed to allocate a buffer of the right size (as returned by the int31 call) and pass it to the save/restore function in ES:EDI. Anyway, I'm not sure you need this functionality at all, the current implementation should work OK (except that it needs a dummy protected mode entry point). -- Alexandre Julliard julliard(a)winehq.com

1 0

vxd support?
by Osvaldo Fornaro 22 May '01

22 May '01

Hi, I were far from the project for a while, so sorry if this topic is trivial, but I wish to use a parallel port scanner with wine. Under Windows, appears a device to treat the parallel port as a SCSI port, but is based on a VxD archive, and wine don't find it. Is there any solution to deal with VxD or not yet? Thanks in advance. -- Dr. Osvaldo Fornaro <ofornaro(a)exa.unicen.edu.ar> Universidad Nacional del Centro de la Provincia de Buenos Aires Instituto de Física de Materiales Tandil - CICPBA Pinto 399 (B7000GHG) Argentina

3 3

Question on exposing non-windows functions from dlls...
by Mike Bond 22 May '01

22 May '01

I just submitted a patch to wine-patches that provides the implementation of spawnl and spawnlp. I had been hoping to implement execl and execlp as well but found that the underlying functionality that I would need is not exposed outside scheduler/process.c. My question is what guidelines are there, if any, are there to exposing non-win functions, such as exec_wine_binary in scheduler/process.c? Also, from just a cursory glance at exec_wine_binary that I may need to wrap it to do some of the work that fork_and_exec and PROCESS_Create are doing, such as calling DOSFS_GetFullName. I'm not sure what, if anything, the server would need to know about this. -- TTFN MikeB

3 5

Re: Patch for a bug in server/select.c
by Alexandre Julliard 22 May '01

22 May '01

Bang Jun-Young <bjy(a)mogua.org> writes: > It has been observed that poll always returns POLLNVAL without waiting > when fd is -1. Then we cannot use the current code on NetBSD, otherwise we'll be eating 100% CPU as soon as an fd becomes -1. You'll probably need to do a poll() wrapper that removes the invalid fds before calling the real poll. Or you could ask the NetBSD folks to fix their implementation. -- Alexandre Julliard julliard(a)winehq.com

2 1

history of CVS files?
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How can I see the history of files in CVS? Is there a WebCVS access provided? Reason: I have a 20010112 version of wine running fine but current CVS version does not start any windows application. - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7CiQypm53PRScYygRAuZsAKDhwkJRltKTFWU8Dtmg4DHIOGkYMwCgsusj Izxj4GqmLT7dYzVkEpZVHjA= =DzY7 -----END PGP SIGNATURE-----

3 2

problem starting winword 97SR2
by Heiko Nardmann 22 May '01

22 May '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When starting WinWord I get a dialog saying that either I have not enough work space or memory space. The program exits then. So after playing with the debug options I found out that this happens after a key named "Office.SharedMemory.1" is accessed inside the registry. Can someone tell me what to do to make word no longer complain? BTW: I use wine 20010112 since the last snapshot 20010418 does not work on my machine (unhandled exception). Here is the last line from the logfile when starting wine with '+reg': trace:reg:NtOpenKey (0x80000000,L"Office.SharedMemory.1",0,0x405b6d10) - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7COAjpm53PRScYygRAibvAKCXFuh51LK3S//Ber6iQSjgjvrmNwCffRTy MRUAdaCXrhST+oDmu5WHjtg= =2kDj -----END PGP SIGNATURE-----

3 6

Re: Small fixes in controls/menu.c
by gerard patel 22 May '01

22 May '01

At 10:20 AM 20/05/2001 -0700, you wrote: >gerard patel <gerard.patel(a)asi.fr> writes: > >> (patch using NC_HandleNCCalcSize instead of SetWindowPos) >> >> IMO it's better and it solves my problem as well. > >I think the SetWindowPos one was better. If the app handles >WM_NCCALCSIZE we shouldn't try to bypass it. But does Windows send this message in this case ? From what I can see in the traces, I don't think so. Maybe Maciek could look at the behaviour of his app under Windows. Or I could download it and try to solve the problem myself (I'd better not :-/) Gerard

2 1

Re: Wine build failure in tools/winebuild/spec16 due to recent change
by Ove Kaaven 21 May '01

21 May '01

On Mon, 21 May 2001, Marcus Meissner wrote: > Changelog: > In case our stat already supports 64bit operations (like FreeBSD > stat does), we don't need to stub them, we can just define the > x64 functions to x. You know, glibc would also have such an interface if you used the -D_FILE_OFFSET_BITS=64 compilation option. Wouldn't it be simpler to unify the 64-bit interface code by using that?

1 0

Re: warning fixes
by Francois Gouget 21 May '01

21 May '01

On Mon, 21 May 2001, eric pouech wrote: > ChangeLog: fixed a couple of warnings This does not fix the warnings, it just hides the bug. As the comments say, the assignments are plain wrong in the first place. /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__environ = GetEnvironmentStringsA(); + MSVCRT__environ = (char**)GetEnvironmentStringsA(); MSVCRT___initenv = MSVCRT__environ; /* FIXME: This is plain wrong, we must convert from a '\0' separated * memory block to an array of pointers to string format. */ - MSVCRT__wenviron = GetEnvironmentStringsW(); + MSVCRT__wenviron = (WCHAR**)GetEnvironmentStringsW(); MSVCRT___winitenv = MSVCRT__wenviron; -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

1 0

Anybody know int-31?
by Bob Goodwin 21 May '01

21 May '01

I want to run an application that requires win95 but relys heavily on DOS interupt functions. Specifically it requires interupt 31 which is just a stub in Wine. It appears (from R.B.'s list) that there is no limit on calls to interupt_31-AX=0305 (request the address of (?:the:a) save/restore handler.) That implies more than one thread could have a save/restore pointer. When calling the save/restore handler function, the only parameter passed is a byte in AL to indicate whether to save the current context or restore a saved context. My question is, are there multiple copies of the save/restore function or at least multiple entry points? It seems that this would be the only way of having multiple unique context saves. It would be differrent if a unique `handle' was returned by int_31 instead of a call address. If only one context can be stored at a time, do I need a spin-lock within the save/restore function to keep other applications holding until their turn? Thanks. Bob Goodwin

1 0

Re: Networking with Mandrake 8.0 and SuSE 7.1
by Steve Fox 21 May '01

21 May '01

This weekend I upgraded to Mandrake's 2.4.4 kernel from Cooker (since it fixed both my mouse and token ring) and suddenly this problem has gone away (using Notes 5.0.7 and wine-20010305). I'm still planning to go through Mandrake's 2.2.19 SRPM and find which patch messes things up (I can't use a Linus-only kernel because I need reiserfs). I will post again once I have narrowed down the list of suspects. I'm guessing it has to be a common patch since SuSE seems to have the same symptoms. Steve Fox IBM Linux Technology Center http://www.ibm.com/linux/ltc http://k-lug.com

1 0

Re: Small fixes in controls/menu.c
by Alexandre Julliard 21 May '01

21 May '01

gerard patel <gerard.patel(a)asi.fr> writes: > But does Windows send this message in this case ? From what > I can see in the traces, I don't think so. Maybe Windows does this differently then. But doing the NC calculation without sending a WM_NCCALCSIZE does not seem right. -- Alexandre Julliard julliard(a)winehq.com

1 0

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