Re: Fix Font Manager?

[jamesp@pro-nsdapple.cts.com (James D. Pangrazzi)]

Eric S. Ford Writes:
 
>> There is a third FixFontManager. It was put out by GS Softdisk. There
>> is a local BBS that has it in their file library however one of the 3
>> files is corrupt. I spoke, by voice mail, to the one who put it up and
>> he said that he would get to it when he had the chance. The explain
file is good and so is the init file. It is the Doc file that is corrupt.
 
> If it came out on GS Softdisk, what's it doing on a "local BBS".  I
> thought everything Softdisk puts out is copyrighted and redistribution
> disallowed.
 
Eric:
 
Rather then explain it myself, and still leave you in doubt, I thought I
would post the Explain file. If this is not enough to chill out your fever
perhaps you should procure it or dial the Number listed below.
 
Dear Online User--
 
There has been considerable confusion over the FixFontMgr601 patch that
Nathan Mates (and then Greg Templeman) uploaded to several of the online
services lately. This new upload supersedes and replaces ALL previous
versions. Do not use any of the older versions. For clarification this
version has a v2.0 designation. Please make it known to your online
buddies that there is a newer version and that they should get it.
 
The confusion was a result of several things: Nathan's original upload had
some problems and should also have been copyright Softdisk Publishing,
Greg uploaded a replacement of the same name, Bryan Pietrzak wrote several
(somewhat rude) letters that confused the issue, Sysops were inconsistent
in the version they chose to leave online, and we took longer than
expected to respond to the "crisis".
 
I apologize for the confusion and the necessity to download yet another
file to fix the Font Manager. Hopefully, this will clear up any and all
questions/problems. If you have ANY trouble, feel free to contact me
personally at 1-318-221-8718. Thank you and enjoy it!
 
Lee Golden, editor
Softdisk Publishing
 
 
AN ADDITIONAL NOTE TO Jack Mortimer and others: The reason I did not post
the name of the bbs is because I wanted to give the person who posted the
fix an oppertunity to replace the corrupt file. Thus avoiding any further
confusion.
 
Happy Computering!!  Jim
------------------------------------------------------------------------------
ProLine:  jamesp@pro-nsdapple              Internet: jamesp@pro-nsdapple.cts.com.cts.com
UUCP:     crash!pro-nsdapple!jamesp        ARPA:     crash!pro-nsdapple!jamesp@nosc.mil