QuickBasic Cafe Forum

You could use vbdos which pretty much is qb 4.5 with windowing built in.

Occassionally, when I get around to it and feel like it I will still write something fun in an old BASIC dialact for DOS (GWBasic/QBasic/QuickBASIC/VBDOS/TurboBASIC). None of them are really useful except perhaps as examples for those wanting/needing to learn a really old BASIC dialect but they migh...

QBasic OUT Command & Modern PCs The old QBasic OUT command worked under Windows 98 because programs could write directly to the parallel port. Starting with Windows XP, Microsoft removed direct hardware access for stability and security reasons. On top of that, most modern PCs no longer include par...

Are you trying to create a game in qb?

Your question is very broad, could you be more specific?

When it comes to file i/o in qb look up the following in the help:
OPEN statement
EOF function
LINE INPUT # statement

Those should get you started.

No, qb doesn't support optional arguments. What are you trying to do?

Perhaps you could try DOSBox or DOSBox-X?

You're welcome!

I tried this once and had the same issue. I found this in Quick Basic 4.5's help: Note: To use COMMON with CHAIN when you are compiling outside the BASIC environment, you must use the BRUN45.EXE module. This module is used when you compile from the command line without the /O option or when you use ...

Here's the vb.net implementation:

https://www.programmingalgorithms.com/a ... rt/vb-net/

If you like I can try converting it to QBasic.

Why? I should be able to go to 32000 shouldn't I? And in fact it seems to go wrong anywhere above 2000. I believe you can't declare any array with the total number of bytes exceeding 64kb. It's not just the number of elements but the resulting size that matters. Since you didn't explicitly declare ...

Writing an OS in QBasic is impossible. Do you mean you want to write a shell?

Try Googling for "redirect lpt1 to usb":

https://superuser.com/questions/182655/ ... sb-printer

Your main issue is that you aren't assigning a value to be returned in your function: DECLARE FUNCTION Hello$() PRINT Hello$ END FUNCTION Hello$() Text$ = "Hi, This is Suraj" END FUNCTION This results: I modified your function to be of the type string ("$") and to return instead of print your text.

Personally I prefer to use NASM or for very small things you can even use the MS-DOS debugger to create small binary files. Also, I wouldn't link binary files but rather use CALL ABSOLUTE to call snippets of binary code. What does you assembly code look like btw?