🚀 go-pugleaf

<pre> In article 46jb6u$3hc@crocus.csv.warwick.ac.uk,
eoaai@csv.warwick.ac.uk (Chris Tilbury) wrote:

#Rich Graves (llurch@networking.stanford.edu) wrote:
#: I suggest addressing this bug by taking advantage of another bug. The
#: Win95 NetWare login script processor cannot handle commands with commas in
#: them, or that use lower-case drive letters, and cannot execute TSRs.
#: Create login scripts that require one of these things, and give the Win95
#: users nasty instructions if the parsing fails. I'm no NetWare guru, but
#: one should be able to help you write such a script. Win95 also fails to
#: parse no_default.
#
#This is a rather, well, immature approach for a systems administrator to
#take, don't you think? I can say with some certainty that were I to decide
#to "break" peoples machines remotely, not only would I get the reputation
#of a BOFH, I'd probably lose my job.

Not sure what you mean. What I meant to suggest was, devise a script that
takes advantage of the script parser oddities to allow Win3 machines to
log on gracefully, and also allow Win4 machines to log on, but send the
Win94 machines a message that they should really reconfigure their
machines in such-and-such a way. You're not breaking anybody's machine
remotely, I don't think.

#: Here's the relevant section of our FAQ. I think it needs to be revised if
#: you're seeing this behavior with 4.1.
#
#[snip]
#
#It certainly does. Last time I checked, this could also be caused by
#an old .LAN driver which itself was incapable of supporting packet
#burst. Hence, the other option may be to upgrade your network card drivers
#on the server.

<em>Thanks.</em> Despite my ego and immaturity, I would like the FAQ to be
a group project. I know very little about NetWare myself (obviously), and
the FAQ should.

#If you're going to support these machines, BTW, then you'll probably
#want to look into using system user & group policies, so you can
#prevent some of the other little 'suprises' which Windows 95 has in
#store, such as SAP advertising.

Unfortunately, those of us in .edu don't have the luxury of deciding what
we do and do not want to support. Students and faculty are going to plug
in whatever they want, and we have to react. The Communication department
here has a 3.12 server supporting machines running Win95, UNIX, every
version of MacOS, OS/2, and DOS 4.0 with NETX. They're not going to fix it
just because it's a mess.

-rich graves, llurch@networking.stanford.edu
 moderator of the win95netbugs list <a href="
 http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html">the FAQ</a>
 My old PGP key has been compromised. Please finger this account
 for the revocation certificate and my new key.</pre>
 There. I think I got the HTML more or less right. Happy?