February 2004 - Wine-Devel - list.winehq.org

Wine 0.9 TODO

by Dimitrie O. Paun

Hi folks, Here is the detailed TODO in all it's glory. We _really_ need to get this over with, so please help us out to get this release out the door. I'll mark names by the tasks based on conversations I had with folks at WineConf (and on the list). If you notice any mistakes, please let me know. Items marked with (???) have no owner. If you think you can help on any of these (including ones that do have owners!), please let me know. Help is needed and appreciated. If it's not clear what needs to be done for any of these, get in touch with me, I'll be more than happy to help you get started. Enjoy! A. WineHQ.org ============== 1. History page (Brian) [IN PROGRESS] 2. Testing status (Ferec) [IN PROGRESS] 3. I18n status (Vincent) [IN PROGRESS] 4. Porting status (Dimi, Steven) [IN PROGRESS] 5. Who's Who (Tom) 6. Documentation page update (???) 7. Download page (esp. source) needs work (???) 8. Acknowledgment page (???) 9. UI status update (???) 10. Integrate API status into WineHQ (???) B. Documentation ================ User Guide ---------- 1. Update configuration instructions based winecfg & regedit (???) 2. Suggest winefile instead of Calmira (???) 3. Misc cleanups (Dimi) Devel Guide ----------- 1. Update COM section/widl (???) 2. Redo Multimedia section (???) 3. Add i18n section (Vincent) 4. Suggest adding tests w/ patches (Dimi) 5. Cross compilation on RH (Michael) 6. Add section on KERNEL32 (???) 7. Misc cleanups (Dimi) Winelib Guide ------------- 1. Update around MinGW/winegcc (Dimi, Francois) 2. Misc updates (Dimi) C. Configuration ================ 1. Complete regedit (Attila) [IN PROGRESS] 2. Complete winecfg (Chris, Mike) 3. Setup API .inf scripts (Chris) [IN PROGRESS] D. UI Code ========== 1. Visible region handling in server (Alexandre) 2. Inter-process handle management (Urlich, Alexandre) E. File Formats =============== 1. .spec files [DONE] 2. .reg files [DONE] 3. I18n output (Vincent) [IN PROGRESS] F. Exported API =============== 1. DLL separation I [DONE] 2. DLL separation II (Alexandre, Eric) [IN PROGRESS] 3. wineserver protocol (Alexandre) G. Tools ======== 1. winebuild: build DLLs from .def files (Alexandre) 2. winegcc: add simple gcc-independence (Dimi) 3. winegcc: generate DLLs/-shared (Dimi) 5. winemaker: generate MinGW compatible makefiles (???) 4. winemaker: use dsw2make from MinGW (???) 5. winemaker: no configure script (???) 6. autoconf: add all Wine-specific macros to the aclocal (???) 7. winedesktop: create new tool (Alex) [IN PROGRESS] H. Miscellaneous ================ 1. Testing daemon to run as a Windows service (???) 2. Exec-shield support (???) 3. Prelink support (???) 4. Version symbols in libwine & libwine_unicode (Alexandre) 5. Find packager for a PE-build of Wine on SF (???) 6. Standardize Wine handling in autoconf (Dimi) -- Dimi.

Feb. 3, 2004

Re: WineConf update

by Vizzini

On Mon, 2004-02-02 at 16:14, Steven Edwards wrote: > Hi Guys, > --- Vizzini <vizzini(a)plasmic.com> wrote: > > There was a very interesting question brought up on Saturday morning > > by > > one of the Wine guys (Mike perhaps?) regarding running ReactOS inside > > Linux, like Win4Lin. I was skeptical at first, but having slept on > I think its do-able. > The real > question is what more do you get by running ReactOS as Win4Lin rather > than running Wineserver and WINE. Do we open up Win32k.sys for grahpics > drivers like Captive has done for Filesystem drivers? These are two different approaches. Captive can be very useful as-is (or nearly so) for running individual drivers. I've heard the safedisc driver might be a good next target here. Unrelated to this might be the ability to run the native Windows OS, off of the Microsoft CD, but with a replaced kernel and HAL. Obviously that gets you a whole virtual machine, whereas Captive is focused on giving Linux extra capabilities. -Vizzini

Feb. 2, 2004

Re: File probably truncated

by Alexandre Julliard

Thomas Brix Larsen <killar(a)get2net.dk> writes: > 0009:trace:module:map_image mapped PE file at 0x400000-0xf89000 > 0009:trace:module:map_image mapping section .text at 0x401000 off 1000 > size 6a4000 flags 60000020 > 0009:err:module:map_image Could not map section .text, file probably > truncated This is fixed in current CVS. -- Alexandre Julliard julliard(a)winehq.com

Feb. 2, 2004

Re: File probably truncated

by Uwe Bonnes

>>>>> "Thomas" == Thomas Brix Larsen <killar(a)get2net.dk> writes: Thomas> Hi again, I'm getting stuff like this when trying to use Windows Thomas> programs: Thomas> 0009:trace:module:map_image mapped PE file at 0x400000-0xf89000 Thomas> 0009:trace:module:map_image mapping section .text at 0x401000 Thomas> off 1000 size 6a4000 flags 60000020 0009:err:module:map_image Thomas> Could not map section .text, file probably truncated Thomas> Why? Maybe the file is really truncated or prpbably it has a Virus... -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Feb. 2, 2004

Re: WineConf update

by Steven Edwards

Hi Guys, --- Vizzini <vizzini(a)plasmic.com> wrote: > There was a very interesting question brought up on Saturday morning > by > one of the Wine guys (Mike perhaps?) regarding running ReactOS inside > Linux, like Win4Lin. I was skeptical at first, but having slept on > it a > day or two, I think this is a really cool idea. The proposal is that > we > adapt our own ntoskrnl.exe and hal.dll to run correctly in user mode, > just like user mode linux does, and use them to run the rest of a > native > Windows XP system. In other words, it replaces Win4Lin with free > software, and it would be compatible with the current Windows OSes. > Much investigating remains to be done, of course - I can't really > even > guess at the level of difficulty or time required at this point - but > it > is worth pursuing in my opinion. I think its do-able. I am planning on discussing this with Mike and Codeweavers guys more after I return from Vacation on the 8th. The real question is what more do you get by running ReactOS as Win4Lin rather than running Wineserver and WINE. Do we open up Win32k.sys for grahpics drivers like Captive has done for Filesystem drivers? Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/

Feb. 2, 2004

File probably truncated

by Thomas Brix Larsen

Hi again, I'm getting stuff like this when trying to use Windows programs: 0009:trace:module:map_image mapped PE file at 0x400000-0xf89000 0009:trace:module:map_image mapping section .text at 0x401000 off 1000 size 6a4000 flags 60000020 0009:err:module:map_image Could not map section .text, file probably truncated Why? Anybody please? -- Thomas Brix Larsen <killar(a)get2net.dk>

Feb. 2, 2004

Re: New registry key adding patch

by Zimler Attila

Dimitrie O. Paun wrote: >On February 2, 2004 03:05 am, you wrote: > > >>Yes, I nee help :) It's the old problem :) what task could I start :) If >>I saw correctly in the list, regedit is implemented meantime :) >> >> > >We still need to add support for delete/rename of keys. > > > > Ok, I all will do it :) (if I don't know something I will ask it) Attila

Feb. 2, 2004

WineConf update

by Vizzini

After a slippery drive home (12 stressful hours from Minneapolis -> Kansas City, rather than the six it took me to get there on Friday), I finally have time to report a bit on WineConf. First of all, I'd like to thank Codeweavers on behalf of those of us from ReactOS that attended the conference. It was really run well, with ample free food (always a requirement). I didn't even mind -5F as much as I thought! There were about 35 Wine and ReactOS hackers there, and two days worth of presentations. I started getting serious questions about ReactOS the instant people figured out who I was. There was about a 50/50 split between people wanting to know what it was and people wondering why we are bothering to do this. There were a lot of interesting (and passionate) conversations about the role of Linux on the desktop, the stupidity of trying to clone the windows kernel, intellectual property considerations, etc. I can say that in all cases, the discussions were very positive and open. I'm certain that I didn't convince everyone, but just the opportunity to make the case was worthwhile. The ReactOS presentation on Sunday morning went as well as can be expected, given the state of our code. I spoke from a prepared deck (http://plasmic.com/~vizzini) for about 15 or 20 minutes, and then we demonstrated various aspects of the system. Steven ran the demonstrations, which included showing off Explorer, Windows XP Notepad, and our installation system. Then, the four of us (Steven, Art, Mark, and me) took questions. Most of the questions this time around were very technical in nature, and there was at least one question (from Gavriel State, regarding our DIB engine), that pretty much stumped us (can one of the UI guys please comment?). We had two crashes due to the floppy driver (well, also due to my stupidity at not configuring VMWare with a blank floppy disk image before starting), and one non-detected mouse incident. There was also a bit of a repainting problem, but on the whole, the system represented itself well. There was a very interesting question brought up on Saturday morning by one of the Wine guys (Mike perhaps?) regarding running ReactOS inside Linux, like Win4Lin. I was skeptical at first, but having slept on it a day or two, I think this is a really cool idea. The proposal is that we adapt our own ntoskrnl.exe and hal.dll to run correctly in user mode, just like user mode linux does, and use them to run the rest of a native Windows XP system. In other words, it replaces Win4Lin with free software, and it would be compatible with the current Windows OSes. Much investigating remains to be done, of course - I can't really even guess at the level of difficulty or time required at this point - but it is worth pursuing in my opinion. Jan Kratochvil also joined us to present about his Captive NTFS project. For those that don't remember what this is, Jan got the ntfs.sys driver from Windows XP running in Linux, in part by using chunks of ReactOS code. Jan and I had some offline discussions as well about bringing Captive's improvements back into our tree, and about other captive-like projects that could be implemented. I expect a lot of focus will be applied to this area of Quasi-Wine, Quasi-ReactOS hacking over the next year. All in all, it was a really great conference, and I'll definitely try to attend again next year. Presentations were good, conversations were interesting, people were friendly, and Minnesota at -5 was beautiful! ;-) -Vizzini

Feb. 2, 2004

Found this on ATI's devel pages, might help with directx ?

by Lars Segerlund

I don't know if you have seen this before, but it's a program to run the grafix pipeline interactive, thought it might be usefull. http://mirror.ati.com/developer/sdk/rage128SDK/Multex/Multex3D.html / have a look, Lars Segerlund.

Feb. 2, 2004

Re: TransparentBlt

by Dimitrie O. Paun

On Mon, 2 Feb 2004, Kevin Koltzau wrote: > I just submitted a new variant of my original patch without using MaskBlt, > which works under both Windows and wine currently > Not meaning to hide a possible issue with MaskBlt, but my new patch > should be a bit faster as MaskBlt does quite a bit of work... Sounds good. Not high priority, but would be great if you can take a look at our current implementation of MaskBlt. If there are problems in it, we can probably eliminate a few nasty visual artifacts. -- Dimi.

Feb. 2, 2004