There was an interesting problem I encountered at the eleventh hour, just before the release of "Willy Games: The First 30 Years Quiz", with the BASIC loader / loading process.
I thought I would start a new topic about it, as it doesn't really concern the Quiz as such, it's more about the loading process itself, I think.
I solved the problem, but I would be interested if someone - Andy, perhaps? - could shed some light on why it happened.
The loader, in the released version of the Quiz, is like this:
While I was working on it, I had PAUSE 50 in line 35. Everything was fine then.
I then changed it to PAUSE 150.
Just before the release, I realised that the game wouldn't load correctly.
Interestingly, it would load OK (in Spectaculator) when the "Enable fast loading" option was on. However, when I tried loading it with that option turned off, there was a critical problem.
First, the loading screen wouldn't show. All that I could see after it should have shown was the screen created by the BASIC loader.
Then, after a considerable time of the game loading, corruption started on that screen.
At one point it looked like that:
Then it got even worse:
And then the game would just crash. I can't remember exactly what happened, but it wouldn't load at all.
I first thought it was a problem with the overall length of the BASIC loader. So I reduced it by merging two lines into one. The loader was now shorter than when it had been when everything worked fine, but the problem persisted, with the same symptoms.
And then I compared the loader when it worked fine with the current one, and turned my attention to the length of the two PAUSE instructions.
The second one (PAUSE 200 after loading the loading screen proper) didn't seem to matter. However, the first one, in line 35, made all the difference.
The loading was just fine when it was 50.
The loading crashed when it was 150.
I tried 100 and it crashed, and I tried 90 and it was fine. So I assume it must be a two-digit number to work (I guess PAUSE 99 would work, too, although I didn't try it).
But why is it? And why does an emulator load it correctly with a PAUSE over 100 when fast loading is enabled, but doesn't load it at all when it's disabled?
Another little mystery, for me, at least...