This is the mail archive of the
cygwin-xfree@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: XWin Direct Draw error
- To: <cygwin-xfree at sourceware dot cygnus dot com>
- Subject: RE: XWin Direct Draw error
- From: "Suhaib Siddiqi" <ssiddiqi at inspirepharm dot com>
- Date: Fri, 9 Jun 2000 08:32:00 -0400
>
> I have managed to get the XGDI and DXWin32 servers to work, but XWin
> throws an error in a dialogue box:
>
> Direct Draw Init Failed
> Error = 88760078(unknown error)
Seems to be a DirectX DLL intiallization problem. Perhaps try
DirectX 7.1.
The XWin.exe is not linked directly to DirectX/DirectInput DLLs.
Instead executing XWin.exe calls, the xf_dx.dll, which contains
the actual X-server code and a loader code to load directx dlls
from Windows.
>
> This is on Win95, cygwin1.1.2, DirectX7.0a. Is there some way to fix
> this?
>
> The XGDI and DXWin32 servers perform VERY slowly. I have a 233MHz PIII
> and 128MB RAM. Is there a way to speed them up? Will the XWin server be
> quicker when I get it running?
I will look into it. I need to find someone's old machine. BTW:
is there a 233 MHz PIII? or do you mean Pentium only?
>
> BTW: for those having a problem getting things to work; unpack the
> bzip2s and then use winzip to install the tar file contents. When I used
> 'bzip2 ... | tar -xvf -' in bash, I ended up with X11 dirs which could
> only be accessed by cygwin and not from DOS/Windows. This makes the font
> files and rgb.txt file unreadable from the windows servers at least.
> Maybe someone else could explain why this happens?
I do not understand why extracting the archive under Cygwin bash shell
would make the extracted directory invisible/inaccessable?
Suhaib
>
> Nick.