Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Is There Support for a PATH Equivalent, Allowing Fonts, Drivers, DLLs, etc., to be Placed Elsewhere in FILESYSTEM Besides WINDOWS?

April 26, 2017DLLs Drivers equivalent filesystem path Placed support

0

Posted

Is There Support for a PATH Equivalent, Allowing Fonts, Drivers, DLLs, etc., to be Placed Elsewhere in FILESYSTEM Besides WINDOWS?

1 Answer

0

Posted

• Fonts can be placed anywhere. By default, Windows CE will only load fonts from the \Windows directory. But, an application or an embedded shell can call AddFontResource to load a font and make it available system wide. • A DLL can exist anywhere as long as you observe the rules for LoadLibrary() as documented in the SDK. Note that in version 2.1, a new rule was added for looking in the application directory. • All system components including drivers should be placed in the “\Windows” directory. But, since a driver is a DLL, you could potentially place it outside the “\Windows” directory (see #2 above). However, we do not encourage this practice.