Filer setup 21-07-13

BB -xm C1

Selecting Filer in Configuration generates an error, ‘Filer setup may have gone wrong. Click continue…’ . Describe gives, ‘Invalid Component ID (0×3e).’ Repeated clicking on ‘Continue’ opens the Filer configuration window. Changing an item and selecting ‘Set’ generates the same errors again. Repeated clicking on ‘Continue’ in the error box sets the item.

Same thing is happening for the Windows setup. Error this time is, ‘Invalid Component ID (0×5)’. Again, clicking continue opens the configuration window. This time selecting ‘Continue’ doesn’t allow the window to close.

My choices for those options have been reset to default values in the configuration windows but not in fact. For instance, for windows movement is allowed off screen for both options whereas I had configured top & left off. In testing, windows are indeed prevented from going off screen in those directions.

BB -xm C1
Selecting Filer in Configuration generates an error, ‘Filer setup may have gone wrong.

As ever:
What version of ROM and what version of Boot? With more specific information people can make a better estimate of the source of the problem.

If you have upgraded the ROM recently did you also do a Boot upgrade or are you still using the pre-upgrade boot sequence?

Well I can substantiate Fred’s issues as I get those errors as well.

21st July 13 Hard disc image and 22nd July 13 ROM.

Used merge over existing !Boot which was itself last updated with the previous update of 9th July 13.

I also tried a clean update i.e. renamed existing !Boot and copied 21st July version and rebooted my Beagleboard and I don’t get the errors in Filer and Windows set up but I do now get and error when using SndSetup which I didn’t get using the previous method:

File SCSI::HardDisc4.$.!Boot.RO500Hook.
Res.Configure.!sndsetup.messages not found.

Think the earlier issues may require either a full overwrite of an existing !Boot rather than a merge or a clean install subject to the file missing issue being resolved in later HardDisc image.

Used merge over existing !Boot which was itself last updated with the previous update of 9th July 13.

The date on the build machine appears to have been wrong, so anything generated during the build would be believed to be older that the copy you already have, and not be updated.

If you use the filer to ‘stamp’ everything in the ZIP file first it should merge properly (likewise stuff updated with filer ‘Newer’ on).

What version of ROM and what version of Boot? With more specific information people can make a better estimate of the source of the problem.

Version of Boot – see thread title 21-7-13. Version of ROM 22-7-13.

The date on the build machine appears to have been wrong, so anything generated during the build would be believed to be older that the copy you already have, and not be updated.

I usually update at each disc image release using a combination of DirSync & SideDiff so probably been caught out too. I’ll try some forced writes or backtrack.

On a different note, The latest update has a new MimeMap file. The one I have has a number of extra entries having been updated over the years to add in contributions from Acorn, ROL, ROOL & others. Is it of interest?

Fixed. Thanks Sprow.

On a different note, The latest update has a new MimeMap file. The one I have has a number of extra entries having been updated over the years to add in contributions from Acorn, ROL, ROOL & others. Is it of interest?

If you check the CVS entry:
http://www.riscosopen.org/viewer/view/mixed/RiscOS/Sources/SystemRes/Internet/Resources/files/MimeMap.diff?r1=4.5&r2=4.6

You can pick out the specific lines altered. Zip file type handling on PC shares is the issue:
http://www.riscosopen.org/viewer/revisions/logs?ident=1373734093-754398.html

You can pick out the specific lines altered

Thanks Steve but that’s not what I meant.

Thanks Steve but that’s not what I meant.

Ah, input rather than output.