Startup progress bar

[Guest]

I have a system that seems to running ok. It runs from a flash card. So I
copied the contents of that card to a file on my HD, formatted and
bootprepped a new flash card, and recopied the files onto it. (I realize this
would cause trouble if I was on a network - identical SIDs). It comes up and
runs, except...

The original system shows a progress bar at the bottom of the screen just
after the BIOS power on, then goes on to a blue screen Welcome, etc etc. The
copy comes up to a blank screen (after BIOS display) for about 15 seconds,
then goes on to the blue screen, etc.

Any idea why the progress bar isn't showing up on the second system? Is
there a setting somewhere that controls that?

Thanks,
SteveS

 

[KM]

SteveS,

On your "copied" image double check the boot.ini content.
For the active ARC path there, do you see /NOGUIBOOT switch.

 

[Guest]

It was there. If I remove it I get the Windows 'Splash' Screen, but not the
progress bar. At least the splash screen is better than a blank screen.

The unit that shows the progress bar has it on for several seconds. This is
a large text-mode looking bar, black and white. Then the splash screen comes
up.

Don't know why the other units don't show the bar, but searching thru here
via Google (which I now realize is much better than via microsoft NET
search), it seems the bar may not show up on fast systems.

- SteveS

 

[KM]

SteveS,

It was there. If I remove it I get the Windows 'Splash' Screen, but not the
progress bar. At least the splash screen is better than a blank screen.
Wierd.

The unit that shows the progress bar has it on for several seconds. This is
a large text-mode looking bar, black and white. Then the splash screen comes up.

This doesn't sound good to me. What progress bar you are referring to? It must be a new fancy one you can see on XP Pro.
What type of boot you have set up on the target? Is it a RAM boot by any chance?

Don't know why the other units don't show the bar, but searching thru here
via Google (which I now realize is much better than via microsoft NET

Much better.
If I want to search even msdn, I still go to Google.

search), it seems the bar may not show up on fast systems.

 

[Guest]

This doesn't sound good to me. What progress bar you are referring to? It must be a new fancy one you can see on XP Pro.

It's a real basic progress bar that comes up right after the BIOS stuff is
done. The bar is big - like the old text graphics (oops, dating myself).
It's in black and white, takes up the whole width of the screen, and is near
the bottom - no text or message.

What type of boot you have set up on the target? Is it a RAM boot by any chance?

I boot from flash and use the EWF RAM reg. I use Winlogon now, but I
probably should be using Minilogon.

It's strange, I building a short run of units and they are all supposed to
be identical. I seem to see some differences between them, though I have
copied the same image to all. The one with the progress bar is an early unit
and perhaps there are some differences in the BIOS or hardware.

- SteveS

 

[KM]

SteveS,

It's a real basic progress bar that comes up right after the BIOS stuff is
done. The bar is big - like the old text graphics (oops, dating myself).
It's in black and white, takes up the whole width of the screen, and is near
the bottom - no text or message.

I can imagine such progress bar only if you use:
- RAM/SDI (or remote) boot
- Resume from hibernated image
- a custom loader

I boot from flash and use the EWF RAM reg. I use Winlogon now, but I
probably should be using Minilogon.

Actually I was asking a bit different thing. Could you post the exact content of your boot.ini file here?

Also, do you use the SP2 HORM feature?

It's strange, I building a short run of units and they are all supposed to
be identical. I seem to see some differences between them, though I have
copied the same image to all. The one with the progress bar is an early unit
and perhaps there are some differences in the BIOS or hardware.

Is that only differences in boot process or something else as well?

 

[Richard]

My Original image comes up with a Black Screen and a Black and white
Progress bar on the bottom line. My Copied images (Cloned) do not have it
either.

Richard

 

[Guest]

Actually I was asking a bit different thing. Could you post the exact content of your boot.ini file here?

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect

it originally had /noguiboot switch as well, but I removed that

Also, do you use the SP2 HORM feature?

I don't know what that is! , so I don't know.

Is that only differences in boot process or something else as well?

Here's one. A couple units came up fine , ran my app, and then a minute or
so later, the new HW wizard comes up and says it needs to install a
multimedia controller. I go thru it but it can't find files, then it says
it's installed and asks to reboot. I say no and do a EWF commit or else it
keeps coming up every time. Once I commit it it seems happy. Other units
don't do this. Same image (I think - I'm trying to meet deadlines and I may
have missed something).

- SteveS

 

[Guest]

My Original image comes up with a Black Screen and a Black and white
Progress bar on the bottom line. My Copied images (Cloned) do not have it
either.

Richard

Interesting, as the one unit of mine that has the bar is the first one I
built up and did the FBA on.

- Steve

 

[KM]

SteveS,

The boot.ini looks fine. I was basically wondering if you were using any other "special" switches of boot.ini besides the noguiboot.
You did not.

Interesting.. You are saying you see the text mode progress bar instead of regular XP/XPe graphic logo progress screen?

Can you provide us a bit more info about your device:
- Is the CF card marked as fixed or is it removable? What interface to the card - IDE, built-in controller, etc.?
- Have you ever tested the device under DOS? Were you able to switch to VGA 640x480 mode there without any problems?
- Do you have files boot.bmp and dots.bmp under \windows directory (or under root, or under \windows\system32)?
- When the progress bar switches to the text one (B&W): on first boot to pre-FBA image, on some next boot, after cloning?
- How XP Pro works on the same device with the same CF card installed?
- Are all the devices the same in hardware and BIOS settings? If not, what are the differences?

KM

Actually I was asking a bit different thing. Could you post the exact content of your boot.ini file here?

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded"
/fastdetect

it originally had /noguiboot switch as well, but I removed that

Also, do you use the SP2 HORM feature?

I don't know what that is! , so I don't know.

Is that only differences in boot process or something else as well?

Here's one. A couple units came up fine , ran my app, and then a minute or
so later, the new HW wizard comes up and says it needs to install a
multimedia controller. I go thru it but it can't find files, then it says
it's installed and asks to reboot. I say no and do a EWF commit or else it
keeps coming up every time. Once I commit it it seems happy. Other units
don't do this. Same image (I think - I'm trying to meet deadlines and I may
have missed something).

- SteveS

 

[Slobodan Brcin \(eMVP\)]

Konstantin,

I just read this thread :-(

The boot.ini looks fine. I was basically wondering if you were using any
other "special" switches of boot.ini besides the noguiboot. You did not.

Interesting.. You are saying you see the text mode progress bar instead of
regular XP/XPe graphic logo progress screen?

Is it possible that you never saw this?
This text mode B&W progress is shown by ntldr in the bottom of the screen
while it load files from extremenly slow mediums.
After that kernel take ower and show 'fancy" screen with "moving" progress
bar.

Regards,
Slobodan

Can you provide us a bit more info about your device:
- Is the CF card marked as fixed or is it removable? What interface to
the card - IDE, built-in controller, etc.?
- Have you ever tested the device under DOS? Were you able to switch to
VGA 640x480 mode there without any problems?
- Do you have files boot.bmp and dots.bmp under \windows directory (or
under root, or under \windows\system32)?
- When the progress bar switches to the text one (B&W): on first boot to
pre-FBA image, on some next boot, after cloning?
- How XP Pro works on the same device with the same CF card installed?
- Are all the devices the same in hardware and BIOS settings? If not,
what are the differences?

KM

Actually I was asking a bit different thing. Could you post the exact
content of your boot.ini file here?

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

it originally had /noguiboot switch as well, but I removed that

Also, do you use the SP2 HORM feature?

I don't know what that is! , so I don't know.

Is that only differences in boot process or something else as well?

Here's one. A couple units came up fine , ran my app, and then a minute
or
so later, the new HW wizard comes up and says it needs to install a
multimedia controller. I go thru it but it can't find files, then it says
it's installed and asks to reboot. I say no and do a EWF commit or else
it
keeps coming up every time. Once I commit it it seems happy. Other units
don't do this. Same image (I think - I'm trying to meet deadlines and I
may
have missed something).

- SteveS

 

[Slobodan Brcin \(eMVP\)]

Steve,

What kernel/HAL do you use on all these units?
Are they same or they are Standard PC, ACPI, etc?

Regards,
Slobodan

 

[Guest]

Konstantin,

I just read this thread :-(


Is it possible that you never saw this?
This text mode B&W progress is shown by ntldr in the bottom of the screen
while it load files from extremenly slow mediums.
After that kernel take ower and show 'fancy" screen with "moving" progress
bar.

- That's what mine does exactly. It's odd I only see it on one unit. I
tested 4 or 5 and only this one comes up with the bar. These are all PII
PC104 systems - suuposedly all the same. Some parts were bought at different
times, so maybe there is a timing difference in the flash drives or
something. In any case, the big problem I had was the blank screen for 20-30
seconds on power up because I had /noguiboot. The one that had the progress
bar at least showed it was doing something. I'll just put up with the Windows
splash screen - it's no big deal since I'd rather have the user know it's
working.

For completeness sake , I've tried to answer KM's questions below.

Thanks for all the input.

- SteveS

Regards,
Slobodan

It's from Kontron and called a ChipDisk. It's basically CF chips built on a
PCB that plugs directly into the 44pin IDE connector on the CPU board. This
is the device I had problems trying to set to 'fixed', until you all led me
to the EWF RAm reg mode, which seems to work great. (thanks again for that!)


I've booted to DOS (to format and bootprep) with no problems. Didn't try
640x480 mode.

No I don't have them at all.


I don't think it happened under FBA. It does happen every boot (on one unit).

- Don't think I saw it under XP Pro. (this would be booting from HD)

- They are all the same as far as I know. I've checked everything I can
think of; but , as I noted above there must be some difference I've missed.



Thanks,
SteveS

 

[Guest]

All the same, standard PC.

- SteveS

Steve,

What kernel/HAL do you use on all these units?
Are they same or they are Standard PC, ACPI, etc?

Regards,
Slobodan

 

[KM]

Slobodan,

Konstantin,

I just read this thread :-(

I figured you were not commenting in this thread becuase you were far from computer

Is it possible that you never saw this?

Yes, it is. Even with pretty slow CF cards I had I always saw the graphic progress bar.
(unless, of course, I used sdiboot or remoed from hibernated image or etc.)

This text mode B&W progress is shown by ntldr in the bottom of the screen
while it load files from extremenly slow mediums.
After that kernel take ower and show 'fancy" screen with "moving" progress bar.

This must be true since the graphic logo progress bar belongs to kernel anyway (and therefore the Logo is eas yto change in the
kernel resources).
Also, just exploring the ntldr it is obvious that there is no graphic progress bar unless boot.bmp file is there (that is what I
mentioned in the previous reply and that got me confused on what Steve was seeing).
Probably I have always missed the ntldr bar on my image. I was probably "lucky" to work with pretty fast targets

Well.. Always live and learn

Regards,
Konstantin

Can you provide us a bit more info about your device:
- Is the CF card marked as fixed or is it removable? What interface to
the card - IDE, built-in controller, etc.?
- Have you ever tested the device under DOS? Were you able to switch to
VGA 640x480 mode there without any problems?
- Do you have files boot.bmp and dots.bmp under \windows directory (or
under root, or under \windows\system32)?
- When the progress bar switches to the text one (B&W): on first boot to
pre-FBA image, on some next boot, after cloning?
- How XP Pro works on the same device with the same CF card installed?
- Are all the devices the same in hardware and BIOS settings? If not,
what are the differences?

KM

:

Actually I was asking a bit different thing. Could you post the exact
content of your boot.ini file here?

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Embedded"
/fastdetect

it originally had /noguiboot switch as well, but I removed that


Also, do you use the SP2 HORM feature?


I don't know what that is! , so I don't know.

Is that only differences in boot process or something else as well?


Here's one. A couple units came up fine , ran my app, and then a minute
or
so later, the new HW wizard comes up and says it needs to install a
multimedia controller. I go thru it but it can't find files, then it says
it's installed and asks to reboot. I say no and do a EWF commit or else
it
keeps coming up every time. Once I commit it it seems happy. Other units
don't do this. Same image (I think - I'm trying to meet deadlines and I
may
have missed something).

- SteveS

 

[KM]

SteveS,

By replying all my questions you basically confirmed what Slobodan said.
Seems like you've got very slow medium boot on that target (1 of 5). Just to understand whether it is the CF or the controller, you
can swap the card between two targets and see if you still get the B&W progress bar on the "slow" device. If you do, some problems
with the controller or MB are there. If not, CF is either damaged or just ready to be disposed.

One thing I couldn't understand those. Are you saying that XP Pro boots just fine (no B&W progress bar there) on the slow target
device?

 

[Guest]

One thing I couldn't understand those. Are you saying that XP Pro boots just fine (no B&W progress bar there) on the slow target
device?

- I don't recall the bar with XP Pro (which boots off a HD). I guess that
points at the CF. Problem now is that unit went out so I can't investigate
further. But I see what to do if it comes up again. I'm willing to write it
off to a slow CF.

I really appreciate the help. I'm more of a '8-bit processor' guy (PICs,
etc) thought I keep getting pulled into the Windows world. I've learned
enough here to see how much I don't know ;-). Hope I can be on the answering
side on this group in the future. Wish there was a group this good when I
did NT Embedded!


- SteveS

 

[Guest]

Well here is an update for anyone still listening:

- Seeing the progress bar after boot does seem to be tied to a single CPU
and/or flash card. I'm guessing CPU. I finally realized that one system took
much longer to fully boot up than other systems. Another strange thing,
everytime it boots, it advances the time by one hour.

So , I guess they all have the progress bar, but as pointed out by others,
most systems are too fast too see it.

- SteveS

 

[Slobodan Brcin \(eMVP\)]

much longer to fully boot up than other systems. Another strange thing,

everytime it boots, it advances the time by one hour.

Do you have RAM EWF?

If daylight change happened you must commit EWF to avoid time being updated
each time you boot :-(

Regards,
Slobodan