override files in winecfg: Why makes it sense to set files to builtin?

Questions about Wine on Linux
Post Reply
Opako
Level 2
Level 2
Posts: 13
Joined: Mon Jun 08, 2020 9:23 am

override files in winecfg: Why makes it sense to set files to builtin?

Post by Opako » Sun Jun 21, 2020 3:55 am

This is my winecfg "override configuration" after installing a program in wine:
winecfg from prefix.png
What I do not understand:
1) There are entries that are set to "builtin". For example "ctfmon.exe". I thought, that using the builtin version is anyhow the default. So why is it set to builtin?

2) *docbox.api is "ausgeschaltet" -> meaning "turned off".
What can be the reason for "turning off" any file?

Would appreciate some clarification. Thank you.

spoon0042
Level 5
Level 5
Posts: 304
Joined: Thu Dec 24, 2009 11:00 am

Re: override files in winecfg: Why makes it sense to set files to builtin?

Post by spoon0042 » Mon Jun 22, 2020 3:50 pm

1. I'm not 100% on this but 'builtin' meaning 'builtin only, never native' may have some use. Or it may just be down to having a consistent interface.

2. 'disabled' in english, I believe. Which prevents the dll or exe from ever loading which is useful in certain circumstances. Possibly to prevent running some optional component that has issues, or prevent some program from using a certain api that causes issues, whether bugs or undesired behavior. etc.

Post Reply