Glenn Christensen wrote in a message to All:
 GC> Looking in UNCHECK from within Max I could see nothing - not the
 GC> old or the new. However, from Windows Explorer and from a directory
 GC> command from the command line ALL the files were present!
Glenn, did you give yourself R/W access to UNCHECK?  (-:
 GC> On a hunch, I went back into Max and used the HURL command to throw
 GC> the files into another area. No problem. They moved to the new
 GC> directory and are now visible there from within Max.
Now I'm confused.  If you couldn't see the files, how then did you HURL them?
 GC> So the question now is whether I've uncovered a Max bug or whether
 GC> this is one of Win95's idiocyncracies. Also, as this has happened
 GC> only to one caller, maybe the problem somehow lies with him?
Did you check all of your upload paths?  I run Max from OS/2 Warp and Win95 
and have not had the problem you're talking about.
 GC> Not known is whether or not callers could see these "cloaked"
 GC> files, as my UNCHECK area is not available to them. If they can't,
 GC> and a SysOp allows uploads to a lot of areas, the potential for a
 GC> real mess for a lot of people is here. (Not me. My file's areas are
 GC> very small. ) 
All of my upload paths are to UNCHECK.  That's the safest way to protect not 
only yourself, but your callers as well, regardless of your file area size.
 GC> Any thoughts on this would be appreciated...
Just remember you asked for this.  (-:
Regards,
Roger
--- timEd/2 1.10+
---------------