| Re: [hatari-devel] Hatari WinUAE vs oldUAE information, and MiNT with MMU? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Hatari WinUAE vs oldUAE information, and MiNT with MMU?
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Thu, 14 Jan 2021 15:31:06 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1610634667; bh=43FQJ5JzzkGQ97crqL2Fn9srg6FGv5Ilada2Icc55gs=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=aEa7zjScult0tAW0sY4of0sMo7Ee1zg1igYpG92ptpF/J5PgsCd2zfyjbCNGLA1QM C8pGeXmU64FuoRXS/5hff8zW3storWNKMG3oeqLncbCU4YXfCGdC/NPBgilj7km/QC 14qzkpXmqJ2TFnWWk5HpDWzjrnk81wL5I9Gb8f2Q=
Thorsten Otto schrieb:
What might be possible though is to install a short handler that gives a
short hint that a FPSP should be installed, when such an exception occurs.
Do you know if an unimplemented FPU instruction on a 68060 causes a
dedicated trap? Then it would certainly be possible to add a message to
that effect. However, asking the user to install the FPSP only makes
sense if the FPSP exists in *installable* form, i.e., as an AUTO folder
program.
Regards
Christian
--
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
WWW: https://www.chzsoft.de/
PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA