DOS compatibility issue

by (no login)

Aloha Michael

I think I got it; i.e. it has to do location of the
executables and the data and the current directory

in my qb45 world

lookups.exe resides in e:\bin (as do most of the exe files)

the input data can be anywhere e.g.
%checks%\checks\boh\checks.sdf
%checks%\checks\bamchk\checks.sdf
actually it's on a SanDisk and it may be G: one day and H: the next

so the following rebuilds my tmp file in the current directory

@del tmp
@lookups %checks%\checks\boh\checks.sdf tmp
@lookups %checks%\checks\bamchk\checks.sdf tmp
@lookups %checks%\checks\1sthichk\checks.sdf tmp


I can do the same in the QB64 world provided all executables
are in my current directory!

there is also a program in my current directory create.exe and
is called in lookups.exe as follows

shell "if not exist TABLE3.raf create TABLE3 TABLE3.raf 0027 0021 0006 "

when lookups.exe is in the current directory, table3.raf gets
created in the current directory. but when it resides in e:\bin,
the table3.raf get created in e:\bin (which is obviously in the path)

i'm guessing since a child process is created in the qb64 world when
lookups is executed, and then the whereabout of the current directory
gets lost and lookups only know where the parent is (e.g. e:\bin)
therefor that's where the files wind up unless each file is fully
qualified


does this sound right to you

regards

hans becker

Posted on Jun 8, 2012, 7:38 PM

Respond to this message   

Return to Index


Response TitleAuthor and Date
Re: DOS compatibility issue on Jun 8
 DOS compatibility issue on Jun 12