Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!nih-csl!lhc!mimsy!kelso
From: kelso@mimsy.umd.edu (Stephen Kelley)
Newsgroups: comp.sys.amiga.tech
Subject: PopUpMenu good Path bad (on an A3000)
Keywords: PopUpMenu,Path,Dos2.0
Message-ID: <26728@mimsy.umd.edu>
Date: 26 Sep 90 18:31:24 GMT
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 27

First the good news (and possibly a repeat) as they say:
	PopUpMenu (vers 34) works *great* w/ 2.0! My thanks to the
	author(s).

Next the bad news:
	Path (as in the 2.0 command) hangs the system if given >7? 8?
(I had about 10) arguments. Really *weird*! The hdisk blinks rythmically
seemingly looking and not finding something crutial. Actually it acts
the same as it did when I installed my extra memory chips in the wrong
slots.
	NO! I did *not* hose it up by pounding on it or dropping it (;-}
After disabling the startup-seq. (thanks for *that* option CBM!) and
breaking the "path ... add" into 2 separate commands it booted fine
(and perceptably quicker, huh!).
	Is there a limit to the no. of parms in a shell? (Oh, Std. 2.0 shell
btw).

Other odd news:
	Has anybody had a problem w/ "ls" in 2.0? I switch (depending on
shells, etc) between Manx's ls, Csh4.01, & 4.0. Anyway, *one* of then
grabs *gobs* of cpu delaying keystrokes and even mouse movements. It
does finish (depending on my patience) but it's definately cpu bound
(no disk light while thrashing).
	I'll try to catch and document this one better, but I thot I'd
mention what I had found while I'm at it. Oh, my 1st reaction on it is
that I'd done 2 or more 'ls' *quickly* (or a cd & an ls) and dir/file
locks were not released/checked correctly.