Page 1 of 2

OWB-MUI on X1000

Posted: Fri Sep 14, 2012 7:13 am
by AmigaDave
Sorry if this question is not really appropriate for this forum, as it probably is not specific to the X1000, and AmigaKit's installation of the initial software included with every X1000, but this is where all the X1000 owners hang out, so I figured someone here could answer this simple question.

Every time I start OWB-MUI, it goes through a font initialization. It doesn't take long, so I haven't asked before now, but I am sure there must be a way to prevent this from needing to be run every time OWB is started, but I have not found out how to prevent this and make it permanent, so it doesn't have to do it at every start?

Unless there is some advantage of having this run every time and it should not be disabled?

Thanks,

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 8:21 am
by LyleHaze
I use the non-MUI version of OWB, and it never scanned fonts on entry until last week when I started copying some fonts around. It now recognizes that things have changed, and mine scans at every opening as well.

I'll be watching this for more information. :)

Lyle

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 8:58 am
by AmigaDave
LyleHaze wrote:I use the non-MUI version of OWB, and it never scanned fonts on entry until last week when I started copying some fonts around. It now recognizes that things have changed, and mine scans at every opening as well.

I'll be watching this for more information. :)

Lyle
The only other experience I have with OWB is by using Odyssey on MorphOS and it sets up Fonts just once when you first install it, and maybe again if you update it, but then it starts right up after that with no scanning of Fonts:, or downloading and installing of any fonts to the Fonts: assign.

I wonder if I am the only person that has this happening every time from the group of First Contact X1000 owners? I would think that someone else would have mentioned it if it was happening to them too, unless they thought it was a normal behavior for OWB to do that every time it starts. Maybe it is a normal behavior for this version on OS4.x, who knows?

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 10:14 am
by ChrisH
AmigaDave wrote:Every time I start OWB-MUI, it goes through a font initialization
This is a known bug with the MUI-OWB port, caused by it failing to correctly regenerate a bad font cache. As I recall, the solution is (with OWB not running) to delete the "Conf/font" folder. It will then regenerate the font cache once more, but hopefully no more after that.

If you still get problems then you may have a fonts problem that needs fixing before the above work-around will work.

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 1:36 pm
by ddni
My X1000 started doing this after I changed the screen settings to make mui owb open on its own screen. I will try the fix that Chris describes.

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 4:15 pm
by BillEaves
Try deleting the files in "muiowb/Conf/font/" I think that is what I had to do when first installing MUI-OWB and it kept reloading the cache.

If so it will then load the fonts just the once.

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 5:50 pm
by ddni
I confirm that deleting the contents of muiowb/conf/font/ fixed the issue.

Thanks for the help :)

Re: OWB-MUI on X1000

Posted: Fri Sep 14, 2012 6:44 pm
by LyleHaze
It seems I _AM_ using the MUI version..

Deleting that folder has got me all fixed up. Thank You!

Lyle

Re: OWB-MUI on X1000

Posted: Sun Sep 16, 2012 12:31 am
by sundown
You guys missed the real problem...

Conf/font/fonts.conf, open it in NotePad & look at the end of line #26

<!-- Font directory list -->

<dir>fonts:_TrueType</dir <------ missing close mark

<dir>fonts:_TrueType</dir> <-----corrected

The ">" marker is missing, so add it & save, this is stopping mui-owb from creating the font cache.
After the change, it will load the fonts the first time, but not after.

Ken

Re: OWB-MUI on X1000

Posted: Sun Sep 16, 2012 12:45 am
by AmigaDave
LyleHaze wrote:It seems I _AM_ using the MUI version..

Deleting that folder has got me all fixed up. Thank You!

Lyle
I knew there had to be a solution (or at least I hoped there would be).

Worked for me as well. Thanks guys for the answers.