WHDLoad MantisBT - LordsOfTheRisingSun
View Issue Details
0001807LordsOfTheRisingSun[All Projects] Generalpublic2008-01-04 21:172017-11-27 17:38
ReporterRixa 
Assigned ToStingRay 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
MachineA1200
CPU68EC020
CPUSpeed14
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem8 MB
WorkbenchOther
KickROM40 - Kick 3.1
KickSoftNone
WHDLoad16.8
importedyes
Summary0001807: Lords of the Rising Sun: Crashes all the time. Sometimes as long as a few
DescriptionInstall: Lords of the Rising Sun (Cinemaware) http://whdload.de/games/LordsOfTheRisingSun.html
GameVersion: The download from Cinemaware web page.
SlaveVersion: 1.2 from 12.10.06

Crashes all the time. Sometimes as long as a few minutes into gameplay but often even before the title screen shows up. The error is usually if not always something to the effect of:
Wxception 'Privilege Violation' ($20) at $9AC8F6 (Task 'input.device', ExpMem $876)
I've tried NOCACHE, NOAUTOVEC, NOVBRMOVE, PAL, NTSC but seen no improvement. WHDLoad works fine for me with most other games.
TagsNo tags attached.
related to 0002094closed Wepl WHDLoad "privilege violation" at expmem+$8f6 
Attached Files

Notes
(0000468)
haynor666   
2009-04-23 08:42   
I tried this with original and works for a while on PAL (but might hangs later) but indeed fails on NTSC version.
(0002933)
StingRay   
2013-03-03 17:44   
WHDLoad version uses a very strange & dirty approach to bypass the Herndon HLS protection which causes these problems. I have already made a new patch and cracked the HLS protection in a clean way, no crashes anymore! Updated patch will be released after a bit of testing.
(0003656)
Wepl   
2014-01-11 18:27   
please try the whdload attached to 0002094, it should solve that issue
(0003688)
Rixa   
2014-01-25 10:57   
I played for a while with the WHDLoad from that bug and the 1.3-B slave and got no crashes. However, it also worked when using WHDLoad 17.2, so I think StingRays new patch is probably what fixed it.

Either way, looks like the crashes are gone, so the bug can be closed.

Issue History
2009-04-10 01:18administratorNew Issue
2009-04-10 01:18administratorStatusnew => assigned
2009-04-10 01:18administratorAssigned To => JOTD
2009-04-10 01:18administratorMachine => A1200
2009-04-10 01:18administratorCPU => 68EC020
2009-04-10 01:18administratorCPUSpeed => 14
2009-04-10 01:18administratorChipSet => AGA
2009-04-10 01:18administratorGFXCard => None
2009-04-10 01:18administratorChipMem => 2 MB
2009-04-10 01:18administratorFastMem => 8 MB
2009-04-10 01:18administratorWorkbench => Other
2009-04-10 01:18administratorKickROM => 40 - Kick 3.1
2009-04-10 01:18administratorKickSoft => None
2009-04-10 01:18administratorWHDLoad => 16.8
2009-04-10 01:18administratorimported => yes
2009-04-22 22:10JOTDStatusassigned => acknowledged
2009-04-23 08:42haynor666Note Added: 0000468
2013-03-03 17:44StingRayNote Added: 0002933
2013-03-03 17:44StingRayAssigned ToJOTD => StingRay
2013-03-03 17:44StingRayStatusacknowledged => assigned
2013-12-23 16:52WeplRelationship addedrelated to 0002094
2014-01-11 18:27WeplNote Added: 0003656
2014-01-25 10:57RixaNote Added: 0003688
2017-11-27 17:38StingRayStatusassigned => resolved
2017-11-27 17:38StingRayResolutionopen => fixed