Starting ADFFS hangs the A3000

[Radiofan]

I have an A3000 with RISCOS 3.1, UniBoot 2, Arm 3 and WE super VIDC fitted.

I am trying to access greaseweazled ADFS 1600 format discs, by opening them in ADFFS.

I can get images onto USB and then onto the 1GB ZIDEFS drive. Unfortunately, as soon as I start ADFFS, the screen goes black and the computer stops reponding. I have to power off and back on again.

I have temporarily disabled the anti-virus module during boot, to no avail.

I have tried the latest version of ADFFS and also a version from 2023, same result.

Any ideas as to what I can try?

[Radiofan]

To answer my own question, I managed to comment out loading of the AutoVIDC module in the !Run file and ADFFS now starts up fine.

Changing the image types to "Floppy" and dragging it to the ADFFS icon, I can now see the contents of ADFS type F images.

[JonAbbott]

It sounds like AutoVIDC doesn't like the WE super VIDC, which is odd because I'm sure it supports it.

Do you have another Module loaded that handles mode changes for it? If so, let me know what its called and I'll modify the ADFFS start-up script to check for it and not load AutoVIDC if it's loaded.

[Radiofan]

Maybe it's the combination of ARM3 and WE super VIDC. Or maybe my VIDC is installed differently (I use *configure sync 0).

All versions of AutoVIDC I tried hang the machine. There is no other video related modules loaded at the time of trying.

Oddly and thankfully, LCDGameModes works nicely.

[JonAbbott]

AutoVIDC 2.08 added support for the WE Super VIDC Enhancer, the discussion thread about it is here. Mentioned in that thread, and probably the likely cause of the lock=up, is the clock detection.

It was so long ago, I can’t remember if the clock detection code ended up shutting off DMA to do its tests, which might be the root cause. One test worth doing, just to rule out something else causing the lock-up, is a SHIFT-BOOT to bypass the WIMP startup and then manually run AutoVIDC without the Wimp loaded (CTRL-SHIFT+F12 twice when at the Desktop, or hit * on the number pad during POST to boot to Supervisor)

[Radiofan]

So I did that, shift held on boot, shift-ctrl-f12 twice, dropped into console, listed modules to check no modules were loaded.

rmload AutoVIDC still hangs the machine.

[JonAbbott]

Thanks for confirming, I'll find the source and figure out if there's some tests you can do to try and pin down where it's hanging.

[JonAbbott]

I've taken a look at AutoVIDC and made a few changes. Could you please try the attached to see if it still hangs when manually loaded.

If it doesn't hang, could you grab the output from *AutoVIDCStatus please.

EDIT: Attachment removed

[JonAbbott]

AutoVIDC still hangs the machine.

Have you had a chance to try the test build of AutoVIDC above?

[Radiofan]

Sorry, I just noticed you produced this new version. I shall try it in the next few days.

[Edit]: Just tried it, same result unfortunately (hangs).