Re: Cygwin XFree86 installation on D:

[Harold L Hunt <huntharo at msu dot edu>]

Mark,

I know exactly what happened.

You had Cygwin/XFree86 installed on the C drive.  Then you removed it by
deleting it.  (Which left a registry key for Cygwin's mounts either under
HKEY_LOCAL_MACHINE/Software/Cygnus Solutions/Cygwin/mounts
v2/'/usr/X11R6/lib/X11/fonts' or under the same key for
HKEY_CURRENT_USER.  This key points to c:\cygwin\usr\X11R6\lib\X11\fonts.)

You then reinstalled Cygwin/XFree86 via setup.exe but pointed it to the d:
drive this time.  Cygwin's setup.exe was smart enough to correct the mounts
for the standard mounts, but it does nothing for other mounts, such as for the
fonts directory.

We basically need a pre-install script for the fonts package that always
unmounts the fonts mount and remounts it to the current Cygwin installation. 
Then we are ensured that we will intall the fonts on the correct drive or
path.  I'm not sure if there is such pre-install script handling.

Your workaround follows:

Open up regedit.exe or regedt32.exe and proceed to the registry keys mentioned
above.  Edit the fonts mount key and change the drive letter to 'd'.  That
should do it.  You've already moved the fonts to the d drive, so they should
be in the right place.

Alternatively you can fix this by doing an `unmount' and a `mount', but I
don't remember the parameters well enough to tell you exactly what to run...
perhaps someone else will give you a quick example.

Harold



mark.hackmann@philips.com said:

> All,
> 
> I'm new to this, but I spent some time looking through the instructions, web
pages and archives for this problem, and couldn't find it.  My apologies if I
missed it.
> 
> I installed a complete Cygwin and XFree86 on my Windows NT box in standard
fashion, with the exception of pointing everything to the D: drive (a
partition of the physical drive).  This worked swimmingly, and came up with no
trouble.  However, I noticed a
> Cygwin subtree on the C: drive that was pretty sparse, having nothing in it
until you get down to  C:\Cygwin\usr\X11r6\lib\X11\fonts, where there are lots
of subdirectories.
> 
> Hmmm, says I.  Is this necessary?
> 
> So, I moved it to the D: drive in the same place, where, incidentally, there
was nothing, and lo and behold, XFree86 is now broken!  Here's the log file:
> 
> ==============================================
> winInitializeDefaultScreens () - w 1024 h 768
> winDetectSupportedEngines () - Windows NT/2000
> winDetectSupportedEngines () - DirectDraw installed
> winDetectSupportedEngines () - Allowing PrimaryDD
> winDetectSupportedEngines () - Returning, supported engines 0000001b
> winSetEngine () - Using Shadow DirectDraw
> winAdjustVideoModeShadowDD () - Using Windows display depth of 16 bits per pixel
> winAdjustForAutoHide - Original WorkArea: 0 0 768 1024
> winAdjustForAutoHide - Taskbar is auto hide
> winAdjustForAutoHide - Found BOTTOM auto-hide taskbar
> winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024
> winCreateBoundingWindowWindowed () - WindowClient w 1018 h 742 r 1018 l 0 b
742 t 0
> winCreateBoundingWindowWindowed () -  Returning
> winInitVisualsShadowDD () - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16
> winLayerCreate () - dwDepth 16
> winRandRInit ()
> winCreateDefColormap () - Deferring to fbCreateDefColormap ()
> winScreenInit () - returning
> Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing
from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing
from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing
from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing
from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing
from list!
> 
> Fatal server error:
> could not open default font 'fixed'
> =============================================
> 
> Sure enough, the font paths are not qualified with a drive letter.  When I
copy the stuff back to the C: drive, everything is hunky-dorry.
> 
> Anyone seen this before, or know what I should do?  Maybe it's a bug in setup?
> 
> Thanks,
> 
> -Mark
> 
>