custom shell problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I am using a custom shell with my own application that needs some driver to
be initialized by windows when loggin on. But since the custom shell is
opening when windows in logging on, some drivers are not still avalaible for
my application. I have tried to use Explorer shell and add a Runonce Request
to open my application at logging on and it is working. Since all drivers all
loaded when the runonce happens.

Is there a way to delay the custom shell to open when windows is logging on?
Or any other idea would be aprreciated.

thanks for your help...
 
Have you changed the load time on the required driver? This can be done in
the registry via
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\whatever\Start.
 
The problem is that the driver needed has two option for the registry :
2 start at log on
3 does not start at log on

It is a driver from a third party and not windows itself.
When I use 2 as value for this registry, the driver is not loaded fast enough.
 
The following, provided by Slobodan, in a past post, will allow the shell to
wait until the OS is ready.
My shell actually does this, before it loads the custom application.


Use following in loop for 50-100 times
{
CMP_WaitNoPendingInstallEvents(INFINITE);
Sleep(10);
}
 
Back
Top