> > You might want to take a look at microwindows if
> you
> > want GDI/framebuffer
>
> However, keep in mind that Microwindows can be had
> at
> either MPL and GPL licenses.
True, but you might be able to get them relicense
certain parts for wine.
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
Fix for GetNearestColor so it returns the true color rather than the system
palette if the device does not support a palette (ie > 256 colors). This not
quite what the Windows SDK docs say, but it's what happens in practice...
Dave Hawkes
While this is not critical, or even a large amount of work, I noticed
when playing around with the floppy media problem that wine does not
attempt to mount either a floppy or CD to display the contents.
Was this intentional does anyone remember ? If not does anyone have
reservations about trying to enable it?
--
Keith Matthews
Frequentous Consultants - Linux Services,
Oracle development & database administration
Fallout II requires that a certain file is located
on a CDROM drive. For some reason it checks this using
SetFileAttributes, which is supposed to fail on readonly
drives. This used to work until the following patch broke
this behaviour (message continues after the patch):
Index: file.c
===================================================================
RCS file: /home/wine/wine/win32/file.c,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- file.c 2001/05/14 20:09:39 1.26
+++ file.c 2001/05/18 23:18:25 1.27
@@ -104,7 +104,7 @@
{
FILE_SetDosError();
MESSAGE("Wine ERROR: Couldn't set file attributes for existing file \"%s\". Check permissions or set VFAT \"quiet\" flag !\n", full_name.long_name);
- return FALSE;
+ return TRUE;
}
return TRUE;
}
The above patch obviously breaks Windows compatibility (and likely has a
bug related to FILE_SetDosError). I would like to suggest that this patch
is either removed or replaced with a patch that includes a C comment that
properly documents reasons for this deliberate incompatibility and that
either only affects non-CDROM drives or drives configured using
some magic flag in Wine configuration file.
--
Jukka Heinonen <http://www.iki.fi/jhei/>
Hi folks,
I just installed WINE for the first time and had some trouble getting
dlls to load until I set the "system" option to my Win2k partition's
system32 directory in wine.conf. Auto discovery of the proper system
directory for wine.conf by wineinstall seems like a useful thing for new
users. Would it be useful if I put together a small patch to the
wineconf program so that running wineinstall will select the right
system directory for configuration?
Also, is it correct to assume that if a system32 subdirectory exists
under the winnt or windows directory that it should be set given
preference in wine.conf as the system directory?
Thanks,
Brian
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
and while we are on the subject what is the philosophy on ifdefing header
files?
(I have freetype 2.0.1 from RedHat 7.1 so this morning's build failed
because I don't have the trig stuff.)
If we test for a header file and only include it if it is present should we
be putting similar ifdefs around the code that required the header and
providing alternatives when it is not present, or specifying that it NEEDS
to exist?
Bill
Hi everyone,
We just put this together for some testing, and thought that someone might
find it handy. I'm not submitting it to wine-patches, since we haven't
tested it on the most recent winehq tree, but it should be pretty easy to
integrate in. It's not 100% complete by any means, but it has both GDI
bitmap and DDraw support. We can vouch that it runs some of the DDraw
samples, but beyond that, who knows.
That said, the SDL driver should be a useful alternative to the ttydrv
for testing purposes.
-Gav
--
Gavriel State, CEO
TransGaming Technologies Inc.
http://www.transgaming.com
gav(a)transgaming.com
At 10:11 AM 1/29/02 +0100, you wrote:
>Running the program The 4th Coming after updating
>today,
>results into these messages :
>fixme:win32:SetCriticalSectionSpinCount
>critsection=0x7ff063b8: spincount=1000 not supported
<snip>
This patch is not yet applied, it can hardly be responsible.
See documentation/cvs-regression for the complete
procedure to make sure a particular patch has caused
a regression.
Gerard