wine-devel November 2002

wine-devel@winehq.org

152 participants
501 discussions

Re: help support
by Sylvain Petreolle 10 Nov '02

10 Nov '02

CHM is a special extension of IE. The patch to make any windows compatible with CHM (except Win 3.1) is downloadable at http://www.microsoft.com/downloads/release.asp?ReleaseID=30328 To handle and generate CHM I found a french page (tools are in english). http://www.jurixt.com/informatique/hlp_compile_aide.htm Utility to decompile CHM and many many more : http://www.keyworks.net/keytools.htm Google power ! ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: int21 move a8
by Jukka Heinonen 09 Nov '02

09 Nov '02

Again, no full review, just quickly browsed through the patch. I have a feeling that I have just scratched the surface regarding this patch series and it would need a full review before it can be accepted. Function 0x40 change in winedos/int21.c breaks DOS VGA text console. Function 0x3f handling drops WIN16_hread which used to check for segment size. That check seemed to be for running buggy Win16 programs. At least I wouldn't have courage to delete this kind of checks. -- Jukka Heinonen <http://www.iki.fi/jhei/>

1 0

Re: winamp patch A0
by Vincent Béron 09 Nov '02

09 Nov '02

Le sam 09/11/2002 à 11:22, Andreas Mohr a écrit : > Hi all, > > IMHO we should now switch to Win98 SE as default Windows version. > Too many programs expect at least Win98 to be running already. > > Winamp also checks the Version registry keys, so I added them to > winedefault.reg. > > Index: winedefault.reg > =================================================================== > RCS file: /home/wine/wine/winedefault.reg,v > retrieving revision 1.58 > diff -u -r1.58 winedefault.reg > --- winedefault.reg 25 Oct 2002 19:05:19 -0000 1.58 > +++ winedefault.reg 9 Nov 2002 16:20:36 -0000 > @@ -72,6 +72,9 @@ > "ProgramFilesDir"="C:\\Program Files" > "RegisteredOrganization"="Change preferred organization in ~/.wine/system.reg" > "RegisteredOwner"="Change preferred owner in ~/.wine/system.reg" > +"SubVersionNumber"=" A " > +"Version"="Windows 98" > +"VersionNumber"="4.10.2222" This doesn't seem the place to do it, since if we specify something different (in config) then the registry keys do not match, and some other app could possibly have some problems. Would it be possible to generate automatically those keys with a call to GetVersionEx or something similar? Vincent

3 2

Re: GetCurrentObject
by steve.lustbader＠philips.com 09 Nov '02

09 Nov '02

GetCurrentObject returns 0, but as far as it knows, it is returning successfully. This is because in the line case OBJ_BITMAP: ret = dc->hBitmap; break; dc->hBitmap is 0, although dc is a valid DC. The HDC that is passed to GetCurrentObject to get dc is obtained by calling CWindow::BegingPaint(PAINTSTRUCT *) from a class derived from ATL's CWindow. I'm guessing that this is where the problem is probably coming from - the app is written in C++ with ATL. -Steve I've seen this occur when wine frees a gdi handle it shouldn't. Check that the OBJ_BITMAP handle is really valid. Also wierd stuff can occur if the app expects a HDIB but we provide it a HBITMAP... or vice versa. Mike steve.lustbader(a)philips.com wrote: > My app calls GetCurrentObject with a valid HDC and OBJ_BITMAP. > It returns 0, however, which causes my app to crash. What further > info can I provide to help debug this? > > -Steve >

2 1

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

09 Nov '02

---------- Forwarded Message ---------- Subject: Re: So lets say we do it Date: Sat, 9 Nov 2002 02:51:47 -0800 From: Kenny Smith <kenny(a)blindinstinct.com> To: dpaun(a)rogers.com I don't know how to use mail lists, so i though I might mail you In responce to your ideas about reorganizing the winehq site, i think there should be a site for development, like winehq, and a site for users. most users don't want to know about listview overhauls, etc. They wnat to know if their precious Quicken will run on linux or not. I'm sure a web design would be EASILY feasible. I'm a web designer (never done anything that big), and a 6-month linux user and there are tons of people like me who i'm sure would love to help. I use wine because I am somewhat computer-savvy (A+ certified savvy). I hope this message can be passed along, if you can't maybe you can tell me how to quickly... would google-groups let me?? kenny smith (AIM:standsolid) ------------------------------------------------------- -- Dimi.

1 0

re: Wine 0.8: VB compatibility !!
by Dan Kegel 09 Nov '02

09 Nov '02

Andreas Mohr wrote: > I keep encountering people mentioning that VB stuff has > lotsa problems on Wine. > While I really can't say that I like VB, a lot of people > seem to use it for critical tasks in companies on a > daily basis, so it sounds like perfect > VB compatibility would be utterly important. > IMHO improving that should be a goal of 0.8. Make sense. How about this: let's add a visual basic regression test suite to Wine. I'm not kidding! Ought to be pretty easy to hit at least the non-gui parts... - Dan

6 6

Re: wine button
by Mike Hearn 09 Nov '02

09 Nov '02

[ps i assumed by what was written you meant for this to go to wine-devel but didn't hit reply-to-all, sorry if it was meant for me only] > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. heh, true. It doesn't look good with the first letter capitalized, at least imho, and probably wouldn't alter the impression non-initiates would get. I tried putting "windows emulator" underneath, but it looks a bit out of place and kind of reduces the impact. It also makes it harder to scale down, at 50% of the size you can still read the "works with wine" text, but not the "windows emulator" underneath. It might also piss off people who say "Wine is not an emulator" :) Actually, letting people make jokes about it might be a good thing - I doubt many people would actually take it literally and assuming they do find out, if they're talking and joking about it, they're more likely to remember it too. On Fri, 2002-11-08 at 15:35, Rick Romero wrote: > > On Fri, 2002-11-08 at 08:53, Mike Hearn wrote: > > Here is my first attempt. I'm hardly an ace designer, so feel free to > > criticize, tell me to junk it etc. > I think it looks great, but if I were a Windows app owner, how would my > potential users see it? > > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. > > Of course we all know what it means, should the 'W' be capitalized to > differentiate it from alcohol? > > I don't intend to start a logo flame war, but I think perceptions are > everything. > > Good thing I'm only around for another 90 minutes today :P > > Rick > > > > > > > -- > -- > Rick Romero > IT Manager > Valeo, Inc. ph: 262.695.4841 > Sussex, WI. fax: 262.695.4850 > Rick(a)valeoinc.com > >

3 2

wine button
by Mike Hearn 09 Nov '02

09 Nov '02

Here is my first attempt. I'm hardly an ace designer, so feel free to criticize, tell me to junk it etc. I did try at first to make a browser style button, but it was very hard to make the wine logo fit in a way that didn't look odd, as it's largely a vertical type of logo. Also, is the Windows logo usable? I'd assume it's trademarked or something, but i've seen the 4 colour blocks used in for instance icon overlays in KDE. If it's thought that this is too large, I can either scale it, or try and make another from scratch that is more button sized. thanks -mike

7 10

Wine 0.9 TODO v0.1
by Dimitrie O. Paun 09 Nov '02

09 Nov '02

This is based upon the Wine 0.8 TODO v0.2 send earlier to the list. It is important to get a comprehensive list of what needs to be done, in order to have a successful 0.9 release. This includes all things Wine-related, not only the code. I can not do it alone -- I need your input. Before I start, a quick reminder for the 0.9 criteria: -- 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.9: -- stable server protocol (no binary compatibility) -- DLL separation (phase 2) Please review it, and let me know if: - I've left something out - Something is in, and it doesn't belong in here (for 0.9 that is) - I have put your name on a task you are not working on - I have NOT put your name on a task you are working on - You have a status update (if you're working on something) - You want to start working on some of these. Comments, flames, suggestions, are appreciated, as always. A. WineHQ work (Beta at: http://lostwages.winehq.org) 0. Website redesign [IN PROGRESS] - worker: Jeremy Newman <jnewman(a)codeweavers.com> 1. Reorganize the navigational menu [BETA] - wine-devel consensus merged into new site 2. Create some really sexy screenshots [IN PROGRESS] -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 3. Rework the FAQ interface [IN PROGRESS] - workers: Dimitrie Paun, Keith Matthews, Thomas Wickline) 4. Enlist some 'official' distribution maintainers [TODO] (at the minimum RedHat, SUSE, Mandrake, Debian) 5. Create nice page with apps that run virtually flawless [IN PROGRESS] They should not require MS dlls, tricks, etc. to run - worker: Carlos <clozano(a)andago.com> B. Documentation work 0. We need to first figure _what_ is out of date. [TODO] 1. Convert man pages to SGML [TODO] 2. Move CVS docu from User Guide to Devel Guide [TODO] C. Wine configuration 0. Merge configuration into the registry [TODO] 1. Write control panel applets for editing it [TODO] 2. Have decent defaults so we can start control panel without prior configuration [TODO] 3. Have wizard like app to autoconfigure wine [TODO] WineSetupTk proposed by Jeremy White <jwhite(a)codeweavers.com> 4. Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO] 5. Write .inf script to setup a new Wine installation [TODO] 6. Have a wineboot script for RunOnce stuff [IN PROGRESS] - worker: Shachar Shemesh <wine-devel(a)sun.consumer.org.il> D. Stabilize utilities 0. Get rid of the init directive from .spec files [DONE] - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Make sure the .spec file format is fairly stable [TODO] Any other things that may need changing here? 2. Ensure the various utilities' options are stable [IN PROGRESS] - Alexandre fixed winebuild options Anything here? E. Important fixes 0. Window management rewrite, so we can install apps in managed mode. - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Finish DLL separation Phase 1 [IN PROGRESS] That is, DLLs should use only functions exported through .spec file. Phase 2 is getting rid of unwanted functions from .spec file, and this is not a target for 0.9. -- Dimi.

10 25

Re: dosconf move try 2
by Jukka Heinonen 09 Nov '02

09 Nov '02

György 'Nog' Jeney wrote: > ChangeLog: > * dlls/winedos/dosconf.c > * include/callback.h > * msdos/dmpi.c > * msdos/dosconf.c (removed) > * dlls/ntdll/Makefile.in > * dlls/winedos/winedos.spec > * dlls/winedos/Makefile.in > Move dosconf to winedos. This still won't work if Dos3Call is called directly before winedos.dll has been loaded. If this is fixed, I don't see any reason why this patch couldn't be applied. This reminds me that int21 handling is quite messy. Interrups call first DOSVM_Int21Handler and might be chained to Dos3Call. But, if you call Dos3Call directly, execution does not go through DOSVM_Int21Handler. This causes some code duplication and makes things like dosconf unnecessarily complicated. I was hoping that I could leave this stuff to its current state until I had cleaned up other interrupts. Simple solution would be to make Dos3Call load winedos.dll and call DOSVM_Int21Handler through function pointer, move all common code from old Dos3Call to DOSVM_Int21Handler and move code that is difficult to handle in winedos to INT_Int21Handler which would be chained to from DOSVM_Int21Handler when a few selected functions need to be emulated. But this requires lots of work because each int21 function must be separately evaluated in order to see how it must be emulated to properly support both Win16 and DOS; first step would probably just add check if(DOSVM_IsWin16()) to each DOSVM_Int21Handler function and chain to INT_Int21Handler if true. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

← Newer
1
...
32
33
34
35
36
37
38
...
51
Older →

Jump to page:

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