Path: utzoo!attcan!uunet!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: HELP Dave Hanie or Kim E. DeVaughn.
Keywords: ls 4.0k problems or somthing wrose.
Message-ID: <1965@lpami.wimsey.bc.ca>
Date: 11 Sep 90 20:31:58 GMT
Lines: 68
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <2063@nyx.UUCP>, bscott@nyx.UUCP (Ben Scott) writes:
>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:
>
>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.  

This too, is possible, though how likely it is depends a lot on whether you use
paths, and whether the files in question were ever in a directory other than
the one he thinks they are in.

>>>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 didn't notice if he was using any 'DirTools' or not. I am not familiar with
any of them, as I never use them. Whenever someone has a problem like this, I
assume (probably erroeously) that they have gone to the CLI in order to find
out what's really happening.

>>>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.  

Yes and no. I am not really blaming BAD for those problems where the user
crashed the machine while BAD was running, but I have blamed BAD for many
problems in the past, even though I have never used it. Many, many folks have
reported problems with BAD, and when they do, I recommend that theyFULLY back
up any partition they are going to run it on. Any program that shuffles your
data around on a partition leaves it is a bad state for at least a short time,
and the author's first priority should be to minimize this window of
innoportunity, in addition to the more obvious steps taken to ensure data
integrity. BAD has not always lived up to these criteria. I don't know if it
does now, or in the version to come, but not everyone has the latest version.

>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.   

Maybe I'll even buy it one day, but certainly not until it is proven to be safe
to use. IMHO, it has not proven itself yet.

-larry

--
It is not possible to both understand and appreciate Intel CPUs.
    -D.Wolfskill
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+