Partial Solution to display settings and more questions

Hello everyone,

Like many of you, I have been struck down with XPe not being able to set the
screen resolution correctly. I have some solutions, most of which have come
from other people on this newsgroup, I just thought I'd bring them all
together.

Many people would have seen this in their FBA log:

[FBAChangeDisplaySettings] Settings not found!

The reason this happens is because XPe tries to set the display before the
graphics card has been fully setup by PNP.
Solution: In TD you need to be in expert mode (Tools->Options->Mode). Go
to the recourses tab of you video card, in there you will see a "FBA DLL/COM
Registration" item. Double-click it. In the extended properties section
there is a "Phase" value (probably set to 6501 or something). This phase is
too early, change it to 8501.

If you have an ATI card, while on the recourses screen you will notice an
item "AtiHotKey Puller". Right mouse on this and set it to disabled.
Apparently this interferes with XPe's initialisation stuff.

Naturally, you have to make sure you have all the PNP components included.

The final thing is to make sure you DON'T include the following component:
Microsoft_San_Serif. I don't know why this affects things (although the
fact it is from MS is an indicator) but under no circumstances should you
include this component. Don't worry about dependencies asking for it, just
ignore them.

The only problem I have left is the dreaded 96 DPI problem that causes my
application to be displayed incorrectly. To try and describe it, it seems
as if the app is being stretched. It goes way off the screen, even when I
up the res to 1600x1200. From what I can gather, the problem seems to be
related to the DPI setting in the advanced section of the display
properties. No matter what I include, or what I do, the only setting
available is "Custom setting...". If I click on custom setting and try and
change the scale, I get a popup telling me I don't have the correct
privileges (even though I am administrator) to do that operation. MS seem
to know about this problem, but don't seem to be doing anything about it. I
can't work out why it doesn't just have the usual "Small/Large/Other"
settings like XP pro.

Well, that's it. I hope this helps stop some of you going through the
extreme pain I had to to find all this out. I don't want to bash MS, but I
really think XPe needs some work. I saw in another post someone asked about
two errors in the FBA log and the MS response was "If it doesn't seem to
have an effect, don't worry about it". What the hell kind of response is
that ?

Incidentally, I'd be interested to see what Andy Allred from MS has to say
about all this.

If anyone out there knows a solution to the DPI problem (and why it happens)
please, please, PLEASE post it here.

Kind regards,
Brad

Thanks for the info, but two comments/questions:
1) I set the screen settings manually after FBA & haven't noticed a problem.
2) What does including the font Microsoft_San_Serif cause? Is it related to
screen settings (ie. if my screen settings are okay, can I ignore your
advice?).

Rob

"Yabbie" <god@heaven.com> wrote in message
news:evYwZGnnDHA.2232@TK2MSFTNGP09.phx.gbl...

> Hello everyone,
>
> Like many of you, I have been struck down with XPe not being able to set

the

> screen resolution correctly. I have some solutions, most of which have

come

> from other people on this newsgroup, I just thought I'd bring them all
> together.
>
> Many people would have seen this in their FBA log:
>
> [FBAChangeDisplaySettings] Settings not found!
>
> The reason this happens is because XPe tries to set the display before the
> graphics card has been fully setup by PNP.
> Solution: In TD you need to be in expert mode (Tools->Options->Mode). Go
> to the recourses tab of you video card, in there you will see a "FBA

DLL/COM

> Registration" item. Double-click it. In the extended properties section
> there is a "Phase" value (probably set to 6501 or something). This phase

is

> too early, change it to 8501.
>
> If you have an ATI card, while on the recourses screen you will notice an
> item "AtiHotKey Puller". Right mouse on this and set it to disabled.
> Apparently this interferes with XPe's initialisation stuff.
>
> Naturally, you have to make sure you have all the PNP components included.
>
> The final thing is to make sure you DON'T include the following component:
> Microsoft_San_Serif. I don't know why this affects things (although the
> fact it is from MS is an indicator) but under no circumstances should you
> include this component. Don't worry about dependencies asking for it,

just

> ignore them.
>
> The only problem I have left is the dreaded 96 DPI problem that causes my
> application to be displayed incorrectly. To try and describe it, it seems
> as if the app is being stretched. It goes way off the screen, even when I
> up the res to 1600x1200. From what I can gather, the problem seems to be
> related to the DPI setting in the advanced section of the display
> properties. No matter what I include, or what I do, the only setting
> available is "Custom setting...". If I click on custom setting and try

and

> change the scale, I get a popup telling me I don't have the correct
> privileges (even though I am administrator) to do that operation. MS seem
> to know about this problem, but don't seem to be doing anything about it.

I

> can't work out why it doesn't just have the usual "Small/Large/Other"
> settings like XP pro.
>
> Well, that's it. I hope this helps stop some of you going through the
> extreme pain I had to to find all this out. I don't want to bash MS, but

I

> really think XPe needs some work. I saw in another post someone asked

about

> two errors in the FBA log and the MS response was "If it doesn't seem to
> have an effect, don't worry about it". What the hell kind of response is
> that ?
>
> Incidentally, I'd be interested to see what Andy Allred from MS has to say
> about all this.
>
> If anyone out there knows a solution to the DPI problem (and why it

happens)

> please, please, PLEASE post it here.
>
> Kind regards,
> Brad
>
>

OK.
1) If you want to set the screen manually, that is fine, but don't you want
to set it by default ?

2) Typical MS bug. ;-) Don't really know why, that's just the way it
is.

"Rob Neff" <robn@paltronics.com> wrote in message
news:%23ryQCbnnDHA.644@TK2MSFTNGP11.phx.gbl...

> Thanks for the info, but two comments/questions:
> 1) I set the screen settings manually after FBA & haven't noticed a

problem.

> 2) What does including the font Microsoft_San_Serif cause? Is it related

to

> screen settings (ie. if my screen settings are okay, can I ignore your
> advice?).
>
> Rob
>
> "Yabbie" <god@heaven.com> wrote in message
> news:evYwZGnnDHA.2232@TK2MSFTNGP09.phx.gbl...

> the

> come

the

Go

> DLL/COM

section

phase

> is

an

included.

component:

you

> just

my

seems

I

be

> and

seem

it.

> I

but

> I

> about

is

say

> happens)

>
>

FBA configures the video settings right before it reboots the machine, the
phase is late enough. Check out the tip article submitted on this subject.
http://www.microsoft.com/windows/emb...xp/default.asp

The ATI Hotkey Poller service is in the RelNotes supplied with the XPe
product.

Your concern about "not worry about that error" is *possibly* being
misinterpreted. You may be thinking of a couple of benign error codes in the
FBA log that translate to a DLL or service reporting during FBA something
equivalent to this:

"hey setup, you're trying to configure me and i've already been configured,
you're wasting your time here".

The Documentation team is working on doc updates that will interpret the FBA
errors customers have reported to the newsgroup in the past, it's something
we've needed for quite a while.

I'll file a work item bug to look into the Sans Serif issue you raise.

Thanks for the feedback. You seem to know what you're talking about so
perhaps you can help the rest of the community by writing up some Tip
articles on any subject and get your name in lights on our web page? Please
submit your tips here:
http://www.microsoft.com/windows/emb...ips/submit.asp

If you want a second pair of eyes to review the tip before submittal, feel
free to mail me offline, you'll need to remove "online" from my address.

Thanks again!
Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ========


"Yabbie" <god@heaven.com> wrote in message
news:eoE$JqnnDHA.2272@tk2msftngp13.phx.gbl...

> OK.
> 1) If you want to set the screen manually, that is fine, but don't you

want

> to set it by default ?
>
> 2) Typical MS bug. ;-) Don't really know why, that's just the way

it

> is.
>
> "Rob Neff" <robn@paltronics.com> wrote in message
> news:%23ryQCbnnDHA.644@TK2MSFTNGP11.phx.gbl...

> problem.

related

> to

set

have

> the

> Go

> section

> phase

> an

> included.

> component:

the

> you

> my

> seems

when

> I

> be

try

> seem

> it.

> but

to

> is

> say

>
>

Hello Andy,

Firstly, I don't know that much about XPe, just what I've learnt through
suffering and what others have said on this newsgroup.

Interesting what you say about the phase setting the video, if I don't
change the phase to 8501 it won't work.

What you say about "not to worry about that error" is correct, it was to do
with DLL's.

Thanks for filing the bug report about the MS font issue, please post your
results here.

I notice you didn't comment on the DPI issue. Anything to add there ? (as
that is the one thing really holding me back now).

"Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
news:%23cg%23b$nnDHA.2776@tk2msftngp13.phx.gbl...

> FBA configures the video settings right before it reboots the machine, the
> phase is late enough. Check out the tip article submitted on this subject.
> http://www.microsoft.com/windows/emb...xp/default.asp
>
> The ATI Hotkey Poller service is in the RelNotes supplied with the XPe
> product.
>
> Your concern about "not worry about that error" is *possibly* being
> misinterpreted. You may be thinking of a couple of benign error codes in

the

> FBA log that translate to a DLL or service reporting during FBA something
> equivalent to this:
>
> "hey setup, you're trying to configure me and i've already been

configured,

> you're wasting your time here".
>
> The Documentation team is working on doc updates that will interpret the

FBA

> errors customers have reported to the newsgroup in the past, it's

something

> we've needed for quite a while.
>
> I'll file a work item bug to look into the Sans Serif issue you raise.
>
> Thanks for the feedback. You seem to know what you're talking about so
> perhaps you can help the rest of the community by writing up some Tip
> articles on any subject and get your name in lights on our web page?

Please

> submit your tips here:
> http://www.microsoft.com/windows/emb...ips/submit.asp
>
> If you want a second pair of eyes to review the tip before submittal, feel
> free to mail me offline, you'll need to remove "online" from my address.
>
> Thanks again!
> Andy
> --
>
> This posting is provided "AS IS" with no warranties, and confers no

rights.

> ================================================== ========
>
>
> "Yabbie" <god@heaven.com> wrote in message
> news:eoE$JqnnDHA.2272@tk2msftngp13.phx.gbl...

> want

> it

> related

> set

> have

all

before

(Tools->Options->Mode).

notice

disabled.

> the

should

it,

causes

> when

to

setting

> try

MS

about

"Small/Large/Other"

the

MS,

asked

seem

> to

response

to

>
>

Hi,

I have seen error with larger dialogs in my first few build, long time ago.
It was problem that I solved very easily while solving other problems, so
there is no chance to remember what I have done.

I have minlogon and winlogon builds that are working correctly, so I'll give
you my setup for minlogon:

Font: Marlett
Fonts: Central Europe font substitute
Fonts: EGA
Fonts: Fonts Arial
Fonts: Fonts Arial bold
Fonts: Fonts Arial Bold Italic
Fonts: Fonts Arial Italic
Fonts: Fonts ariel black
Fonts: Fonts Courier
Fonts: Fonts Courier bold
Fonts: Fonts Microsoft_San_Serif <---- Do you have this font I think that
it is needed
Fonts: Fonts Tahoma
Fonts: Fonts tahoma_bold
Fonts: Fonts webdings
Fonts: Fonts wingdings
Fonts: Western Europe font substitute
Fonts:vgaoem_fon

This is everything in my build that starts with fo:
I was surprised not to see FontsPI-96 in this list.

Win32 API - User - Hotfix Q328310 <----- This is last component
that have some relevance to any appearances in my build.

I don't have video driver component, not what anyone except me would call
display component anyway.
I have modified inf file so I have only three files that support all NVIDIA
chipset based video cards. This mean that I don't use FBA for installation
of driver, but I rely on PNP to do the job.
Since we are using two monitors FBA support for setting resolution was
anyway useless for us, we made support in our setup for changing resolution.

Also I tried ATI Radeon 9600 and it worked but I had other problems non
related to XPE so I gave up on supporting ATI, for now.



Let me know if you find it useful.

Regards,
Slobodan


"Yabbie" <god@heaven.com> wrote in message
news:OnOLSOonDHA.2232@TK2MSFTNGP09.phx.gbl...

> Hello Andy,
>
> Firstly, I don't know that much about XPe, just what I've learnt through
> suffering and what others have said on this newsgroup.
>
> Interesting what you say about the phase setting the video, if I don't
> change the phase to 8501 it won't work.
>
> What you say about "not to worry about that error" is correct, it was to

do

> with DLL's.
>
> Thanks for filing the bug report about the MS font issue, please post your
> results here.
>
> I notice you didn't comment on the DPI issue. Anything to add there ? (as
> that is the one thing really holding me back now).
>
> "Andy Allred [MS]" <andyall@online.microsoft.com> wrote in message
> news:%23cg%23b$nnDHA.2776@tk2msftngp13.phx.gbl...

the

subject.

> the

something

> configured,

> FBA

> something

> Please

feel

> rights.

you

way

your

to

> all

> before

> (Tools->Options->Mode).

"FBA

This

> notice

> disabled.

(although

> should

> it,

> causes

it

even

seems

> to

> setting

and