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

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

Wine 0.8 TODO v0.2
by Dimitrie O. Paun Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

> 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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

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 Nov. 2, 2002

Nov. 2, 2002

--- "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 Nov. 2, 2002

Nov. 2, 2002

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

RtlQueryTimeZoneInformation
by György 'Nog' Jeney Nov. 2, 2002

Nov. 2, 2002

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

1 0

Re: Hungarian resources
by nagyzoli＠drotposta.hu Nov. 2, 2002

Nov. 2, 2002

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

1 0

Re: Wine 0.8 TODO v0.1 + help request :)
by Kye Lewis Nov. 2, 2002

Nov. 2, 2002

> 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 Nov. 2, 2002

Nov. 2, 2002

<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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 + +(a)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 Nov. 1, 2002

Nov. 1, 2002

> > 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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

> > 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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

--- "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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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 Nov. 1, 2002

Nov. 1, 2002

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

RE: Wine 0.8 TODO v0.1
by Patrik Stridvall Nov. 1, 2002

Nov. 1, 2002

> Oh, one other thing that would be nice, while I think of > it... is there > any reason (now we are GPL'ed) that we cannot incorperate cabextract > (http://www.kyz.uklinux.net/cabextract.php3) into Wine? Because we are not GPL:ed. We are LGPL:ed. Application that go under programs/ might as an exception go under GPL. However in the case of cabextract we need substantial parts of it to implement functions like SetupIterateCabinet in SETUPAPI.DLL so only the LGPL or less restrictive is acceptable. However the author(s) of cabextract might agree to release the parts we need under the LGPL. Perhaps it better if he release it all under the GPL since we might want to implement the CAB SDK tools like cabarc.exe that is supposed to do almost exactly what cabextract does (and possibly more) AFAICS. What don't you ask him? > Currently we shell out to it as an external program, Do we? Hmm. OK, it seems we do in dlls/urlmon/umon.c. Ugly. That code should probably call SetupIterateCabinet instead. Of course that function is not implemented yet. See above. > in order to run > Microsoft's setup APIs ecetra. This is really annoying for > new users, as > unless they look closely at pages of logs... theres no real indication > that's why installation of a Microsoft program failed. True.

1 0

Tucows top-100 applications :)
by Carlos Lozano Nov. 1, 2002

Nov. 1, 2002

Hello, It is today top 100 tucows list. I think that it shouldn't be the better wine top 100 list, some entries should be removed, and some new added. (For example some cdrecord program). 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

2 1

What is a leap second
by György 'Nog' Jeney Nov. 1, 2002

Nov. 1, 2002

While I was looking through dlls/ntdll/time.c I came across the following two comments: "FIXME: Compute the number of leap second corrections here" and "FIXME: get the GMT offset here" What do these mean? nog.

4 9

Status of libwine MFC and msvcrt compilation
by Uwe Bonnes Nov. 1, 2002

Nov. 1, 2002

Hallo, what is the status of winelib compilation of MFC and msvcrt? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

Versions & mass-appeal
by Dimitrie O. Paun Nov. 1, 2002

Nov. 1, 2002

People, I think everybody here agrees that Wine's biggest problem is the lack of developers. No developers, slow progress, no users, back to no developers. We are in this vicious circle for a while, spinning our wheels like crazy. We've achieved great progress lately, but I hope we all agree that Wine is a vast project that can succeed only with a mass appeal similar to the fueling the development of the Linux Kernel. Why are we in this position? For reasons I will not go into right now, it seems painfully obvious to me that we are suffering from a severe case of Bad Public Image (tm). Whenever I talk to people not intimately familiar with Wine, about our beloved project, I am _always_ treated with the same reaction: a surprised "Really, it works? Hmmm, I thought it was only running Freecell...". Translation: people consider Wine a huge hack that can run (by some strange happenings) some apps, sometimes. It is viewed as unreliable, "freak of nature sideshow"; something (maybe) cool to talk about, but utterly useless. THIS IS OUR PROBLEM. The lack of users follows trivially. We know the above opinion is not true. *I* get constantly amazed by how much progress we've made. Something must be done, and I think there is something to be done. How do we change this state of affairs? Well, people need major events to reevaluate their opinions. Being major, they are by definition few, and so we don't have too many chances. For Wine, these events are the upcoming x.y releases. What I'm trying to say is that we have to prepare properly for them. Here's my concrete proposal for releases: 0.8.x : Wine is usable, we don't guarantee binary compatibility 0.9.x : Wine is usable, and we kinda guarantee binary compatibility 1.0.x : Wine is quite usable, we guarantee binary compatibility I'll define these things more precisely later, but before that, let me explain why we should introduce the 0.8.x series: -- a chance to attract more users into the fold -- Wine is approaching that stage fast -- it's a logical, interim step to 0.9 -- will help us focus Whatever the reason, it's a _logical_ step that we must go through in our journey to 0.9, and from a user's perspective, it makes sense to make it public. There's no point in robbing us of the userbase for a abstract techy goal of binary compatibility. That's the next stage. Criteria for these releases: 0.8.0 -- Wine runs several popular apps well (we're close) -- Web site is updated (e.g. Who's Who, etc) -- Existing docs are up-to-date -- Utilities are close to final form (winebuild, etc.) 0.9.0 -- DLL separation complete -- Server protocol complete 1.0.0 -- Major bugs squashed -- Flawless UI -- Complete docs I'll leave it at that. Comments, flames? -- Dimi.

18 45

Getting actively involved in the Wine project
by Thomas Wickline Nov. 1, 2002

Nov. 1, 2002

From the page: ----- PR manager Currently we almost have no Public Relationship management at all. This should change for the better. Currently almost the only form of PR is "preaching to the choir", since we're having articles on online IT sites (by far most are Linux only !). We should have much more coverage on traditional Windowsish sites and, most importantly, in dead-tree newspapers, to enlighten the general public also known as The Great Unwashed Masses ! ----- Wine users , CodeWeavers & WineX customers could do Previews/Demo's at there local lug meetings as well.. This is what I did a couple months back and it was a huge success there were Windows users at the meeting to see Linux and Win app's being run on Linux ... Also it gives Linux users a look at wine as well. So I suggest that we try to encourage wine users to volinteer to show Wine at there local user groups/Installfest/Computer shows and so on. This is not a PR manager but it is PR...... Tom

3 3

Re: RFC: msvcrt _popen/_wpopen/_pclose
by chrismorgan＠rcn.com Nov. 1, 2002

Nov. 1, 2002

What is wrong with using wcmd and extending it if necessary? Chris > > From: "Jaco Greeff" <jaco(a)puxedo.org> > Date: 2002/10/31 Thu PM 04:27:43 EST > To: wine-devel(a)winehq.com > Subject: RFC: msvcrt _popen/_wpopen/_pclose > > Hi, > > I want some comments on the possibility of a _popen/_wpopen/_pclose > implementation in Wine. Reference available at: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html… > > The open functions basically operate in the same way as the popen function > in Linux, ie. it spawns a process with the command via the command > interpreter. Now, unfortionately we don't have our won cmd.exe available, > but should people really need this functionality it might not be too much to > ask as to copy it from a working Windows installation. > > In my mind, supporting the Win 95/98 command interpreters might be a > nightmare - my gutt feel is that these two rely too much on DOS internals to > be sucessfully launched via Wine. No, I haven't tried it, so I might be > completely wrong. Either way, something like this might be better > implemented via the Win NT/2000/XP cmd.exe. (I'll test my assumptions > tomorrow, I don't have access to the command interpreters tonight.) > > I've hacked (yes, it was quick) a potential implementation of the _popen > family of functions. (Haven't compiled, haven't tested, this is just and RFC > - if it can work, I'll spend some real time on it.) Anyway, here it is, > comments appreciated: > > --[ inline-ish RFC ]---- > > #include "config.h" > #include "wine/port.h" > > #include <stdio.h> > #include <stdlib.h> > #ifdef HAVE_UNISTD_H > # include <unistd.h> > #endif > > #include "winbase.h" > #include "winnls.h" > #include "wine/unicode.h" > #include "msvcrt/stdio.h" > #include "msvcrt/string.h" > > #include "wine/debug.h" > > #define POPEN_FLAG_READ 0x0001 > #define POPEN_FLAG_WRITE 0x0002 > #define POPEN_FLAG_TEXT 0x0004 > #define POPEN_FLAG_BINARY 0x0008 > > inline CHAR *LPCWSTRToLPSTR(const LPCWSTR lpwstrIn, INT nIn) > { > INT nLen = WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, NULL, 0, NULL, > NULL); > CHAR *szOut = (CHAR *)malloc((nLen+1)*sizeof(CHAR)); > if (szOut) > { > WideCharToMultiByte(CP_ACP, 0, lpwszIn, nIn, szOut, nLen+1, NULL, NULL); > szOut[nLen] = '\0'; > } > return szOut; > } > > INT POPEN_parseModeFlags(const CHAR *szMode) > { > INT nFlags = 0; > while (szMode && *szMode) > { > switch (*szMode) > { > case 'r': > { > if (nFlags & POPEN_FLAG_WRITE) > WARN(": _popen: Cannot set both read and write open > flags, ignoring read flag\n"); > else > nFlags = nFlags & POPEN_FLAG_READ; > break; > } > case 'w': > { > if (nFlags & POPEN_FLAG_READ) > WARN(": _popen: Cannot set both read and write open > flags, ignoring write flag\n"); > else > nFlags = nFlags & POPEN_FLAG_WRITE; > break; > } > case 'b': > case 't': > { > FIXME(": _popen: %c mode flag not implemented, ignoring\n", > *szMode); > break; > } > default: > { > WARN(": _popen: unknown mode flag %c, ignoring\n", *szMode); > break; > } > } > } > return nFlags; > } > > MSVCRT_FILE *MSVCRT_popen(const CHAR *szCommand, const CHAR *szMode) > { > MSVCRT_FILE *fProcess = NULL; > > if (!szCommand || !szMode) > return NULL; > > INT nFlags = POPEN_parseModeFlags(szMode); > if (!(nFlags & (POPEN_FLAG_READ|POPEN_FLAG_WRITE))) > { > ERR("No open mode flag r or w specified\n"); > return NULL; > } > > /* _popen/_wpopen executes the required command via the command > * processor, either command.com (Win 95/98) or cmd.exe (Win NT/2000/XP). > * Wine does not currently have it's own "cmd.exe" hence we cannot > * really do anything more at this point. However, we try to lauch it > * and hope for the best... > */ > CHAR *szExec = (CHAR *)malloc(strlen("wine -- C:/cmd.exe -C > ")+strlen(szCommand)+1); > if (szExec) > { > sprintf(szExec, "wine -- C:/cmd.exe -C %s", szCommand); > fProcess = popen(szExec, (nFlags & POPEN_FLAG_READ) ? "r" : "w"); > if (!fProcess) > ERR("Execution of C:/cmd.exe via wine failed\n"); > else > WARN("Launch of %s succeeded, no guarentees of success made\n", > debugstr_a(szExec)); > free(szExec); > } > > return fProcess; > } > > MSVCRT_FILE *MSVCRT_wpopen(const WCHAR *wszCommand, const WCHAR *wszMode) > { > MSVCRT_FILE *fProcess = NULL; > > if (!wszCommand || !wszMode) > return NULL; > > CHAR *szCommand = LPCWSTRToLPSTR(wszCommand, strlenW(wszCommand)); > if (szCommand) > { > CHAR *szMode = LPCWSTRToLPSTR(wszMode, strlenW(wszMode)); > if (szMode) > { > fProcess = _popen(szCommand, szMode); > free(szMode); > free(szCommand); > } > free(szCommand); > } > > return fProcess; > } > > int MSVCRT_pclose(MSVCRT_FILE *fProcess) > { > if (!fProcess) > return -1; > return pclose(fProcess); > } > > > >

2 2

So lets say we do it
by Dimitrie O. Paun Nov. 1, 2002

Nov. 1, 2002

That is, Lets assume for the sake of argument that Alexandre likes my 0.8 idea so much, that he releases Wine 0.8 with much fanfare next Monday (so we have a good audience), and the news reaches Slashdot where a message with a link to http://www.winehq.org is posted, in good CmdrTaco fashion... And so, let's see what's going to happen: 1. 90% of /.ers will click on the link, and WineHQ gets Slashdotted! :) 2. People will look for the typical left-side menu: Home About Status Development Download Screenshots *BZZT* We don't have any. 5% will drop off here. 3. Then they'll visually search for the word "Screenshot" *BZZT* We don't have any on front page. 30% will drop off. *I* drop off here when I visit other projects, for crying out loud! So let's assume that by a miracle they'll discover the screenshots: do they make them drool? No, we loose another 15%. Damn, that's tough! Let's see what happens to the rest: 4. Let's download, and try it out Do we have officially sanctioned binaries (at the very least .rpms for RH, and .deb for Debian)? No. *BZZT* We loose another 30%. Again, *I* don't care about stuff that doesn't come as a binary .rpm for my RH system. I used to, not anymore. Fine, some will install what they download. What next? Hm, this Wine thing just sits there, it's not that simple. We need to read some docs. Back to the site. 5. Look at the docs Oh, we have some. We hate to read docs, but Wine is cool, so we swallow the pill. Only to find out it's out of date!!! What a piece of #@$%! *BZZT* Another 10% drop off. Thats 90% drop-off before they really tried it out! The rest 10%, go on. So, what do we do with it? 6. Look for a list of Win-apps that we can run Is there something on the site? No. Blah, too much hassel... *BZZT* Another 5% go. (Don't even mention app-db, it's *way* too complicated!) So the 5% left, install wine, install a Win-app, and play around. Great, it works! They start learning the utilities, etc., but those are in flux, and we change them, and they get PO-ed. Another percent, or two leave the fold... -- Dimi. P.S. A story-like TODO (with embedded rationale) for 0.8.0 :)

10 27

Re: Treeview notifications
by Dustin Navea Nov. 1, 2002

Nov. 1, 2002

--- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > Dustin, Adrian, can you please try this one, and let me > know if it fixes your problems? > > ChangeLog > Fix some treeview notification codes between ANSI/Unicode mode. > Another sidenote... in TREEVIEW_NotifyFormat shouldnt (lParam == NF_REQUERY) be (lParam == NF_QUERY) and change the corresponding line in TREEVIEW_Create since that is the original query? I have already searched throughout the sources and the only place that TREEVIEW_NotifyFormat is called is in treeview.c in TREEVIEW_Create ... -Dustin __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/

2 1

Re: I suck...
by Dimitrie O. Paun Nov. 1, 2002

Nov. 1, 2002

On October 31, 2002 08:17 pm, Greg Turner wrote: > Inlined for your viewing pleasure. Cool, thanks! :) -- Dimi.

1 0

Re: Treeview notifications
by Dustin Navea Nov. 1, 2002

Nov. 1, 2002

Unfortunately, no it didnt fix the problem. :( -Dustin --- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > Dustin, Adrian, can you please try this one, and let me > know if it fixes your problems? > > ChangeLog > Fix some treeview notification codes between ANSI/Unicode mode. > __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/

1 0

Re: So lets say we do it
by John K. Hohm Nov. 1, 2002

Nov. 1, 2002

> Once we have that we need to make sure we have suitable defaults to > allow running at least the drives/paths control panel without registry > files at all. We also need the Wine dlls to register themselves > instead of having to merge winedefault.reg by hand. Then it should be > possible to write a .inf script to setup a new Wine install > automatically from scratch. Once upon a time (well okay, in July) I said I would make the Wine dlls self-registerable, and now I've gone and created bug #1117 to remind me to do it. I plan to use the (mostly-)static-array-driven, dumb but generic, regsvr_register and regsvr_unregister functions that are currently situated in dlls/comcat. I don't like the idea of copying around exact duplicates of regsvr.[hc], but they seem too small to put in their own libwine_regsvr.so; what do you recommend?

1 0

Re: wine/dlls/rpcrt4 ndr_marshall.c
by Greg Turner Nov. 1, 2002

Nov. 1, 2002

On Thursday 31 October 2002 07:47 pm, Alexandre Julliard wrote: > Fix stupid clone of broken macro, found by Marcus. On Thursday 31 October 2002 07:17 pm, I wrote: > - fix stupid clone of broken macro, found by Alexandre. sheesh! I can't even get the fixer's fixed. oh well :( Like I said in the patch subject, I suck... -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

Re: I suck...
by Alexandre Julliard Nov. 1, 2002

Nov. 1, 2002

Greg Turner <gmturner007(a)ameritech.net> writes: > Thanks for catching the first, Alexandre, or > I wouldn't have caught this second... Actually I didn't catch anything, the first one was fixed by Marcus. -- Alexandre Julliard julliard(a)winehq.com

1 0