From: Doron Holan [MSFT] on 10 Dec 2009 17:59 It is not that KMDF turns it off by default. it is by default off as per the documentation and you must explicitly opt into this behavior. note that hosting the paging file requires you to meet some expectations like guaranteed fwd progress which is only available in kmdf v1.9 d -- This posting is provided "AS IS" with no warranties, and confers no rights. "Guilherme Moro" <guilherme.moro(a)gmail.com> wrote in message news:e03fe41e-f66f-44b4-8bdc-315d8f0c73d8(a)m25g2000yqc.googlegroups.com... > Ok, you hit the exact point, with your hint I found the solution. > WDF turn off support for special files by default, I need to call > WdfDeviceSetSpecialFileSupport for both the Bus FDO and the child PDO, > so the framework handle the IRP_MN_DEVICE_USAGE_NOTIFICATION > correctly. > > Many thanks! > > Guilherme Moro > > On Dec 7, 5:23 pm, "Don Burn" <b...(a)stopspam.windrvr.com> wrote: >> Pagefiles have to be on disks that support them. For one thing take a >> look >> at IRP_MN_DEVICE_USAGE_NOTIFICATION is you are not handling it you will >> not >> be able to support paging. There is nothing about disk driver being >> loaded >> later, the paging file is created through the file system which is loaded >> onto the disk driver, so certainly is not the problem. >> >> -- >> Don Burn (MVP, Windows DKD) >> Windows Filesystem and Driver Consulting >> Website:http://www.windrvr.com >> Blog:http://msmvps.com/blogs/WinDrvr >> Remove StopSpam to reply >> >> "AMV" <A...(a)discussions.microsoft.com> wrote in message >> >> news:BC7E18C8-1634-4ED9-B910-A688F26FF18F(a)microsoft.com... >> >> >> >> >> >> > "Guilherme Moro" wrote: >> >> >> hello, >> >> >> I have a virtual ( net backed ) disk drive, and everytime I boot from >> >> this disk I got a "Your System Has No Paging File, or the Paging File >> >> Is Too Small" error, and windows create a temporarypagefile >> >> somewhere. >> >> >> Windows cant create thepagefile.sys, but I dont know why, someone >> >> told me about user permissions, but everything looks just fine with >> >> the permissions. >> >> >> I search around, even in the Windows Internals book, but cant find a >> >> decent explanation of the process of creation of thepagefile, to >> >> figure out what the problem is. >> >> >> Anyone has any ideas? >> >> >> Guilherme >> >> . >> >> > 1. probably pagefiles can't be on virtual disks >> > 2. disk driver loaded much more later, than system need forpagefile, >> > in this case you can manually add, for example (1900-4000 Mb on z:): >> > CSCRIPT //B //NoLogo "pagefileconfig.vbs" /Create /I 1900 /M 4000 /VO >> > z: >> >> > __________ Information from ESET NOD32 Antivirus, version of virus >> > signature database 4661 (20091204) __________ >> >> > The message was checked by ESET NOD32 Antivirus. >> >> >http://www.eset.com >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 4668 (20091207) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com >
First
|
Prev
|
Pages: 1 2 Prev: CM_ENABLE_DEVNODE/CM_DISABLE_DEVNODE Next: FS filter driver post create |