|
From: Eric K. <ek...@rz...> - 2002-06-14 09:41:11
|
"Jason Filby" <jas...@ya...> wrote: > >Sorry, that was a typo. I meant vgamp.sys. Vidport.sys should > >handle the create requests and retrieve the process id or handle > from > >csrss and do the initialization for int10 calls. > > But doesn't it already do this? It does, but now vidport.sys is loaded when vgamp.sys is loaded. Both are system-start drivers. Csrss does not run at that time, so opening the csrss process by its id will fail! :-/ > >Btw, I guess it is useful to rename vidport.sys to videoprt.sys > >since other video drivers will rely on the name of the port driver. > > I thought other drivers would look for the device name in the object > manager? Vidport.sys does not appear in the object managers name space. It is now automatcially loaded by ntoskrnl when vgamp.sys is relocated and no loaded 'vidport.sys' module/driver can be found. This is very much like the automatic loading of dlls. Btw, the same will apply to scsiport.sys and class2.sys, or better 'all port drivers'. Eric |