- Wine-devel - list.winehq.org

Re: msvcrt-A06: _popen + COMSPEC
by Jaco Greeff 04 Nov '02

04 Nov '02

On Sun, 3 Nov 2002 12:53:15 -0500, "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote : > But the question is whether or not CreateProcess _should_ find it, or not. > If it is, than it's a bug in CreateProcess, and working around it is rather > detrimental. If not, than fine, use the full path. We should always try > to fix the bug at the source, not to invent workarounds. Agreed, if a know bug exists it needs to be fixed. I was in a rush when replying to your initial request for clarification, so I didn't express it properly. I however, did look at what the correct behaviour of CreateProcess should be when I came across this. According to MSDN: "The string can specify the full path and file name of the module to execute or it can specify a partial name. In the case of a partial name, the function uses the current drive and current directory to complete the specification. The function will not use the search path. If the file name does not contain an extension, .exe is assumed. Therefore, if the file name extension is .com, this parameter must include the .com extension." So no, I didn't try to create workarounds. As I've said, it is something that bugged me as well. :) Greetings, Jaco

2 2

A heartfelt thank you!
by Dimitrie O. Paun 03 Nov '02

03 Nov '02

To all our WWN editors (past, and present), a big THANK YOU! for doing the Wine's Weekly News. You guys are doing an excellent (and quite important work). I love them dearly. Keep up the good work! :) -- Dimi. P.S. People may think that I lost my mind. Not really, it's backed up somewhere on tape... :) Seriously, I just felt like saying this. So sue me! :P P.P.S. Monday I'm gonna have a full day of meetings at a large financial company, and I hate it. It's gonna be worse than Friday. So if I return to the list in a bellicose mood, please excuse me: you have to go once to understand... :/ P.P.P.S. I love working on Wine -- and the prospect that I have to go to said company tomorrow makes it so obvious, that I just hate ending this email to go to sleep to wake up very early tomorrow to go there... :)))

1 0

My WineHQ menu structure proposal
by Dimitrie O. Paun 03 Nov '02

03 Nov '02

This is my proposal for the WineHQ menu structure, based on the discussions I had with Francois. The Home Page should just be our news page. Many projects opt for this, and I think it's good: News are 'zero' click items. It should consist of the WNN box to the right (as our current home page), and a bigger central box for announcements. Each box should have a link at the bottom to their respective archive pages. Below, the numbers are for reference only, they should not appear on the site. Top Level --------- 1. About 2. Status 3. Screenshots 4. Download 5. Support 6. Documentation 7. Development 8. Contributing 9. Forums Expanded -------- 1. About 1.1 Intro 1.2 Why Wine 1.3 Myths 1.4 Technology 1.5 History 1.6 Related projects 1.7 Who's Who 1.8 Community 1.9 Companies 1.10 Contacts 1.11 Legal (1.1-1.3 may be collapsed in one page, that is served when you click on About; there are too many subitems like this) 2. Status (our current status page, with links to TODOs, etc) 3. Screenshots (add real sexy shots, as discussed in other mail) 4. Download (link to tarballs, and binary packages) 5. Support 5.1 FAQ 5.2 Howto 5.3 Bugzilla 5.4 Troubleshooting 5.5 Application database 5.6 Commercial support 6. Documentation 6.1 User Guide 6.2 Developer Guide 6.3 Packager Guide 6.4 API Docs 7. Development 7.1 Source (page with explanation of the CVS trees, LXR, cvsweb, etc.) 7.2 Developer Hints 7.3 Submitting Patches 7.4 Outstanding Work (page with the 0.9/1.0 TODOs, Tasklist/bug 395, FIXMEs/bug 455, Tasklets/bug 406, most wanted bugs) 7.2 Tools 7.3 References (Win32 documentation, X doc, etc.) 8. Contributing 8.1 Application maintainer 8.2 Bug triage 8.3 Website maintenance 8.4 Development (short page with links to the development section) 8.5 Support Wine-based products 9. Forums 9.1 Mailing Lists 9.2 Newsgroup 9.3 IRC Channel ----- So we don't forget, some related bugs in Bugzilla: Other relevant Web Site tasks ----------------------------- * 597 - How to get the web site files * 598 - Update the Who's Who * 600 - Add a Site Map * 601 - Add drop-down menus * 605 - Add 'tables of contents' * 607 - Add screenshots * 608 - Reorganize the Web site -- Dimi.

7 37

A problem with comctl32
by DanteAliegri 03 Nov '02

03 Nov '02

Hey, I've come across what appears to be a simple problem in comctl32. When running icq99b, wine was dying in imagelist.c while trying to dereference a null pointer. Upon looking at the file, there was code for returning FALSE if that pointer was null, thus I felt it being null may be a valid choice. I made the attached change, and the problem was fixed. Comments? Index: imagelist.c =================================================================== RCS file: /home/wine/wine/dlls/comctl32/imagelist.c,v retrieving revision 1.65 diff -u -r1.65 imagelist.c --- imagelist.c 23 Oct 2002 22:19:11 -0000 1.65 +++ imagelist.c 2 Nov 2002 20:40:53 -0000 @@ -1082,11 +1082,14 @@ HBITMAP hImageBmp, hOldImageBmp, hOldImageListBmp, hOldMaskListBmp, hBlendMaskBmp; BOOL bIsTransparent, bBlend, bResult = FALSE; const HIMAGELIST himl = pimldp->himl; - const INT lx = himl->cx * pimldp->i + pimldp->xBitmap; - const INT ly = pimldp->yBitmap; + static INT lx; + static INT ly; if (!pimldp || !himl) return FALSE; if ((pimldp->i < 0) || (pimldp->i >= himl->cCurImage)) return FALSE; + + lx = himl->cx * pimldp->i + pimldp->xBitmap; + ly = pimldp->yBitmap; fState = pimldp->cbSize < sizeof(IMAGELISTDRAWPARAMS) ? ILS_NORMAL : pimldp->fState; fStyle = pimldp->fStyle & ~ILD_OVERLAYMASK;

3 2

WINE for PowerPC?
by Adam Ernst 03 Nov '02

03 Nov '02

I'm sorry if this is off topic or doesn't belong here. I'm not a developer (at least not in C) so I'll wait a few years while I learn C before I come back and help you guys. But I was wondering... What are the technical issues with putting WINE on the PowerPC? So someday we could run WINE with native Windows apps on Linux for PPC or even (!) the Macintosh? (Mac OS X is Unix based, so...) Is it feasible to put a x86 emulator in there, so Win32 apps will think they're on a standard x86 processor? I've got visions of Windows exes running on Linux for PPC or a running Windows applications on a Mac... I know WINE is far from being done even for Linux x86, but I'd appreciate everyones' knowledge on his question. Thanks, Adam Ernst

9 9

Fwd: Re: WINE for PowerPC?
by Dustin Navea 03 Nov '02

03 Nov '02

--- Igor Izyumin <igor(a)mlug.missouri.edu> wrote: > From: Igor Izyumin <igor(a)mlug.missouri.edu> > To: Dustin Navea <speeddymon(a)yahoo.com> > Subject: Re: WINE for PowerPC? > Date: Sun, 3 Nov 2002 08:18:42 -0600 > > On Saturday 02 November 2002 07:26 pm, Dustin Navea wrote: > > --- Adam Ernst <adam1234(a)athenet.net> wrote: > > > I'm sorry if this is off topic or doesn't belong here. I'm not a > > > developer (at least not in C) so I'll wait a few years while I learn C > > > before I come back and help you guys. But I was wondering... > > > > Ok, I dont want to sound rude, but you should be glad anyone is > replying... > > Its not really off-topic as there arent any set topics and it certainly > > doesnt not belong here. > > > > > What are the technical issues with putting WINE on the PowerPC? So > > > someday we could run WINE with native Windows apps on Linux for PPC or > > > even (!) the Macintosh? (Mac OS X is Unix based, so...) Is it feasible > > > to put a x86 emulator in there, so Win32 apps will think they're on a > > > standard x86 processor? > > > > Do you know all of the routines for an x86 processor? Neither do any of > us > > ;). If we put in x86 emulator in there then we need a hardware emulator > > also so that it translates the codes from x86 hardware codes to mac ones. > > > And the only hardware emulator I know of (even for x86) is vmware and it > > royally sux. > > Not really. It's not THAT difficult to emulate x86 - after all, many > emulators (like snes9x, snes9x.com) do the same thing with very > poorly-documented consoles. In fact, there IS an open-source x86 emulator > (Bochs, http://bochs.sourceforge.net/) > > The real challenge is making it efficient - the Super Nintendo runs at > about > 5MHz but requires a 300MHz processor to emulate it with decent speed. > Unless > you want your 800MHz Mac to perform like a 486, you will probably want a > more > efficient way to emulate it. This is a big challenge, and Wine quite > frankly > has bigger fish to fry. > > Besides, why would you want to run stuff under wine on the Mac? Virtual PC > is > much better for most things. If you really want to go 100% Windows-free, > you > could run Linux inside a Bochs session and run Wine on top of that. If you > > don't use MacOS on your Mac, just get an x86 PC - it will work better with > Linux anyway. > -- > -- Igor __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/

1 0

Re: move dosconf to winedos
by Jukka Heinonen 03 Nov '02

03 Nov '02

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 03 Nov '02

03 Nov '02

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 03 Nov '02

03 Nov '02

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 03 Nov '02

03 Nov '02

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