I am keen to set up my QB64 programming environment in a similar way to what I once had in QB4.5.  This involved having separate directories for each basic program project.  To test this I have placed the QB64 directory name in the path statement for the Windows 7 environment system variable list.  I have also checked the QB64 option box to save exe files to the source directories.  I then change to the program directory I wish to address and then execute the QB64.exe from the command line.  This seems to work fine for trivial “hello world” programs.  The only aberration I’ve observed so far is when compiling and running code before that source code has been saved.  In that case it seems that the untitled.exe file is saved to the QB64 directory,  and the _CWD$ statement returns the QB64 directory rather than the actual current working directory.  Once the source file has been updated and saved things seem to work as intended.

What I would like to know is whether my proposed setting up is valid in QB64.  Are there any resources in the QB64 directories that may not be found during compilation by virtue of the PATH setting? 

If I run the following 5 commands I get a directory list on the output screen as expected:

However if I run:


by itself I see the directory listing for a few milliseconds and then a blank output screen.

In QuickBasic 4.5 the SHELL “dir” command does produce a directory listing to the output screen and it remains there.

I am keen to know how to interpret what I am seeing here.

No Pete, I  haven’t.  I’ve never used DOSBox but I’ll certainly give it a try if you think it has prospect.