Custom Startup Screen

  • Thread starter Thread starter Philipp Stampfl
  • Start date Start date
P

Philipp Stampfl

Hi All!

I know that there are options to disable MS startup screens and other popups
(thanks to Peter Boden) but my embedded device needs some time to startup
and I would like to somehow show the user that the system is not hanging but
warming-up. This would be nice using some kind of custom graphics or popup
(better would be graphics).

Does anybody know something like that?

Thanks for any help!

Philipp
 
There is no legal way to do this since you must modify ntoskrnl.exe
There were discussions in this NG about this many times already.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Thanks for the info!

This wouldn't be a problem if the system would boot faster. Is there any
possibility to find out why it starts up that slow. I am currently using an
embedded single board computer from aaeon with 667mhz, 256mb ram and XPE on
a 256mb CF-Card.

Thanks!

Philipp
 
Just a couple of extra makeweights...

1) http://www.soft32.com/download-BootVis-19687-5.html
Interesting.. Why MS removed the tool from MS website?! Don't see any
obvious reason.

2) You may also use /SOS switch in boot.ini to see what drivers get loaded
and what slows down the boot. Also, sometimes /BOOTLOG switch is also
helpful.

--
KM,
BSquare Corporation
1)
I know that Microsoft used to offer a boot profiling tool for XP called
Click to expand...
bootvis.exe, but this tool is no longer available for download from
Microsoft's site -- perhaps you can find a copy from an alternate source.
2)
You can modify the boot.ini on your target to send out debug messages via
Click to expand...
serial -- add the following flags to your XPe boot option:
/debugport=COM1 /baudrate=115200

Set up a host PC with the Microsoft Windows Debugger* (windbg.exe) and
Click to expand...
connect the host PC to your target device via NULL modem cable. Configure
the debugger for verbose mode, and boot up your target. Messages displayed
in the debugger command window during target startup may provide some hints
as to what is causing the lengthy boot times.
*NOTE: windbg.exe can be downloaded as part of the Debugging Tools For
Click to expand...
Windows kit from http://www.microsoft.com/whdc/ddk/debugging/default.mspx
3)
By default, if your XPe device has a NIC installed and networking has been
Click to expand...
added to the target image, DHCP will be enabled. If your device is not
connected to a DHCP server, then your target device may be stalling at boot
due to a DHCP timeout. Either connect your target to a DHCP server or
assign your target a static IP address to resolve this problem.
 
Hi ,

The serial port debugging and the addition of switch option is of
good help .But personally the Bootvis provides good report on the
booting performance.As KM , it also surprises me why the Bootvis has
been removed from the MS Website.

I guess someone from MS could look into it.*It's really a helpful
utility i think*

Thanks
Kesavan
 
Thanks to all!

I have tried bootvis.exe but it doesn't start, it is not able to find some
function entry point in advapi32.dll.
I also tried the boot.ini options /SOS and /bootlog and I could see, that
XPE halts about 60 to 90 seconds at CLASSPNP.SYS. I use the very same
machine just booted from HD for development and the there installed XP-Pro
(starting with the same boot.ini options) also halts for 60 to 90 seconds
after loading all drivers on an black screen (/noguiboot) with an blinking
cursor on the top left side.

Has anyone ever seen something like this?
I know that the system used to startup quicker in the past using the HD
version of XP-Pro, but no changes where made since then. Also my first XPE
images used to startup faster.

Thanks for your tips!

Philipp
 
Hi all!

I found out that the problems somehow comes from the CF-Card used. Using a
AVL CF card with 256MB XPE hands on startup and also XP-pro hangs if the
cf-card is connected to the system during the startup.
Using another manufactured card, this delay disapeared!!

Philipp
 
Stefan,

It's not that there is no way to do it, rather that it's not legal to do it.
Modifying the NT Kernel is against you OEM agreement. HTH,

--
Brad Combs
Imago Technologies, LLC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top