I reported a problem with HP computers a couple of weeks ago but got it resolved at that time by upgrading to the latest version 3.1 and modifying my code for the fact that the adapter name has got a \NPF instead of a \packet. Well, now there are problems again. HP are using there own Windows. Well, it is of course MS Windows, but they have their own install CD's with a lot of their own drivers etc. The solution from last week worked with a generic Windows on the HP computer, but installing the HP Windows gives stability problems. It has a tendency to lock up or disable all network drivers after the WinPCap installation program was ran. In fact once it had to be booted up in safe mode and uninstall the new winpcap installtionprogram in order to get the PC to boot up at all. So something wierd is going on here since the same computer works with generic windows but not with HP's versions.
This was found by one of our tech guys and I haven't had the HP computer with the HP windows in my own hands yet. However, is anybody else aware of those problems with HP computers? Jens. ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
