Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dinosaur (1990)(Falcom) - Seems to have issue with disk scenario 1 on certain behavior #14

Open
wwark opened this issue Aug 10, 2024 · 2 comments

Comments

@wwark
Copy link
Collaborator

wwark commented Aug 10, 2024

If I set only "Dinosaur (Program disk)" on Drive 1:
After selecting "Start the game"
I have this message
20240810_112718-screen
After inserted Dinosaur (Scenario disk 1) and click of space key. It doesn't go in game but still print this message.

If I reset on the OSD with both disks still inserted and "Start the game", I can go in game.
20240810_112809-screen

Thanks!

@yosinda
Copy link
Contributor

yosinda commented Aug 11, 2024

This is a common issue with Falcom games.
If no disk is inserted in drive 2 when booting, drive 2 seems to be excluded from processing.

For example, if you boot with only "Disk A" on Ys and select "Disk Load"(press F1), you will be prompted to insert the user disk into drive 1.
On the other hand, if you boot with a "User disk" inserted in drive 2, you will be prompted to insert it in drive 2.

I suspect that this is because the Falcom disk driver checks the ready signal of floppy disk drives and counts the number of floppy disk drives installed.

In Puu-san's implementation of the floppy disk drive, the ready signal is not asserted unless a disk is inserted.
If you try clipping the ready signal, this problem will not occur. However, this has a side effect.

@wwark
Copy link
Collaborator Author

wwark commented Aug 11, 2024

Thank you for the explanation !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants