Tweet
In researching the failures of PowerBASIC SYS3170 errors in DOS-VDM's
in OS/2, the Norman Virus group has focused on the possibility of
the compiler not being aware of certain timing issues during output
of it's product(s) at compile time.
On suggestion that we temporarily exclude the output file path for
the output product for research purposes, that's easy enough in my
case, for what one would expect of the designated operations as
set forth in the setup program for PB 3.5 for DOS and in the way I
use the product.
However, a picky little feeling that goes back many months ago down
one branch of this trail, is nagging me. Am I right to recall that
the PB compiler, can, at least in some conditions .. create a temporary
file internally to its own uses, I think? Isn't it in the TEMP file
path for the DOS system on which it is running?
I sorta recall that maybe this is for error tracing and internal
housekeeping puposes, maybe? If this is so, can I please have the
name or names of any such files? For test purposes we need to
exempt them from the probes of the virus utility for research ..
I discovered it in one case, if my memory is correct, in a file in
which the error was bad enough to hard lock the box. I think I found
this otherwise unknown file as part of the /FOUND0 OS/2 HPFS file
recovery from dirty byte shutdown and CHKDSK32 on cleanup on the
Big Red Switch power down and re-boot. I think it was either in the
avowed TEMP directory, or even in the WINOWS such TEMP directory that
is known to be in the path in the environment in the DOS OBJECT that
is the whole virtual computer experience for DOS in OS/2.
It would help to know this file name or names and the path for
research for us, if possible and if it even exists. Since that
path is far different from the known and uses environment, a fair
run at this will need to have that information in order to report
back what timing issues we find with the product.
Thanks ..
------------------
Mike Luther
[email protected]
[This message has been edited by Mike Luther (edited October 29, 2002).]
in OS/2, the Norman Virus group has focused on the possibility of
the compiler not being aware of certain timing issues during output
of it's product(s) at compile time.
On suggestion that we temporarily exclude the output file path for
the output product for research purposes, that's easy enough in my
case, for what one would expect of the designated operations as
set forth in the setup program for PB 3.5 for DOS and in the way I
use the product.
However, a picky little feeling that goes back many months ago down
one branch of this trail, is nagging me. Am I right to recall that
the PB compiler, can, at least in some conditions .. create a temporary
file internally to its own uses, I think? Isn't it in the TEMP file
path for the DOS system on which it is running?
I sorta recall that maybe this is for error tracing and internal
housekeeping puposes, maybe? If this is so, can I please have the
name or names of any such files? For test purposes we need to
exempt them from the probes of the virus utility for research ..
I discovered it in one case, if my memory is correct, in a file in
which the error was bad enough to hard lock the box. I think I found
this otherwise unknown file as part of the /FOUND0 OS/2 HPFS file
recovery from dirty byte shutdown and CHKDSK32 on cleanup on the
Big Red Switch power down and re-boot. I think it was either in the
avowed TEMP directory, or even in the WINOWS such TEMP directory that
is known to be in the path in the environment in the DOS OBJECT that
is the whole virtual computer experience for DOS in OS/2.
It would help to know this file name or names and the path for
research for us, if possible and if it even exists. Since that
path is far different from the known and uses environment, a fair
run at this will need to have that information in order to report
back what timing issues we find with the product.
Thanks ..
------------------
Mike Luther
[email protected]
[This message has been edited by Mike Luther (edited October 29, 2002).]
Comment