.NET Framework Bookmark and Share   
 index > 64-Bit .NET Framework Development > Service with driver interaction on Vista 64-bits
 

Service with driver interaction on Vista 64-bits

Hello guys,

I'm having a problem with my application when running under 64-bits version of Windows Vista. The application consists of a service that intercepts network connections and redirects them to a proxy server. That service uses a hook driver that catches all connections and let me do whatever I want with them through the managed code in the service.
The driver is not signed yet, but I'm working around that by disabling the Driver Signature Enforcement in the boot screen (F8). The driver actually works with a simple application that only prints the connections caught by the driver in a Command Prompt window. My application works fine in XP and Vista 32-bits, but I can't make it work in 64-bits versions of Windows. I'm developing with .Net Framework 2.0.

Am I forgetting something?

-Regards
Gustavo Leuck
You might want to be carefull with what you are doing, running all network traffic thougha hook driver and then processing it in managed code is gonna cause the network stack to take quite a performance hit, run performance tests and make sure you're not causeing a too significant slowdown before you send off your code to any customers.

Does your application work if you force the compiler to generate a 32bit executable (change any cpu to x86 in the project configuration) it could be that the dll you use (if you use one, not enough information provided) is a 32 bit one which you can't load into 64 bits processes.

Ray M_
The most common problem is incorrect p/Invoke signatures that just happen to work on 32-bit. Check for any places you may be using int where IntPtr should be used.

If that's not it, could you expound on your problem? e.g., what errors do you see, if any?

-Steve
Programming blog: http://nitoprograms.blogspot.com/
Including my TCP/IP .NET Sockets FAQ
MSBuild user? Try out the DynamicExecute task in the MSBuild Extension Pack source; it's currently in Beta so get your comments in!
I will be at the Grand Rapids BarCamp 4 unconference - come on by, fellow Michiganders!
Stephen Cleary
You might want to be carefull with what you are doing, running all network traffic thougha hook driver and then processing it in managed code is gonna cause the network stack to take quite a performance hit, run performance tests and make sure you're not causeing a too significant slowdown before you send off your code to any customers.

Does your application work if you force the compiler to generate a 32bit executable (change any cpu to x86 in the project configuration) it could be that the dll you use (if you use one, not enough information provided) is a 32 bit one which you can't load into 64 bits processes.

Ray M_
That just worked! All I had to do was change the platform target to x86. Thanks!
Gustavo Leuck

You can use google to search for other answers

Custom Search

More Threads

• Terrible .Net performance on XP 64!
• Loading 32/64-bit unmanaged DLLs
• compile projekt VS 2005 on 64bit machine
• .NET development 2.0 = 32bit ?
• Why MFC project manifest includes Microsoft.Windows.Common-Controls dependentAssembly and others don't?
• AVIMakeCompressedStream - InterOp problems
• Stack overflow Exception.
• How to select Oracle client folder with System.Data.OracleClient
• InkAnalysis using Windows 2003 R2 x64
• 32-bit compiled trying to run on x64?