| From: | David McMinn |
| Date: | 22 Sep 99 at 20:17:23 |
| Subject: | Re: More of those damn Blitz problems |
Hi Neil
> I'm getting sick of it now, so can anyone suggest any reasons why it may
> behave so irratically? What other information would you need to offer advice?
H/W specs? Perhaps you don't have enough memory to complete the
compilation, Blitz certainly doesn't like low mem situations. And
certainly, some of your memory will have become fragmented after
running a program from the editor. Also try using the commands
"NoCLI" (doesn't open default CLI) and "CloseEd" (closes TEd) at the
top of your programs to free up some memory when you run the programs
(although that may not help in this case).
And all the usual things for freeing memory, i.e. booting no startup,
reducing #colours in teh WB, and on the TEd screen.
If your program is working so that it won't crash, turn off the
debugger too. Just remember to program correctly first time round ;)
Make sure you are using "Make smallest" option and not using
"Increase 150%".
Or perhaps Blitz doesn't like your accelerator (a couple of folks had
problems with Apollos I thnk).
Did you re-install the patches for the debugger and editor after re-
installing Blitz?
Does it actually crash on compilation the first time you run your
program? Or does it only crash during compilation after you have run
your program once? That would be something in your program screwing
up memory.
---------------------------------------------------------------------
To unsubscribe, e-mail: blitz-list-unsubscribe@netsoc.ucd.ie
For additional commands, e-mail: blitz-list-help@netsoc.ucd.ie