[609] in Tooltime
Nick and printing
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Nov 28 10:29:11 1997
Date: Fri, 28 Nov 1997 10:33:45 -0500
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Looks like Larry Egan resolved this printing issue.
Could someone (Rob, Peter) relay this to Nick and other help desk staff.
Thanks,
..Steve
[0576] daemon@ATHENA.MIT.EDU (Larry Egan) Tooltime 11/20/97 16:58 (11 lines)
Subject: Printing with Scopus on NT Machines
Date: Thu, 20 Nov 1997 16:58:23 -0500
To: tooltime@MIT.EDU
From: Larry Egan <legand@MIT.EDU>
Printing a log from Scopus causes Scopus to rudely abend. A remedy is to
change the Page setup option from Simple Style justified to Paginating
Styles layout.
Hope this suggestion helps,
Larry
--[0576]--
>To: tooltime@MIT.EDU
>Cc: help-super@MIT.EDU
>Subject: my job
>Date: Wed, 26 Nov 1997 16:09:51 EST
>From: Nicholas S Howard <nhoward@MIT.EDU>
>
>I am having serious trouble doing my job here. Monday I went to print out a
>log (log#87017) and on every (NT) machine I tried, clicking "print" or
>selecting print from the file menu to print this particular log crashed the
>program with the good old "application error Exception error: access
>violation.
>I went to print through netscape but no one I could find knew the address. I
>was over fifteen minutes late to the client's office because I couldn't PRINT.
>
>When are we going to have a reasonable way of printing logs?
>(and NO netscape doesn't qualify. running netscape, finding the page, typing
>in the log number, finding out you're trying to use someone elses
>certificates,
>quitting netscape, creating a new profile, getting new certificates, finding
>the page, typing in the log# and printing with netscapes print manager to get
>something that takes more than twice the amount of pages it should is NOT an
>acceptable substitute to clicking "print" and getting a useful printout of
>the log.
>
>Then, today, I did a "find open" realized how useless it is to have summary
>as the last thing on the list and modified result set to put it in a more
>reasonable place. Decided to leave it on the screen and closed all of the
>found
>sets and it resulted in the same form of crash (access violation) I was unable
>to reproduce it, which makes it even worse.... a program that crashes
>RANDOMLY.
>
>Here it is, 4:00 and I haven't even begun to TOUCH a housecall log yet.
>
>The queue is at 430 and climbing for no other reason than this program.
>
>WHEN WILL ANYONE AT MIT LEARN TO CALL A SINKHOLE WHAT IT IS???
>
>Sincerely,
>Nick
>
>
>
>
>
>
