WHDLoad MantisBT - DIC
View Issue Details
0005877DIC[All Projects] Generalpublic2022-11-18 01:472022-11-22 23:50
ReporterCFOU 
Assigned ToWepl 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version1.2 
Target VersionFixed in Version1.3 
MachineA1200
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.0
KickROM40 - Kick 3.1
KickSoftNone
Summary0005877: SKIPTRACK issue
DescriptionWorking on Dragon Lord package I had to use RawDIC instead of DIC.

Indeed, I think the latest version of DIC is buggy.

I've had the same problem twice with protection on track 158 (with Passing Shot too)

indeed SKIPTRACK=158 is not taken into account then SKIPTRACK= 1 or SKIPTRACK=100 works correctly.

With SKIPTRACK=158
DIC tries to read track 158 which causes read errors since in my case the protection is on this track :)
Could you look at the problem?
I didn't check but maybe the maximum track taken into account is 157 and not 159...

Best regard,

Bertrand
TagsNo tags attached.
Attached Files? DIC (4,668) 2022-11-22 22:53
http://www.whdload.de/mantis/file_download.php?file_id=1518&type=bug

Notes
(0012012)
CFOU   
2022-11-19 13:35   
i think track is skipped in "DISK.x" file
but DIC try to read track data even if it skip it.

see:
https://imgur.com/oEImSzh

no problem with DIC 1.1 (tested)
(0012028)
Wepl   
2022-11-22 22:55   
Yes, the last change broke SkipTrack option completely.
Attached version 1.3 should fix that.
Can you check?
(0012030)
CFOU   
2022-11-22 23:14   
V1.3 tested with several SKIPTRACK options.

it seems to be working fine now :)

Thanks a lot Bert

Issue History
2022-11-18 01:47CFOUNew Issue
2022-11-18 01:47CFOUAssigned To => Wepl
2022-11-18 01:47CFOUStatusnew => assigned
2022-11-19 13:35CFOUNote Added: 0012012
2022-11-22 22:53WeplFile Added: DIC
2022-11-22 22:55WeplNote Added: 0012028
2022-11-22 23:14CFOUNote Added: 0012030
2022-11-22 23:33WeplSticky IssueNo => Yes
2022-11-22 23:33WeplSticky IssueYes => No
2022-11-22 23:50WeplStatusassigned => resolved
2022-11-22 23:50WeplResolutionopen => fixed
2022-11-22 23:50WeplFixed in Version => 1.3