07698: kollon: Kollon doesn't Boot

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07698	Crash/Freeze	Critical (emulation)	Always	Jul 4, 2020, 22:39	17 days ago

Tester	danylopez123	View Status	Public	Platform	MAME (Official Binary)
Assigned To	smf	Resolution	Fixed	OS	Windows 10 (64-bit)
Status [?]	Resolved			Driver	sony/taitogn.cpp
Version	0.222	Fixed in Version	0.275	Build	64-bit
		Fixed in Git Commit	c6f90b4	Github Pull Request #

Summary	07698: kollon: Kollon doesn't Boot
Description	It seems that Kollon now doesn't wan't to boot, it haves now the same problem with Space Invaders Anniversary (sianniv) I've tried to Boot it without deleting the nvram from previous Mame versions, didin't worked. I've tried deleting the nvram and make a fresh new one in version 0.222, didin't worked. I've tried booting the game with the v2 Bios, didin't worked.
Steps To Reproduce	This problem it's always present during booting after the game finishes loading.
Additional Information
Github Commit

Flags
Regression Version	0.218
Affected Sets / Systems	kollon

Attached Files	0000.png (1,501 bytes) Jul 31, 2022, 20:20 Uploaded by georgc3

No.17812 Tafoid Administrator Jul 5, 2020, 00:11	Possible regression revision found testing daily builds - January 4, 2020 https://github.com/mamedev/mame/commit/4c40152837f0625242be10264fa0fa47d8bc1c72 I'm unsure if this happens for other games as well, only tested this one reported.
No.17813 hap Developer Jul 5, 2020, 16:23	The other games are unaffected, and cloneset kollonc still works.
No.20107 Robbbert Moderator Apr 28, 2022, 12:47	Tested reverting the suspected revision, makes no difference. Currently the game loads up to "COMPLETE" but then reboots, creating an endless cycle. The game is marked as MNW, so should we just close this?
No.20417 georgc3 Tester Jul 31, 2022, 19:58 edited on: Jul 31, 2022, 20:20	The cloneset kollonc seems to stop booting. When I tried to load the game and doing the steps above, it now hangs on an error screen with Japanese message that I'm not sure what it says. If anyone knows how to bypass that error screen, like to know how to get pass it.
No.22365 JimCarlTay Tester Oct 8, 2024, 04:55 edited on: Oct 8, 2024, 05:04	For kollonc, you have to disable the BIOS Flash setting in the DIP switch menu after that notice pops up, and reset the system. There, the game will begin initializing. The parent set (kollon) causes boot loops after the game has finished initializing, so that's why it's not working.
No.22950 smf Developer Feb 7, 2025, 14:05	The loader passes control to the executable without disabling interrupts, the handler is in the same area of ram as the BSS of the new executable. It appears to work on hardware through luck, either timing or the code ends up in the instruction cache. For now I've added code to disable interrupts when the executable is started.
No.23050 danylopez123 Tester 17 days ago	Kollon doesn't seem to be booting for me yet, i also tried to clear the nvram, resetted the settings and disabled plugins i had enabled before, still doesn't boot. Am i missing something?
No.23051 Robbbert Moderator 17 days ago	Just tested it now, after deleting NVRAM and CFG, etc. Wait for the blue bar to go across, it says COMPLETE, then the screen goes black, then it starts up. KollonC is a bit different, it wants to flash the bios first, so when that eventually finishes (with a large Japanese message) you have to turn the dipswitch off and reset. Then it does the same as Kollon.
No.23053 danylopez123 Tester 17 days ago edited on: 17 days ago	So i tried to flash the bios, let Kollon (Not KollonC) re-generate the memory, the bar is completed, re-filled the bar to let the game boot and.. still doesn't boot and resets. Again, no other plugins enabled and done from scratch.. this is like a weird case for me. Also, i did not used soft-resets, i did the hard-resets. Also, yes, this was done with the recently MAME 0.275 released.
No.23054 hap Developer 17 days ago	It works fine. Like Robbbert said, make sure to delete old files first, also the one in the "diff" folder.
No.23055 danylopez123 Tester 17 days ago edited on: 17 days ago	Oh my.. i must have missed that "diff" folder, i'll be honest with you, i had no idea that folder did something but then i saw it was a "Hard Disk Difference" folder. So i cleared the kollon.dif file and NOW it booted, it was a simple folder that i just kept on missing.. Oh well.. at least my issue it's finally fixed, thank you hap.