[prev in list] [next in list] [prev in thread] [next in thread]
List: winpcap-users
Subject: Re: [Winpcap-users] OEM pcap installation problem
From: "Gianluca Varenni" <gianluca.varenni () cacetech ! com>
Date: 2009-11-09 22:51:21
Message-ID: 4A9C5643CE6B4F9F923B5F3EDFF8F771 () NELSON3
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
This mailing list is for the open source version of WinPcap, only. Please send your \
request to support@cacetech.com or to me directly.
Have a nice day
GV
----- Original Message -----
From: Sagi Shechter
To: winpcap-users@winpcap.org
Sent: Monday, November 09, 2009 12:08 PM
Subject: [Winpcap-users] OEM pcap installation problem
Hi,
We are using the OEM pcap with our application, and noticed
that when the dll (packet.dll) is loaded, a key is added to the registry at : \
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\ The \
PendingFileRenameOperations key is added, with a value of
\??\C:\WINDOWS\SysWOW64\WPRO_40_1040woem.tmp
This in turn leads to some patches/other installers not running properly, because \
they assume the system has to be rebooted first.
Thank you,
Sagi Shechter
Guardium Inc.
------------------------------------------------------------------------------
_______________________________________________
Winpcap-users mailing list
Winpcap-users@winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>This mailing list is for the open source version of WinPcap,
only. Please send your request to <A
href="mailto:support@cacetech.com">support@cacetech.com</A> or to me
directly.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Have a nice day</FONT></DIV>
<DIV><FONT size=2>GV</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 \
2px solid; MARGIN-RIGHT: 0px"> <DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=sagi.shechter@guardium.com
href="mailto:sagi.shechter@guardium.com">Sagi Shechter</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=winpcap-users@winpcap.org
href="mailto:winpcap-users@winpcap.org">winpcap-users@winpcap.org</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, November 09, 2009 12:08
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [Winpcap-users] OEM pcap
installation problem</DIV>
<DIV><BR></DIV>Hi, <BR>We are using the OEM pcap with our application, and
noticed<BR>that when the dll (packet.dll) is loaded, a key is added to the
registry at : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\<BR>The PendingFileRenameOperations key is added, with a value of
<BR><BR>\??\C:\WINDOWS\SysWOW64\WPRO_40_1040woem.tmp <BR><BR>This in turn
leads to some patches/other installers not running properly, because they
assume the system has to be rebooted first.<BR><BR>Thank you,<BR><BR>Sagi
Shechter<BR>Guardium Inc.<BR><BR><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>Winpcap-users
mailing
list<BR>Winpcap-users@winpcap.org<BR>https://www.winpcap.org/mailman/listinfo/winpcap-users<BR></BLOCKQUOTE></BODY></HTML>
_______________________________________________
Winpcap-users mailing list
Winpcap-users@winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic