I have this proven to work routine in one of my programs to pull a
directory into memory of all files ending with *.MSG in a given
directory, and for me and 99.9% of the users out there, it works
flawlessly.
There is ONE user (yes, only one) who reports that even though files
are in the directory (and no errors are reported, and I trap them)
that the program seems to 'ignore' the files...
The routine is as follows, and once again - no errors occured, the
trap routine was not called, it simply did not load files, and of
course the user sent me a directory which indeed listed files in
the directory ending in "*.MSG" and he DID have the right path
(which I check for validity earlier in the code anyway):
------------------------------------------------------------------------
ON ERROR GOTO TRAP5
 count=1
 chdir netmail2$
 a$=dir$ ("*.MSG"):if a$="" then count=0:goto DIRTMP
 nm$(1)=a$
 do until a$="" or count=8000
  a$=dir$
  if a$"" then count=count+1:nm$(count)=a$
 loop
-----------------------------------------------------------------------
Now remember - this only happens to this ONE user, who's running DOS 6.22
on a regular IBM clone, and no errors are reported.  DIRTMP is a routine
which reports onscreen and in logs that no files were found.
I mean, it works *perfectly* for me and everyone else.
Is there a tiny tech note or something about this command not working
with some setups?
I suggested to the user, since no errors were generated, it could be
a disk sector error which hides the directory sometimes, or maybe
its a problem with a doubledrive or superstore or stacker drive, but
the user has not told me (yet) if he runs a compressed drive.  Nor
should it matter, right?  This user reports other strange things
which nobody else reports and has never happened to me, but I'd like
some comments on possibilities of this command not working on some
setups.
Thanks to anyone who can help.
-James
--- QuickBBS 2.80 GoldBase (Zeta-1)
---------------