WHDLoad MantisBT - Twylyte
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005854Twylyte[All Projects] Generalpublic2022-11-05 22:192022-11-14 17:47
Reporterretrogamer 
Assigned ToCFOU 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
MachineA600
CPU68000
CPUSpeed7
ChipSetOCS
GFXCardNone
ChipMem256 KB
FastMem0 MB
WorkbenchOS 3.2
KickROM47 - Kick 3.2
KickSoftNone
WHDLoad18.8
importedyes
Summary0005854: Exception "Integer Divide by Zero" ($14) at $1B624 (Task 'Initial CLI')
DescriptionGameVersion: english,pal,2 disks
SlaveVersion: 1.0 from 20.05.2000

Exception "Integer Divide by Zero" ($14) at $1B624 (Task 'Initial CLI')
occurred when running the game with 68010 cpu.
TagsNo tags attached.
Relationships
Attached Files? .whdl_registertwylyte (6,404) 2022-11-06 00:27
http://www.whdload.de/mantis/file_download.php?file_id=1495&type=bug

Notes
(0011929)
retrogamer   
2022-11-06 00:27   
registerfile attatched.
(0011935)
CFOU   
2022-11-09 18:26   
i think is a WHDLoad's bug.

indeed i use WHDLF_EmulDivZero flag, normally WHDLoad would not leave on error message and ignore this exception.

same problem with Hyperion and Hoversprint (soon released)

I asked Bert (WEPL) about this.

I'm waiting for his answer.

see AUTODOC:
WHDLF_EmulDivZero / WHDLB_EmulDivZero
                   This flag has an effect only if the VBR is moved by WHDLoad
                   (i.e. the machine is at least a 68010 and the tooltype
                   NoVBRMove is not set).
                   If the flag is set all division by zero exceptions are
                   emulated by the exception handler inside WHDLoad. I.e. the
                   handler checks if the vector ($14) is initialized and if
                   the routine to which the vector points to will be called by
                   WHDLoad.
                   This flag has precedence over the flag NoDivZero.
(0011942)
CFOU   
2022-11-10 01:02   
of course temporary solution is to use NoVBRMove option.
(0011953)
CFOU   
2022-11-10 23:36   
@retrogamer
have you compare with real 68010?

it's pehaps an issue with Winuae?
(0011955)
CFOU   
2022-11-11 14:25   
see:
https://eab.abime.net/showthread.php?t=112420
(0011983)
CFOU   
2022-11-14 17:47   
fixed with v1.1

Issue History
Date ModifiedUsernameFieldChange
2022-11-05 22:19administratorNew Issue
2022-11-05 22:19administratorStatusnew => assigned
2022-11-05 22:19administratorAssigned To => CFOU
2022-11-06 00:27retrogamerFile Added: .whdl_registertwylyte
2022-11-06 00:27retrogamerNote Added: 0011929
2022-11-09 18:26CFOUNote Added: 0011935
2022-11-10 01:02CFOUNote Added: 0011942
2022-11-10 23:36CFOUNote Added: 0011953
2022-11-11 14:25CFOUNote Added: 0011955
2022-11-14 17:47CFOUStatusassigned => resolved
2022-11-14 17:47CFOUResolutionopen => fixed
2022-11-14 17:47CFOUNote Added: 0011983