Very, very, very very very slow star of Timberwolf (SOLVED)

Hello.

After 2 hours of install (yes 2) every star of Timberwolf takes about 20 minutes, I can't undestand why.

I have so many fonts, ( usually for desktop publishing with Page Stream ), and the mayor time used in the install was making the cache of fonts.

But with this star time I don't like this program.

Anyone know what's the problem.

Thanks

Edit : I have le 4.1 update 2 installed and other programs runs well.

@RIBDEVIL

I needed only 10-15 min .Than was it finished

@tommysammy

10 min install here and 10-12 sec. startup now.
Maybe Rogue knows what the problem is?

@RIBDEVIL

My guess is you need to rebuild your font caches.

Do an "fc-cache --force --system-only" in a shell (and go for a cuppa while it works). Afterwards, an "fc-list" should be quick, and so should Timberwolf's start - at least after the first time.

Best regards,

Niels

@RIBDEVIL

has fc-cache been run correctly? without error?
do you have a multi-font assign?
i found this a) making problems with fc-cache and b) thus resulting in timerwolf to start slowly.

*if* you have multi-assigned fonts: try the following:
- in the shell just type
assign fonts: sys:fonts
- then
c:fc-cache -s -f -v
and see what fc-cache is doing.

if it is ending correctly without an error start timberwolf and see if this has helped.

-> i hope the os4 devs know about the problem of fc-cache with multi-assigned fonts:? anyone here?

regards...

Could you tell which filesystem you're using, too?
If it's FFS without long filename support, fontconfig might fail to create the cache file, since it exceeds 31 (or so, i don't remember FFS old limit there) characters. If that's the case, it would recreate the cache each time, which would be extremely painful, of course.

@Fab

Well I think the problem is the file system, It?s FFS, I'm rebuilding the cache, and try again, but after this reinstall the boot partition.

Thanks

@Fab

Quote:30, but AmigaOS 4.x can't be used on a short name FFS SYS: partition anyway, which is of course mentioned in the documentation. For example "DejaVu Sans Mono Bold Oblique.font" is longer as well, and there are several other filenames in AmigaOS 4.x which are longer than 30 chars.

Additionally libfreetype2 is unusable slow on FFS partitions, for example with the old SDL builds of OWB from Andrea which didn't have an AmigaOS font implementation yet but used libfreetype2 as well. If the SYS: partition (or whereever FONTS: is if he changed the default setup) is a short name FFS partition, which can't be used for AmigaOS 4.x and has to be reformatted anyway, he should reformat it using SFS/00 instead of DOS/07.

@ALL

Thanks to all, The problem has solved.

It's the file system.

Make a backup and change the filesystem to SFS/00

restore the backup and all is O.K.

Thanks again to all for your help.

The few times I have tried TimberWolf, it usually started very slowly, like I had just installed it. I think it may have something to do with it crashing on exit?

Although I do have a mad multi-assign Fonts.

EDIT: Just tried it again, and it now seems to be starting fast (and not crashing on exit) - for no obvious reason!

@ChrisH

Quote:

have you tried it without that? just like i described above?

thanks and
regards...

@ChrisH

The crash on exit might prevent the config file from being written. When the config file is missing, it always scans the installed plugins and components. Once a config file is written, it only checks those with a newer date than what it has stored.

Therefore, it might be that on your system, it is always scanning on every startup.

Can you send me a crash log of this exit crash ? Preferably to my email address (thomas@friedenhq.org). I'll check if there's something I can do...

@tfrieden

I have the opposite problem, here often it crash at startup, but sometimes it crash during browsing web, then it can't close, Exorcist will be the unique solution ...

Yes, it did it. Reformatted SYS under SFS and TW starts at a decent speed. Now for me the main problems are :

1) it's almost impossible to configure (the prefs windows are unusable
2) It eats lots of processor time, and by the warm season we are experiencing right now, the CPU temperature rockets too high!