|
|
Hi,
Our product makes use of a system wide mouse hook (WH_MOUSE) and a message hook( WH_GETMESSAGE) that are implemented in a DLL. It works well on all 32 bit systems9 (W2K, XP) we are having some problems on XP x64 version. The moment the mouse hook is installed, the system slows down drastically. The CPU usage remains normal ( 99% consumed by System Idle process).
I do not understand what is happening or why the system slows down like this? Has anybody experienced anything like this before? I have tried googling to see if anything like this has been reported before, but could not find anything.
MSDN says that both for WH_MOUSE both 32 bit and 64 bit hooks might be called. Could this be causing this slowdown? We are using #pragma data_seg to share data between the DLL instances.
Any information/pointers would be appreciated very much.
-- Cheers, RR
|
|
You are aware that 32bit *:DLL's cannot be called from a 64bit process? If both your product and this DLL is of the same bitness, it should work if the files are installed correctly. This means that the Program files Directory on a 64bit system is reserved for 64bit programs and the SysWow64 Directory is where you put the 32bit stuff. A standard installer should handle this, but if you put things inside manually you will have to consider this. But both need to be the same bitness.
Appart from this, there aren't that many development questions being treated here, it is a User Interface related group. You will get better answers in one of the MSDN forums or one of the targeted developer groups.
Tony. . .
"RR >" <rr[ at ]<.> wrote in message news:uFCbkNzpHHA.3264[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > Hi, > > Our product makes use of a system wide mouse hook (WH_MOUSE) and a message > hook( WH_GETMESSAGE) that are implemented in a DLL. > It works well on all 32 bit systems9 (W2K, XP) we are having some
problems on > XP x64 version. > The moment the mouse hook is installed, the system slows down drastically. > The CPU usage remains normal ( 99% consumed by System Idle process). > > I do not understand what is happening or why the system slows down like this? > Has anybody experienced anything like this before? > I have tried googling to see if anything like this has been reported before, but > could not find anything. > > MSDN says that both for WH_MOUSE both 32 bit and 64 bit hooks might be called. > Could this be causing this slowdown? > We are using #pragma data_seg to share data between the DLL instances. > > Any information/pointers would be appreciated very much. > > -- > Cheers, > RR > >
|
|
Hi,
Yes I am aware that 32 bit DLL's will be injected into 32 bit processes and 64 bit DLL's into 64 bit processes only. The process in question is a 32 bit process and I expect to only hook into other 32 bit processes that are running. I could not find any other 64 bit group ( other than a French and Japanese group).
Thanks for answering.
Regards, RR
"Tony Sperling" <tony.sperling[ at ]dbREMOVEmail.dk> wrote in message news:ukB14AWqHHA.3372[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > You are aware that 32bit *:DLL's cannot be called from a 64bit process? If > both your product and this DLL is of the same bitness, it should work if the > files are installed correctly. This means that the Program files Directory > on a 64bit system is reserved for 64bit programs and the SysWow64 Directory > is where you put the 32bit stuff. A standard installer should handle this, > but if you put things inside manually you will have to consider this. But > both need to be the same bitness. > > Appart from this, there aren't that many development questions being treated > here, it is a User Interface related group. You will get better answers in > one of the MSDN forums or one of the targeted developer groups. > > > Tony. . . > > > "RR >" <rr[ at ]<.> wrote in message > news:uFCbkNzpHHA.3264[ at ]TK2MSFTNGP04.phx.gbl... >> Hi, >> >> Our product makes use of a system wide mouse hook (WH_MOUSE) and a message >> hook( WH_GETMESSAGE) that are implemented in a DLL. >> It works well on all 32 bit systems9 (W2K, XP) we are having some > problems on >> XP x64 version. >> The moment the mouse hook is installed, the system slows down drastically. >> The CPU usage remains normal ( 99% consumed by System Idle process). >> >> I do not understand what is happening or why the system slows down like > this? >> Has anybody experienced anything like this before? >> I have tried googling to see if anything like this has been reported > before, but >> could not find anything. >> >> MSDN says that both for WH_MOUSE both 32 bit and 64 bit hooks might be > called. >> Could this be causing this slowdown? >> We are using #pragma data_seg to share data between the DLL instances. >> >> Any information/pointers would be appreciated very much. >> >> -- >> Cheers, >> RR >> >> > >
|
|
Unfortunately this particular forum is not geared toward programming, it's geared toward the users of 64-bit operating systems.
If there aren't any programming forums that seem to be applicable to your situation, then MSDN has programming information.
http://msdn.microsoft.com/msdnmag/issues/06/05/x64/default.aspx is one link. You may have to search around if there isn't anything helpful at this link.
RR wrote:
[Quoted Text] > Hi, > > Yes I am aware that 32 bit DLL's will be injected into 32 bit processes and 64 > bit DLL's into 64 bit processes only. > The process in question is a 32 bit process and I expect to only hook into other > 32 bit processes that are running. > I could not find any other 64 bit group ( other than a French and Japanese > group). > > Thanks for answering. > > Regards, > RR > > "Tony Sperling" <tony.sperling[ at ]dbREMOVEmail.dk> wrote in message > news:ukB14AWqHHA.3372[ at ]TK2MSFTNGP03.phx.gbl... >> You are aware that 32bit *:DLL's cannot be called from a 64bit process? If >> both your product and this DLL is of the same bitness, it should work if the >> files are installed correctly. This means that the Program files Directory >> on a 64bit system is reserved for 64bit programs and the SysWow64 Directory >> is where you put the 32bit stuff. A standard installer should handle this, >> but if you put things inside manually you will have to consider this. But >> both need to be the same bitness. >> >> Appart from this, there aren't that many development questions being treated >> here, it is a User Interface related group. You will get better answers in >> one of the MSDN forums or one of the targeted developer groups. >> >> >> Tony. . . >> >> >> "RR >" <rr[ at ]<.> wrote in message >> news:uFCbkNzpHHA.3264[ at ]TK2MSFTNGP04.phx.gbl... >>> Hi, >>> >>> Our product makes use of a system wide mouse hook (WH_MOUSE) and a message >>> hook( WH_GETMESSAGE) that are implemented in a DLL. >>> It works well on all 32 bit systems9 (W2K, XP) we are having some >> problems on >>> XP x64 version. >>> The moment the mouse hook is installed, the system slows down drastically. >>> The CPU usage remains normal ( 99% consumed by System Idle process). >>> >>> I do not understand what is happening or why the system slows down like >> this? >>> Has anybody experienced anything like this before? >>> I have tried googling to see if anything like this has been reported >> before, but >>> could not find anything. >>> >>> MSDN says that both for WH_MOUSE both 32 bit and 64 bit hooks might be >> called. >>> Could this be causing this slowdown? >>> We are using #pragma data_seg to share data between the DLL instances. >>> >>> Any information/pointers would be appreciated very much. >>> >>> -- >>> Cheers, >>> RR >>> >>> >> > >
|
|
The most common thing to go wrong for many people seems to be the installation process, there are no specific 64bit developer forums that I'm aware of, any developer group would probably be able to give advice.
Tony. . .
"RR" <No[ at ]spamforme.null> wrote in message news:eh8halcqHHA.3296[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Hi, > > Yes I am aware that 32 bit DLL's will be injected into 32 bit processes
and 64 > bit DLL's into 64 bit processes only. > The process in question is a 32 bit process and I expect to only hook into other > 32 bit processes that are running. > I could not find any other 64 bit group ( other than a French and Japanese > group). > > Thanks for answering. > > Regards, > RR > > "Tony Sperling" <tony.sperling[ at ]dbREMOVEmail.dk> wrote in message > news:ukB14AWqHHA.3372[ at ]TK2MSFTNGP03.phx.gbl... > > You are aware that 32bit *:DLL's cannot be called from a 64bit process? If > > both your product and this DLL is of the same bitness, it should work if the > > files are installed correctly. This means that the Program files Directory > > on a 64bit system is reserved for 64bit programs and the SysWow64 Directory > > is where you put the 32bit stuff. A standard installer should handle this, > > but if you put things inside manually you will have to consider this. But > > both need to be the same bitness. > > > > Appart from this, there aren't that many development questions being treated > > here, it is a User Interface related group. You will get better answers in > > one of the MSDN forums or one of the targeted developer groups. > > > > > > Tony. . . > > > > > > "RR >" <rr[ at ]<.> wrote in message > > news:uFCbkNzpHHA.3264[ at ]TK2MSFTNGP04.phx.gbl... > >> Hi, > >> > >> Our product makes use of a system wide mouse hook (WH_MOUSE) and a message > >> hook( WH_GETMESSAGE) that are implemented in a DLL. > >> It works well on all 32 bit systems9 (W2K, XP) we are having some > > problems on > >> XP x64 version. > >> The moment the mouse hook is installed, the system slows down drastically. > >> The CPU usage remains normal ( 99% consumed by System Idle process). > >> > >> I do not understand what is happening or why the system slows down like > > this? > >> Has anybody experienced anything like this before? > >> I have tried googling to see if anything like this has been reported > > before, but > >> could not find anything. > >> > >> MSDN says that both for WH_MOUSE both 32 bit and 64 bit hooks might be > > called. > >> Could this be causing this slowdown? > >> We are using #pragma data_seg to share data between the DLL instances. > >> > >> Any information/pointers would be appreciated very much. > >> > >> -- > >> Cheers, > >> RR > >> > >> > > > > > >
|
|
|