Search found 78 matches

by PaulV
Sun Dec 29, 2013 11:42 pm
Forum: AutoVIDC
Topic: AutoVIDC 2.11
Replies: 10
Views: 1507

Re: AutoVIDC 2.11

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 ...
by PaulV
Mon Dec 09, 2013 12:16 am
Forum: AutoVIDC
Topic: AutoVIDC 2.11
Replies: 10
Views: 1507

Re: AutoVIDC 2.11

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...
by PaulV
Sun Dec 08, 2013 2:14 pm
Forum: AutoVIDC
Topic: AutoVIDC 2.11
Replies: 10
Views: 1507

Re: AutoVIDC 2.11

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 ...
by PaulV
Wed Dec 04, 2013 5:29 pm
Forum: AutoVIDC
Topic: AutoVIDC 2.11
Replies: 10
Views: 1507

Re: AutoVIDC 2.11

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...
by PaulV
Wed Dec 04, 2013 1:18 pm
Forum: AutoVIDC
Topic: AutoVIDC 2.11
Replies: 10
Views: 1507

AutoVIDC 2.11

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...
by PaulV
Wed Jul 03, 2013 12:46 am
Forum: AutoVIDC
Topic: MakeModes
Replies: 4
Views: 466

Re: MakeModes

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 ...
by PaulV
Tue Jul 02, 2013 8:31 pm
Forum: AutoVIDC
Topic: MakeModes
Replies: 4
Views: 466

Re: MakeModes

JonAbbott wrote:Have you seen this thread on RiscOS Open?
Who? Me or Steve?

Paul
by PaulV
Tue Jul 02, 2013 8:30 pm
Forum: Web site
Topic: RSS/Atom feeds
Replies: 9
Views: 2211

Re: RSS/Atom feeds

JonAbbott wrote:Have you successfully authenticated into the feeds?
No, it's most odd...

At the moment, I can't seem to consume the public feed correctly anyway. I need to check why and get back to you.

Paul
by PaulV
Sat Jun 29, 2013 9:41 am
Forum: LCDGameModes
Topic: RiscPC support
Replies: 140
Views: 4996

Re: RiscPC support

Good point, unfortunately I don't have the LCDGameModes 0.21 code to check ... however, there's a comment at the end of 0.22 saying "need to disable 25175Hz clock now...", which made me think early on that there should be clock manipulation code in there somewhere. Steve may have stripped it out fo...
by PaulV
Fri Jun 28, 2013 10:28 pm
Forum: LCDGameModes
Topic: RiscPC support
Replies: 140
Views: 4996

Re: RiscPC support

Running at 66Hz indicates that you're running the VIDC clock at 24MHz. LCDgm is setting the clock to 24MHz, should I change LCDgm to set 25.175 instead? That'd be for Steve to decide I guess... The reference clock is fixed at 24MHz, the VCO output can be anything from 55MHz to 100MHz which is then ...