Hi all,

I have a program I am working on and I keep getting

"out of ** Space" (** = either Data / String or memory )

How can I make my applciation that will allow me to complie it to run. I am not a happy boy as I have spend 2 months working on this app and now I can not do anything. (I was going to do it in FreeBASIC but I wanted to stick with QuickBasic)

QB64 can do it without memory limitations and has full compatibility with QuickBasic. Also new commands within QB64 work seamlessly with old QuickBasic commands.

QB64

If your source doesn't work with QB64 but works with QuickBasic then you can report it in Bugs/Incompatibilities on the forums. There are very few things that don't work in QB64 but works in QuickBasic.

does qb64 make dos exes?

No, it creates Windows, Mac, and Linux exes.

Ahem, QB64 rules. Thank you, that is all. lol

See I would use QB64 but the machines I am using are DOS only machines :(

Anyway I have managed to figure a work around move most of the sun fucntions into one bas file :)

In that case I would recommend having many subs instead of all in the main.

Be careful if you start getting memory problems in QB (DOS), I've got so deep that I couldn't even save the program, so save often in case you need to go back a version ;)

I am now backing the program up every night to a new zip file and storing them on a remote secured server. So if that happens again AT lest i have a working program :)

All I need to do now is figure out how I can update the screen WITH Out it flickering (as it is starting to give me a headace)

I always had problems with that too. For that reason I always used SCREEN 7,0,1,0 with PCOPY 1,0. In the old days there were a lot of source which managed to avoid flickering on SCREEN 13 programs, but they never worked for me (at least not as good as it should). You could find some of those programs (perhaps even on here). Look for all kind of games, they should use techniques which avoids flickering. I wish you good luck on this!

Hey gablea, got a few tips for that one, used to have that problem all the time! Easiest one would be to try to replace as many IF statements as possible with a SELECT CASE statement instead. Also check your DIM SHARED variables and try to limit them or re-use them if possible. You can also try to use the CLEAR command at certain parts of your code, that helps sometimes but you'll lose all variables in memory lol ummm, Just scan through your code and see if you can shorten some code, sometimes you can figure a simpler way of doing things... That's all I can think of for now lol good luck :)

Oh and if your program is SUPER huge then you can try to cheat and get your program to run a second bas file LOL just use the RUN command.. Also use the OPEN command to save all your variables so you can load them in the second program. it's a lot of work but with this technique you can create a program with basically limitless memory!! HAHAHA Of course this is only for qbasic cuz it's really not much of an issue nowadays :)

@TopGun

I am in the process of changing all the If statments to Select Cases and the only Dim Shared I have are gloabl options (like the terminal ID Number etc)

Also I would love to use Screen 7 But it is not the right size for me :( what about screen 9 does that work with pCopy?

Yes, Screen 9 has video page 0 and 1 so it works with PCOPY. It displays 640*350, hope that's enough room :)

SCREEN - QB64 Wiki - lists the screenmodes and the attributes of them.

@Cyperium

I am working at 640x480 and I am using the locate command to print the items on the scteen so would I just need to change the locations on the items near the bottom? and the program should then work ok

Yes, as long as it doesn't go beyond the last row for LOCATE. You can also experiment with VIEW PRINT to make the printable area larger.

I wish you good luck on this.