2012-08-23 BBxM ROM: errors during boot

I updated to the 2012 August 23 BBxM image today. I wish I hadn’t.

Where are (or should be) <grep$Dir>.!Sprites, <Indent$Dir>.!Sprites and <Patch$Dir>.!Sprites?

I have also and the HDImage. No Problems at this point (ppp-connections does not work yet again).

I got the HardDisc4 self-extracting image from August 23 too, and copied it over my existing HardDisc4. It appears to have made zero difference.

The boot process doesn’t complete, so the screen comes up with monitor Auto, and (I think) 640 * 480. Every time I boot it I have to reconfigure the screen parameters – and of course it has a bug where it refuses to save because the colours or resolution are unknown, which is clearly not the case.

Are the missing sprites a consequence of a missing theme manager or something like that?

The boot process doesn’t complete, so the screen comes up with monitor Auto, and (I think) 640 * 480. Every time I boot it I have to reconfigure the screen parameters – and of course it has a bug where it refuses to save because the colours or resolution are unknown, which is clearly not the case.

This is most likely due to the removal of the VIDCBandwidthLimit *command. Update your PreDesk.Configure.!Run as described here

Are the missing sprites a consequence of a missing theme manager or something like that?

A few weeks ago a bug was fixed which was preventing *IconSprites from reporting an error when sprites were missing. So as a consequence, lots of programs which try to load non-existent sprite files are now generating errors. Delete the offending IconSprites lines from the !Boot files of the broken programs, or add your own sprite files for them to use, or pester the authors to fix their programs, or some combination of the above.

Well, that’s certainly changed the symptoms…

Now when I cancel the error window “File ‘<grep$Dir>.!Sprites’ not found”, it remains there, clearly being redrawn several times per second, and gets no further. It’s gone from being a bit broken to completely broken!

… but I found the offending applications much more easily than I expected, and now it boots OK. (I had to plug the hard drive into the Iyonix to search and to make the changes.)

Thanks again, Jeffrey!