- wine-devel - winehq.org

Re: So lets say we do it
by Dimitrie O. Paun 04 Nov '02

04 Nov '02

On October 31, 2002 04:26 pm, Andreas Mohr wrote: > I wouldn't be 100% against placing a Screenshot link on the main page > - it's a mere 99% only. > But with the current menu infrastructure, I'm about 150% against it. > If we added a separate Screenshots menu item (which, by the way, I don't > think is needed, since we do have that nice About page), > then the whole page would grow overly long. Agreed. I say, let's get some of the content in shape, and worry about the form a wee bit later. BTW, any web-design guys around, that may want to take on this task? -- Dimi.

5 13

Debug messages specific to COM components?
by Mike Hearn 04 Nov '02

04 Nov '02

Hi all, I posted a similar query on Thursday but got no response, and was then away for a few days, so I'll try again a few times before filing something in bugzilla and forgetting about it. Basically my question is whether there is any way of restricting debug messages to one particular COM component: I have some problems with seemingly spurious mouse messages going to the Adobe SVG Viewer plugin in IE6 and would like to cut down on the huge log files wine can generate in these circumstances. In case anybody might know of such an issue, I've found that the ASV triggers onMouseMove events for (0,0) incorrectly, and when dragging with the LMB down bad onMouseUp events are handled. I'm guessing Wine is sending mouse messages to the plugin incorrectly, but I'm not really sure how to start verifying that. thanks -mike

1 0

lostwages (alpha 1)
by Jeremy Newman 04 Nov '02

04 Nov '02

Alpha 1 of WineHQ is up at http://lostwages.winehq.org The site is very very red. I'm not sure of that idea right now, but tell me what you think anyway. I think it hurts my eyes, but this is a short notice thing, I'll come up with something better. Feel free to submit color ideas. It does not have Francois' latest menu's in yet, but that is easy to change, the menu system reads the menu from an array in the config file. So it's much more dynamic. Anyway it's late, and I imagine you all will tear this to shreads, so have fun doing so. I'm always flame retardant (mostly cause I don't care, and will do what I want anyway >:) nighty night! -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

5 4

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

04 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

Re: My WineHQ menu structure proposal
by Andreas Mohr 03 Nov '02

03 Nov '02

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

03 Nov '02

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

03 Nov '02

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

header layout agreements
by Christian Neumair 03 Nov '02

03 Nov '02

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

02 Nov '02

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

Wine 0.8 TODO v0.2
by Dimitrie O. Paun 02 Nov '02

02 Nov '02

This will probably get renamed to Wine 0.9 TODO, after Alexandre's clarification, but I haven't changed the name just yet, to avoid confusion. Once again, what I mean by 0.8: -- Users can start using Wine -- works well for a fair number of apps -- no MS DLLs required (from real Windows) -- User facing stuff (website, docs, etc.) are in a decent state, to avoid scaring them away What is NOT in 0.8: -- stable server protocol: no binary compatibility -- DLL separation: ditto That being said, this is my initial list. Comments, flames, suggestions, are appreciated. A. WineHQ work (Beta at: http://lostwages.winehq.org) 0. Website redesign Jeremy Newman <jnewman(a)codeweavers.com> 1. Reorganize the navigational menu There is a proposal being discussed on the list 2. Create some really sexy screenshots -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 3. Rework the FAQ interface (static HTML, a la http://www.dvddemystified.com/dvdfaq.html, all on one page, with a clickable question list at the top) Agreed on the list. Should be written in SGML, so we can output all sorts of formats. Which means we need layouts, etc. Any takers? 4. Enlist some 'official' distribution maintainers (at the minimum RedHat, Suse, Mandrake, Debian) 5. Create nice page with apps that run virtually flawless They should not require MS dlls, tricks, etc. to run Small explanation, screeshot, optional link to download page, such as Tucows. Carlos <clozano(a)andago.com> is running with it. B. Documentation work Andy, take it away! :) 0. We need to figure first _what_ is out of date. C. Wine configuration 0. Merge configuration into the registry 1. Write control panel applets for editing it 2. Have decent defaults so we can start control panel without prior configuration 3. Have wizard like app to autoconfigure wine WineSetupTk proposed by Jeremy White <jwhite(a)codeweavers.com> 4. Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg 5. Write .inf script to setup a new Wine installation 6. Have a wineboot script for RunOnce stuff D. Stabilize utilities 0. Get rid of the init directive from .spec files Alexandre Julliard <julliard(a)winehq.com> volunteered 1. Make sure the .spec file format is fairly stable Any other things that may need changing here? 2. Ensure the various utilities' options are stable Anything here? E. Important fixes 0. Window management rewrite, so we can install apps in managed mode. -- Dimi.

3 6

Re: Wine FAQ - call for a volunteer
by Dimitrie O. Paun 02 Nov '02

02 Nov '02

On November 2, 2002 02:39 pm, Tony Lambregts wrote: > I will volunteer to take on the task of taking it from text and > converting to sgml. It needs to be SGML. Do we have styles for > <question> and <answer> already? ... Just Checked No... That's cool, but more importantly we need, styles to convert the SGML to the HTML of our choice. Help here would be _greatly_ appreciated. -- Dimi.

1 0

Re: WineSetupTk
by John K. Hohm 02 Nov '02

02 Nov '02

> First off, thanks for the offer -- it's generous, and very > useful IMO. It certainly sounds interesting, and I would like to > take a peak at the code. The big problem I have with WineSetupTk > it's that it's written in Tcl/Tk (I suppose). I don't know the > language, and I don't care to learn it. Moreover, I think Wine > should use itself for such tools, so we get to use all the nice > controls we have <g>. One thing that I'd like to see is a > programs/winesetup utility that's based on WineSetupTk, but > it's written in C, with the Win32 API & Controls. I believe Alexandre plans to have Wine configured via the registry eventually. Then it would probably make sense to have a C program that acted as a control panel applet and did what WineSetupTk does, but in a dynamic fashion using the registry APIs. Until then I would expect a C version of WineSetupTk to be rather ugly from having to deal with much text config parsing and manipulation.

2 1

Re: Today wine's compatibility with 20 popular apps from tucows
by Carlos Lozano 02 Nov '02

02 Nov '02

El sáb, 02 de nov de 2002, a las 16:54, Keith Matthews escribio: > > 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) > > > Do we really want things which have serious native alternatives. > > The ones I am especially looking at are Ws-FTP and putty. Most distros > have a FTP server, even if it's the grotty WU-ftp with it's bad > security record, and all the sensible distros are shipping OpenSSH. It is the same that when you are doing a videogame console emulator. You don't start testing the comercial games first, you start with simple demos, when you will get the basic working, then start with more complex one, and so. The important is not run this applications, the important is that sure that the authors of this applications have used features what are the base of other more complex. So if this features are working correctly, it will be easier run more complex software in the future :) 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

1 0

Re: Today wine's compatibility with 20 popular apps from tucows
by Joerg Mayer 02 Nov '02

02 Nov '02

On Sat, Nov 02, 2002 at 04:54:47PM +0000, Keith Matthews wrote: > Do we really want things which have serious native alternatives. The make good test cases and are good as demo applications too, because people who use Windows may know theses already and the list is obviously not a list put together for that purpose because the apps have been selected by Downloaders at tocows. Ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

1 0

Plea to fix winelib COM vtable bug
by Matthew Bloch 02 Nov '02

02 Nov '02

This is a summary of my recent probs with Winelib in the hope that someone who knows the COM stuff can fix them quickly, because hacking through the jungle of include files and definitions is hard work In short, I've built the latest wine cvs with the ICOM_MSVTABLE_COMPAT flag set in include/wine/obj_base.h, so each vtable has two dummy words at the start for g++'s benefit. I then added these statements to the start of my WinMain to cause a segfault: IDirectDraw* dd; DirectDrawCreate(0, &dd, NULL;) and for good measure, wrapped the call to IDirectDraw7_QueryInterface in DDRAW_Create (which is where the segfault occurs) in ddraw/main.c with these two warnings: WARN("about to call IDirectDraw7_QueryInterface vtbl size = %d\n", sizeof(DDCF_Vtbl)); hr = IDirectDraw7_QueryInterface(pDD, iid, lplpDD); WARN("called IDirectDraw7_QueryInterface\n"); and when running the program, the trace clearly shows that the Release entry point is being called instead, and crashing, though the vtable is the expected size (5 entry points, plus 2 dummy dwords): warn:ddraw:DDRAW_Create about to call IDirectDraw7_QueryInterface vtbl size = 28 warn:ddraw:DDRAW_Create offset is 12271064 trace:ddraw:Main_DirectDraw_Release (0x403a7c70)->() decrementing from 1. warn:ddraw:Main_DirectDraw_Release doing final release Looking at the pre-processor output from compiling ddraw/main.c, I can see that IDirectDraw7Vtbl type has the two extra words grafted onto the front, as it should: struct IDirectDraw7Vtbl { long dummyRTTI1; long dummyRTTI2; HRESULT (__attribute__((__stdcall__)) *QueryInterface)(IDirectDraw7* me, const IID* const a, LPVOID* b); ULONG (__attribute__((__stdcall__)) *AddRef)(IDirectDraw7* me); ULONG (__attribute__((__stdcall__)) *Release)(IDirectDraw7* me); ... The problem seems to be that the call is offset not just by two table entries, but four. Somewhere in that jungle of macros, the "vtable base adjustment" of +2 is being applied twice, I'm sure of it. But I'm buggered if I can find out where this is happening; I'm still looking but it's slow progress and I believe it's a winelib bug. Any suggestions on how to fix it would be welcome. cheers, -- Matthew Bloch Bytemark Computer Consulting Limited http://www.bytemark.co.uk/ tel. +44 (0) 8707 455026

3 4

Re: dlls/msvcrt: msvcrt-popen-2.diff
by Jaco Greeff 02 Nov '02

02 Nov '02

On Sat, 2 Nov 2002 10:56:02 -0500, "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote : > On November 2, 2002 10:41 am, Jaco Greeff wrote: > > +#define POPEN_WCMD_EXEC "C:\\Windows\\System32\\cmd.exe /c" > > Do we need this hardcoded path here?!? What about the COMSPEC > idea that Francois suggested? I'm still trying to get that one to go. As soon as I've got it, I'll submit the small change. <snip> > > + else > > \ > > + CloseHandle(hHandle); > > What's up with all the macro abuse? :) We don't like cpp that much! ;) > Please, try to do things without macros, it can't be that bad. And everybody is a critic ;) I really hate duplicating code in any function. I'd rather use a macro which make the function 1. more readable, 2. shorter :) I would potentially rather more it to it's own header file than doing the cut-n-paste thing inside a function... Would it be 50% ok with macro abuse in a seperate header file? Greetings Jaco

2 1

PATCH: DirectDraw vtable fixes
by Matthew Bloch 02 Nov '02

02 Nov '02

Found it; a few of the DirectDraw ICOM_VTABLE declarations did not have the ICOM_MSVTABLE_COMPAT_DummyRTTIVALUE macro prefixing their elements. This meant that, well, all sorts of havoc broke loose when wrong functions were called :) I hope this is an uncontentious patch attached. -- Matthew Bloch Bytemark Computer Consulting Limited http://www.bytemark.co.uk/ tel. +44 (0) 8707 455026

1 0

Re: dlls/msvcrt: msvcrt-popen-2.diff
by Dimitrie O. Paun 02 Nov '02

02 Nov '02

On November 2, 2002 10:41 am, Jaco Greeff wrote: > +#define POPEN_WCMD_EXEC "C:\\Windows\\System32\\cmd.exe /c" Do we need this hardcoded path here?!? What about the COMSPEC idea that Francois suggested? > +#define LPCWSTR_TO_LPSTR(wszIn, nIn, szOut, nOut) \ > + *nOut = WideCharToMultiByte(CP_ACP, 0, wszIn, nIn, NULL, 0, NULL, > NULL); \ > + szOut = (CHAR *)MSVCRT_malloc((*nOut+1)*sizeof(CHAR)); > \ > + if (szOut) > \ > + { > \ > + WideCharToMultiByte(CP_ACP, 0, wszIn, nIn, szOut, *nOut+1, NULL, > NULL); \ > + szOut[nLen] = '\0'; > \ > + } > \ > + else > \ > + *nOut = 0; > + > +#define CREATE_PIPE(hRead, hWrite, security) \ > + if (!CreatePipe(&hRead, &hWrite, &security, 0)) > \ > + { > \ > + TRACE("Creation of pipe failed\n"); > \ > + return NULL; > \ > + } > + > +#define REDIRECT_STREAM(type, handle)\ > + if (!SetStdHandle(type, handle)) > \ > + { > \ > + TRACE("Redirection of stream failed"); > \ > + return NULL; > \ > + } > + > +#define RESTORE_STREAM(type, handle) \ > + if (!SetStdHandle(type, handle)) > \ > + TRACE("Restore of stream failed\n"); > + > +#define DUPLICATE_HANDLE(hHandle, hDup, type, hOrig) \ > + if (!DuplicateHandle(GetCurrentProcess(), hHandle, > \ > + GetCurrentProcess(), &hDup, 0, > \ > + FALSE, DUPLICATE_SAME_ACCESS)) > \ > + { > \ > + TRACE("Duplication of piped handle failed\n"); > \ > + RESTORE_STREAM(type, hOrig); > \ > + return NULL; > \ > + } > \ > + else > \ > + CloseHandle(hHandle); What's up with all the macro abuse? :) We don't like cpp that much! ;) Please, try to do things without macros, it can't be that bad. -- Dimi.

1 0

Re: Wine 0.8 TODO v0.1
by Dustin Navea 02 Nov '02

02 Nov '02

--- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > On November 2, 2002 09:42 am, Dustin Navea wrote: > > apps such as slocate to gain root access and then that would give wine a > > bad rep with both windows newbies and linux users... > > That can't happen as WIne runs non-root. At mostthey can gain user access. > Anything more is a Linux bug. > No but if there is a big enough hole, they could use it to get access to the /etc/passwd and then use a dos program (crackerjack comes to mind here) to decrypt the program (especially if they are dual-booting win9x and linux) --Dustin __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/

2 1

Re: Wine 0.8 TODO v0.1
by Dimitrie O. Paun 02 Nov '02

02 Nov '02

On November 2, 2002 03:26 am, Keith Matthews wrote: > Note that an increasing number of apps are assuming that IE is present > and use it to provide crucial functionality. For this, we should look into supporting the IWebBrowser interface, via Mozilla. It's been mentioned here before. Actually, there is a LGPL implementation for this in the Mozilla tree, it's just that it's written in C++. One option would be to just install the binaries, and that would be it, but it's not that sexy... -- Dimi.

1 0

games
by Mark Hannessen 02 Nov '02

02 Nov '02

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

RtlQueryTimeZoneInformation
by György 'Nog' Jeney 02 Nov '02

02 Nov '02

Does anyone know anything about RtlQueryTimeZoneInformation? I would like to implement it... nog.

1 0

Re: Hungarian resources
by nagyzoli＠drotposta.hu 02 Nov '02

02 Nov '02

Upgraded: dlls/user/resources/user32_hu.rc Thanks Zoly

1 0

Re: Wine 0.8 TODO v0.1 + help request :)
by Kye Lewis 02 Nov '02

02 Nov '02

> These are my success stories with a plain installation of wine (i do > have windows, but i created a new config which doesn't use it) > > Well, Acrobat can install and run pretty much perfectly. > http://www.adobe.com/ With Latest CVS Acrobat Reader 4.0 seems to only have 1 problem (the licence agreement screen comes up behind the splash screen - but it is visible enough to move it anyway) > Family Tree Maker 9 runs really well as well > Not freely downloadable > Only problem with this one is the installer shows the setup instructions > behind the background. - but the actual app works pretty much fine Apart from setup this works very well, although not flawlessly. I don't know if the internet functions work or not. > The #1 at Tucows - IrfanView - works pretty much flawlessly as well. > http://www.tucows.com/ - look for the #1 (or search for it) In fact, after a little more detailed look, I would say this works *perfectly* > MS Calculator ;) works well > >From the Microsoft Plus! Pack: > Again, not freely downloadable. > > Spider Solitaire: FLAWLESS :) - just a tad slow on animations > Pinball also FLAWLESS - again a little slow but works! > > More coming soon... Note: Pinball now comes with windows - so It can be tested out. Don't include this in the list of working apps, but Adobe Premiere 6.0 has made great progress in the last month or two - It now not only opens, but will add titles and transitions (normal AVI files will not open however - it says that they are not a known compression format) - and when printing to video, it freezes after a few seconds (well, when I tried it anyway). There are also slight problems with the timeline (but it is still workable - a great wine success story) Also, DK Multimedia's "The Way things work" works almost perfectly I've done some screenshots of running applications in Wine which i'm going to post to: http://winepics.oxygen-x.net/ a little later on today. Thanks, Kye Lewis kyethespy(a)liquid2k.com

1 0

Re: Hungarian resources
by Dmitry Timoshkov 02 Nov '02

02 Nov '02

<nagyzoli(a)drotposta.hu> wrote: > dlls/user/resources/user32_hu.rc Please use either CVS or release 20021031 as the source for user32 resources. Specifically there is no such an identifier MDI_IDS_MOREWINDOWS but IDS_MDI_MOREWINDOWS instead and one more string in the user32 string table has been added. -- Dmitry.

1 0

Earthviewer 3D Setup
by Kye Lewis 01 Nov '02

01 Nov '02

Hi, When I run the EarthViewer 3d setup (www.keyhole.com), wine tells me this: ERROR: You need to merge the 'winedefault.reg' file into your Wine registry by running: `regedit winedefault.reg' fixme:ole:_LocalServerThread CoMarshalInterface failed, 80070057! Can someone help me with the ERROR: part (typing that command tells me that winedefault.reg doesn't exist) It's an InstallShield Wizard - not sure what version, but it's a newer one - I would bet InstallShield 6. Wine Version is latest CVS. Thanks, Kye Lewis kyethespy(a)liquid2k.com

1 0

C/C++ Users Journal is looking for a WINE author
by JCasad＠cmp.com 01 Nov '02

01 Nov '02

WINE Developers-- Is anyone interested in writing an article on the winelib development toolkit for the C/C++ Users Journal? This article would be a great way to bring some practical information about winelib to advanced C/C++ programmers who may not be familiar with it (plus you get paid). We're looking for an article that will give some background on winelib and also provide a practical example of how to use winelib to port a Windows app to Linux. Our focus is on the code. We'd be looking for a very detailed description of how to use winelib in a specific, real-world situation. Let me know if you, or someone you know, would be interested in helping us. You can contact me at: jcasad(a)cmp.com -Joe Casad Editor-in-Chief C/C++ Users Journal __________________________________________________________________________________________ Any views or opinions are solely those of the author and do not necessarily represent those of CMP Media. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message please do not read, copy, use or disclose this communication and notify the sender immediately. It should be noted that any review, retransmission, dissemination or other use of, or taking action or reliance upon, this information by persons or entities other than the intended recipient is prohibited. __________________________________________________________________________________________

1 0

Name, life-cycle, directory structure, autoconf, temporary kludges for wine rpcss subtitute?
by Greg Turner 01 Nov '02

01 Nov '02

Sorry, in advance, for this barrage of questions... but I'm getting anxious to proceed with this thing. Naming: This guy needs a name if I'm ever going to start coding it. How about: Wine Remote Procedure Call System Server aka wrpcss.exe.so? A little misleading with the "ss" thing, but this name will look familiar to windows users, and is more accurate than my previous idea of wine-epmap, since it will eventually need to do more than just endpoint mapping. I pretend this is the right name below, but if there's a better one, just substitute that in everywhere you see "wrpcss" in the following discussion. Life Cycle: Some scenarios will require wrpcss to run all the time as a daemon-type-thingy; most wont -- the majority of scenarios require dynamic on-demand invocation and auto-termination upon unmapping of all registered endpoints, as Ove suggested. Are command line arguments an appropriate way to differentiate between these modes? This ends up going back to the open question of how to implement services in wine; but, of course, I don't want to wait for this to be resolved before proceeding. Whatever solution wine implements for services, adapting wrpcss to it won't be insurmountable (assuming it's a good solution). Also: if run as a service, how do I get "detached" without using "fork()"? Is there some existing example of this I ought to emulate? Directory Structure: dlls/rpcrt4/wrpcss/ ? programs/wrpcss/ ? Autoconf: I can try to implment the necessary infrastructure myself, but if history is any guide, I will screw it up. If anyone is feeling generous with their time, they could give me a skeleton to fill in. Temporary Kludges: DCE does, indeed, provide the necessary idl to implement the endpoint mapper. Unfortunately, although the IDL is reasonably simple, there are just too many types in there to "do it right" from the beginning. Meanwhile, I am getting sick of dragging along the unmerged server parts (it isn't that hard, but I'm lazy). So, as discussed earlier, I propose the named-pipes hack until a full implementation is possible. I would, of course, take some care to keep the kludge-based parts separate from meaningful, potentially permanent parts of the code... howsabout I just listen at \\.\pipe\wrpcss for the time being? thanks for your input, -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

3 5

RFC: prototype skeleton for wrpcss
by Greg Turner 01 Nov '02

01 Nov '02

Is this even close? As before, I didn't include diffs to configure because of an autoconf version mismatch between myself and wine. diff -ur -x CVS -x 'bigdif*' ../wine.test/configure.ac ./configure.ac --- ../wine.test/configure.ac 2002-10-31 03:10:18.000000000 -0600 +++ ./configure.ac 2002-11-01 08:54:33.000000000 -0600 @@ -1512,6 +1512,7 @@ programs/winetest/Makefile programs/winhelp/Makefile programs/winver/Makefile +programs/wrpcss/Makefile server/Makefile tools/Makefile tools/widl/Makefile diff -ur -x CVS -x 'bigdif*' ../wine.test/programs/Makefile.in ./programs/Makefile.in --- ../wine.test/programs/Makefile.in 2002-09-18 18:10:21.000000000 -0500 +++ ./programs/Makefile.in 2002-11-01 09:17:41.000000000 -0600 @@ -27,7 +27,8 @@ winepath \ winetest \ winhelp \ - winver + winver \ + wrpcss # Sub-directories to run make install into INSTALLSUBDIRS = \ @@ -47,7 +48,8 @@ winemine \ winepath \ winhelp \ - winver + winver \ + wrpcss # Programs to install in bin directory # We don't install everything to avoid polluting /usr/bin too much @@ -63,12 +65,14 @@ winefile \ winemine \ winepath \ - winhelp + winhelp \ + wrpcss # Symlinks to apps that we want to run from inside the source tree SYMLINKS = \ wineconsole.exe \ - winedbg.exe + winedbg.exe \ + wrpcss.exe @MAKE_RULES@ @@ -121,7 +125,11 @@ winedbg.exe$(DLLEXT): winedbg/winedbg.exe$(DLLEXT) $(RM) $@ && $(LN_S) winedbg/winedbg.exe$(DLLEXT) $@ +wrpcss.exe$(DLLEXT): wrpcss/wrpcss.exe$(DLLEXT) + $(RM) $@ && $(LN_S) wrpcss/wrpcss.exe$(DLLEXT) $@ + wineconsole/wineconsole.exe$(DLLEXT): wineconsole winedbg/winedbg.exe$(DLLEXT): winedbg +wrpcss/wrpcss.exe$(DLLEXT): wrpcss ### Dependencies: --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/wrpcss/.cvsignore 2002-11-01 08:39:51.000000000 -0600 @@ -0,0 +1,3 @@ +Makefile +wrpcss.exe.dbg.c +wrpcss.exe.spec.c --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/wrpcss/Makefile.in 2002-11-01 08:44:10.000000000 -0600 @@ -0,0 +1,14 @@ +TOPSRCDIR = @top_srcdir@ +TOPOBJDIR = ../.. +SRCDIR = @srcdir@ +VPATH = @srcdir@ +MODULE = wrpcss.exe +APPMODE = cui +IMPORTS = user32 kernel32 + +C_SRCS = \ + main.c + +@MAKE_PROG_RULES@ + +### Dependencies: --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/wrpcss/README 2002-11-01 08:42:27.000000000 -0600 @@ -0,0 +1,14 @@ +wrpcss README + +wrpcss, copyright 2002, Greg Turner +wrpcss is to be distributed under the LGPL/X11-MIT licenses +See the Wine License for further information. + +Wine needs a server whose role is somewhat like that +of rpcss.exe in windows. wrpcss stands for Wine Remote +Procedure Call System Server. + +Enjoy. + +KNOWN BUGS: + Doesn't do anything yet. --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/wrpcss/main.c 2002-11-01 08:51:26.000000000 -0600 @@ -0,0 +1,28 @@ +/* + * wrpcss (main.c) + * + * Copyright 2002 Greg Turner <gmturner007(a)ameritech.net> + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + */ + +#include "main.h" +#include "msvcrt/stdio.h" + +int main( int argc, char **argv ) +{ + printf("Yes, I run.\n"); + return 0; +} --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/wrpcss/main.h 2002-11-01 08:45:47.000000000 -0600 @@ -0,0 +1,26 @@ +/* + * Copyright 2002 Greg Turner <gmturner007(a)ameritech.net> + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a cop Alexandre Julliard <julliard(a)winehq.com>y of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + */ + +#ifndef _WRPCSS_MAIN_H +#define _WRPCSS_MAIN_H + +#include <windows.h> + +#endif /* _WRPCSS_MAIN_H */ + +/* end of header */ -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

3 4

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by John K. Hohm 01 Nov '02

01 Nov '02

> > No, it's wrong. You should be using the Windows API (CreateProcess > > etc.) not the Unix popen(). Then you can build a proper MSVCRT_FILE. > Sorry, I had a few beers tonight ;) Ok, I just remembered what my concerns > were about using CreateProcess initially when I looked at MSDN: I think you need to look more closely at the LPSTARTUPINFO lpStartupInfo argument to CreateProcess. It points to a STARTUPINFO structure having HANDLE hStdInput, HANDLE hStdOutput, and HANDLE hStdError members, which are used if the dwFlags member has the STARTF_USESTDHANDLES bit set.

1 1

MDAC
by Gustavo Junior Alves 01 Nov '02

01 Nov '02

Hi guys, I don't know if this is the right place, but I actually trying to run some commercial applications on Wine. We have sucess in all aplications, but VB. These applications need to use MDAC, and this Microsoft package need to be licensed for commercial use. Anybody know any MDAC project? If not, what about to implement it on Wine? I know that it a huge API, but we need to start someday. Any comments??? Gustavo

1 0

Re: Wine FAQ - call for a volunteer
by Jeremy White 01 Nov '02

01 Nov '02

> > I expect to be living close to it for the next few months and may > well get some questions that don't appear on the mailing list. I also > don't see myself being able to find the time to do much coding, however > much I'd like to. > > On the other hand I'm not sure I can do things in a timely manner with > other commitments. Might be better to have a primary and reserve > maintainer. I'd certainly be prepared to take on the latter. > > I can at least offer to do things from a static IP to make access > control more certain (sorry, I'm a bit of a security freak). Okay, we have a backup FAQ volunteer. Who will be our primary? A certain path to fame, fortune, and a lot of thankless work <grin>. Jer

1 0

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by Jaco Greeff 01 Nov '02

01 Nov '02

On 01 Nov 2002 08:40:20 -0800, Alexandre Julliard <julliard(a)winehq.com> wrote : > No, it's wrong. You should be using the Windows API (CreateProcess > etc.) not the Unix popen(). Then you can build a proper MSVCRT_FILE. Sorry, I had a few beers tonight ;) Ok, I just remembered what my concerns were about using CreateProcess initially when I looked at MSDN: CreateProcess executes a Windows executable with parameters, whereas _popen executes as shell, ie. you can do stuff like _popen("dir/w") which will return an open file in which you can read the directory contents from. In essence under Windows, this gets executed at "cmd.exe /C dir/w". Now using CreatePorcess we can potentially do the same, provided that the executable (command interpreter) resides in your path. From 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." Now wera are faced with a problem in that wcmd is not a pure Windows application and it doesn't reside in your Windows filesystem, rather it is in your *nix path. In the case of _popen, a file-handle is returned which allows you to either read or write to the application unsing the normal fwrite/fprintf/etc. commands. CreateProcess has an information structure containing the following information: typedef struct _PROCESS_INFORMATION { HANDLE hProcess; HANDLE hThread; DWORD dwProcessId; DWORD dwThreadId; } PROCESS_INFORMATION; I don't see any clear way of doing, 1. Converting the above structure into something usable, eg. MSVCRT_FILE 2. Actually allowing us to read or write to the application Potentially the magic lies in the current Wine CreateProcess implementation, I'll have a look at it. Is doing this really feasable using the CreateProcess family? In essence a HANDLE will map back to an fd with the wine implementation (rather we can get an fd for a HANDLE), but can this be used to read/write to the process? The first obstacle however, will be in having a clean way to get wcmd going if it doesn't reside in C:\. Maybe it should be there and should be installed like notepad.exe for example? Some questions, and yes I'm slow tonight... :) I think that just by typing this some concerns have been aleviated so excuse my rumblings but just check the logic. Greetings, Jaco

4 4

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by Jaco Greeff 01 Nov '02

01 Nov '02

On Fri, 1 Nov 2002 20:50:07 +0100, Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> wrote : > Giving a fully qualified patch is probably bad advice here. Try "wcmd.exe" > only and have cmd.exe.so in wine's program directory. Wine sets on startup > WINEDLLPATH to "$topdir/dlls:$topdir/programs" and wineapploader there > should manage to start the application. Umm, that might help a bit. When I get to the point of testing again, I'll give it a bash. What seems to be the concensus as to the "right-way-to-do-things(tm)" in this case? Greetings, Jaco

1 0

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by Jaco Greeff 01 Nov '02

01 Nov '02

On Fri, 1 Nov 2002 11:21:26 -0800 (PST), Francois Gouget <fgouget(a)free.fr> wrote : > Try c:\Windows\System\wcmd.exe and I think you will find that it works. *lol* Like I've said, expect me to be slow tonight :)

1 0

Wine securityflaw.
by Peter Andersson 01 Nov '02

01 Nov '02

Hello again, (FYI, I took the liberty to change the topic since I started the former thread "How is Win/Dos syscalls implemented in Wine?" which I feel has gone a little bit off-topic) I had some more thoughts on the issue... I believe most wine users trust wine not to touch anything outside of its configured drive space. Malicious Linux/Unix syscalls could be embedded in windows apps and if executed do a great deal of damage. After all checking your app is run whithin Wine is not that hard (reading registry settings for instance). Lets call such an malicious app a wine-virus from now on. At present a wine-virus would even be allowed to fork itself, leaving the wine environment and continue to run even after you shutdown the wineserver, and in some cases even after the user logs out. The virus would now have full access to the system whithin the users permission, doing much greater damage than you expected. The question is...Would you expect that damage from running a windows app in wine, when you know it could be safely run in Windows? In just a few embedded bytes in the code it could remove your home directory in a single syscall. Would you expect that? - I wouldnt. I really love the idea of Wine, and the fact that its working good and rather stable now does mean its gaining popularity and a broader user base, which further IMHO accelerates the wine movement. If wine users were aware of the risks of using wine at present, I believe wine would be used more cautiously. Cant we atleast try implement some protection in wine against these attacks, before something really nasty happens. I do think company policy decissions againt using wine, will do just as much damage to the wine movement as too the free software movement at large. I would, despite my current lack of knowledge, gladly offer my help. But I hope someone more experienced would take the lead. Best Regards, Peter Andersson

18 35

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by Jaco Greeff 01 Nov '02

01 Nov '02

On 01 Nov 2002 08:40:20 -0800, Alexandre Julliard <julliard(a)winehq.com> wrote : > Jaco Greeff <jaco(a)puxedo.org> writes: > > > 1. Calling the popen function returns a FILE* which needs to be > > converted to a MSVCRT_FILE*. The apprach taken here is potentially not > > the best route but the only one I could think of. Is it suffiecient? > > No, it's wrong. You should be using the Windows API (CreateProcess > etc.) not the Unix popen(). Then you can build a proper MSVCRT_FILE. I was actually taking a re-look at that this afternoon. I agree, the initial reason for th implementation was obviously that _popen is supposed to mimic popen, but the file conversion leaves me feeling really uncomfortable. I'll fix it up and submit it shortly. Greetings, Jaco

1 0

Re: Treeview notifications before Guy's patch problem
by Dustin Navea 01 Nov '02

01 Nov '02

--- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > On November 1, 2002 02:00 am, you wrote: > > after banging my head on my keyboard for a few minutes > > because i couldnt find treeview_notifyformat i went and looked at cvsweb > > and found out...there is no treeview_notifyformat before guy's patch so > > there is no way for me to get that kind of a debug output... > > Good find. Please add this to Bugzilla. But it presents a big problem: > if we behave correctly, we break the app. What do we do? > I'm wondering if maybe its my app thats broken already and thats why its sending the unicode message.. ---appended--- Maybe Alexandre should look at this too? Appended notes to bug 1073. Does anyone reading this have any ideas on any kind of hack that wont completely break every other app while still fixing this one? __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/

1 0

What does "Printer: Wine Poscript Driver, Error: 709" mean
by David.Goodenough＠DGA.co.uk 01 Nov '02

01 Nov '02

I installed a program called Mind Manager, and tried to run it. It installed OK, but when I came to run it the initial dialog came up and it was totally unresponsive to either keyboard or mouse. So I looked around the system for any errors and found that the title of the window in the KDE window list was as shown above. Anyone got any ideas what error 709 means? Thanks in advance David

1 0

Re: dlls/msvcrt: process.c (msvcrt-popen-1)
by Alexandre Julliard 01 Nov '02

01 Nov '02

Jaco Greeff <jaco(a)puxedo.org> writes: > 1. Calling the popen function returns a FILE* which needs to be > converted to a MSVCRT_FILE*. The apprach taken here is potentially not > the best route but the only one I could think of. Is it suffiecient? No, it's wrong. You should be using the Windows API (CreateProcess etc.) not the Unix popen(). Then you can build a proper MSVCRT_FILE. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: dlls/msvcrt: msvcrt-popen-1.1
by Joerg Mayer 01 Nov '02

01 Nov '02

On Fri, Nov 01, 2002 at 03:16:58PM +0200, Jaco Greeff wrote: > +/* FIXME: Don't know what this value should be, 10 seems enough as > + * the maximum number of simultaneous _popen'ed processes > + */ > #define POPEN_MAX_FILES 10 ... > +INT POPEN_getOpenFileSlotPos(VOID) > +{ > + INT i = 0; > + for (i = 0; i < POPEN_MAX_FILES; i++) > + { > + if (!POPEN_Files[i].fProcess) > + { > + POPEN_Files[i].fProcess = (MSVCRT_FILE *)POPEN_FILE_IN_USE; > + return i; > + } > + } Please output an ERR here to ask people to report that POPEN_MAX_FILES needs to be increased. > + return -1;

2 1

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