Sorry for the delay in getting back to you. I've had no feedback either way from anyone but it seems stable enough on the clock detection front. I'm extremely busy with work and I'll be in New York until the 13th Jan. so I don't have the time to update the docs with the extra SWI info at the moment ...
Attached is the AutoVIDC 2.11 beta version and a small basic program to test the thing. If you place the AutoVIDC module in the RAM disc and run the BASIC program, it should load the module, check the clocks with you to confirm the detection is correct, then go into an infinite look killing an re-lo...
Ok, whilst cleaning up and testing with my BASIC test rig, I've discovered that the ranges defined for characterising the clock speeds are *all* out on *all* machines depending on the screen mode used. The issue as I first characterised it is definitely there but by addressing this more fundamental ...
The clock detection code is the same for all Arc's from the A300 through to the A5000 in that it counts a number of interrupts based on the speed of the VIDC clock and the count returned should fall within specific ranges for specific clock speeds. Once the machines have warmed up a bit it seems the...
In the couple of months, I've had only a small amount of time to have a look at my Arc's and when doing so, I spotted a couple of issues with AutoVIDC 2.09/2.10 when running AutoVIDC on an A5000. From a cold (and I mean temperature cold) boot, AutoVIDC 2.09/10 work perfectly. However, once the machi...
Nope, not me, it's !CustomVDU which is a non-Acorn predecessor to !MakeModes for pre RISC PC Archimedes machines which I have the source code for and provided fixes to but even then I can't release new versions without sending the changes back to the original author as CustomVDU is written in BASIC ...