Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!haven.umd.edu!uflorida!travis!hardy!leoh
From: leoh@hardy.hdw.csd.harris.com (Leo Hinds)
Newsgroups: comp.windows.ms
Subject: Re: Why won't Windows print?
Message-ID: <3237@travis.csd.harris.com>
Date: 3 May 91 03:49:57 GMT
References: <1991Apr28.203109.9185@midway.uchicago.edu> <1991May1.201553.19249@sbcs.sunysb.edu>
Sender: news@travis.csd.harris.com
Organization: Harris Computer Systems, Ft. Lauderdale, FL
Lines: 34

In article <1991May1.201553.19249@sbcs.sunysb.edu> altman@sbstaff2.cs.sunysb.edu (Jeff Altman) writes:
>Actually, Scott, you are probably the only one who has tried to install 
>all of the fonts and keep all of the fonts.  I have download many fonts.
>Many are of poor quality, and others are broken.  So I installed them 
>one at a time seeing if I liked it or not then deciding.  Of all the fonts
>I currently have about 128.

I (unfortunately) do not have the time (at work) to go through all the fonts
individually & weed out the ones I really want to keep, and sometimes 
decide which version of the font with the same name I prefer.  So I too 
tried to install all the ones I had obtained from cica.  

As I responded previously to this post, I also ran into the same problems 
as the original poster.  I have since contacted uSoft on two occasions 
about this (neither person knew much), and subsequently called Adobe who 
promptly said that there are problems in the windows handling of softfonts 
that are "well known, but not acknowledged by uSoft".  The tech support 
person at Adobe recommended that I keep no more than 100 (130 max) fonts 
in my win.ini (system memory dependent point of failure) & have multiple 
win.ini's listing all the fonts I wanted.

>Now, Microsoft did not write the PS driver nor do they support it.  They
>distribute it free of charge with Windows.  But the driver belongs to and
>was written by Aldus.  You might consider giving them a call and mention 
>the limitation to them.

I am at home now (no win3), but I would have guessed that the PS driver 
was written by Adobe, not Aldus ... not that that really helps as the Adobe 
tech support person categorically denied their involvement in the Win3 PS driver.


leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr