I have (in the past few days) received a number of comments from THD 
users 
telling me that TBSCAN v7.07 does not work under THD. After some 
investigation 
into the problem, I wrote the following note to 'support@thunderbyte.nl'. I 
would encourage registered users of TBAV to make short and simple queries in 
this regard if they are having difficulty with THD and TBAV707. Please do not 
'hassle' them as even if the problem is entirely their fault these things do 
take time to track down.
   This is a copy of the letter I sent to ThunderByte on January 16, 1997
   ----------------------------------------------------------------------
    Hello.
    This letter 'attempts' to explain a problem with TBAV707. Note that I 
suggest it 'attempts' to explain in that while I can give the symptoms (and 
hopefully a way to reliably reproduce it) I can not say what causes the 
problem.
    The problem. TBSCAN.EXE does not work with THD ProScan. Now of course, 
this is not a concern to you per-ce. What 'should' be a concern is that 
'exactly' the same command line from a dos prompt does work. However that 
same 
command may or may not work from the command line 'after' running it via THD 
ProScan.
    
    This problem is not evident in older versions and does stay when running 
either TBSCAN16.EXE or TBSCAN32.EXE
    Now I do know that THD releases the memory it uses to run TBSCAN.EXE, and 
this would lead me to believe that TBSCAN is somehow accessing something in  
memory which may or may not be present if the file is run from the command 
line (memory not controlled by the program). And that whatever this is is 
changed by running THDPRO.EXE and is not restored. However since all memory 
seems to be available and usable by other programs, I don't see why this 
would 
cause TBSCAN any problems... And of course, I know nothing about how you've 
programmed TBSCAN so this could be entirely off base.
    I do know that scanning with TBSCAN 7.07 under THD ProScan v12.x will 
cause this error to occur.
    As the author of THD ProScan, I can tell you 'just about' anything in 
regard to how THD is doing what it's doing, but can see no reason that this 
might be occurring under THDPRO.EXE.
    The only thing I can see 'related' is THD's use of EMS to swap out while 
TBSCAN runs. I don't see however how this would cause TBSCAN to give the help 
screen (as if an error in the command line had been passed). Notably though 
when the OS/2 native version of THDPRO.EXE is used and a fresh dos window is 
spawned for this execution, the error is not present. Notably as well, when 
there is no EMS or XMS and THD swaps to disk, the problem is still present.
    "MY" tests were performed on a 486DX100 with 24 megs running WARP 3 (no 
fixpaks) all drives formatted with FAT. However the problem also occurs under 
MSDOS 6.22 with no multitasking environment (also tested on this system) as 
well as numerous other systems (the problem was reported to me three times 
'today' by people running different systems).
    The problems mentioned do not occur with TBSCAN version 7.06 or prior.
    Also curious as to why you don't allow TBSCAN16 or TBSCAN32 to be renamed 
to TBSCAN.EXE and be run directly.
    THD ProScan is available from my web site at 
http://www.naples.net/~nfn03274
    The problem occurs with version 12.3 as well as 12.5, and most certainly 
if it turns out to be something I have done in error, please let me know. 
However, since the problem persists after THDPRO.EXE has completed and all 
memory has been freed, I can't see how this would be the case.
If I can be of any assistance, please let me know.
David Muir... Author THD ProScan.
... THD ProScan support on the web, http://www.naples.net/~nfn03274
~~~ TGWave v1.20 Beta-07+
--- Telegard 3.02/Gecho
---------------