VOGONS

Common searches


First post, by noshutdown

User metadata
Rank Oldbie
Rank
Oldbie

qb2.0 and later versions can be easily found on the web, but v1.0 is nowhere to be found. the only place i could find is a site selling some original boxed retail floppy disks for $500 usd, which seems a bit insane for me.
i heard that qb1.0 was released about the same time as the ms bascom v6.0(also rebranded as ibm bascom v2.0), doesn't have an ide like qb2.0 and later, just the compiler, and works just like bascom6.0. so is it just a plain rebrand of bascom6.0, or any difference between them?

Reply 1 of 11, by keenmaster486

User metadata
Rank l33t
Rank
l33t

Probably because 1.0 didn't come with an IDE, and was most likely little more than a rebranded and cleaned up GW-BASIC with QB syntax.

Why are you trying to find QB 1.0? Do you have a program that won't run with later versions?

I flermmed the plootash just like you asked.

Reply 2 of 11, by noshutdown

User metadata
Rank Oldbie
Rank
Oldbie
keenmaster486 wrote:

Why are you trying to find QB 1.0? Do you have a program that won't run with later versions?

no, not really, but i just want to know how the product evolved.

Reply 3 of 11, by cyclone3d

User metadata
Rank l33t++
Rank
l33t++

So did some more searching and from what I can find, multiple places say that MS just renamed the Basic compiler to Quick Basic.

http://www.pldos.pl/basic/basic.htm
http://www.emsps.com/oldtools/msbasv.htm

Yamaha YMF modified setupds and drivers
Yamaha XG resource repository - updated November 27, 2018
Yamaha YMF7x4 Guide
AW744L II - YMF744 - AOpen Cobra Sound Card - Install SB-Link Header
Epstein didn't kill himself

Reply 4 of 11, by Gene Wirchenko

User metadata
Rank Member
Rank
Member
cyclone3d wrote:

So did some more searching and from what I can find, multiple places say that MS just renamed the Basic compiler to Quick Basic.

http://www.pldos.pl/basic/basic.htm
http://www.emsps.com/oldtools/msbasv.htm

That is my impression, too.

Reply 5 of 11, by noshutdown

User metadata
Rank Oldbie
Rank
Oldbie

qb1.0 was found by some people! its earlier than ms bascom6.0(also rebranded as ibm bascom v2.0), and said to be very buggy.
maybe qb1.0 was intended to be a value product which was not so serious as bascom, just like turboc++ compared to borlandc++.

Reply 6 of 11, by Jo22

User metadata
Rank l33t++
Rank
l33t++

QuickBasic 1.0 is pretty useless, I suppose. QB started to get interesting with version 3 onwards, I think.
Earlier versions aren't fun to thinker with. Too limited. Like MS BASCOM or MBASIC.

Even GW-BASIC might be more interesting/fun to work with than that.
(The Mac version of QB might be a different beast, though.)

Gratefully, QB 4.x, PDS 7.x and VBDOS got archived already.
These are really neat and can be used to solve any problem with ease.

Edit: The only thing worthile on such dinosaurs might be DOS 2.x compatibility.
MS-DOS 2.11 and DOS Plus 1.x were interesting little OSes that ran on DOS compatibles.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 7 of 11, by noshutdown

User metadata
Rank Oldbie
Rank
Oldbie
Jo22 wrote:
QuickBasic 1.0 is pretty useless, I suppose. QB started to get interesting with version 3 onwards, I think. Earlier versions are […]
Show full quote

QuickBasic 1.0 is pretty useless, I suppose. QB started to get interesting with version 3 onwards, I think.
Earlier versions aren't fun to thinker with. Too limited. Like MS BASCOM or MBASIC.

Even GW-BASIC might be more interesting/fun to work with than that.
(The Mac version of QB might be a different beast, though.)

Gratefully, QB 4.x, PDS 7.x and VBDOS got archived already.
These are really neat and can be used to solve any problem with ease.

Edit: The only thing worthile on such dinosaurs might be DOS 2.x compatibility.
MS-DOS 2.11 and DOS Plus 1.x were interesting little OSes that ran on DOS compatibles.

in fact, qb is the "value product" line of microsoft basic. the high-end business products are bascom, pds and vbdos.
i don't really think i would need it to do anything, i just want to dig up history of how things went.

Reply 8 of 11, by cyclone3d

User metadata
Rank l33t++
Rank
l33t++

Just as an update in case anybody is interested.

Here is an online emulator that has most of the QuickBasic versions including 1.00. Sadly no 1.01 or 1.02 though.
https://www.pcjs.org/software/pcx86/lang/micr … uickbasic/1.00/

Yamaha YMF modified setupds and drivers
Yamaha XG resource repository - updated November 27, 2018
Yamaha YMF7x4 Guide
AW744L II - YMF744 - AOpen Cobra Sound Card - Install SB-Link Header
Epstein didn't kill himself

Reply 9 of 11, by pan069

User metadata
Rank Member
Rank
Member

The command line compiler BASCOM.EXE from version 1 seemed to have been renamed to BC.EXE in version 4.5 (the most common version of QuickBasic, maybe even the last?).

Anyhow, 4.5 is the version of QuickBasic I always use. I think I there used to be version 4 before that, can't remember back that far... 😀

Reply 10 of 11, by cyclone3d

User metadata
Rank l33t++
Rank
l33t++

Found the 1.02 update documentation on Programmers Corner:

Filename
QBASIC.zip
File size
3.26 KiB
Downloads
3 downloads
File license
Public domain
The following is a description of the fixes and changes in the free update to the Microsoft QuickBasic compiler. All users of Q […]
Show full quote

The following is a description of the fixes and changes in the free update to
the Microsoft QuickBasic compiler. All users of QuickBasic who sent in their
registration cards should have received notification of the update. Contact
Microsoft if you sent in your card and were not notified. If you did not send
in your registration card, you should do so right away or contact Microsoft if
you can't locate the card.

This file is reproduced with permission from Microsoft Corporation.

Microsoft QuickBasic Compiler version 1.02

UPDATE.DOC

Jan. 27, 1986

Several changes have been made to this version of the QuickBasic
compiler. They are listed below.

- When the device "SCRN:" is opened for output, the output
will be double spaced. For example, consider the follow-
ing program:

OPEN "SCRN:" FOR OUTPUT AS #1
PRINT #1,"LINE 1"
PRINT #1,"LINE 2"
PRINT #1,"LINE 3"
CLOSE

The resulting output will be double spaced, as follows:

LINE 1

LINE 2

LINE 3

The correct output would be single spaced. The next
release of the compiler will correct this problem. In
the meantime, one way to work around this problem
is to open the device "CONS:" instead of "SCRN:"
This works as expected (single spaced output) unless
you are mixing PRINTing to the "CONS:" device and
regular PRINT statements to the screen. Since DOS
keeps track of cursor position when the "CONS:" device
is used and QuickBASIC keeps track of cursor position
when regular PRINT statements are used, it is possible
to interleave output to the screen. In that case,
modifying the sample program as follows will be the
preferred work around:

OPEN "SCRN:" FOR OUTPUT AS #1
PRINT #1,"LINE 1";CHR$(13);
PRINT #1,"LINE 2";CHR$(13);
PRINT #1,"LINE 3"

Note the addition of ";CHR$(13);" should be made to
each PRINT statement except the last. WRITE-ing to
"SCRN:" behaves the same as PRINTing, and the same
work arounds apply.

- PRINTing to an area not in a VIEW port now correctly
generates an error.

- A combination of error processing (ON ERROR...) and illegal
parameters in STICK and KEY ON could hang the machine.
Corrected.

- In version 1.0, if the user ran out of memory when returning
from SHELL, the machine could hang. Corrected.

- When no line numbers were used, sometimes FOR/NEXT loops
would not execute the correct number of times. Corrected.

- The utility program REMLINE.BAS will correctly handle multiple
GOSUBs on the same line.

- INKEY$ has been corrected so that it will no longer go
to the keyboard if standard input is redirected.

- The third parameter of the CLEAR statement now works properly.

- QuickBasic will now restore vectors EF and F0 upon program
termination and SHELL.

- Arithmetic involving elements of dynamic arrays now works
properly.

- A "DISK FULL ERROR" could occur erroneously. Corrected.

- Source files formatted with Microsoft WORD could cause the
compiler to generate a "Too Complex" error. Corrected.

- The listing file now reflects the correct version number,
1.02.

- An error in which dynamic arrays in COMMON would result in
syntax errors in graphics GET and PUT statements has been
corrected.

- Closing a file in a multiline function and then accessing the
file did not give an error. Corrected.

- Compression of the heap when DIMensioning dynamic arrays could
clobber the arrays. Corrected.

- Output to different printer device names was inconsistent.
Corrected.

- Using an integer variable in LOCK and UNLOCK statements was
not handled properly. Corrected.

- Illegal parameters in LOCATE statement did not always generate
the correct error message. Corrected.

- If a dynamic array was erased in a multiline function,
subsequent attempts to access elements of it would not give
an error. Corrected.

- Elements of static arrays passed to subroutines can now be
used in arithmetic expressions.

- Printing control characters to the screen now does the same
thing in QuickBasic as in IBM's BASICA.

- Opening the device "LPT1:" in random mode could sometimes
cause "String Space Corrupt" errors later in the program.
This has been corrected.

- An error 14, "Out of String Space" now occurs when the user
program runs out of string space, instead of error 7 ("Out of
Memory").

- QuickBasic now handles CHR$(10) (linefeed) and CHR$(13)
(carriage return) when printed to the screen, the same way
IBM's BASICA does.

- QuickBasic will now recognize drive Z: on a network.

- The PLAY statement will now work even if a subroutine (in
assembly language) has disabled the speaker port.

- The WIDTH command now works correctly with the device "LPT1:".

- The KILL statement using complex string expressions no longer
will give "Too Complex" errors.

- When filenames are too long, they are now shortened accor-
ding to MS-DOS conventions.

- CHAIN with some files open could cause the machine to hang.
Corrected.

- SWAPping elements of an integer array in a subroutine could
cause the system to hang. Corrected.

- "GET #n,0" will now generate an error message.

- Imbedded form feeds (CHR$(12)) and vertical tabs (CHR$(11))
in source files created by Microsoft WORD were not being
handled correctly. Corrected.

- The key sequences ALT-128, ALT-254, and ALT-255 are now
handled as they are in IBM's BASICA.

- Redefined function keys on line 25 now work correctly.

- Repeatedly printing the same element of a dynamic array could
cause garbage to be printed. Corrected.

- PAINT, in a VIEW port, that was not on a boundary, could be
ragged. Corrected.

- The IMP logical operator did not work properly if both
arguments were the same. Corrected.

- Sometimes, very large complex programs would cause the
compiler to give a spurious syntax error. Corrected.
ICA.

- Redefined function keys on line 25 now work correctly.

- Repeatedly printing the same element of a dynamic array could
cause garbage to be printed. Corrected.

- PAINT, in a VIEW port, that was not on a boundary, could be
ragged. Corrected.

- The IMP logical operator did not work properly if both
arguments were the same. Corrected.

So the 1.02 update was free from MS.

Yamaha YMF modified setupds and drivers
Yamaha XG resource repository - updated November 27, 2018
Yamaha YMF7x4 Guide
AW744L II - YMF744 - AOpen Cobra Sound Card - Install SB-Link Header
Epstein didn't kill himself

Reply 11 of 11, by noshutdown

User metadata
Rank Oldbie
Rank
Oldbie
cyclone3d wrote on 2020-11-20, 06:55:

Found the 1.02 update documentation on Programmers Corner:
QBASIC.zip
So the 1.02 update was free from MS.

a pity that its only the document and not the update patch.

Epstein didn't kill himself

maybe he did, guess he suffered depression because he knew too much.🤣