[253] in installers
Re: concerns re: LPRSpooler and MINK interaction
daemon@ATHENA.MIT.EDU (Susan B. Jones)
Thu Oct 21 16:36:27 1999
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a11b4352946c5f6@[18.152.1.82]>
In-Reply-To: <v04020a0bb43526f3a23e@[18.152.1.182]>
Date: Thu, 21 Oct 1999 16:35:18 -0400
To: Alicia Allen <iggy@mit.edu>, installers@mit.edu, sw-release-team@mit.edu
From: "Susan B. Jones" <sbjones@MIT.EDU>
Cc: rccsuper@mit.edu
Could someone tell us which version of MinK you are trying to install?
And from where you are getting it?
Thanks,
Susan
At 4:27 PM -0400 10/21/1999, Alicia Allen wrote:
>Hi,
>These guys are RCCs. I'm not really sure what to respond to their concerns
>about LPR Spooler and MINK, because I was under the impression that
>everything was working.
>
>This resulted out of a specific problem with a client.
>
>thanks,
>Alicia
>
>
>>To: rccsuper@MIT.EDU
>>Cc: "Michael P. Phillips" <mpp@MIT.EDU>
>>In-Reply-To: Your message of "Thu, 21 Oct 1999 08:28:50 EDT."
>> <199910211228.IAA00349@holygrail.mit.edu>
>>Date: Thu, 21 Oct 1999 14:23:03 EDT
>>From: "Joshua C. Randall" <jrandall@MIT.EDU>
>>
>>
>>It might be that the new mink installer only installs the 32-bit
>>version of leash by default, and that the LPRspooler only knows
>>how to call the 16-bit version? Seems like we should either change
>>the installer to warn users that they may need the 16 bit versions,
>>or change the LPRspooler installer to get them itself.
>>
>>We certainly do need a new LPRspooler installer though... the current
>>installer has always had a bunch of errors in the installation that
>>complain about syntax of the files it uses to setup the queues for
>>specific printers. The printers seem to get setup okay anyway, but
>>the person installing has to click through a few errors for each
>>printer in order to get to the end (and this doesn't instill confidence
>>in the program).
>>
>>As for the winsock.dll problem, I continue to run into cases where either
>>Eudora or a Mink installer fails because of this file being corrupted.
>>The only place to find the fix for it (and the fact that it could be a
>>problem in the first place) seems to be on the internal helpdesk Eudora
>>errors page
>>( http://web.mit.edu/helpdesk/www/dontindex/eudora_errors_win.html )
>>
>>Seems like we could really use a stock answer for this, that includes all
>>programs that use the Mink installer (LPRspooler, HostExplorer, Eudora,
>>etc..)
>>and names this as a possible problem. The common error for the Mink
>>installer is "FTP Error 2001." We DO have an answer in the HostExplorer
>>section that deals with this error, but the answer blames another cause
>>(
>>http://hdstock.mit.edu/stockanswers/FMPro?-db=Answers&-lay=Main&-format=answer
>>.h
>>tml&-Token=24&AnswerID=622&Status=Ready&-find ). We could probably put
>>the answer in a "Mink Installer" section, and link to it from all the
>>programs
>>that use Mink installer. The answer could just be the appropriate section
>>of the eudora errors page, rewritten for normal people and with the addition
>>of it also being a problem for Mink (and actually most, if not all, 16-bit
>>network applications -- it's just that most people don't have any anymore).
>>
>>Let me know if you want me to write this up...
>>
>>josh
>>
>>>From: "Michael P. Phillips" <mpp@MIT.EDU>
>>>Message-Id: <199910211228.IAA00349@holygrail.mit.edu>
>>>To: jrandall@MIT.EDU
>>>X-Cc: rccsuper
>>>Date: Thu, 21 Oct 1999 08:28:50 EDT
>>>
>>>Josh,
>>> Thanks for the help on this one. I had long since forgotten about
>>>the mighty-morphing Winsock.dll problem.
>>>
>>>rccsuper: From his final mail it sounds like LPRspooler does not work
>>>with our new Mink installer. If this is true then we need a new LPR
>>>spooler, right?
>>>
>>>Thanks,
>>>Mike
>>>
>>>------- End of Forwarded Message
>>
>
>
>
>
>----------------------------------------------
>Alicia Allen iggy@mit.edu
>
>MIT Resnet Coordinator (617) 253-0191
>MIT Network Security N42-140
>----------------------------------------------
