A KeQuerySystemTime alternate function under x64 ?
in [Device Drivers]
|
From: GeminiServer on 8 Dec 2009 14:34 Don Burn schrieb: > So are you trying to get the function address or just trying to use the > function? If you want the function address you are out of luck. The macro > works fine and no 0xFFFFF78000000000UI64 means a constant that is an > Unsigned Integer 64-bits not something that works only on Itanic (i.e. > IA64). > > I'm just trying to use the function (macro) under x64 ;) I was really unsure and thought that the constant was a kind of IA64 specific adress. Now i'm sure and can use the macro for x64 (AMD64). Thank's and cheers, GeminiServer
From: Alexander Grigoriev on 8 Dec 2009 23:22 Are you using BUILD to build your driver? Are you including ntddk.h? "GeminiServer" <melih_ataoglu(a)hotmail.com> wrote in message news:4B1EAA29.3020109(a)hotmail.com... > Don Burn schrieb: >> So are you trying to get the function address or just trying to use the >> function? If you want the function address you are out of luck. The >> macro works fine and no 0xFFFFF78000000000UI64 means a constant that is >> an Unsigned Integer 64-bits not something that works only on Itanic (i.e. >> IA64). >> >> > I'm just trying to use the function (macro) under x64 ;) > I was really unsure and thought that the constant was a kind of IA64 > specific adress. Now i'm sure and can use the macro for x64 (AMD64). > > Thank's and cheers, > GeminiServer
From: GeminiServer on 9 Dec 2009 03:38 Alexander Grigoriev schrieb: > Are you using BUILD to build your driver? Are you including ntddk.h? > > "GeminiServer" <melih_ataoglu(a)hotmail.com> wrote in message > news:4B1EAA29.3020109(a)hotmail.com... >> Don Burn schrieb: >>> So are you trying to get the function address or just trying to use the >>> function? If you want the function address you are out of luck. The >>> macro works fine and no 0xFFFFF78000000000UI64 means a constant that is >>> an Unsigned Integer 64-bits not something that works only on Itanic (i.e. >>> IA64). >>> >>> >> I'm just trying to use the function (macro) under x64 ;) >> I was really unsure and thought that the constant was a kind of IA64 >> specific adress. Now i'm sure and can use the macro for x64 (AMD64). >> >> Thank's and cheers, >> GeminiServer > > I'm building with makefiles. I don't include to this specific source the ntddk.h. I just stripped out the Ke* functions i need from.
From: Don Burn on 9 Dec 2009 07:48 Why would you do that, it is a maintenance nightmare and really a bad idea. -- 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 "GeminiServer" <melih_ataoglu(a)hotmail.com> wrote in message news:4B1F6203.9090900(a)hotmail.com... > Alexander Grigoriev schrieb: >> Are you using BUILD to build your driver? Are you including ntddk.h? >> >> "GeminiServer" <melih_ataoglu(a)hotmail.com> wrote in message >> news:4B1EAA29.3020109(a)hotmail.com... >>> Don Burn schrieb: >>>> So are you trying to get the function address or just trying to use the >>>> function? If you want the function address you are out of luck. The >>>> macro works fine and no 0xFFFFF78000000000UI64 means a constant that is >>>> an Unsigned Integer 64-bits not something that works only on Itanic >>>> (i.e. IA64). >>>> >>>> >>> I'm just trying to use the function (macro) under x64 ;) >>> I was really unsure and thought that the constant was a kind of IA64 >>> specific adress. Now i'm sure and can use the macro for x64 (AMD64). >>> >>> Thank's and cheers, >>> GeminiServer >> >> > I'm building with makefiles. > I don't include to this specific source the ntddk.h. > I just stripped out the Ke* functions i need from. > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4672 (20091209) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4672 (20091209) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
First
|
Prev
|
Pages: 1 2 Prev: WinUSB - iterating devices to get serial numbers. Next: WDDM Driver Vidpn implementation. |