WHDLoad MantisBT - BobsBadDay
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003607BobsBadDay[WHDLoad Installs Games] OCSpublic2017-01-02 19:242017-01-03 14:06
Reporterhamakei 
Assigned ToStingRay 
PrioritynormalSeverityblockReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
MachineA1200
CPU68040
CPUSpeed40
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem8 MB
WorkbenchOS 3.1
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad18.2
imported
Summary0003607: Crash to desktop after intro with "Access fault" exception
DescriptionWhen using version 1.4 of the slave, the game crashes to desktop after the intro with the error:

Exception "Access Fault" ($7008)
PC = $971908 (Resload $6908)
Long Read from $973FFC

This initially happened when I simply replaced the 1.2 slave with the 1.4 slave, but even a complete game install from disk images causes the same error
Additional InformationThis seems to be related to the CPU - it runs fine with a 68020, but if I switch to an emulated 68040 then it crashes as described.
TagsNo tags attached.
Relationships
Attached Files

Notes
(0005425)
hamakei   
2017-01-02 19:25   
WHDLoad dump - https://www.dropbox.com/s/kpiz9t6c635meop/whdl_dump.zip?dl=0
(0005429)
StingRay   
2017-01-02 22:44   
It's not CPU related, extended memory wasn't set correctly in the patch, it needs to be aligned. This bug will also happen with the 1.2 slave depending on the location of the free memory. Updated patch will be available tomorrow.
(0005430)
hamakei   
2017-01-02 22:46   
Aah. Is that because the 68020 wouldn't be able to access the full 8Mb of fast RAM? Forgive my ignorance, but I'm curious...
(0005431)
StingRay   
2017-01-02 22:51   
No, it has nothing to do with that. The game expects the extended memory to start at an aligned address, i.e. low word of the memory ptr (f.e. $200000, $c00000 etc. will work fine) has to be clear. If this is not the case certain game routines will not work correctly causing the crash.
(0005432)
StingRay   
2017-01-03 14:06   
v1.5 of the patch is now available which fixes this problem.

Issue History
Date ModifiedUsernameFieldChange
2017-01-02 19:24hamakeiNew Issue
2017-01-02 19:25hamakeiNote Added: 0005425
2017-01-02 22:44StingRayNote Added: 0005429
2017-01-02 22:44StingRayAssigned To => StingRay
2017-01-02 22:44StingRayStatusnew => assigned
2017-01-02 22:46hamakeiNote Added: 0005430
2017-01-02 22:51StingRayNote Added: 0005431
2017-01-03 14:06StingRayNote Added: 0005432
2017-01-03 14:06StingRayStatusassigned => resolved
2017-01-03 14:06StingRayResolutionopen => fixed