Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!isis!nyx!bscott From: bscott@nyx.UUCP (Ben Scott) Newsgroups: comp.sys.amiga Subject: Re: HELP Dave Hanie or Kim E. DeVaughn. Summary: Sure, blame B.A.D., everyone else does... Keywords: ls 4.0k problems or somthing wrose. Message-ID: <2063@nyx.UUCP> Date: 9 Sep 90 11:11:29 GMT References: <1932@lpami.wimsey.bc.ca> Reply-To: bscott@nyx.UUCP (Ben Scott) Organization: Public Access Unix - University of Denver Lines: 61 In article <1932@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >In <1990Sep6.034154.9272@ecn.purdue.edu>, yorkw@stable.ecn.purdue.edu (Willis F York) writes: >>well I have this WEIRD problem., I can't find some files. >>i know they are there. They are in my C: dir nd they run and everything. >>the problem i can't SEE them, I try ls -h (for hidden and No GO!) > >There are two ways, in general, that the Amiga finds files on disk. One is by >knowing the name of a file, and going directly to it. This is how a program >gets executed. The other was is by not knowing the name, and having to traverse >the directory structure. This is how a LIST or DIR works. [...] >Well, they are hidden, but not on purpose, and not properly. The directory >structure is corruptThere are a number of ways this could be, but in general, >one of the subdirectory or file headers that gets examined before the hidden >file has bad pointers in it. I can think of two other possibilities. One: I am told that the list command (the ARP list command, possibly not the normal Amiga one) has a bug that causes it to not list files with an invalid file date. This doesn't entirely explain why a "dir" wouldn't show them, though. Two: The files are NOT in the C: dir but are somehow on the command path, thus they run but do not show up when a dir or list of C: is performed. This seems most likely to me. >>also i got a "Weird" file in my c: dir it just called "t" >>with Dirtools is shows up as a square box then a "t" >>i can't delete this bugger to save my life. > >That is probably a corrupt file header showing up. Maybe - but it also could be just an errant (but otherwise normal) file with some odd character before the "t" (showing up in Dirtools as a non-printable character). I'd bet if he could figure out what character this is or find a dir util which can use nonprintable characters in filenames it could be deleted without harm. Then again, you may be right. >>I'll run FixDisk (I did run B.A.D on this floppy a week ago) on it. >>any help is welcomed, I have no idea what's going on. > >Ahh... there's the probable reason for all this. Something interrupted a run of >B.A.D. or perhaps it got confused. Sure... blame B.A.D. BTW: B.A.D. 4.0 still on RSN, but is more like RRRSN now. It's 100% operational, but there are a few details in the user interface yet to be properly finished. (no more real coding is needed, however) The authors tell me it'll be another two weeks. Note that they said something very similar back in March to me. But it is closer to release now than it was in March, this much I can vouch for. . <<<>>> -- .---------------------------------------------------------------------------. |Ben Scott, professional goof-off and consultant at The Raster Image, Denver| |Amiga UUCP node domain: bscott@vila.denver.co.us Else: bscott@nyx.cs.du.edu| |FIDO point address 1:104/421.2, or call the Arvada 68K BBS at (303)424-9831| |"Don't embarrass us..." "Have I ever?" - Buckaroo Banzai | *AMIGA POWER* | `---------------------------------------------------------------------------'