- Wine-Devel - list.winehq.org

Re: move dosconf to winedos
by Jukka Heinonen Nov. 3, 2002

Nov. 3, 2002

György 'Nog' Jeney wrote: > After applying this patch, please remove msdos/dosconf.c. > > ChangeLog: > * dlls/winedos/dosconf.c > * include/callback.h > * msdos/dpmi.c > * msdos/dosconf.c (removed) > * dlls/ntdll/Makefile.in > * dlls/winedos/winedos.spec > * dlls/winedos/Makefile.in > Move dosconf to winedos. While I appreciate helping me moving stuff to winedos, this patch has some questionable design choices (and a few bugs, too). - Condition (!done && !Dosvm.ReadConfig && !DPMI_LoadDosSystem()) in file msdos/int21.c contains 2-3 bugs (depends on how you count, I shall leave fixing this as an exercise :). - Moving stuff to winedos is supposed to be because it reduces amount of code not required in win32 from ntdll (which this patch does) but also because it reduces dependencies between winedos and ntdll (this patch adds more dependencies than it removes). Because the only reason for ntdll needing dosconf is extended control-break checking state (which is not used by Wine for anything) I think the best would be to move this code to dlls/winedos/int21.c and either remove it from msdos/int21.c or replace it with stub that succeeds but does nothing. - If we really want to add stuff to DOSVM_TABLE, only one function should be necessary. Either winedos always initializes dosconf or it initializes it when the first call to DOSVM_TABLE.GetConfig is made. - Don't use INT21_ReadConfigSys() and Dosvm.GetConfig() pairs. It is better to refactor these into INT21_GetConfigSys which does both. This makes code more readable (and even reduces amount of code generated). -- Jukka Heinonen <http://www.iki.fi/jhei/>

1 0

Important problem with cabextract in debian unstable
by Carlos Lozano Nov. 3, 2002

Nov. 3, 2002

Hello, Debian unstable includes the package cabextract 0.5-1, it is a important problem because, in this version the option -d is broken. Then the function Extract of the builtin urlmon.dll will not work :(( Regards, Carlos. -- ___ _ \ | / Infraestructuras | . |._ _ _| | ___ ___ ___ http://www.andago.com | || ' |/ . |<_> |/ . |/ . \__ GNU/Linux |_|_||_|_|\___|<___|\_. |\___/ _ \ __|\ \ / Carlos A. Lozano <___'/ | \ -_) __/\__ \ > < -_) [ carlos.lozano(a)andago.com ]\___|_| ____/ _/\_\___| [ calb(a)epsxe.com ] http://www.epsxe.com

3 2

menu resource parsing question...
by Chris Morgan Nov. 3, 2002

Nov. 3, 2002

Upon the testing of Kazaa lite I ran into numerous errors like: err:menu:MENU_ParseResource not a string item, flags: 0x0800 These entries appear to be intended as separators and in fact the flag of 0x800 is MF_SEPARATOR. The code in question is : if (!IS_STRING_ITEM(flags)) ERR("not a string item, flags: 0x%04x\n", flags ); Where IS_STRING_ITEM is a macro: #define IS_STRING_ITEM(flags) (MENU_ITEM_TYPE ((flags)) == MF_STRING) And: #define MENU_ITEM_TYPE(flags) \ ((flags) & (MF_STRING | MF_BITMAP | MF_OWNERDRAW | MF_SEPARATOR)) So, what appears to be occuring is that Kazaa is passing in MF_SEPARATOR as a flag and wine expects instead to get a MF_STRING with a string of null and in MENU_SetItemData() it does 'flags |= MF_SEPARATOR;' I'm only posting to wine-devel because this check has been in the code since the initial import into cvs and I wanted to see if anyone knew more of the background on the issue. The fix is pretty simple, just ignore the fact that IS_STRING_ITEM() returns false. The rest should be taken care of by the existing checks. Thanks, Chris

2 2

Re: msvcrt-A06: _popen + COMSPEC
by Dimitrie O. Paun Nov. 3, 2002

Nov. 3, 2002

On November 3, 2002 10:38 am, Jaco Greeff wrote: > If COMSPEC > is not set, or not found on disk, _popen makes use of > c:\windows\system32\cmd.exe binary. Why not cmd.exe only, and hope to find it in the PATH? I think the PATH in Windows contains windows\system32 in it by default. -- Dimi.

1 0

Re: My WineHQ menu structure proposal
by Andreas Mohr Nov. 3, 2002

Nov. 3, 2002

On Sun, Nov 03, 2002 at 03:07:48PM +0000, Keith Matthews wrote: > On Sun, 3 Nov 2002 15:24:14 +0100 > "Andreas Mohr" <andi(a)rhlx01.fht-esslingen.de> wrote: > > > On Sun, Nov 03, 2002 at 02:28:54AM -0800, Francois Gouget wrote: > > > * Who cares about an 'Applications Database'? What's that anyway? > > > Would a potential Wine user want to have dealings with a database? > > > Nah. Must be for geeks. What users want to know is what applications > > > run in Wine and thus that's how the menu entry and the thing itself > > > should be called: 'Supported Applications'. Even if the truth is > > > that it lists applications that do not work too. > > True. Application Database is somewhat non-descriptive. > > Well, why not call its item "(Non-)Supported Applications" then ? ;-) > > > This seems to be an area where conciseness and descriptiveness are > diametrically opposed. We will probably argue long and hard. My > contribution "Application Support States". Close, but no whole cigar ;-) I like "Application Support Progress" somewhat better. (and "Progress" has a coolness factor associated with it :) Although it's 3 not very short words, so that might disqualify it easily... Hmm, and what about doing away with "Support" entirely ? Then it'd be usable. > > > 6. Miscellaneous > > > 6.1. Community > > > 6.2. Related projects > > > 6.3. Contacts > > > 6.4. Legal > > > > Hmm, (almost) everything ok so far, but can't we do away with Misc ? > > Misc is so horribly non-descriptive. > > IMHO as last entry, it might be better to have "The Wine Team", > > which then includes Community, Contacts and Legal. > > I'm not sure yet about where to put Related Projects (probably About > > would be best), but apart from that... > > > Can't say I like 'Misc' either, and I do think that legal should be more > visible. The project is getting to be fairly visible to governments and > big corporations, and they like to check legalities early on. How about > 'Contacts and Legal'. Then you'd expel "Community", I think (it wouldn't really fit in there). But of course I'm aware that "Legal" might not easily get associated with "The Wine Team". Hmm, this could still need some improvement... -- "My attitude is, everybody should try competing with Microsoft once in their life. Once." - Marc Andreessen, former Netscape lead employee, in a "browser wars" interview

1 0

Today wine's compatibility with 20 popular apps from tucows
by Carlos Lozano Nov. 3, 2002

Nov. 3, 2002

Hello :) I have taken the 20 first entries of the top 100 tucows list, except that some entries has been removed, mainly antivirus and programs what need other different program to work. (URL: http://tucows.uam.es/toppicks.html) Comments, improves, ... are welcomed :)) Regards, Carlos. -- ___ _ \ | / Infraestructuras | . |._ _ _| | ___ ___ ___ http://www.andago.com | || ' |/ . |<_> |/ . |/ . \__ GNU/Linux |_|_||_|_|\___|<___|\_. |\___/ _ \ __|\ \ / Carlos A. Lozano <___'/ | \ -_) __/\__ \ > < -_) [ carlos.lozano(a)andago.com ]\___|_| ____/ _/\_\___| [ calb(a)epsxe.com ] http://www.epsxe.com

5 9

Re: My WineHQ menu structure proposal - counterproposal
by Andreas Mohr Nov. 3, 2002

Nov. 3, 2002

On Sun, Nov 03, 2002 at 09:43:40AM +0000, Keith Matthews wrote: > On 02 Nov 2002 23:51:01 -0600 > "Jeremy White" <jwhite(a)codeweavers.com> wrote: > > > > > > So, I propose the following instead: > > > > First, this assumes that we use Jeremy Newman's idea of a rotating > > screen shot on main page, and continued prominence of the news. > > > Ugh. Why do people insist on thinking that 'sexy' images are the be-all > and end-all of web design. When I go to a web site I want _information_, > not some bandwidth-soaking image that gives nothing useful. Have > screen-shots for those that can't see beyond them, but don't put them on > the home page, put a clear link to them. > > A lot of people are still on analogue dial-up links, they don't > appreciate large images increasing download time, I'm on DSL and I > switch off images to get faster downloads. But a screenshot showing a sufficient amount of information should only have about 5 KB or slightly more (I hope :). Also add a subtitle describing the current screenshot, and then 5 KB "ought to be enough for everybody" to be interested about a particular screenshot. > Other than that you may want to promote 'legal' to the top level, if > only to reduce the number of menu options for item 1 at the next level. > 9 is as many as one should have and 7 is a better limit. Yep, 7 is the standard amount of things you can manage/grasp. -- The Declaration of Software Freedom: http://freedevelopers.net/freedomdec/index.php

1 0

games
by Mark Hannessen Nov. 3, 2002

Nov. 3, 2002

>> Game-wise: >> Jazz Jackrabbit 2 >> Fallout > Neverwinter Nights > Grand Prix Legends Discworld II Wing Command 4 ( use the win95 exe instead of the dos exe ) most games i own install and run ferfectly, but will not give you "out the box" experience because wine lacks good copy protection code. Diablo II is a good example Can't we be a little bit more flexible and add these games to the list as well ??? Mark Hannessen

13 20

header layout agreements
by Christian Neumair Nov. 3, 2002

Nov. 3, 2002

As the topic suggests this thread focusses on the layout of our existing wine header code. Maybe it sounds a bit pedantic but it's essential to have unified guidelines all developers should follow: Dimitrie O. Paun <dpaun(a)rogers.com> already did a great job [1]: He just added additional comments to a common header describing exactly what still remains to do. We should have a unified header which contains at least: /* * ... * ####### HEADER (normally license terms) ######## * * DESC * This DLL manages <...> * * FUNC * -- 1st function * Internal FAN flags: * FAN_TASY - specifies our imaginary code * FAN_TASTIC - this array stores some code (not yet * implemented) * -- 2nd function * -- 3rd function (not yet implemented) * -- etc. (* * Optional : * * TODO * -- 1st function: implement FAN_TASTIC. * -- yet another item * * BUGS * -- 1st function: we need to handle a call without FAN_TASY being * passed * -- plain old item */) We're already providing detailed information on parameters, return values etc. above many functions so adding this to the file header would just bloat it. Comments on that, please :) regs, Chris [1] http://www.winehq.com/hypermail/wine-patches/2002/10/0343.html

3 2

Strange problem on serial port
by David D. Hagood Nov. 2, 2002

Nov. 2, 2002

There seems to be a strange problem related to the serial port. Specifically, when running Delorme AAA MapNGo 4.0, and attempting to use GPS navigation, it is unable to communicate with the GPS device. On stderr Wine is printing out RtlNtStatusToDOSerr - unable to map 00000102 This only happens when the GPS device is connected and sending data, otherwise no error is printed. I know that the device is sending, because Minicom will show the data stream from the device. This also leaves out permission problems as both Wine and Minicom are running with the same permissions. A bit of grepping through the code indicates the likely error code is STATUS_TIMEOUT. Could it be that the serial I/O routines are incorrectly returning STATUS_TIMEOUT to the calling program when data was read? Additionally, I have another Windows program that accesses the serial port without problems - could it be that second program is ignoring the timeout error, while the first is not?

1 0