Re: XWin - multiwindow problem

[terry <tg5027 at citlink dot net>]

Harold,

I finally got a break from 'real' work to pursue this problem.  I got 
the latest ATI drivers (dated 2001) and DirectX 9 installed, but still 
no luck with running XWin -multiwindow.  There are no MS drivers for the 
card in Win98.  I got some additional display depths and tried them too. 
 The log is the same as below.  Any more hints?

I'm running the application o.k. not multiwindow, but it's tough 
training a windoze user to operate an xterm and twm.

Thanks,

terry

Harold wrote:
> In this case I think you need to try to install the drivers directly from your video card manufacturer on the non-working system and see if that helps.  On the other hand, if the manufacturer drivers are installed on the system that does not work while the other has the default MS drivers, then the manufacturer drivers might be the problem.
>
> Note that "non-multiwindow" mode on both computers will use DirectDraw, which has its own seperate driver, while "multiwindow" mode on both computers will use the GDI drivers.  These drivers are distinct, so problems with one won't necessarily cause problems with the other. Oddly enough, upgrading to DX 9.x might install some fresh drivers that could fix your problem.
>
> Give those things a try and let us know what happens.
>
> Harold
>
> terry wrote:
>
> > Harold,
> >
> > Thanks - I get the same log output using 16 and 8 bit.  I don't have other choices with the driver I'm using.  Both systems have ATI graphics cards of type Rage 128.  The working system has a specific monitor (Hitachi 751), while the non-working one is using Plug-and-Pray with a NEC 77F.  If you think it's worthwhile I can play with the 98 configuration.
> >
> > Terry
> >
> > ---------------------------------------------------------------------------
> > Harold wrote:
> >
> > Try changing the display depth on the problem machine from 32 bits to 24, 16, or 15 bits.  In fact, try each one of those depths if the first one you try doesn't work.
> >
> > Report your results to the mailing list please.
> >
> > Harold
> >
> > terry wrote:
> >
> >  > I have successfully setup a Win98se system with CygWin using startxwin.bat from a download a couple of weeks ago (Perhaps if it had been difficult, I would know better how to deal with this problem :>) ).
> >  >
> >  > I am attempting to do the same on another system with almost identical hardware, also using Win98se.  The significant difference between the systems is that the successful system has a 19" monitor @1600x1200 while the problem system has a 17" monitor @1024x768.  I have not modified startxwin.bat, and everything works fine 'non-multiwindow'.  I cannot determine how to deal with the error in the XWin log below. Many thanks for any help.
> >  >
> >  > terry
> >  >
> >  >
> >  > ddxProcessArgument - Initializing default screens
> >  > winInitializeDefaultScreens - w 1024 h 768
> >  > winInitializeDefaultScreens - Returning
> >  > OsVendorInit - Creating bogus screen 0
> >  > (EE) Unable to locate/open config file
> >  > InitOutput - Error reading config file
> >  > winDetectSupportedEngines - Windows 95/98/Me
> >  > winDetectSupportedEngines - DirectDraw installed
> >  > winDetectSupportedEngines - DirectDraw4 installed
> >  > winDetectSupportedEngines - Returning, supported engines 00000017
> >  > InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
> >  > winSetEngine - Multi Window => ShadowGDI
> >  > winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
> >  > winCreateBoundingWindowWindowed - User w: 1024 h: 768
> >  > winCreateBoundingWindowWindowed - Current w: 1024 h: 768
> >  > winAdjustForAutoHide - Original WorkArea: 0 0 768 1024
> >  > winAdjustForAutoHide - Taskbar is auto hide
> >  > winAdjustForAutoHide - Found LEFT auto-hide taskbar
> >  > winAdjustForAutoHide - Adjusted WorkArea: 0 1 768 1024
> >  > winCreateBoundingWindowWindowed - WindowClient w 1023 h 768 r 1023 l 0 b 768 t 0
> >  > winCreateBoundingWindowWindowed -  Returning
> >  > winAllocateFBShadowGDI - Creating DIB with width: 1023 height: 768 depth: 32
> >  > winAllocateFBShadowGDI - Dibsection width: 1023 height: -768 depth: 32 size image: 3142656
> >  > winAllocateFBShadowGDI - Shadow blit failure
> >  > winFinishScreenInitFB - Could not allocate framebuffer
> >  > winScreenInit - winFinishScreenInit () failed
> >  >
> >  > Fatal server error:
> >  > InitOutput - Couldn't add screen 0