Open nitrologic opened 1 year ago
lha l archive is listing zero files
[write] -56 1 30.1% 3--48 93:18:58 [write] -62 44 50.6% 3--48 93:18:58 [write] 104 0 6.0% 3--48 93:10:53 [write] -------- ------- ----- --------- ---------127 -17 24.1% 1--20 80:0:0 0 files_ [write] Operation successful.
more logging and things start to make sense
[write] -62 44 50.6% 3--48 93:18:58 [write] 104 0 6.0% 3--48 93:10:53 [dos] lock T: => -24lock SkidMarksDemo.lha => -25open SkidMarksDemo.lha => -32lock SkidMarksDemo.lha => -27 [write] -------- ------- ----- --------- --------_-127 -17 24.1% 1--20 80:0:0 0 files_ [write] Operation successful.
Multiple locks supported per NativeFile solved.
New issue involves CurrentDir being invoked with a positive lock when system locks are all negative...
Still no fix for positive CurrentDir argument.
logging from https://github.com/nitrologic/skid30/blob/main/MyACID500/lha4.log [228]
[write] *** Error on file '' :
which happens way before currentdir, what is it calling,
more logging incoming
new issues are likely signal based.
Amiga signals, in you area now?
http://amigadev.elowar.com/read/ADCD_2.1/Libraries_Manual_guide/node02D4.html
basic signal operations implemented and logged
new task offset for providing root link of 0 means currentdir argument now explained
latest curiosity from lha 16 .log:
[exec] findTask <= 80e000 [read32] 80e0b8 [write16] 80e0b8 [write16] 80e0ba [dos] lock t:,fffffffe => 0 [write16] 80e0b8 [write16] 80e0ba
Ami style exclusive and shared access improved, current point of value smells like seek quirks.
[dos] seek ffffffe0,fffffff2,BEGINNING => 8000 [dos] read ffffffe0 , 581fc , 8000 => 8000 [exec] copyMem 14 [exec] freemem [exec] freemem [exec] fmt WARNING: Skipping corrupt/extraneous data[K => WARNING: Skipping corrupt/extraneous data[K|
Setting mmu_read8 back to unsigned byte fixes this seek nonsense.
Now back to
*** Error on file 'format.iff' : |
New trace clock feature added to both system and machine logs.
Combined raw trace of current issue is here:
https://raw.githubusercontent.com/nitrologic/skid30/main/MyACID500/log/lha_trace_1.log
from latest log, the offset 0xa4 of a task now has magic number to show it up
024ae2 [exec] findTask <= 80e000 024ae5 [read32] 80e0a4,cafeb0b0 024aea [read32] 80e0a4,cafeb0b0 024af5 [exec] findTask <= 80e000
skipping corrupt / extraneous data