Verma and Titanium's ADFS

I was about to compile a report on a recently discovered Verma 0.27c oddity on the Titanium. Extracting a module and saving it to ADFS resulted in a file that was filled mostly with zeros with a little bit of real code at the end of the file. This was with RC5, OS5.24 and OS5.25 (02-Jul-18). It was only ADFS that the extract went wrong on, it was OK to RAM: and SCSI:. StrongED could extract a module successfully. I am not aware of any other similar failures from other software.

The issue has “gone away” with today’s Titanium beta ROM (08-Jul-18). There are a number of CVS changes that may be relevant, SMP, SATADriver 0.09 and OSMemory 19.

Thanks for the fix.

Hmm, that’s reminded me that I’ve still got the broken Iyonix screensave to look into, where pretty much the same thing happens. But the code path there will be very different to what’s used on the Titanium (FileCore → ADFS 3.x → DMAManager? vs. FileCore → ADFS 4.x → SATADriver).

It’s good that it’s working now, but I should really look into why it was broken in the first place!

Two years!

Two years!

Indeed!!! That’s how long I have had the Titanium and it was only the other day I fell into this issue. I think this was because I always extracted modules to the RAM disc for no very great reason. Such are the vagaries of beta testing.

Just to confirm this cvs change has fixed the corrupted Verma extraction.

Many thanks.