SxSI-SCSI HDD Image v2.20

[kinooshi823]

would you be able to send me the link in a PM?

[spectreman]

I tried After Burner II with MIDI sound, but there is no sound.

Fortunately Space Harrier with MIDI sound works perfectly.

For those who don't know, the MIDI sound support for these two games was done amateurishly.

Tests performed with X68000 XVI 16MHz, with Etarikashikoshi 8MB RAM+MIDI, connected to Roland MT-32 and SC-55.

[incrediblehark]

Did you try in 10mhz mode? Runs fine on my pro in 10mhz but if I try to play in 14mhz overclock the game crashes. I may need to add a note to the batch file.

[spectreman]

Starting After Burner II in MIDI mode, both 15kHz and 31kHz, you only hear the sound effects.

Setting the CPU to both 10 MHz and 16 MHz, nothing changes.

I tried moving the folder to the C: partition but nothing changed.

The good thing is that all games with MIDI support, with Etarikashikoshi 8MB RAM + MIDI work.

I think the problem is due to the different emulation offered by Henkan Bancho PRO.

However, Space Harrier also has amateur MIDI support, but it works perfectly.

Too bad they didn't make a version of After Burner II that supports Joycard / Joystick with MIDI sound simultaneously.

[incrediblehark]

Thanks for the info and testing. I recently picked up a henkan bancho and plan to test it out. Hopefully we can find a workaround.

[BlackVega]

I want to confirm this image works perfectly fine on Sharp X68000 first model on BlueSCSIv2 centronics 50 version. I saw a lot of people complaining BlueSCSI is not detected on SASI machines at first and it needs to be reset/power cycled and after that it gets detected. Surprisingly I've never encountered this issue even once and my BlueSCSI always boots up right away, albeit I'm using the newest PCB 2024.03a. Maybe my hardware is just lucky?

There is 1 caveat however- I started getting this dreaded warning in the log file:

WARNING: Host used command 0x1A which is affected by drive geometry. Current settings are 63 sectors x 255 heads = 16065 but image size of 6146048 sectors is not divisible. This can cause error messages in diagnostics tools.

Well, maybe I'm misremembering and this warning had been appearing before but I don't remember? Whatever, I was doing a ton of tests and tweaks so maybe my memory is mixing up. Apparently this warning appears when the image is not perfectly aligned with memory blocks but ultimately it's safe apparently. I also tried another older image "X68000V4" from this website and I never get this warning at all. It's probably not a big deal but if it can get fixed then people won't need to worry about anything

Aha there is 2 more things I want to mention for BlueSCSI users- despite what the manual says the image file needs to be named "HD10_512.HDA" because ID0 is the SASI controller. You also need to create and place bluescsi.ini file with this content:

[SCSI]
System=X68000
EnableParity=0 ; Off

Before doing any of that you need to install SXSI driver of course. After doing all of that you are good to go.

I'm very intrigued by the functionality and the fact that SASI can only address 40MB max as far as I know but this hack breaks the limit into whopping 3GB of space and everything works perfectly fine so far. How does this black magic even work?

[MartinW]

I want to confirm this image works perfectly fine on Sharp X68000 first model on BlueSCSIv2 centronics 50 version. I saw a lot of people complaining BlueSCSI is not detected on SASI machines at first and it needs to be reset/power cycled and after that it gets detected. Surprisingly I've never encountered this issue even once and my BlueSCSI always boots up right away, albeit I'm using the newest PCB 2024.03a. Maybe my hardware is just lucky?

I found that I needed to set the "unit startup time" to a minimum of 2 when running BOOTSET, otherwise the BlueScsi would not have enough time to come up before the system tries to access it. Initially I set it to 1 for no reason other than who likes hanging around more than they need to?

So if people were having problems then check you didn't set it to 1.

[rezb1t]

Made a new version of SLEEP.X. Now instead of using the real time clock to know when to resume execution, it instead counts VBlank periods.

Knew there had to be a better way, turns out it is simple.

[incrediblehark]

Made a new version of SLEEP.X. Now instead of using the real time clock to know when to resume execution, it instead counts VBlank periods.

Knew there had to be a better way, turns out it is simple.

Awesome, thank you! I'll go through and update this in my new image.