FBA

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

Hello

When FBA runs, I get a progress bar, but there is nothing displayed as far
as a status, it is just a blank dialog box with the progress bar. However
sometimes I do get a # sign where you would expect to see a status message.

Am I missing a font in my SLX file?

I've got the components.... Font Protoype, Fonts Application Compatibilty,
Font Object Embedding Library in my image.

Any ideas?
 
Jason said:
Hello

When FBA runs, I get a progress bar, but there is nothing displayed as far
as a status, it is just a blank dialog box with the progress bar. However
sometimes I do get a # sign where you would expect to see a status message.

Am I missing a font in my SLX file?

I've got the components.... Font Protoype, Fonts Application Compatibilty,
Font Object Embedding Library in my image.

Any ideas?
Click to expand...
are there any unresolved dependencies?
 
Hi Jason,

You could try adding the VGA Save component which will bring in
Fonts:vgaoem_fon. This fixed a similar problem for me in the past.

HTH,
Brad
 
This is probably because you've added some mui to the configuration and
the default system font changed. FBA is expecting some other font (i
don't recall off the top of my head, it may be listed in another thread
of the newsgroup a year or three ago). If it's not due to the mui, then
some other language must have stomped on the english default system
font, some languages have their own 'default system font', like Greek
for instance.

Basically, this is not an indication that your runtime is bad or that
you did anything incorrect. We could probably have done a better job
here with the fonts to prevent one from stomping on the other for
critical fonts like this.

-andy
 
Actually I have no MUI in my image.

It's just the way XPe handles Fonts.

I noticed that after it runs and I try to install something, the install
screen is have the size it should, the fonts are not there, and the buttons
"Next", "back" are missing those fonts.
 
This is likely a missing font or codepage component. We have Font
Application Compatibility component and the same for Codepages in the
FP2007 build. You could try one of those to see if it resolves your problem.

Take care,
 
Back
Top