``Glen Carlzen``  wrote in a message to paul marwick:

>and FILES.BBS entries, failure to read most self-extracting archives, 

 `C>      Again I use OSC-124 for managing my files area on the bbs 
 `C> system.  Reading or archiving files.bbs files haven't been an 
 `C> issue here.  It works for me.

Just curious,  does it deals with recursion?  Archives within archives?

Does it have a specific set of archive types that it deals with,  and can you
add to that list?

 `C>      Failure to read "Self-Extracting Archives", if you mean 
 `C> that it runs the files, then I disagree with you.  But to VIEW 
 `C> (F3) an *.exe file works fine or as it should.  If you mean 
 `C> placing the curser on the file and hitting  key I 
 `C> wouldn't call that a BUG.  I would call that "Running the 
 `C> program" as it should.  IF you do the same on any other OS it 
 `C> would be expected to do the same thing.

I call that a pain in the butt!  I am used to the _default_ action when you
hit  (using InspectA) being that you want to _view_ the file,  you have 
to tell it specifically when you want to execute something,  with the F10 key. 
I don't often want to run something from this kind of program,  anyhow.  Yet I 
have that exact behavior to deal with on the Linux box and mc.  Although at
least there I can change it if I wanted to.

>odd behaviour after viewing files within archives, etc..).

 `C>      Odd Behavior after viewing files in an archive.  I have 
 `C> had this one a few times, but later found out that I didn't 
 `C> have my archiver setup properly on my system (info-zip in 
 `C> config.sys path statement - oversight by me).  Once I fixed 
 `C> that problem I haven't had any problems.  I have gone as far as 
 `C> reading 3 archives deep within a zip file with no real 
 `C> problems.  Works for me.

What did you have to do to fix the problem?  I may want to look into using
this program on the OS/2 box,  since InspectA won't deal well with 2GB+ of
free space (and that's the major problem I have with it).

>Having got no replies at all from the author, I wasn't prepared to register
>it

 `C>      I registered it because it DOES MORE than I would ask for. 
 `C>  Untel I tryed OSC-124 I us Norton Commander v4.0 & v5.0 on my 
 `C> OS/2 systems.  I have always used Norton Commander.  OS/2 
 `C> Commander has replaced then as the MOST used program on all of 
 `C> my OS/2 systems.

And would it be fair to say that the bit above about hitting  to
execute comes from that program?  That it's likely to be the case with all of
these "* commander" clones?

--- 
278/111
2433/225