Reading ancient QB/QBX source files

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Hi --

Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS) files? I
have managed to get a copy of QuickBasic v4.5 running, and when I attempt to load
them in there, I'm told:

QuickBASIC is attempting to load a binary file and does
not recognize the binary-file format. QuickBASIC
recognizes two binary-file formats:
1. QuickBASIC program files
2. Help files
This error commonly occurs when QuickBASIC is asked to
use an include file that has been saved in compressed
format. Include files must be saved in text format, so
1. Reload the include file as a module
2. Save it in text format
3. Run the program again.

It's (obviously) way past time I converted to ASCII those that are still locked in
the past. Anyone know of any utilities, or algorithms, to uncompress these
critters? I believe they were originally created in either QB 4.0 or 4.5, though
some of them may have be PDS vintage.

Other ideas I've tried, that also failed:

- Loading in PDS 7.1 caused it to freeze up. Not sure if that's a symptom of it
running under XP, and I really need to fire up a DOS VM or something?

- Visual Basic 1.0 failed to recognize the format as well.

Thanks... Karl
--
..NET: It's About Trust!
http://vfred.mvps.org

Archived from group: microsoft>public>vb>dos

Dan Barclay · Joined: 04 Oct 2007 Posts: 328

Karl,

If you don't get the info here, try again in

microsoft.public.basic.dos

Dan

"Karl E. Peterson" wrote in message @TK2MSFTNGP03.phx.gbl...
> Hi --
>
> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
> files? I have managed to get a copy of QuickBasic v4.5 running, and when
> I attempt to load them in there, I'm told:
>
> QuickBASIC is attempting to load a binary file and does
> not recognize the binary-file format. QuickBASIC
> recognizes two binary-file formats:
> 1. QuickBASIC program files
> 2. Help files
> This error commonly occurs when QuickBASIC is asked to
> use an include file that has been saved in compressed
> format. Include files must be saved in text format, so
> 1. Reload the include file as a module
> 2. Save it in text format
> 3. Run the program again.
>
> It's (obviously) way past time I converted to ASCII those that are still
> locked in the past. Anyone know of any utilities, or algorithms, to
> uncompress these critters? I believe they were originally created in
> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>
> Other ideas I've tried, that also failed:
>
> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
> symptom of it running under XP, and I really need to fire up a DOS VM or
> something?
>
> - Visual Basic 1.0 failed to recognize the format as well.
>
> Thanks... Karl
> --
> .NET: It's About Trust!
> http://vfred.mvps.org
>

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Thanks, Dan. Probably should've cross-posted there originally, but it wasn't on my
radar.

Still searching for ideas on the problem below!

Dan Barclay wrote:
> Karl,
>
> If you don't get the info here, try again in
>
> microsoft.public.basic.dos
>
> Dan
>
> "Karl E. Peterson" wrote in message
> @TK2MSFTNGP03.phx.gbl...
>> Hi --
>>
>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>> I attempt to load them in there, I'm told:
>>
>> QuickBASIC is attempting to load a binary file and does
>> not recognize the binary-file format. QuickBASIC
>> recognizes two binary-file formats:
>> 1. QuickBASIC program files
>> 2. Help files
>> This error commonly occurs when QuickBASIC is asked to
>> use an include file that has been saved in compressed
>> format. Include files must be saved in text format, so
>> 1. Reload the include file as a module
>> 2. Save it in text format
>> 3. Run the program again.
>>
>> It's (obviously) way past time I converted to ASCII those that are still
>> locked in the past. Anyone know of any utilities, or algorithms, to
>> uncompress these critters? I believe they were originally created in
>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>
>> Other ideas I've tried, that also failed:
>>
>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>> symptom of it running under XP, and I really need to fire up a DOS VM or
>> something?
>>
>> - Visual Basic 1.0 failed to recognize the format as well.
>>
>> Thanks... Karl
>> --
>> .NET: It's About Trust!
>> http://vfred.mvps.org

--
..NET: It's About Trust!
http://vfred.mvps.org

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Thanks, Dan. Probably should've cross-posted there originally, but it wasn't on my
radar.

Still searching for ideas on the problem below!

Dan Barclay wrote:
> Karl,
>
> If you don't get the info here, try again in
>
> microsoft.public.basic.dos
>
> Dan
>
> "Karl E. Peterson" wrote in message
> @TK2MSFTNGP03.phx.gbl...
>> Hi --
>>
>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>> I attempt to load them in there, I'm told:
>>
>> QuickBASIC is attempting to load a binary file and does
>> not recognize the binary-file format. QuickBASIC
>> recognizes two binary-file formats:
>> 1. QuickBASIC program files
>> 2. Help files
>> This error commonly occurs when QuickBASIC is asked to
>> use an include file that has been saved in compressed
>> format. Include files must be saved in text format, so
>> 1. Reload the include file as a module
>> 2. Save it in text format
>> 3. Run the program again.
>>
>> It's (obviously) way past time I converted to ASCII those that are still
>> locked in the past. Anyone know of any utilities, or algorithms, to
>> uncompress these critters? I believe they were originally created in
>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>
>> Other ideas I've tried, that also failed:
>>
>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>> symptom of it running under XP, and I really need to fire up a DOS VM or
>> something?
>>
>> - Visual Basic 1.0 failed to recognize the format as well.
>>
>> Thanks... Karl
>> --
>> .NET: It's About Trust!
>> http://vfred.mvps.org

--
..NET: It's About Trust!
http://vfred.mvps.org

Jim Horvath · Joined: 04 Oct 2007 Posts: 8

Old .BAS files could also be in GWBASIC/BASICA binary format which I
don't believe QB can interpret. To decode those, you need to find a copy
of GWBASIC, start the interpreter and load the file. I'm pretty sure
it's just "LOAD filename.BAS" from the GWBASIC command prompt.

Presuming you get no errors from loading, you can then LIST the file to
view its contents. I can't remember whether it's SAVE or STORE to write
back to disk, but you have to provide an ",A" switch to save in ASCII
format. That is:

SAVE filename.bas,A

(I can't remember if you need quotes around the file name.)

I think you type SYSTEM to exit GWBASIC and return to DOS.

Jim H.

Karl E. Peterson wrote:
> Thanks, Dan. Probably should've cross-posted there originally, but it wasn't on my
> radar.
>
> Still searching for ideas on the problem below!
>
>
> Dan Barclay wrote:
>> Karl,
>>
>> If you don't get the info here, try again in
>>
>> microsoft.public.basic.dos
>>
>> Dan
>>
>> "Karl E. Peterson" wrote in message
>> @TK2MSFTNGP03.phx.gbl...
>>> Hi --
>>>
>>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>>> I attempt to load them in there, I'm told:
>>>
>>> QuickBASIC is attempting to load a binary file and does
>>> not recognize the binary-file format. QuickBASIC
>>> recognizes two binary-file formats:
>>> 1. QuickBASIC program files
>>> 2. Help files
>>> This error commonly occurs when QuickBASIC is asked to
>>> use an include file that has been saved in compressed
>>> format. Include files must be saved in text format, so
>>> 1. Reload the include file as a module
>>> 2. Save it in text format
>>> 3. Run the program again.
>>>
>>> It's (obviously) way past time I converted to ASCII those that are still
>>> locked in the past. Anyone know of any utilities, or algorithms, to
>>> uncompress these critters? I believe they were originally created in
>>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>>
>>> Other ideas I've tried, that also failed:
>>>
>>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>>> symptom of it running under XP, and I really need to fire up a DOS VM or
>>> something?
>>>
>>> - Visual Basic 1.0 failed to recognize the format as well.
>>>
>>> Thanks... Karl
>>> --
>>> .NET: It's About Trust!
>>> http://vfred.mvps.org
>

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Hi Jim --

Yep, I fired up GWBASIC yesterday, and gave it a try. This is how it went:

GW-BASIC 3.23
(C) Copyright Microsoft 1983,1984,1985,1986,1987,1988
60300 Bytes free
Ok
LOAD"dio.bas"
Direct statement in file
Ok
LIST
Ok

Sad

Thanks... Karl

Jim Horvath wrote:
> Old .BAS files could also be in GWBASIC/BASICA binary format which I
> don't believe QB can interpret. To decode those, you need to find a copy
> of GWBASIC, start the interpreter and load the file. I'm pretty sure
> it's just "LOAD filename.BAS" from the GWBASIC command prompt.
>
> Presuming you get no errors from loading, you can then LIST the file to
> view its contents. I can't remember whether it's SAVE or STORE to write
> back to disk, but you have to provide an ",A" switch to save in ASCII
> format. That is:
>
> SAVE filename.bas,A
>
> (I can't remember if you need quotes around the file name.)
>
> I think you type SYSTEM to exit GWBASIC and return to DOS.
>
> Jim H.
>
>
>
>
> Karl E. Peterson wrote:
>> Thanks, Dan. Probably should've cross-posted there originally, but it wasn't on
>> my radar.
>>
>> Still searching for ideas on the problem below!
>>
>>
>> Dan Barclay wrote:
>>> Karl,
>>>
>>> If you don't get the info here, try again in
>>>
>>> microsoft.public.basic.dos
>>>
>>> Dan
>>>
>>> "Karl E. Peterson" wrote in message
>>> @TK2MSFTNGP03.phx.gbl...
>>>> Hi --
>>>>
>>>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>>>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>>>> I attempt to load them in there, I'm told:
>>>>
>>>> QuickBASIC is attempting to load a binary file and does
>>>> not recognize the binary-file format. QuickBASIC
>>>> recognizes two binary-file formats:
>>>> 1. QuickBASIC program files
>>>> 2. Help files
>>>> This error commonly occurs when QuickBASIC is asked to
>>>> use an include file that has been saved in compressed
>>>> format. Include files must be saved in text format, so
>>>> 1. Reload the include file as a module
>>>> 2. Save it in text format
>>>> 3. Run the program again.
>>>>
>>>> It's (obviously) way past time I converted to ASCII those that are still
>>>> locked in the past. Anyone know of any utilities, or algorithms, to
>>>> uncompress these critters? I believe they were originally created in
>>>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>>>
>>>> Other ideas I've tried, that also failed:
>>>>
>>>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>>>> symptom of it running under XP, and I really need to fire up a DOS VM or
>>>> something?
>>>>
>>>> - Visual Basic 1.0 failed to recognize the format as well.
>>>>
>>>> Thanks... Karl
>>>> --
>>>> .NET: It's About Trust!
>>>> http://vfred.mvps.org

--
..NET: It's About Trust!
http://vfred.mvps.org

Jim Horvath · Joined: 04 Oct 2007 Posts: 8

Are you sure the files are not old Visual Basic?

Although text format has been the default for a long time now, the first
VB IDEs defaulted to binary, and .BAS was still the extension for VB
non-form modules prior to .NET.

JH

Karl E. Peterson wrote:
> Hi Jim --
>
> Yep, I fired up GWBASIC yesterday, and gave it a try. This is how it went:
>
> GW-BASIC 3.23
> (C) Copyright Microsoft 1983,1984,1985,1986,1987,1988
> 60300 Bytes free
> Ok
> LOAD"dio.bas"
> Direct statement in file
> Ok
> LIST
> Ok
>
> Sad

>
> Thanks... Karl
>
>
> Jim Horvath wrote:
>> Old .BAS files could also be in GWBASIC/BASICA binary format which I
>> don't believe QB can interpret. To decode those, you need to find a copy
>> of GWBASIC, start the interpreter and load the file. I'm pretty sure
>> it's just "LOAD filename.BAS" from the GWBASIC command prompt.
>>
>> Presuming you get no errors from loading, you can then LIST the file to
>> view its contents. I can't remember whether it's SAVE or STORE to write
>> back to disk, but you have to provide an ",A" switch to save in ASCII
>> format. That is:
>>
>> SAVE filename.bas,A
>>
>> (I can't remember if you need quotes around the file name.)
>>
>> I think you type SYSTEM to exit GWBASIC and return to DOS.
>>
>> Jim H.
>>
>>
>>
>>
>> Karl E. Peterson wrote:
>>> Thanks, Dan. Probably should've cross-posted there originally, but it wasn't on
>>> my radar.
>>>
>>> Still searching for ideas on the problem below!
>>>
>>>
>>> Dan Barclay wrote:
>>>> Karl,
>>>>
>>>> If you don't get the info here, try again in
>>>>
>>>> microsoft.public.basic.dos
>>>>
>>>> Dan
>>>>
>>>> "Karl E. Peterson" wrote in message
>>>> @TK2MSFTNGP03.phx.gbl...
>>>>> Hi --
>>>>>
>>>>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>>>>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>>>>> I attempt to load them in there, I'm told:
>>>>>
>>>>> QuickBASIC is attempting to load a binary file and does
>>>>> not recognize the binary-file format. QuickBASIC
>>>>> recognizes two binary-file formats:
>>>>> 1. QuickBASIC program files
>>>>> 2. Help files
>>>>> This error commonly occurs when QuickBASIC is asked to
>>>>> use an include file that has been saved in compressed
>>>>> format. Include files must be saved in text format, so
>>>>> 1. Reload the include file as a module
>>>>> 2. Save it in text format
>>>>> 3. Run the program again.
>>>>>
>>>>> It's (obviously) way past time I converted to ASCII those that are still
>>>>> locked in the past. Anyone know of any utilities, or algorithms, to
>>>>> uncompress these critters? I believe they were originally created in
>>>>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>>>>
>>>>> Other ideas I've tried, that also failed:
>>>>>
>>>>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>>>>> symptom of it running under XP, and I really need to fire up a DOS VM or
>>>>> something?
>>>>>
>>>>> - Visual Basic 1.0 failed to recognize the format as well.
>>>>>
>>>>> Thanks... Karl
>>>>> --
>>>>> .NET: It's About Trust!
>>>>> http://vfred.mvps.org
>

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Yep, VB1 fails to load them, as well.

---------------------------
Microsoft Visual Basic
---------------------------
Can't load module; invalid format
---------------------------
OK
---------------------------

The file dates are 1990-91, for context.

Jim Horvath wrote:
> Are you sure the files are not old Visual Basic?
>
> Although text format has been the default for a long time now, the first
> VB IDEs defaulted to binary, and .BAS was still the extension for VB
> non-form modules prior to .NET.
>
> JH
>
>
> Karl E. Peterson wrote:
>> Hi Jim --
>>
>> Yep, I fired up GWBASIC yesterday, and gave it a try. This is how it went:
>>
>> GW-BASIC 3.23
>> (C) Copyright Microsoft 1983,1984,1985,1986,1987,1988
>> 60300 Bytes free
>> Ok
>> LOAD"dio.bas"
>> Direct statement in file
>> Ok
>> LIST
>> Ok
>>
>> Sad

>>
>> Thanks... Karl
>>
>>
>> Jim Horvath wrote:
>>> Old .BAS files could also be in GWBASIC/BASICA binary format which I
>>> don't believe QB can interpret. To decode those, you need to find a copy
>>> of GWBASIC, start the interpreter and load the file. I'm pretty sure
>>> it's just "LOAD filename.BAS" from the GWBASIC command prompt.
>>>
>>> Presuming you get no errors from loading, you can then LIST the file to
>>> view its contents. I can't remember whether it's SAVE or STORE to write
>>> back to disk, but you have to provide an ",A" switch to save in ASCII
>>> format. That is:
>>>
>>> SAVE filename.bas,A
>>>
>>> (I can't remember if you need quotes around the file name.)
>>>
>>> I think you type SYSTEM to exit GWBASIC and return to DOS.
>>>
>>> Jim H.
>>>
>>>
>>>
>>>
>>> Karl E. Peterson wrote:
>>>> Thanks, Dan. Probably should've cross-posted there originally, but it wasn't
>>>> on my radar.
>>>>
>>>> Still searching for ideas on the problem below!
>>>>
>>>>
>>>> Dan Barclay wrote:
>>>>> Karl,
>>>>>
>>>>> If you don't get the info here, try again in
>>>>>
>>>>> microsoft.public.basic.dos
>>>>>
>>>>> Dan
>>>>>
>>>>> "Karl E. Peterson" wrote in message
>>>>> @TK2MSFTNGP03.phx.gbl...
>>>>>> Hi --
>>>>>>
>>>>>> Anyone have any good ideas for recoving "compressed" QB/QBX source (*.BAS)
>>>>>> files? I have managed to get a copy of QuickBasic v4.5 running, and when
>>>>>> I attempt to load them in there, I'm told:
>>>>>>
>>>>>> QuickBASIC is attempting to load a binary file and does
>>>>>> not recognize the binary-file format. QuickBASIC
>>>>>> recognizes two binary-file formats:
>>>>>> 1. QuickBASIC program files
>>>>>> 2. Help files
>>>>>> This error commonly occurs when QuickBASIC is asked to
>>>>>> use an include file that has been saved in compressed
>>>>>> format. Include files must be saved in text format, so
>>>>>> 1. Reload the include file as a module
>>>>>> 2. Save it in text format
>>>>>> 3. Run the program again.
>>>>>>
>>>>>> It's (obviously) way past time I converted to ASCII those that are still
>>>>>> locked in the past. Anyone know of any utilities, or algorithms, to
>>>>>> uncompress these critters? I believe they were originally created in
>>>>>> either QB 4.0 or 4.5, though some of them may have be PDS vintage.
>>>>>>
>>>>>> Other ideas I've tried, that also failed:
>>>>>>
>>>>>> - Loading in PDS 7.1 caused it to freeze up. Not sure if that's a
>>>>>> symptom of it running under XP, and I really need to fire up a DOS VM or
>>>>>> something?
>>>>>>
>>>>>> - Visual Basic 1.0 failed to recognize the format as well.
>>>>>>
>>>>>> Thanks... Karl
>>>>>> --
>>>>>> .NET: It's About Trust!
>>>>>> http://vfred.mvps.org

--
..NET: It's About Trust!
http://vfred.mvps.org

Jim Horvath · Joined: 04 Oct 2007 Posts: 8

Karl E. Peterson wrote:
> Yep, VB1 fails to load them, as well.
>

I guess I should have read the original message to the end Smile

>
> The file dates are 1990-91, for context.
>

Definitely the PDS 7, QB 4.5 era.

DIO.BAS? Sounds like an interface to an ISA bus Digital I/O card (at
least in my world that's what it would be - I actually found several
GWBasic files from 1989 named DIO1.BAS in my archive folders).

Isn't it time you threw away that obsolete junk? Smile

Jim

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Hi Jim --

>> Yep, VB1 fails to load them, as well.
>
> I guess I should have read the original message to the end Smile

You see I calmly refrained from pointing that out.

>> The file dates are 1990-91, for context.
>
> Definitely the PDS 7, QB 4.5 era.

Yep. I think these were general purpose modules I used in both.

> DIO.BAS? Sounds like an interface to an ISA bus Digital I/O card (at
> least in my world that's what it would be - I actually found several
> GWBasic files from 1989 named DIO1.BAS in my archive folders).

I *think* it was short for DiskIO... in my scheme of things.

> Isn't it time you threw away that obsolete junk? Smile

Prolly. A question actually came up in the VB groups the other day, though, about
pulling a hard disk serial number from DOS, and, well, call it OCD maybe? I *swear*
I have that code somewhere...
--
..NET: It's About Trust!
http://vfred.mvps.org

Jim Horvath · Joined: 04 Oct 2007 Posts: 8

Karl E. Peterson wrote:

> A question actually came up in the VB groups the other day, though, about
> pulling a hard disk serial number from DOS, and, well, call it OCD maybe? I *swear*
> I have that code somewhere...

Sounds like a DOS or BIOS interrupt to me. Probably you could find the
information somewhere in Ralf Browns interrupt list.

Here's one useful link:
http://www.ctyme.com/rbrown.htm

(...I know what you mean about the OCD, but why else would you keep with
computers after all these years... )

Jim

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Jim Horvath wrote:
> Karl E. Peterson wrote:
>
>> A question actually came up in the VB groups the other day, though, about
>> pulling a hard disk serial number from DOS, and, well, call it OCD maybe? I
>> *swear* I have that code somewhere...
>
> Sounds like a DOS or BIOS interrupt to me. Probably you could find the
> information somewhere in Ralf Browns interrupt list.
>
> Here's one useful link:
> http://www.ctyme.com/rbrown.htm

Yep, that list even came up. Thought I'd have a CALL INTERRUPT example to offer, as
opposed to all the other suggestions to use ASM or C.

> (...I know what you mean about the OCD, but why else would you keep with
> computers after all these years... )

Heh, no doubt...
--
..NET: It's About Trust!
http://vfred.mvps.org

Tom Lake · Joined: 04 Oct 2007 Posts: 4

I have most versions of BASIC so if you'd like to send me one of the
programs,
I could try to find out which version it needs and send it back as an ASCII
file
which you could then load into any version.

Tom Lake

Karl E. Peterson · Joined: 04 Oct 2007 Posts: 4836

Tom Lake wrote:
> I have most versions of BASIC so if you'd like to send me one of the
> programs,
> I could try to find out which version it needs and send it back as an ASCII
> file
> which you could then load into any version.

Only if you promise not to laugh. (The code is nearly 20 years old, remember! )

Hey, that'd be great. I've tried most that I have, and no luck yet.

Thanks... Karl
--
..NET: It's About Trust!
http://vfred.mvps.org

Dick Grier · Joined: 04 Oct 2007 Posts: 238

Hi Karl,

>>
Only if you promise not to laugh.
<<

I know what you mean. I cringe when I look at some of my old code (even
stuff I did just a few years ago, much less, 20.

Dick

--
Richard Grier, MVP
Hard & Software
Author of Visual Basic Programmer's Guide to Serial Communications, Fourth
Edition,
ISBN 1-890422-28-2 (391 pages, includes CD-ROM). July 2004, Revised March
2006.
See www.hardandsoftware.net for details and contact information.

VBDOS question again, reading in a while file I'm trying to read in a while file and display it in a text box. I can read in a character, I can read in a line, but I can't read in the whole thing at once. I tried the following: Do WHILE NOT EOF(1) INPUT 1, txt + txt LOOP That do

Overflow err6, reading an ini file Hi, I am writting a script that reads an ini file. I know that the value in the INI file is above 32767, the limit for the for the CInt function. The value is 65000. How do I get this value into the variable rader? rader = CInt(GetField (InEntry, 3, ","))

A few VBDOS questions regarding Drive sizes and reading from I'm a VB programmer trying to create some software for Dos. I'm having a hard time finding any commands to get size of the current drive and/or it's available space. Also I want open and read one character from a file. I'm trying to find the simplest s

Deleted Files Greetings. Can anyone tell me how Windows deletes files? I know that the file is somehow marked. Does that mean the file's entry in the file allocation table is marked, or is the file itself marked with some kind of token character that's added to the beg

vbdos - run time files Hi, Whats the best way to compile a vbdos exe, I noticed that if I use runtime option, my main exe becomes very small and then VBDRT10E.EXE is needed with the exe to run, My file is about 200k if i compile it as a full exe with runtime inside it and its