[13021] in Athena Bugs
Re: MZ1.1: No Ticket File Found
daemon@ATHENA.MIT.EDU (Scott McGuire)
Mon Dec 12 13:54:05 1994
Date: Mon, 12 Dec 94 13:53:18 EST
To: rita@MIT.EDU (Rita A. DiCecca)
From: smcguire@MIT.EDU (Scott McGuire)
Cc: maczephyr@MIT.EDU, bugs@MIT.EDU
> I mean that she can run/execute the program once (send many zephyrs, etc.)
> But after she hits that command-Q, it's history. The program won't run
> a "second" time. It doesn't crash the machine, but it does hang up
> on the Authentication dialog box for a bit and then MZ quits with
> the error.
Okay, that's what I thought you meant.
>> When I experienced the problem on my machine, I reinstalled the system
>> software and this solved the problem.
>
> No. I refuse to tell this person to reinstall the system software.
As I said, it isn't a good answer at all and I didn't expect you to tell
them that. I just offered it as a data point for what fixed the problem
for me. (But the authentication-dialog-bug for me only developed after I
had a failed system reinstallation, so it was logical for me to try again.)
I don't know if it actually would help anyone else because no one else
wants to try it just to fix this silly bug, and I don't blame them in the
least.
>> I am still hoping it's some sort of INIT conflict, although you say that
>> she turned all the extensions off. Can we get a list of INITs the user is
>> running?
>
> We can but she's tried to run the program w/ ext. off so wouldn't that help?
I assume you didn't have her turn *all* the extensions off because MacTCP
is an extension? (Sorry, I don't mean to tell you your job or imply you
don't know what you're doing, I just don't know what you mean by
"extensions off" - I am assuming you mean "all but essential extenstions
off.") That's why I asked again. Anyway, I'm flailing here on this bug,
so I thought maybe if I got a list of extensions from all the people who
were experiencing it, I could get a likely culprit. I ask only because the
very first person to report this problem later reported that he solved it
by upgrading an out-of-date extension (Greg's Buttons, but since no one
else who has this bug has had Greg's Buttons running, I don't think it's
the sole cause, if a cause at all).
>> Can we also get them to try this - throw out old copy of MZ, reboot
>> machine, get new copy, and try from there? (I have developed a strange
>> belief that running a "bad" copy first may result in any new copy of MZ
>> that is run directly afterwards being similarly affected.)
>
> Did it, tried it. Threw out old copies, got new copies, rebooted
> and sang the National Anthem. Nothin' :-(
Okay, thanks. Just checking!
>> Thanks for the info, and any more you can provide.
>
> PS- Customer will be out until Thursday 12/15 so we'll need to
> wait until after then to ask her to do anything.
All right.
Wordily,
--Scott McGuire / smcguire@mit.edu
MacZephyr Programmer / IS-DCNS, MIT
Please send all MacZephyr comments to: maczephyr@mit.edu
