Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!tut.cis.ohio-state.edu!bgsuvax!jyoull
From: jyoull@bgsuvax.UUCP (Jim Youll)
Newsgroups: comp.sys.novell
Subject: Re: KILL text file oddity NW 386 3.1A
Message-ID: <7235@bgsuvax.UUCP>
Date: 3 Apr 91 01:41:02 GMT
References: <5359@mindlink.UUCP>
Reply-To: jyoull@bgsuvax.UUCP (Jim Youll)
Organization: Bowling Green State University B.G., Oh.
Lines: 19

In article <5359@mindlink.UUCP> Ullrich_Fischer@mindlink.UUCP (Ullrich Fischer) writes:
>On a Netware 386 3.1A file server using Version 3.01 Rev D of the NET3.COM
>I ran into the following oddity:
>
>I created a batch file (KILL.BAT) containing 7 lines of the following form:
> [... details omitted]
>When I tried to find KILL, Neither DIR, nor FLAG found it.  QEDIT also couldn't
>find it and tried to create an empty KILL file.
>Has anyone heard of this problem?  Any ideas as to what might be going on?
>Is KILL a reserved filename under Netware 386?
>
I dunno, but I run Advanced Netware 2.15c, and after loading IPX and NET3
(specifically NET3) if I try to create a file called "NEXT" on any drive
at all (even local drives when I'm not logged in) the machine hangs.

Maybe I'm missing something obvious here (advance blush) but the filename NEXT
just wreaks havoc. You should have seen my confusion as I tried to d/l
a file that I had named "NeXT" last week - the machine kept crashing for
No Good Reason.