Re: zero byte output after executing program

2021-02-22T19:06:08-05:00

That's weird.

Tried the same exact thing in DOSbox here in QB1.0 and QB4.5 and it returned a LOF = 17.

TEST.BAS:

Code:

PRINT "TESTING 123 ABC"SYSTEM

TEST2.BAS:

Code:

CLSSHELL "qb /run test.bas > test.out"SHELL "type test.out"OPEN "test.out" FOR BINARY AS #1    PRINT "LOF ="; LOF(1)CLOSE #1END

Output:

Code:

TESTING 123 ABCLOF = 17

Also tried using absolute paths like you did and worked as well.

Statistics: Posted by Erik — Mon Feb 22, 2021 7:06 pm

zero byte output after executing program

2021-02-03T00:11:00-05:00

This is a QuickBasic 1.1 and MS-DOS question

I created the following code and saved it as test.bas in the root of my C drive:

Code:

print "TESTING 123 ABC"system

Then I created the following code as a new file:

Code:

shell "\path\to\qbasic.exe /RUN \test.bas > \test.out"open "\test.out" for binary as #1print lof(1)close #1end

as soon as I executed the new code, Qbasic reports test.out has a size of zero bytes. yet if I execute the same command in DOS as follows:

Code:

\path\to\qbasic.exe /RUN \test.bas > \test.out

then the screen flickers blue for a brief second as if it is loading the Qbasic interpreter then it exits and when I check the \test.out file, it shows the expected output of:

Code:

TESTING 123 ABC

Now the story is different if I compile test.bas into its own EXE (lets call it test.exe here and its stored in the root of the C drive). so if instead executed this code instead:

Code:

shell "\test.exe > \test.out"open "\test.out" for binary as #1print lof(1)close #1end

then the file length is reported correct.

Makes me think something funny is going on with the qbasic interpreter unless my DOSBOX is acting up.

Has anyone else experienced this issue? and how have you corrected it?

Statistics: Posted by mikefromca — Wed Feb 03, 2021 12:11 am

Pete's QBASIC Site

Re: zero byte output after executing program

zero byte output after executing program