Driver Installation Windows Vista
in [Device Drivers]
|
Prev: ReadFile() fails with error Incorrect Parameter
Next: error C1017: invalid integer constant expression
From: subhash on 21 May 2008 11:35 Hi, We are using DDK 6001.17121 . we tried to install src\kmdf\echo driver in Windows Wista Buisiness Edition. We have only put some "kdprint" to trace DriverEntry. As per the documentaton, We used add hardware wizard to install the driver. I am not getting any prints in DbgView . Driver gets installed but the system asks for a restart. Devcon shows the driver in the listing. I used DbgPrint also. I want to know why I am not getting any prints. I want to know what is the best way to trace wista driver code. Looking forward for your response. Thanks and Regards Subhash
From: Don Burn on 21 May 2008 11:47 In all likelyhood the driver is loaded before you start up DbgView, so you do not see the debug prints since DriverEntry is called then exited before you get there. You need to use WinDBG, either with two systems, or with virtualization (if your driver will work in than environnemt) to create to systems. -- Don Burn (MVP, Windows DDK) Windows 2k/XP/2k3 Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr Remove StopSpam to reply "subhash" <subhashsukumaran(a)gmail.com> wrote in message news:954edfd1-c013-4383-a32e-0695f1a0d9ac(a)s21g2000prm.googlegroups.com... > Hi, > We are using DDK 6001.17121 . we tried to install src\kmdf\echo > driver in Windows Wista Buisiness Edition. We have only put some > "kdprint" to trace DriverEntry. As per the documentaton, We used > add hardware wizard to install the driver. I am not getting any prints > in DbgView . Driver gets installed but the system asks for a restart. > Devcon shows the driver in the listing. I used DbgPrint also. I want > to know why I am not getting any prints. > I want to know what is the best way to trace wista driver code. > > Looking forward for your response. > > Thanks and Regards > Subhash
From: Tanya Radeva [MSFT] on 21 May 2008 17:42 If you've installed echo.sys driver properly it will be loaded upon Windows start. So DriverEntry will be executed at this time and you won't be able to see any messages because your Windows shell is not started yet. To actually stop with the debugger in DriverEntry you need to Break (Ctrl+Break) with WinDbg immediatly after you start the Windows Target machine (hopefully fast enough, so the echo.sys driver is not loaded yet) and then set a deffered breakpoint at the DriverEntry function. When the driver gets loaded by Windows your breakpoint will get bound and the debugger will stop at this breakpoint. Best regads, Tanya "subhash" wrote: > Hi, > We are using DDK 6001.17121 . we tried to install src\kmdf\echo > driver in Windows Wista Buisiness Edition. We have only put some > "kdprint" to trace DriverEntry. As per the documentaton, We used > add hardware wizard to install the driver. I am not getting any prints > in DbgView . Driver gets installed but the system asks for a restart. > Devcon shows the driver in the listing. I used DbgPrint also. I want > to know why I am not getting any prints. > I want to know what is the best way to trace wista driver code. > > Looking forward for your response. > > Thanks and Regards > Subhash >
From: subhash on 22 May 2008 03:47 On May 22, 2:42 am, Tanya Radeva [MSFT] <TanyaRadevaM...(a)discussions.microsoft.com> wrote: > If you've installed echo.sys driver properly it will be loaded upon Windows > start. So DriverEntry will be executed at this time and you won't be able to > see any messages because your Windows shell is not started yet. To actually > stop with the debugger in DriverEntry you need to Break (Ctrl+Break) with > WinDbg immediatly after you start the Windows Target machine (hopefully fast > enough, so the echo.sys driver is not loaded yet) and then set a deffered > breakpoint at the DriverEntry function. When the driver gets loaded by > Windows your breakpoint will get bound and the debugger will stop at this > breakpoint. > > Best regads, > Tanya > > > > "subhash" wrote: > > Hi, > > We are using DDK 6001.17121 . we tried to install src\kmdf\echo > > driver in Windows Wista Buisiness Edition. We have only put some > > "kdprint" to trace DriverEntry. As per the documentaton, We used > > add hardware wizard to install the driver. I am not getting any prints > > in DbgView . Driver gets installed but the system asks for a restart. > > Devcon shows the driver in the listing. I used DbgPrint also. I want > > to know why I am not getting any prints. > > I want to know what is the best way to trace wista driver code. > > > Looking forward for your response. > > > Thanks and Regards > > Subhash- Hide quoted text - > > - Show quoted text - Thanks for the help. Thats exactly what is happening. But the drivers I tried with Vista asks for a restart. Why Vista is doing so, when XP or 2000 dont. Is there any way I can insert the driver on the run.
From: Tanya Radeva [MSFT] on 22 May 2008 17:24
By default Vista has WDF (UMDF/KMDF) version 1.5. You have to restart only if: a) you are trying to update the framework version (e.g. the current system has WDF 1.5 installed and you're trying to install a WDF 1.7 driver). AND b) there are WDF drivers that are running. In pre-Vista there are no inbox drivers, so by default there should be no WDF drivers that are running, whereas in Vista there are inbox kmdf drivers, which are running (i.e. the above prerequisite is always true), so you need to restart when you're updating the framework. If you want to see echo.sys driver working and trace and debug it - set breakpoints in the driver's EchoEvtTimerFunc routine or in EchoEvtIoWrite/EchoEvtIoRead (all in queue.c) and start EchoApp test application as it is explained in the KMDF/echo sample documentation. Best Regards, Tanya "subhash" wrote: > On May 22, 2:42 am, Tanya Radeva [MSFT] > <TanyaRadevaM...(a)discussions.microsoft.com> wrote: > > If you've installed echo.sys driver properly it will be loaded upon Windows > > start. So DriverEntry will be executed at this time and you won't be able to > > see any messages because your Windows shell is not started yet. To actually > > stop with the debugger in DriverEntry you need to Break (Ctrl+Break) with > > WinDbg immediatly after you start the Windows Target machine (hopefully fast > > enough, so the echo.sys driver is not loaded yet) and then set a deffered > > breakpoint at the DriverEntry function. When the driver gets loaded by > > Windows your breakpoint will get bound and the debugger will stop at this > > breakpoint. > > > > Best regads, > > Tanya > > > > > > > > "subhash" wrote: > > > Hi, > > > We are using DDK 6001.17121 . we tried to install src\kmdf\echo > > > driver in Windows Wista Buisiness Edition. We have only put some > > > "kdprint" to trace DriverEntry. As per the documentaton, We used > > > add hardware wizard to install the driver. I am not getting any prints > > > in DbgView . Driver gets installed but the system asks for a restart. > > > Devcon shows the driver in the listing. I used DbgPrint also. I want > > > to know why I am not getting any prints. > > > I want to know what is the best way to trace wista driver code. > > > > > Looking forward for your response. > > > > > Thanks and Regards > > > Subhash- Hide quoted text - > > > > - Show quoted text - > > Thanks for the help. Thats exactly what is happening. But the drivers > I tried with Vista asks for a restart. > Why Vista is doing so, when XP or 2000 dont. Is there any way I can > insert the driver on the run. > |