Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!jetson.uh.edu!honp9 From: honp9@jetson.uh.edu (Jason Tibbitts/The Blob Shop) Newsgroups: comp.sys.amiga.tech Subject: ls bugs (was: Strange filesystem prob. w/2.0) Message-ID: <6633.26aa3109@jetson.uh.edu> Date: 23 Jul 90 04:04:41 GMT References: Organization: Blob Shop Programmers Lines: 36 [Munch all you want, I'll type more] In article , kim@uts.amdahl.com (Kim DeVaughn) writes: > I've had a report from Christopher Wichura on a strange problem that has > shown up when using the new version of "ls" that was recently posted (v4.0k) > under 2.0 on a 3000 (Kickstart 36.141 and Workbench 36.68). I'm at a loss > to figure out what the problem is, so ... I also have been experiencing intermittent crashes when running both version 4.0k and version 3.1 of ls. To repeat the problem I: Boot machine, ending with open shell. Control-D at beginning of startup-sequence does not change things. type ls. BOOM. I get a disk corrupt requester. God this scared me when it first happened. A reboot returns everything to normal. My system: Amiga 2000 rev 4.4 (I believe) 1.3 roms, 1.3 wb 1 meg ram (512K chip, 512K fast) HardFrame HD interface rev1.5 Quantum 105S drive with 105P controller My prompt just reads 2.> when I do this. A CD will return 105Meg: if I CD to DH0: , the problem goes away. (In fact, it I CD to anything, I can use ls just fine.) -- \/ Jason L. Tibbitts III // | THEnet: {George|Jane|Elroy|Judy}::HONP9 /\/"Blob Shop Programmers: // | SesquiNet, Telnet, etc: HONP9@JETSON.uh.edu \/ Because We're Bored!" \X/ | CREN (BitNet): HONP9@UHVAX1 "Ewige /\ . DISCLAIMER ." Whose opinions did you think there were?" ; Blumenkraft"