Page 3 of 3
Posted: Wed Dec 24, 2003 7:21 am
by Buttermaker
BBH wrote:Well that's certainly weird. I'm supposed to be in set B, but I tested the nbajamt3 recording, and your first shot goes in. I don't get it...
Your comp is in set A. I don't know why it was listed in set B.
The Stocker recording works too.
SJK could play it back correctly so balsente.c is fixed.
Now let's test the other drivers.
Posted: Wed Dec 24, 2003 7:55 pm
by Chad
Buttermaker wrote:BBH wrote:Well that's certainly weird. I'm supposed to be in set B, but I tested the nbajamt3 recording, and your first shot goes in. I don't get it...
Your comp is in set A. I don't know why it was listed in set B.
Because BBH's computer WAS and still IS in Set B for the mame63 bug, these problems are NOT the mame63 bug they are completely different. We have to make a new set system for this bug that has been around LONGER than mame63.
tbm_nbajamt3_63_tgmame69.zip works for me in 98 and doesn't work for me in XP, ON THE SAME MACHINE.
evl_cabal2_957590_wolf77.zip works for me in XP and doesn't work for me in 98, ON THE SAME MACHINE.
evl_cabal_895600_wolf77.zip works for me in XP and doesn't work for me in 98, ON THE SAME MACHINE.
cabal was never in the mame63 bug list
viewtopic.php?p=19067#19067 , however it is strange why i'm able to playback an nbajam recording and not on the other operating system (i was never able to do that before with other nba recordings when the mame63 bug was in effect).
Posted: Wed Dec 24, 2003 10:27 pm
by mahlemiut
If I remember right, these Midway games have a serial number, which MAME generates randomly (using rand() at that). The main reason I haven't switched it to mame_rand() is that most of the games on this hardware work fine as it is. I don't know if the serial number would affect how the game generates random numbers, but it might be worth a try. Eventually I'll set this PC up to compile MAME, and we'll see then if this works or not.