Getting the SCREEN mode

[mnrvovrfc]

And as far as making SCREEN 13 bigger, easy peasy:

SCREEN13& = _NEWIMAGE(320,200,13) ' Work Screen
SCREEN _NEWIMAGE(1024,800,32) ' Graphics Screen
_DEST SCREEN13& ' Switch to work screen
' Draw your graphics and such
_DEST 0 ' Switch to graphics screen
_PUTIMAGE ,SCREEN13& ' Map work screen onto graphics screen

I prefer the jaggies only on an IBM PS/2 Model 30 color monitor or something like that from my high school. Not in the recent time on a 64-bit system LOL. This procedure won't be preferred by somebody who wants to import a game in "SCREEN 13" and "needs" to make it larger. A person would have to be clever enough to check the source code of a graphics program to see if it could support larger dimensions. But actually many old programs are hard-coded to certain screen dimensions.

I brought up the point about DOSBOX because a person who cannot have a computer and OS that could run 16-bit Q(uick)Basic has to pick his/her poison: either that or QB64PE, both are complex. That person might not care about 32-bit color, or about resolution larger than old VGA. However there are others who get curious. "But I need to do all that just to make the screen larger? Is there another easier way?" and "What do you think about Freebasic? Could it allow me to do it easier?" and "If I bought Purebasic..." and, well, you begin to understand what is the difficulty of persuading people who want to get into BASIC programming with a small amount of patience.

Many people complain about EXE/Linux-executable file sizes and how long an application finishes work (start from pressing [F5] in QB64PE IDE enough said). They would rather do something which is even less efficient because "I just want it to work like 20 years ago, how hard?"

Sometime ago I had a personal experience with 32-bit Free Pascal. None of my old programs would run correctly compiled by it because too many things were assumed out of "CRT" and "GRAPH" units, the two modules people were most interested in line with the most "popular" QB/QBasic programs posted on the web. It did have a "VIDEO" unit which does "portable console" like Freebasic "SCREEN 0", which could include changing the dimensions of "bash" or "cmd.exe" window.

The line-numbering luddite would just download PC-BASIC which, sadly it's difficult as heck to install it on Fedora and not available for many other Linux distros. It'll be interesting what happens to that one, once a certain popular programming tool finally reaches version 4...

Why would they need DOSBox? They can simply type the code into QB64 and it will run just fine. Remember, QB64 is nearly 100% compatible with all code written for GWBASIC (line numbers) and QuickBasic. No old computer or DOSBox needed.

Not if it supports "FOR... NEXT" loops for delaying eg. in an arcade game.