Path: utzoo!attcan!uunet!snorkelwacker!apple!amdahl!JUTS!ked01 From: ked01@ccc.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga.tech Subject: Re: ls bugs (was: Strange filesystem prob. w/2.0) Message-ID: Date: 30 Jul 90 08:00:54 GMT References: <6633.26aa3109@jetson.uh.edu> Reply-To: ked01@JUTS.ccc.amdahl.com (Kim DeVaughn) Organization: Amdahl Corporation, Sunnyvale, CA 94086 Lines: 36 In article <6633.26aa3109@jetson.uh.edu> honp9@jetson.uh.edu (Jason Tibbitts/The Blob Shop) writes: > > I also have been experiencing intermittent crashes when running both version > 4.0k and version 3.1 of ls. > > BOOM. I get a disk corrupt requester. God this scared me when it first > happened. A reboot returns everything to normal. > > HardFrame HD interface rev1.5 > > 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.) Your's is the 3rd or 4th similar report I've had where the item in common is the HardFrame controller. I'm at a loss for an explanation to this problem, as I have no problems at all with my 2090A/Quantum setup. Anyone know anything "funny" the HardFrame driver/etc. might be doing that could interact with vanilla calls to Examine()/ExNext()/Info()/etc? I thought I had a lead to a problem with ls's mallooc'ing code, but that turned out to be bogus. I'm still hunting for any clues to this and/or the problems people are having with it under 2.0 ... /kim -- UUCP: kim@uts.amdahl.com -OR- ked01@juts.ccc.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25