ADFFS 2.15 RC

Discuss ADFFS development and download test releases
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

I dusted off the SA RPC last night, but didn't get round to testing as had a monitor issue. All sorted now, so I will test tonight.
JonAbbott
Posts: 2938
Joined: Thu Apr 11, 2013 12:13 pm
Location: Essex
Contact:

Re: ADFFS 2.15 RC

Post by JonAbbott »

A4000 and Pi seem okay. I'll test on the A440/1 over the weekend if I get a chance, then it's just the Kinetic and/or RO4/SA issue to resolve (or just list as a known issue to get it out the door)
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

Sorry for the delay, unexpected issues with the Risc PC - network card failed to work, so had to use floppy... but the drive is now refusing to recognise high density discs.

Anyway, after some disassembly and reassembly, I have a working network card (not solved the floppy drive failing to read HD discs - it just says 'drive empty' if I put an HD disc in... possibly something to do with it being a PC floppy drive on a converter cable...).

As the lid was off, I tried Arm610 card and StrongArm cards. Results below, both use latest version of ADFFS (archive dated 10/6/13 off the dev. site) and Zarch JFD:

StrongArm Risc PC, Risc OS 4.02, with Arm 610 card fitted - opens and reads JFD perfectly
StrongArm Risc PC, Risc OS 4.02, with StrongArm 233 card fitted - opens and reads JFD perfectly

Can't fault it, ADFFS 2.15 and the JFD seem fine to me :)

Steve
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

...I did note that Zarch doesn't actually run on either, but that isn't to be expected is it?
JonAbbott
Posts: 2938
Joined: Thu Apr 11, 2013 12:13 pm
Location: Essex
Contact:

Re: ADFFS 2.15 RC

Post by JonAbbott »

steve3000 wrote:...I did note that Zarch doesn't actually run on either, but that isn't to be expected is it?
It will work on the ARM610 if you use "Boot floppy", it may work on the SA, I can't remember if I put the fix in the boot sequence or not.

Thanks for testing, looks like an issue on just the Kinetic then.
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

JonAbbott wrote: It will work on the ARM610 if you use "Boot floppy", it may work on the SA, I can't remember if I put the fix in the boot sequence or not.
I've switched over to RO3.70 now, with Arm610 in, and it's definitely not running with 'Boot Floppy'. Brings up a memory / register dump and an error relating to screen memory location?

StrongArm and RO4.02 just gave a command prompt after 'Boot Floppy' - so does that mean the fix wasn't there?
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

On the Arm610 the error is actually 'data abort' screen memory location is listed in the dump.
JonAbbott
Posts: 2938
Joined: Thu Apr 11, 2013 12:13 pm
Location: Essex
Contact:

Re: ADFFS 2.15 RC

Post by JonAbbott »

steve3000 wrote:On the Arm610 the error is actually 'data abort' screen memory location is listed in the dump.
Check the !Obey file in the ADFFS folder after booting it, I think it's set to only do the memory remap up to RO3.71

If there's no ADFRemapVideoMemory line then I've managed to put an old copy in the JFD folder.
steve3000
Posts: 198
Joined: Thu May 02, 2013 9:25 pm

Re: ADFFS 2.15 RC

Post by steve3000 »

Ok, my fault... I'm running RO 3.70 now, but had popped the StrongArm card back in, not the Arm610 (it did seem quite a lot more responsive)... So the data abort has triggered presumably because of some self modifying code in Zarch.

On RO4, I've looked at the !Obey file after it fails, the "ADFRemapVideoMemory 13 160" is conditionally run if ADFFS$OSVersion >= &35000 AND <= &37100 - so isn't happening on RO4, is that right?
Cheers,
Steve
JonAbbott
Posts: 2938
Joined: Thu Apr 11, 2013 12:13 pm
Location: Essex
Contact:

Re: ADFFS 2.15 RC

Post by JonAbbott »

Yes, that's the correct. I couldn't get it working on my Kinetic, which by the sound of it is possibly a Kinetic specific issue.

You could test it, remove the condition from the line, shell to the Supervisor with Zarch mounted and manually run the !Obey file. That will confirm if the issue in the Abort vector code is RO4 or Kinetic specific - I'm expecting it to work on the ARM610, but fail on the SA with RO4.

That JFD boot script is actually out of date, the one I have in my obey folder is as below, if we can confirm it works I'll update the JFD

Code: Select all

IF ADFFS$OSVersion>=&35000 THEN ADFRemapVideoMemory 13 160
ADFForceVSync 4
ADFS
DIR ADFS::0.$
IF ADFFS$CPUID>=&A10 THEN ADFCacheOff 1500
!BOOT
I'll also modify ADFFS during the week to support script overrides in !ADFFS.Obey, that will make testing easier going forward.
Post Reply