Re: [hatari-devel] Recent changes to GEMDOS harddisk emulation? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Am Donnerstag, den 22.12.2011, 18:31 +0100 schrieb Nicolas Pomarède:
> Hello
> does it work again if you revert the memvalid patch :
>
> --- a/src/stMemory.c Wed Aug 17 23:18:47 2011 +0200
> +++ b/src/stMemory.c Sun Nov 27 23:07:43 2011 +0100
> @@ -129,8 +129,11 @@
> STMemory_WriteLong(0x00, STMemory_ReadLong(TosAddress));
> STMemory_WriteLong(0x04, STMemory_ReadLong(TosAddress+4));
>
> - /* Fill in magic numbers, so TOS does not try to reference MMU */
> - if (ConfigureParams.System.bFastBoot
> + /* Fill in magic numbers to bypass TOS' memory tests in the case */
> + /* of EmuTOS or if more than 4 MB of ram are used */
> + /* (those tests should not be bypassed in the common STF/STE cases */
> + /* as some programs rely on the RAM content after those tests) */
> + if ((ConfigureParams.System.bFastBoot && bIsEmuTOS)
> || (ConfigureParams.Memory.nMemorySize > 4 && !bIsEmuTOS))
> {
> /* Write magic values to sysvars to signal valid config */
>
> (remove '+' line from stMemory.c and put '-' lines instead)
>
Hello,
yes it does work again, if I simply deactivate the if clause and always
call the memory init values:
/* Write magic values to sysvars to signal valid config */
STMemory_WriteLong(0x420, 0x752019f3); /* memvalid */
STMemory_WriteLong(0x43a, 0x237698aa); /* memval2 */
STMemory_WriteLong(0x51a, 0x5555aaaa); /* memval3 */
Hatari does crash with 4 bombs during the boot sequence if I leave them
out. (Crash happens when it does not find the calvino.ovl file)
Regards,
Matthias
--
Matthias Arndt <marndt@xxxxxxxxxxxxxx>
PGP-Key: http://www.final-memory.org/files/marndt.asc
Jabber: simonsunnyboy@xxxxxxxxxxxxxxxx