wine-devel

wine-devel@winehq.org

2 participants
84471 discussions

Error trying to install AutoCad 2002
by Matts 04 Nov '02

04 Nov '02

This is the console output when I try to install Autocad 2002 Trial.I think the trial is identical to the full version in this aspect. Do you want me to log something? The error message in swedish say essantially "Installation package cannot be opened. Make sure that you can acces the package..." [root@localhost root]# cd /mnt/cdrom [root@localhost cdrom]# wine /mnt/cdrom/setup.exe For language 'sv' several language ids were found: sv_SE - 041D; sv_FI - 081D; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=sv_SE err:font:ReadFontDir Can't open directory "/usr/X11R6/lib/X11/fonts/drakfont/ttf" For language 'sv' several language ids were found: sv_SE - 041D; sv_FI - 081D; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=sv_SE err:font:ReadFontDir Can't open directory "/usr/X11R6/lib/X11/fonts/drakfont/ttf" fixme:ntdll:NtOpenThreadToken (0xfffffffe,0x00000004,0x00000001,0x405d5724): stub fixme:advapi:SetThreadToken ((nil), 0): stub (NT impl. only) fixme:ntdll:NtOpenProcessToken (0xffffffff,0x00000008,0x405d5720): stub fixme:ntdll:NtQueryInformationToken (0000cafe,1,0x405d555c,80,0x405d55ac): stub fixme:advapi:SetThreadToken ((nil), cafe): stub (NT impl. only) fixme:thread:SetThreadExecutionState (0x80000001): stub, harmless (power management). fixme:thread:SetThreadExecutionState (0x80000000): stub, harmless (power management). Installationspaketet kunde inte öppnas. Bekräfta att paketet finns och att du kan komma åt det, eller kontakta programvaruförsäljaren för att bekräfta att det är ett giltigt paket för Windows Installer. [root@localhost cdrom]# wine -ver Unknown option '-ver' Wine 20020804 Usage: /usr/bin/wine.bin [options] [--] program_name [arguments] The -- has to be used if you specify arguments (of the program) Options: --debugmsg name Turn debugging-messages on or off --dll name Enable or disable built-in DLLs --help,-h Show this help message --version,-v Display the Wine version _____________________________________________________________ Want a new web-based email account ? ---> http://www.firstlinux.net _____________________________________________________________ Select your own custom email address for FREE! Get you(a)yourchoice.com w/No Ads, 6MB, POP & more! http://www.everyone.net/selectmail?campaign=tag

1 0

Problem with DirectSoundCreate
by steve.lustbader＠philips.com 04 Nov '02

04 Nov '02

My app calls DirectSoundCreate, which fails, returning DSERR_ALLOCATED. I have no idea what the problem is. Any ideas what might be wrong, or any traces, etc I could provide to give more info? -Steve

2 1

make test fails under dlls/advapi32
by Sylvain Petreolle 04 Nov '02

04 Nov '02

Using latest CVS, make test complains about undefined symbol : make[3]: Entre dans le répertoire `/home/wine/dlls/advapi32/tests' ../../../programs/winetest/runtest -q -P wine -M advapi32.dll -T ../../.. -p adv api32_test.exe.so registry.c && touch registry.ok /home/wine/miscemu/wine: could not load 'W:\dlls\advapi32\tests\advapi32_test.exe.so': /home/wine/dlls/advapi32/tests/advapi32_test.exe.so: undefined symbol: winetest_set_ok_location make[3]: *** [registry.ok] Erreur 1 make[3]: Quitte le répertoire `/home/wine/dlls/advapi32/tests' make[2]: *** [tests/__test__] Erreur 2 make[2]: Quitte le répertoire `/home/wine/dlls/advapi32' make[1]: *** [advapi32/__test__] Erreur 2 make[1]: Quitte le répertoire `/home/wine/dlls' make: *** [dlls/__test__] Erreur 2 ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 4

i810 & wineoss & sound formats
by Francois Gouget 04 Nov '02

04 Nov '02

There is something that sees very wrong in OSS_WaveOutInit. We do: smplrate = 44100; if (ioctl(ossdev->fd, SNDCTL_DSP_SPEED, &smplrate) == 0) { ... this format is supported ... } But according to the OSS spect this ioctl call is not garanteed to give you the actual sampling frequency you asked for. So if the device only supports 11025Hz, ioctl will return success but you will find that after the call smplrate==11025. So it seems it would be more correct to do: smplrate = 44100; if (ioctl(ossdev->fd, SNDCTL_DSP_SPEED, &smplrate) == 0 && smplrate==44100) { ... this format is supported ... } There are other issues like you cannot assume that because a sound card supports 44100Hz in mono it supports it in stereo. It might only support stereo up to 22050Hz. Same thing with 8 bits vs. 16 bits. That's for old cards though, with modern cards it's the opposite. Some cards, e.g. based on the i810 chipset, support 48000Hz in 16 bit in stereo but nothing else, not 48000Hz in 16 bit in mono for instance. So assuming we do strict checks (I have code for that), for an i810 card waveOutGetDevCaps should return: 0: "CS4236/37/38" 1.0 (255:1): channels=2 formats=0000 support=006c I.e. none of the formats at 11025, 22050 or 44100 are supported. But testing this on Windows I get: 0: "YAMAHA AC-XG WDM Audio" 5.10 <1:100>: channels=65535 formats=bfff support=002c Which leads me to the following questions: * should waveOutGetDevCaps consider that a format is supported as long as we can up-sample to a format that is? * what does the b mean in 'formats=bfff'? I could not find any documentation... (the support=006c vs. 002c is not significant, it's just WAVECAPS_DIRECTSOUND) -- Francois Gouget fgouget(a)codeweavers.com

2 1

Crash without any usable hint
by Uwe Bonnes 04 Nov '02

04 Nov '02

Hallo, _pn.exe from webpack just stops now (after a webpack service pack has been applied and after a wine update. The controlling terminal tells about memory protection error "Speicherschutzfehler". I don't get any usefull log. Here a log with --debugmsg +seh,+relay,+server: 352180 08074640:Call kernel32.GlobalFindAtomW(40908714 L"PropertySheetInfo") ret=408f623f 352181 08074640: find_atom( local=0, name=L"PropertySheetInfo" ) 352182 08074640: find_atom() = OBJECT_NAME_NOT_FOUND { atom=0000 } 352183 08074640:Ret kernel32.GlobalFindAtomW() retval=00000000 ret=408f623f 352184 08074640:Call kernel32._EnterSysLevel(40921f98) ret=408d28fc 352185 08074640:Ret kernel32._EnterSysLevel() retval=00000008 ret=408d28fc 352186 08074640:Call kernel32._LeaveSysLevel(40921f98) ret=408d292c 352187 08074640:Ret kernel32._LeaveSysLevel() retval=00000000 ret=408d292c 352188 08074640:Call kernel32.GlobalGetAtomNameW(00008002,409231f0,0000003c) ret=408aeee3 352189 08074640:Ret kernel32.GlobalGetAtomNameW() retval=00000007 ret=408aeee3 352190 08074640:Call kernel32._EnterSysLevel(40921f98) ret=408d28fc 352191 08074640:Ret kernel32._EnterSysLevel() retval=00000008 ret=408d28fc 352192 08074640:Call kernel32.lstrcpynW(40923268,42090040 L"",00000010) ret=408d7854 352193 08074640:Ret kernel32.lstrcpynW() retval=40923268 ret=408d7854 352194 08074640:Call kernel32._LeaveSysLevel(40921f98) ret=408d292c 352195 08074640:Ret kernel32._LeaveSysLevel() retval=00000000 ret=408d292c 352196 08074640:Call window proc 0x41d80428 (hwnd=00010023,msg=WM_SETFONT,wp=00000cce,lp=00000000) 352197 08074640:Call kernel32._ConfirmSysLevel(40921f98) ret=408d3d6e 352198 08074640:Ret kernel32._ConfirmSysLevel() retval=00000000 ret=408d3d6e 352199 08074640: *signal* signal=11 ... 352765 08074640: *signal* signal=11 352766 08074640: *killed* exit_code=0 352767 08074640: *exited* signal=11 352768 08074640: *detached* 352769 /home/bon/.wine/user.reg: saving key \\User\\bon 352770 /home/bon/.wine/system.reg: saving key \\Machine 352771 /home/bon/.wine/userdef.reg: saving key \\User\\.Default 352772 wineserver: exiting (pid=28637 I tried to run with winedbg, but winedbg only tells that the thread has died. Any other hints how to takle? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

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

04 Nov '02

On Mon, 2002-11-04 at 02:48, Keith Matthews wrote: > Do please try not to have more javascript than is really necessary. Sexy > looking features are nice from a designer's point of view, but to a No js on this site at all. I prefer to do most on the server side. Works across more browsers that way. > Looks rather black rather than red (Konq 2.2 on laptop). /me loads up Konq and looks. > I prefer the screenshot to the one Francois has, but it could still be > improved by having rather more background that is obviously an OSS > desktop. Both screen shots were made by me. I made a quick new one that didn't have a CodeWeavers logo on it somewhere. The idea is to have that screenshot be random, so feel free to submit me screenshots. I prefer whole desktops, and several Win apps/games running at once. That shows real power. > I'm getting a debug log panel at the bottom, no idea if that is > intentional, critical or what. That's intentional, the site is in debug mode as it's in development. When I say alpha I mean it. The final will look NOTHING like this, this is a rough draft. The fist round it mainly work on the back end code and general layout of the boxes and nav. Everything thing else colors/images/logo will change. -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

1 0

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

04 Nov '02

On Mon, 2002-11-04 at 02:13, David Fraser wrote: > Just wondering, is it really neccessary to have the URLs as queries i.e. > http://lostwages.winehq.org/?page=Support&view=page-support > Couldn't they just be > http://lostwages.winehq.org/support I plan on something similar, the urls will be something like: http://lostwages.winehq.org/index.php/support/ The shorter urls (ie without the index.php) will also work with redirects hard coded in a .htaccess file. We love shortcuts. -- __ _WebGeek/SysAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | / -_) | | / ' \/ _` | ' \ -= jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

1 0

Re: msvcrt-A08: _dup
by Jaco Greeff 04 Nov '02

04 Nov '02

Jaco Greeff wrote: > This patch in the msvcrt-A?? series implements the _dup function, > allowing you to duplicate msvcrt file descriptors. I've got a strange feeling that I stuffed up here, comments will be appreciated. Is the intention that it (_dup/_dup2) should duplicate the associated HANDLE as well? At present I don't duplicate the actual HANDLE, rather return a new fd which at the lowest level still points to the same handle. Something tells me that I should be duplicating the handle as well. I just found some sample code which points to duplicating the actual handle as well - comments please before I "do it right"(tm). Greetings, Jaco

1 0

Re: PATCH: ppc fix 2
by Greg Turner 04 Nov '02

04 Nov '02

On Wednesday 30 October 2002 07:22 am, Marcus Meissner wrote: > Hi, > > Just a bad macro. > > ciao, marcus > > Changelog: > Fixed LITTLE_ENDIAN_32_READ macro to at least compile. > > Index: ndr_marshall.c > =================================================================== > RCS file: /home/wine/wine/dlls/rpcrt4/ndr_marshall.c,v > retrieving revision 1.9 > diff -u -r1.9 ndr_marshall.c > --- ndr_marshall.c 29 Oct 2002 23:07:33 -0000 1.9 > +++ ndr_marshall.c 30 Oct 2002 13:21:15 -0000 > @@ -59,8 +59,8 @@ > > #define LITTLE_ENDIAN_32_READ(pchar) \ > (MAKELONG( \ > - MAKEWORD(*(pchar), *((pchar)+1)) \ > - MAKEWORD(*((pchar)+2), *((pchar)+3))) > + MAKEWORD(*(pchar), *((pchar)+1)), \ > + MAKEWORD(*((pchar)+2), *((pchar)+3)))) > #endif > > /* oops! thanks! strange that this compiles for i386 at all. maybe gcc is automagically fixing the macro for some of us? -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

2 3

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

04 Nov '02

This is the initial TODO for Wine 0.8. I know, 0.8 has been released before, but that's ancient history. Whether or not it gets released with this version number is irrelevant. In fact, even if it never becomes a public release, it is an important point to reach toward 0.9, and so if we complete this work, it would have solved its purpose. Now, 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 0. Reorganize a bit the navigational menu 1. Add a screenshot link to the homepage 2. Create some really sexy screenshots 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) 4. Enlist some 'official' distribution maintainers (at the minimum RedHat, Suse, UnitedLinux, 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. B. Documentation work Andy, take it away! :) 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 (?) 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 D. Stabilize utilities 0. Get rid of the init directive from .spec files 1. Make sure the .spec file format is fairly stable 2. Ensure the various utilities' options are stable E. Important fixes Alexandre, what to you see here? -- Dimi.

19 68

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

04 Nov '02

On Sun, 3 Nov 2002 11:02:02 -0500, "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote : > 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. I have tried this, CreateProcess doesn't find "cmd.exe" if we don't specify the full path. (This happend in the test case with the neccessary changes made to default to "cmd.exe"). But yes, it would be great. Greetings, Jaco

3 3

dialog boxex and DestroyWindow
by Ove Kaaven 04 Nov '02

04 Nov '02

I've found an app which calls DialogBoxParam, but destroys the dialog from inside WM_INITDIALOG, yet expects the dialog to still be alive until WM_INITDIALOG processing is done, i.e. case WM_INITDIALOG: ... initialize and write values to lots of controls ... if (user_dont_want_to_see_this_dialog_today) { DestroyWindow(hDlg); ... mess some more with controls (like reading their current values) ... return; } Does anyone have a good way to deal with this? One way might be to make DestroyWindow map to EndDialog in this case (as EndDialog manages to handle this right), but what would the best way to do that be?

2 2

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel