2023-01-30 03:32 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005877DIC[All Projects] Generalpublic2022-11-22 23:50
ReporterCFOU 
Assigned ToWeplProject InfoDisk Image Creator
http://whdload.de/docs/en/dic.html
 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusresolvedResolutionfixed 
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.
MachineA1200
CPU68020
CPUSpeed50
ChipSetAGA
GFXCardNone
ChipMem2 MB
FastMem0 MB
WorkbenchOS 3.0
KickROM40 - Kick 3.1
KickSoftNone
Attached Files
  • ? file icon DIC (4,668 bytes) 2022-11-22 22:53 -
    óé`T$VER: DIC 1.3 (22.11.2022)$Id: DIC.asm 0.24 2021/03/30 10:55:15 wepl Exp wepl $
    p'FrHA,xN®ÿ:Jgº(@()|0p%CúÔ,TN®ýØ)@gp%CúÌ,TN®ýØ)@ghAúaAú
    ö)HAúº"Aì$v,lN®üâ)@fAú*aÎ`& lJgJfú:gAúµaL`ú , g* @a°JgAúÄa0`Þ)@ Aúì//"OaPr ,$g @")A$rÿ ,(g @")A(J¬g
    p)@$)@( l gxaXg,g-g6*g`VPô4JgV,gØ`F$v`Fa(Jo:¶e6Pô 4Ô¶dö`Ö$a&p*fàR`Ö"_&Hab·Èg
     dNÑAú
    eah`,lN®ÿÊ)@)|
    0a",,lN®üŠ"l,TN®þb"l,TN®þb.,0p'F"L,TN®ÿ. NupNuHç "$	,lN®üFLß@NuÉ`æAú`ö
    /,lN®ÿÄ"gN®þ,_NuAú`Ø*** User Break ***
    /"<,lN®üèJgaÐpÿ,_NuHç<,lN®ÿÊ*"tN®þV"B§$vN®ÿÖ(á`"Y$vN®ÿÖX"tN®ÿ4Jfæ"tN®þVfaÿx Lß@<NuHç3|"tþ,lN®ÿ¬.g< <r,TN®ýT,g "$&<,lN®þnJf
    "F,TN®ýN|",lN®ÿŠ Lß@ÌNuHç@ gJg0f
    J(fAú'/Aú"Oaþ¶OïNu%s (%s/%s)
    unspecified errorHç8,lN®ÿ|"tx@ÄB&N®þ,Aú
      O"wHaßÄLßANuHç?.,x"	$<î,lN®ÿâ*fAú,aª`"$&N®ÿÐxÿ°gAúax"N®ÿÜ Lß@üNuwrite fileHç<(&$	 Baþº*g$Aú,/"OaýÞX  C"Baÿ|$Jg"E,TN®ýN Lß@<Nusave file %s
    Jo
    Øg
    SføB!pNupÿNuHç2Gú$Ð&&JEú,TN®ýöLßLNuÀ·úfSNu°Pm°hn2PÒA20gÐÁ Nu h"fÜpNuHÀHç aÐJgPNu"OpAúEúa 
    X$_Nu%ldHçp"gr-WÇg+f$g0eV9bP0,çÐÐÐ`â0e9b0`"aefbW`AeFb7éÐ`ÄSJgDLßÀNuHç0t"gBv gø	gòSaÿR-gÔ` gø	gò+g-f`ÂS LßNuHç?"$$I~ÿr,lN®ýr"fAúaý|~`vN®ýTJfpAú
    :Cú
    ùaý
    ~` @ (@mpÐÐgj @Jšgb/ hÑÈÑÈpRr@²dX`HCÒaþ _%P@%hD (ÐÐg, @ (å%@H%hL%hP%hT%h$X%h(\`pAú	œCú
    gaüx~rN®ýl LßDüNu/HAúÒaþ @Cú
     	"_`üNdevice accessÿùÿÿ/<V{hardware failed selftestunit is busyinvalid address (IO_DATA)invalid length (IO_LENGTH/IO_OFFSET)unsupported device CMDAbortIO()open device failed2FTey«»ÍÝî&5BMh«not specifiedno sector headerbad sector preamblebad sector idbad header chksumbad sector chksumtoo few sectorsbad sector headerwrite protectedno disk in drivecouldn't find track 0not enough memorybad unit numberbad drive typedrive in usepost resetdata on disk is wrong typeinvalid CMD under current conditionsillegal/unexpected SCSI phasenonexistent board",tÿ,lN®ý*JgÌ.,$SRŸ¬(b€",,lN®ÿ(JVìÔg6Aúï/,/"OaøfPaø",,lN®þaøŸgf
    fðaøZ lar(*gPAú6/"OOïÿð$Opaú ,g$@ J¬ g
    °¬ c ,  E"JaúOï$"E,TN®ýNJg`ÿVB¬0",t,lN®ý*JgNuAú«`ù@Hç?NUÿ`~|Cíÿ`p?ØWÈÿüB!B!Aíÿ`Cíÿ aû~JgÔAúÈ/-ÿàHmÿ Hmÿ`"Oa÷Oï -ÿø"-ÿì,lN®ÿp$ -ÿü­ÿøR"-ÿìN®ÿp& -ÿè"-ÿôN®ÿp( "N®ÿp,Aú//-ÿü/-ÿø/-ÿô/-ÿì/-ÿè"Oa÷"OïJ¬ gŒ¬ cv|RÜŒ¬ eö r,TN®ýT.fpAúõCúÞaø`Aíÿ  "-ÿà"GaJf"G,TN®ýN|~" N]Lß@üNuHç5"NUÿì+@ÿü+Aÿø+IÿôQíÿïQíÿí~,TN®ýf+@ÿðfpAú§Éa÷ª`ð mÿðp8N®ýr$@JfpAú Éa÷`È mÿü -ÿø"Jr/N®þD&Jg*Aú^aúü`"J3|
    N®þ8%j 0Öaö< dJ4 4f(aö`JfPAúÃ/S/"OaõöPB*5|%D$ " lNšÿp%@,Эÿô%@("J,TN®þ8*gôAú¿aútJ¬,föQíÿî*e*ePíÿî*f"J3|
    N®þ8%j 0,ÔÐÐ-ÿîgRg°Rg<AúSaõraõzaõÂgae
    zb RgjQgd
    fÒ`\J-ÿïf2J-ÿífAúÔaõ&aõ.aõvgHae
    zb RgSgAgTgQg
    fÀ
    fpQáH<
    H@/ OaôÊ áRgþSg²QgàAgPíÿí*B*5|%|$ R" lNšÿp%@,Эÿô%@("J,TN®þ8*gL ü/Aú"Oaô:X*Aú5aøê j(p üTDICQÈÿø*f"J3|
    N®þ8%j 0Efÿraô`(Píÿïaô " lNšÿpЭÿô @ ä üTDICSföR¶fý€AúÁaóÒ~ÿ"JB©$3|	,TN®þ8"JN®þ> JN®ýl mÿðN®ý` N]LßD¬NuDF0:
    Insert disk %ld into drive %s and press RETURN (^C to cancel) ...Retry/Skip/skip All/Try sectors/Quit (r/s/a/t/Q): Retry/Quit (r/Q): Disk.%ldInvalid SKIPTRACK/K specification
    read from %s: (%s %ld)
    (blksize=%ld heads=%ld blktrk=%ld lcyl=%ld hcyl=%ld) size=%ld
    save disk as %s 
    save file %s 
    Kreading track %ld left %ld
    limited reading of $%lx=%ld bytes
    Knot enough free storecan't create MessagePortcan't create IO-Requestdevice doesn't existcannot handle this devicespecified device must have trailing colon
    illegal argument for SIZE/K
    sector #%ld read argumentsinhibit filesystemalloc mem for diskread diskget dev infoopen devicedos.libraryutility.libraryDEVICE,NAME,SKIPTRACK/K,SIZE/K,FD=FIRSTDISK/K/N,LD=LASTDISK/K/N,PEDANTIC/SDIC 1.3 (22.11.2022) D22misk 1mI22mmage 1mCreator by Bert Jahn
    ìÂò
    ? file icon DIC (4,668 bytes) 2022-11-22 22:53 +

-Relationships
+Relationships

-Notes

note ~0012012

CFOU (developer)

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)

note ~0012028

Wepl (manager)

Yes, the last change broke SkipTrack option completely.
Attached version 1.3 should fix that.
Can you check?

note ~0012030

CFOU (developer)

V1.3 tested with several SKIPTRACK options.

it seems to be working fine now :)

Thanks a lot Bert
+Notes

-Issue History
Date Modified Username Field Change
2022-11-18 01:47 CFOU New Issue
2022-11-18 01:47 CFOU Assigned To => Wepl
2022-11-18 01:47 CFOU Status new => assigned
2022-11-19 13:35 CFOU Note Added: 0012012
2022-11-22 22:53 Wepl File Added: DIC
2022-11-22 22:55 Wepl Note Added: 0012028
2022-11-22 23:14 CFOU Note Added: 0012030
2022-11-22 23:33 Wepl Sticky Issue No => Yes
2022-11-22 23:33 Wepl Sticky Issue Yes => No
2022-11-22 23:50 Wepl Status assigned => resolved
2022-11-22 23:50 Wepl Resolution open => fixed
2022-11-22 23:50 Wepl Fixed in Version => 1.3
+Issue History