Hello Patriek,
I understand your sarcasm, but trust me we have spend two saterdays on
this problem now. Tried to get rid of it in several ways, but haven't
succeeded in our attempts.
We've been bugsearching, and I can you tell more about this problem. To be
exact it looks like the player is only willing to play in R800 mode on a
Turbo R. When I switch to Z80 before I load the player or when the player
is loaded it crashes. I even tried it without the game and then it also
crashes. The problem is, this moonblaster player that cannot work
correctly on a Turbo R when you switch to Z80 before or after you have
loaded it. All I can do with this is not using it, but nobody is waiting
for a game without music. As I am not a ML programmer and I do not have
the sourcecode from this I cannot search for the bug in this code and if I
had the ML sourcecode I wouldn't know what I should search for as we are
creating our game in TP.
Thanks.
Raymond
Patriek Lesparre <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
28-12-2003 07:50
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
Re: [MSX] switching r800 <-> z80 in TP
Raymond wrote:
>Isn't there somebody out there who can rewrite this so that it will work
>correctly?
<sarcasm>
What would you like rewritten? Your program, the MoonBlaster player, MSX
BIOS, the compiler?
Please send an application form in threefold to the address shown on the
screen when the error occurs.
</sarcasm>
First thing you do is pinpointed the EXACT moment the hang occurs.
Then, find out whether or not the processor is executing an interrupt
routine or whether interrupts are enabled or disabled.
Also check for variables that have values that seem impossible and other
things that are just plain weird.
Only once you find out WHAT is wrong, you can find out how to FIX IT. This
can be tedious, I know, I've been there... But you can't just say 'rewrite
this and that' if you don't know for certain where the problem is, and the
best person to find out is you, the programmer. (hence the sarcasm at the
top)
Even though it may seem to be the moonblaster player, it could be YOUR
program that causes an environment in which moonblaster can't function.
For
instance, you may be overwriting parts of the moonblaster code that causes
the hang.
Good luck, and happy bughunting!
Patriek
_______________________________________________
MSX mailing list ([EMAIL PROTECTED])
Info page: http://lists.stack.nl/mailman/listinfo/msx
_______________________________________________
MSX mailing list ([EMAIL PROTECTED])
Info page: http://lists.stack.nl/mailman/listinfo/msx
