wine-devel October 2005

wine-devel@winehq.org

165 participants
333 discussions

Re: Fix for #3464
by Jakob Eriksson 13 Oct '05

13 Oct '05

Can I create b: on the fly, allocate 1.44 megabyte RAM, do all copies there and then copy it back? Am I on crack? regards, Jakob Eric Pouech wrote: > It turns out that DOS' ioctl 0x440F (set logical drive map) was > strangely implemented. From the doc I have, this ioctl is responsible > for setting the logical drive to access a physical drive. This is used > for example, on a single floppy PC when implementing the copy a:foo > b:bar command, where a: and b: refer to the same physical device (the > floppy), and this ioctl is called to toggle the access from a: or b: > to the physical device. > This implies that this ioctl is not responsible for creating the > mapping of a: and b: to the same physical device. > The current implementation was trying to achieve this goal and > moreover it was done in the wrong way :-/ > The attached patch removes altogether the support for logical drive > map in int21h (and fixed Myst BTW). > > A+ > >------------------------------------------------------------------------ > >Name: int21_mapdrv >ChangeLog: ioctl 440F only returns non mapped drives (for now) >License: X11 >GenDate: 2005/10/12 18:41:20 UTC >ModifiedFiles: dlls/winedos/int21.c >AddedFiles: >RemovedFiles: >=================================================================== >RCS file: /home/cvs/cvsroot/wine/wine/dlls/winedos/int21.c,v >retrieving revision 1.81 >diff -u -u -r1.81 int21.c >--- dlls/winedos/int21.c 18 Sep 2005 11:11:36 -0000 1.81 >+++ dlls/winedos/int21.c 12 Oct 2005 18:40:47 -0000 >@@ -2627,19 +2627,12 @@ > break; > > case 0x0f: /* SET LOGICAL DRIVE MAP */ >- { >- WCHAR dev[3], tgt[4]; >+ TRACE("IOCTL - SET LOGICAL DRIVE MAP for drive %s\n", >+ INT21_DriveName( BL_reg(context))); > >- TRACE("IOCTL - SET LOGICAL DRIVE MAP for drive %s\n", >- INT21_DriveName( BL_reg(context))); >- dev[0] = 'A' + drive; dev[1] = ':'; dev[2] = 0; >- tgt[0] = 'A' + drive + 1; tgt[1] = ':'; tgt[2] = '\\'; tgt[3] = 0; >- if (!DefineDosDeviceW(DDD_RAW_TARGET_PATH, dev, tgt)) >- { >- SET_CFLAG(context); >- SET_AX( context, 0x000F ); /* invalid drive */ >- } >- } >+ /* FIXME: as of today, we don't support logical drive mapping... >+ */ >+ SET_AL( context, 0 ); > break; > > case 0x11: /* QUERY GENERIC IOCTL CAPABILITY */ > > >------------------------------------------------------------------------ > > > >

1 0

Re: [d3d8] Fix cobe texture update support [bug-3550]
by Raphael 13 Oct '05

13 Oct '05

On Wednesday 12 October 2005 21:09, Oliver Stieber wrote: > Hi, > This patch allows cube textures to be updated fixing one of the problems > in BUG 3550 > > Oliver. Good catch (for a long time i was trying to find what happened) Regards, Raphael

1 0

Winefile change - Where do I request one
by Craig macLeod 13 Oct '05

13 Oct '05

Hi, I would like a change to the Winefile application to add the ability to parse the commandline for it. Mainly so you can pass in a startup folder. eg winefile c:/temp will open the selected path under /.wine/ folder. This feature would be useful so an application can open a browse folder option. This is not a bug as such and I am not sure is bugzilla is the appropriate place to request this. Could someone let me know where I should request the small change. Thanks in advance.

2 1

Bugzilla administration policies
by James Hawkins 13 Oct '05

13 Oct '05

Hi, I really appreciate the effort everyone has put into cleaning out the old bugs in our bugzilla recently; however, I do have an issue with the way we're closing some of the bug reports. The ultimate outcome of wine is to enable a user to run windows apps just as they would in windows, so if a user has to run the app with a native dll or follow special instructions to make it work, then there is a bug in wine that needs to be fixed. Quite a few bugs have been closed recently referring the user to the instructions in the AppDB or to a list of dll overrides that makes the app work. Recommending a dll override can be useful to the end user as a temporary workaround, but the bug hasn't been fixed. Cleaning out the bugzilla is well appreciated, but we must keep up due diligence in order to keep wine's bugzilla as a reliable status of wine's bugs. I offer this as the beginning of a discussion of bugzilla administration policies. Any thoughts, comments, and ideas are welcome. -- James Hawkins

8 20

Re: RICHED20: fix bug# 3541 (crash in EM_POSFROMCHAR when offset>=text length)
by Jonathan Ernst 12 Oct '05

12 Oct '05

You forgot to attach the patch... thanks. Le mercredi 12 octobre 2005 à 12:58 -0700, Krzysztof Foltman a écrit : > I'm still surprised how could I overlook that - luckily, the library of > test cases is growing :) > > ChangeLog: > * fix unnecessary (and harmful) repeated statement > -- Jonathan Ernst <Jonathan(a)ErnstFamily.ch>

1 0

New themes question
by Matevz Jekovec 12 Oct '05

12 Oct '05

Now that Wine supports different theme packs for Windows, would it be possible to render Windows widgets using the native current desktop KDE/Gnome theme? Also other stuff like font size, name and colors for Windows widgets, could they all be unified? That would *really* be something:). Big thanks to all developers, that drove Wine so far and best wishes for the future! - Matevž

1 0

Warblade runtime error (Warblade install error cont'ed)
by Sebastien Fievet 12 Oct '05

12 Oct '05

Hi all, I grabbed a CVS snapshot yesterday, and while the builtin COMCTL32 doesn't work, with the native one, i finally managed to install Warblade (as previously reported by Marcus Meissner), whereas wine-20050930 crashed. Now that i moved one step further, a new error appears, when launching the game : err:seh:EXC_DefaultHandling Exception frame is not in stack limits => unable to dispatch exception. According to Marcus it may be copy protection related... Any little help is fairly welcome! Regards, Seb.

1 0

Ping
by Daniel 12 Oct '05

12 Oct '05

Is there anyone that actually receives my mails? confused, Daniel

5 5

D3D7 -> WineD3D, 2nd attempt
by Stefan Dösinger 12 Oct '05

12 Oct '05

Hello, I am trying again to Implement Direct3D 7 using WineD3D, and I've made some progress. The D3D7 Device implementation seems to initialize correctly, with the correct surfaces. My solution looks like this: * DirectDraw is unmodified, and it remains in ddraw.dll. * Direct3D7 uses generally the Direct3D9 interface of WineD3D. The only changes made to WineD3D are in WineD3DDeviceImpl_Release and a little change in WineD3DSurface. * WineD3D Surfaces can be attached to DDraw Surfaces, and they receive the properties of their parents, including the memory reserved for the surface * The D3D7 implementation creates a SwapChain and a RenderTarget from the DirectDrawSurface it's attached to, as well as a DepthStencil WineD3D surface to make WineD3D happy I've made the following changes to WineD3D so far: * Make WineD3D handle dxVersion 7, generally with the same code as with dxVersion 7 * A new parameter to WineD3DDevice_Create: a pointer, which specifies an existing surface memory. If != NULL is passed, no memory is reserved by WineD3D, and it's not Released on WineD3DSurface_Release * When releasing the WineD3DDevice, don't release the parents of the RenderTarget, the DepthStencilBuffer, BackBuffer and FrontBuffer, because ddraw.dll needs it's surfaces. Instead, release the WineD3DSurfaces only. The whole thing is far from beeing useable, if anyone is interested in the code, I can send it, but be warned, it's quite a mess at the moment. My plan is to get some games running, and then I'll send small and clean patches for CVS commit and upload a big patch somewhere for prior testing. Stefan

3 10

winelib .so change in 20050930?
by Michael Ost 12 Oct '05

12 Oct '05

With the advent of 20050930 wine can no longer load the shared libraries used by my winelib app. Are there any docs or descriptions about how to deal with this change? I have an app that gets built into, say, ./app/app.exe.so. It uses a shared library, say ./lib/liblib.so, that uses win32 APIs. To build ./lib/liblib.so I just compiled and linked using gcc. To build app.exe.so I would use winebuild to scan the object files at ./app/*.o and ./lib/*.o. That created wrappers for all the win32 functions both in ./app and ./lib. The wrappers code from winebuild gets linked in to app.exe.so. Wine used to be able to deal with this. With 20050930 wine complains that the win32 references in liblib.so can't be resolved and quits. I am guessing that something about wine dll loading has changed, so that the function wrappers for a wine DLL have to be in the file itself. That is, I would have to run winebuild on the lib object files, create lib.dll.so and then link app.exe.so against that. I started down this path with some success and then realized that, gulp, I would have to create a spec file for my libraries. Hundreds of C++ functions in several libraries. If this is indeed required, is there any help in building a spec file? Is it possible to export C++ functions as opposed to straight C? Winelib has always been the wild and woolly frontier. We haven't been bitten in a while; I guess we were due! ... mo

2 6

← Newer
1
...
17
18
19
20
21
22
23
...
34
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 October 2005