Re: [hatari-devel] _FRB cookie in Falcon emulation

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


Hi,

> I have to admit that I still do not quite understand your concerns here.
> Real hardware either has to have a patched TOS, or an AUTO folder program
> for doing Maddalt() and installing a _FRB cookie. So either way, there
> should be a _FRB cookie, otherwise the floppy disk is unusable, isn't it?
> Or is there a hardware extension for the Falcon that really works without
> the _FRB cookie? If so, how did they manage to get the floppy disk working
> in that case?

As I have tried to explain here and in the email I sent you, I was surprised
by the change in behavior wrt an unpatched TOS when Fast-RAM is installed.
I missed the _FRB-related information in the mailing list. Apparently there
was also a change to the handling of _ramtop and maybe _ramvalid, which is
not mentioned in the release notes.

Whether these changes have any impact on other software than mine I cannot
tell. For me there might have been an impact in future versions of my
software, but fortunately I stumbled upon the change in the beta test
phase. With these changes Hatari does not cover one of my test scenarios
anymore, but this is not an issue because now I am aware of the changes.

With other settings that effectively modify TOS, like "Boot faster by
patching TOS & sysvars" it is obvious in the UI that TOS behavior is
changed. For the changes we are talking about this is not transparent.
This is why I was asking for a note in the "Memory setup" dialog.

It's as simple as that ;-).

Best regards

Uwe



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/