2024-10-05 12:09 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005573SecondSamurai[All Projects] Generalpublic2022-04-10 22:04
ReporterPascal De Maeseneire 
Assigned ToStingRayProject InfoSecond Samurai (Psygnosis/Vivid Image)
http://www.whdload.de/games/SecondSamurai.html
 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
Summary0005573: Hi StingRay, I just finish to test Your latest slave AGA on my real A1200. I
DescriptionGameVersion: english,pal,3 disks from SPS 1624 AGA EUROP
SlaveVersion: versiom 1.3 (10.04.2022) done by StingRay

Hi StingRay,
I just finish to test Your latest slave AGA on my real A1200.
I have an error => return to workbench screen with this message :
Exception Line error 111 Emulator ($2c) at $4D7C"
This problem come when I choose CD32 Option.
But attention : I use a Tom+ USB to support a Logitech F310 PAD with CD32 Emulation ?
The error come when I press Y (Yellow) or B (Red) but custon 5=1 is enable
On my PAD all buttons are like this :
        Y
     X B
        A
on the other slave for ECS game there isn't any problems.
Please could You have a look ?
Best regards,
Pascal
TagsNo tags attached.
MachineA1200
CPU68EC030
CPUSpeed40
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem32MB
WorkbenchOS 3.1.4
KickROM46 - Kick 3.1.4
KickSoftNone
WHDLoad18.7
importedyes
Attached Files

-Relationships
+Relationships

-Notes

note ~0011116

Pascal De Maeseneire (reporter)

@Stingray,
You can close now.
You already resolved the problem about AGA version.
Many Thanks,
Best Regards,
Pascal

note ~0011117

StingRay (developer)

That's because I got a mail with your bug report before this ticket was assigned. :) Thanks for reporting.
+Notes

-Issue History
Date Modified Username Field Change
2022-04-10 19:58 administrator New Issue
2022-04-10 19:58 administrator Status new => assigned
2022-04-10 19:58 administrator Assigned To => StingRay
2022-04-10 21:19 Pascal De Maeseneire Note Added: 0011116
2022-04-10 22:03 StingRay Note Added: 0011117
2022-04-10 22:04 StingRay Status assigned => resolved
2022-04-10 22:04 StingRay Resolution open => fixed
+Issue History