Search Results

Search found 3 results on 1 pages for 'mckenzieg1'.

Page 1/1 | 1 

• Does Windows 7 support multiple simultaneous nVidia graphics cards with different drivers?

  - by mckenzieg1

  On one of my dev machines at work (currently running XP), I have two nVidia graphics cards: Quadro NVS 440 (my original card, for my three primary monitors) GeForce GTX 275 (just added, for CUDA development) I can get both cards to work OK by installing the latest GeForce drivers, but I get some annoying-but-not-crippling display artifacts on the Quadro's screens (mostly scattered black rectanges where repainting fails for a few bits of UI in certain applications). Under XP, this seems to be the best I can do. I can use Device Manager to supposedly install different nVidia drivers for the two cards (the latest Quadro drivers for the NVS, the latest GeForce drivers for the GTX), but I actually end up with the same driver for both, because the driver dlls all have the same names and get installed on top of one another in the system directory. I have read that Win7 has a new video driver architecture that better supports multiple heterogeneous cards. Does anyone know if that will handle my scenario? If so, it will give me a compelling reason to get that machine on Win7 ASAP.

  Read the article

• Tips / techniques for high-performance C# server sockets

  - by McKenzieG1

  I have a .NET 2.0 server that seems to be running into scaling problems, probably due to poor design of the socket-handling code, and I am looking for guidance on how I might redesign it to improve performance. Usage scenario: 50 - 150 clients, high rate (up to 100s / second) of small messages (10s of bytes each) to / from each client. Client connections are long-lived - typically hours. (The server is part of a trading system. The client messages are aggregated into groups to send to an exchange over a smaller number of 'outbound' socket connections, and acknowledgment messages are sent back to the clients as each group is processed by the exchange.) OS is Windows Server 2003, hardware is 2 x 4-core X5355. Current client socket design: A TcpListener spawns a thread to read each client socket as clients connect. The threads block on Socket.Receive, parsing incoming messages and inserting them into a set of queues for processing by the core server logic. Acknowledgment messages are sent back out over the client sockets using async Socket.BeginSend calls from the threads that talk to the exchange side. Observed problems: As the client count has grown (now 60-70), we have started to see intermittent delays of up to 100s of milliseconds while sending and receiving data to/from the clients. (We log timestamps for each acknowledgment message, and we can see occasional long gaps in the timestamp sequence for bunches of acks from the same group that normally go out in a few ms total.) Overall system CPU usage is low (< 10%), there is plenty of free RAM, and the core logic and the outbound (exchange-facing) side are performing fine, so the problem seems to be isolated to the client-facing socket code. There is ample network bandwidth between the server and clients (gigabit LAN), and we have ruled out network or hardware-layer problems. Any suggestions or pointers to useful resources would be greatly appreciated. If anyone has any diagnostic or debugging tips for figuring out exactly what is going wrong, those would be great as well. Note: I have the MSDN Magazine article Winsock: Get Closer to the Wire with High-Performance Sockets in .NET, and I have glanced at the Kodart "XF.Server" component - it looks sketchy at best.

  Read the article

• Non-modal WinForms FontDialog?

  - by McKenzieG1

  Is it possible to display the WinForms "font picker" dialog non-modally? Or is there another font picker other than the standard one that can be used non-modally? Our application has many windows, and users who frequently need to interrupt what they are doing and switch to another window to look at something. This tends to lead to "buried dialog" scenarios with modal dialogs, where the UI is unresponsive, but it isn't immediately apparent why, because the modal dialog that has captured the focus is behind another window.

  Read the article

1