| Re: [hatari-devel] _FRB cookie in Falcon emulation |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] _FRB cookie in Falcon emulation
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sat, 02 Aug 2025 10:54:53 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.de; s=2017; t=1754132093; bh=drpwweVD7dTphB3fPYZiK9uTK1Rj5T0o+F9zVjI8jqc=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=OrexEF0LQsekeQ9uW46lI0k9ph9bVjmi8T4w2KSYYf6nF9a+5iV5/iziIja0UQ6wW qZBpUkqvJnZm0cOnxjfALGLnDTGXCfcQ27Uf1sIzmiRDzC8bxc1ES5+1bRcoVQr+tv Tkdo9goLqs/bRmDMgt8521X5cwYDSa7GU1/vLukYupmrx+pwEDbWehAkumQESd16/L yBS07OUhZB1COTAPKXcMnTKvIwkrObcfcdRMFMJl1/hDPLLqtAWfcNbiz8jBE2V1O+ 9GcSNl808+B8WVNrsJrDLeurOXaBvoaaJu05H9c1pgfx2SzAFRDQ4rIk8SgjDyP9W6 QoSwA7fwtcEcQ==
Am Sat, 2 Aug 2025 12:36:35 +0200
schrieb Uwe Seimet <Uwe.Seimet@xxxxxxxxx>:
> 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 ;-).
Ok, thanks, I think I've got it now.
Unfortunately, there are a couple of reasons for patching TOS and system
variables in Hatari (e.g. when using a 68060 with normal TOS), and I
think we cannot put all that information into the GUI, there's simply not
enough space in the dialogs.
But maybe we could simply add a master switch for disabling all TOS and
sysvar hacks at once? That would of course render a lot of the extensions
like TT-RAM in Falcon mode unusable, but maybe it would help with your
testing?
Thomas