edavies@uvicctr.UUCP (edavies) (01/17/89)
Summary: dir/ls bug in Shell 3.01A
I'm having trouble using Shell 3.01A, by Carlo Borreo and Cesare Dieni.
My trouble is that trying to perform a dir|ls on some directories can
take incredible lengths of time. This problem was present when running
both 1.2 and 1.3 versions of the operating system.
I have an amiga 1000, single internal drive, 2meg fastram.
example scenario:
1.3 workbench in df0:
ls df0:libs /* works fine */
copy ram:arp.library ram:dres.library df0:libs /* dres = dillon resources */
ls df0:libs /* long time intervals between each disk access
perfmon shows cpu totally utilized
after 1 or 2 minutes, the directory is listed
*/
the same symptoms if I:
copy df0:libs ram:libs
ls ram:libs
I believe I observed the same problem happen when I 'globbed' the same
directory as well, ie:
echo *
Is this happening to anybody else?
What is it doing during all that empty time, busy waiting for what?
is there any easy fix?
Thanks in advance.
Eric Davieskent@swrinde.swri.edu (Kent D. Polk) (01/18/89)
In article <603@uvicctr.UUCP> edavies@uvicctr.UUCP () writes: >Summary: dir/ls bug in Shell 3.01A > >I'm having trouble using Shell 3.01A, by Carlo Borreo and Cesare Dieni. >My trouble is that trying to perform a dir|ls on some directories can >take incredible lengths of time. This problem was present when running >both 1.2 and 1.3 versions of the operating system. > >I have an amiga 1000, single internal drive, 2meg fastram. > >example scenario: > 1.3 workbench in df0: > >Is this happening to anybody else? >What is it doing during all that empty time, busy waiting for what? >is there any easy fix? This happens to me under 1.2 & 1.3. I used to use the PD version of VDK:, but had to quit using it since Shell 3.01A locks up on it fairly frequently. I first thought it had to do with the VDK: date problem, & used touch on all files in VDK: before I did a wildcard acess to the file or listed it. Seemed to help some. It seems that any Wildcard directory search (including ls) can 'lock' it up. Anyway, it locks up on reading other directories other than VDK: but I haven't figured out why. Also after doing this on a directory, even Amigados commands seem to have the same problem until the system is rebooted. Browser & Workbench don't have any problem with these directories, & I have found that Browser can sometimes free up Shell's problem by simply having browser list the directory. (But not always). Oh yeah, it does this on an A1000 w/Spirit 1.5 meg expansion & A500 w/501 expansion, running Dmouse & FACC. >Thanks in advance. > >Eric Davies =============================================================================== Kent Polk - Southwest Research Institute |> Frogsoundz: Ultrasonic {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent|> waveforms time-dilated ___/\___/\___/\___/\___/\___/\___/\___/\___/\___/\____|> & played on my Amiga. ===============================================================================
rap@ardent.UUCP (Rob Peck) (01/20/89)
In article <8657@swrinde.swri.edu>, kent@swrinde.swri.edu (Kent D. Polk) writes: > >is there any easy fix? > > This happens to me under 1.2 & 1.3. I used to use the PD version of > VDK:, but had to quit using it since Shell 3.01A locks up on it fairly I guess occasionally we have to post a reminder... there NEVER was an official PD version of VDK:. This was always a commercial (though a VERY low cost) product written by Neil Katin, once of Amiga Computer. At one point in time, when version 1.0 of the product was out, someone Hacked the binary to remove Neil's copyright notice and then posted the binary as though it was a PD product. It is not, and was not PD. I have the commercial version and am quite satisfied with it and there are patches to it available (on PLINK for one) that makes it not report "full" if asked if there is room for a file so downloading into VDK: from some terminal programs works just fine. SOMETIMES when I compile and test programs, I manage to kill VDK:, but then when my programs go awry, I probably kill VD0: and RAD: as well --- wild pointers ahoy! Anyway, if anyone STILL thinks that any version of VDK: is Public Domain, they are mistaken and if it is still roaming on various BBS's, the owner/operator should be told to remove it. Nuff said. Rob Peck
kent@swrinde.swri.edu (Kent D. Polk) (01/20/89)
In article <1891@ardent.UUCP> rap@ardent.UUCP (Rob Peck) writes: > >I guess occasionally we have to post a reminder... there NEVER was an >official PD version of VDK:. This was always a commercial (though a >VERY low cost) product written by Neil Katin, once of Amiga Computer. > >Anyway, if anyone STILL thinks that any version of VDK: is Public >Domain, they are mistaken and if it is still roaming on various >BBS's, the owner/operator should be told to remove it. > >Nuff said. > >Rob Peck Sorry I had this misunderstanding, but I got VDK: when I bought my Spirit 1.5 Meg Ram board. It came with the disk & had a readme file that said something to the effect that the included version of VDK: was a pre-release. It had not info indicating that it was a commercial product. Does this mean that Spirit Tech. messed up when they included it, or did Spirit work out a deal to include VDK: with the Spirit software? I.e. am I officially using it or not? Thanks, =============================================================================== Kent Polk - Southwest Research Institute |> Frogsoundz: Ultrasonic {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent|> waveforms time-dilated ___/\___/\___/\___/\___/\___/\___/\___/\___/\___/\____|> & played on my Amiga. ===============================================================================