Re: depend and launch in init registry
From: bsqr_TSAT (TSatagaj)
Date: 10/28/04
- Next message: Richie: "RE: BSP migration from 4.2 to 5.0"
- Previous message: Nguyen Nguyen: "remove eboot out of nk.exe"
- In reply to: Kursad: "depend and launch in init registry"
- Next in thread: Paul G. Tobey [eMVP]: "Re: depend and launch in init registry"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 28 Oct 2004 09:39:28 -0700
As a follow on to solving your specific problem, you can create and set a
named event in your video driver.
You can create/open the same named event in your application, but make your
application WaitForSingleObject() until your video driver sets the event.
BSQR_TSAT
"Kursad" <Kursad@discussions.microsoft.com> wrote in message
news:47E7B5C2-EE30-408F-AA18-79CD276BF5E6@microsoft.com...
> Hi,
> Can anyone explain the semantics of "dependXX" and "launchXX" in the
> registry key HKEY_LOCAL_MACHINE/init? Specifically:
> 1. LaunchXX tells the order to launch these applications, is that correct?
> 2. DependXX says "If the dependent application doesn't exist, don't launch
> this one either". Is that correct?
>
> Basically, the problem I'm trying to solve is this: The video driver has a
> problem with resetting. As a workaround, I need to launch an application
> during startup that will reset the video. However, this application has to
> run after the video driver finishes its initialization. The windows screen
> comes up after the initialization is complete, so I made my video reset
> application to run after (and it is dependent on) explorer.exe. Is there a
> better way to do this? Is there a way to find out if the video driver has
> completed its initialization?
> Thanks a lot!
- Next message: Richie: "RE: BSP migration from 4.2 to 5.0"
- Previous message: Nguyen Nguyen: "remove eboot out of nk.exe"
- In reply to: Kursad: "depend and launch in init registry"
- Next in thread: Paul G. Tobey [eMVP]: "Re: depend and launch in init registry"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
