20th Jan Iyonix Development softload

Hi,

The softload archive for 20th Jan only contains the ROM image and not the actual softload tool so could this be corrected please.

I have got it working by using an old !Softload app and replacing the ROM

Also as reported else where the latest 5.19 Iyonix ROM, 20th Jan 12, does stop EasyFontPro working.

https://www.riscosopen.org/forum/forums/4/topics/855?page=1

EasyFontPro v5.11 aborts on start up with “Internal Abort on Data Transfer at &20B6A460 – Internal code 63505”. The actual address using *Where states not in module and the address does change each time you try to start EasyFontPro but *Where always states it is not in module. The error code 63505 is always constant.

The error seems to come about after the initial loading screen and normally I get a message at that stage that the Fonts path is being altered so could this be part of the problem?

I can also state that the latest HardDisc4 !Boot image, 21st Jan 12, and 5.19, 20th Jan 12, combination has stopped the SetSound error I reported so thanks for sorting that.

Doug

The error seems to come about after the initial loading screen and normally I get a message at that stage that the Fonts path is being altered so could this be part of the problem?

I think there is a problem with the length of the buffer used when changing the Font$Path. When playing with Calibre recently I found I kept getting an error ‘Buffer too short’ or similar when launching. It was due to Calibre (in the !Run file) adding a new directory to font path for the moon phase symbol font. The font was buried in the app resources directory. Setting a sysvar in the run file pointing to the font directory, and adding that to the font$path instead allowed things to complete correctly. This was on an Iyonix with 5.17, but there is a note in the original distribution from a few years back about some Iyonix users observing this, the workaround being to copy the font into the normal fonts directory, and remove the line from !Run in the app.

The softload archive for 20th Jan only contains the ROM image and not the actual softload tool so could this be corrected please.

The way we build stuff for the site has been transitioning over the last couple of days. The upload on the site now should’ve fixed this issue.

Steve

Thanks for the explanation and fixing the issue.

The autobuild announcement is really good news.

Doug