[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-users
Subject:    Re: [Wireshark-users] Wireshark-users Digest, Vol 147, Issue 1
From:       Chris Lhamon <clhamon () hotmail ! com>
Date:       2018-08-01 16:21:34
Message-ID: DM5PR16MB1868EA28DE0F2E47B101E4B5A52D0 () DM5PR16MB1868 ! namprd16 ! prod ! outlook ! com
[Download RAW message or body]

Unsubscribe
________________________________
From: Wireshark-users <wireshark-users-bounces@wireshark.org> on behalf of \
                wireshark-users-request@wireshark.org \
                <wireshark-users-request@wireshark.org>
Sent: Wednesday, August 1, 2018 8:00:01 AM
To: wireshark-users@wireshark.org
Subject: Wireshark-users Digest, Vol 147, Issue 1

Send Wireshark-users mailing list submissions to
        wireshark-users@wireshark.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.wireshark.org/mailman/listinfo/wireshark-users
or, via email, send a message with subject or body 'help' to
        wireshark-users-request@wireshark.org

You can reach the person managing the list at
        wireshark-users-owner@wireshark.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wireshark-users digest..."


Today's Topics:

   1. latest wireshark 2.6.2 won't install on my        Windows 2008
      standard SP2 (Noel, Andre)
   2. Re: latest wireshark 2.6.2 won't install on my Windows 2008
      standard SP2 (Pascal Quantin)
   3. Re: i4btrace issue using Wireshark 2.6 (Guy Harris)


----------------------------------------------------------------------

Message: 1
Date: Tue, 31 Jul 2018 13:57:45 +0000
From: "Noel, Andre" <andre.noel@bell.ca>
To: Community support list for Wireshark
        <wireshark-users@wireshark.org>
Subject: [Wireshark-users] latest wireshark 2.6.2 won't install on my
        Windows 2008 standard SP2
Message-ID:
        <3f1ba278ef8f430e94c3d9e4fa990791@DG2MBX02-WYN.bell.corp.bce.ca>
Content-Type: text/plain; charset="iso-8859-1"

Hello,

I am running a PC  with   Windows 2008 Standard SP2   Wireshark 2.4.4  run fine  on \
it.  But when I try to  upgrade to the latest 2.6.2  I do receive this message: " \
Windows Vista is no longer supported.  Please install Wireshark 2.2 instead."

I am thinking maybe Wireshark is checking  a registery key that returns a false \
information about the OS   because really, it is not Vista.  That machine  is running \
Windows 2008 Standard SP2...

Is there a way to circumvent that ?  Or do someone knows what is that registery key \
that is being checked ?

Regards.

André Noël
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.wireshark.org/lists/wireshark-users/attachments/20180731/5d95011a/attachment.html>


------------------------------

Message: 2
Date: Tue, 31 Jul 2018 16:04:42 +0200
From: Pascal Quantin <pascal.quantin@gmail.com>
To: Community support list for Wireshark
        <wireshark-users@wireshark.org>
Subject: Re: [Wireshark-users] latest wireshark 2.6.2 won't install on
        my Windows 2008 standard SP2
Message-ID:
        <CAGka-80THH5_TW2nwK4GagzjMzJ2AzXfyveDi=CuytP7hKGfxA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi André,

Le mar. 31 juil. 2018 à 15:58, Noel, Andre <andre.noel@bell.ca> a écrit :

> Hello,
> 
> 
> 
> I am running a PC  with   Windows 2008 Standard SP2   Wireshark 2.4.4  run
> fine  on it.  But when I try to  upgrade to the latest 2.6.2  I do receive
> this message:
> 
> “ Windows Vista is no longer supported.  Please install Wireshark 2.2
> instead.”
> 
> 
> 
> I am thinking maybe Wireshark is checking  a registery key that returns a
> false information about the OS   because really, it is not Vista.  That
> machine  is running
> 
> Windows 2008 Standard SP2…
> 
> 
> 
> Is there a way to circumvent that ?  Or do someone knows what is that
> registery key that is being checked ?
> 

Windows server 2008 is based on the same kernel as Windows Vista. So indeed
Wireshark 2.6.x is not supported on this OS (it looks like we did not
differentiate the error string depending on whether you run a client or
server version).

Best regards,
Pascal.

> 
> 
> Regards.
> 
> 
> 
> André Noël
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@wireshark.org
> ?subject=unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.wireshark.org/lists/wireshark-users/attachments/20180731/ef1f28a0/attachment.html>


------------------------------

Message: 3
Date: Tue, 31 Jul 2018 10:13:26 -0700
From: Guy Harris <guy@alum.mit.edu>
To: Community support list for Wireshark
        <wireshark-users@wireshark.org>
Subject: Re: [Wireshark-users] i4btrace issue using Wireshark 2.6
Message-ID: <43BA46F8-42F2-4AB1-8A63-A573BD16919F@alum.mit.edu>
Content-Type: text/plain; charset=us-ascii

On Jul 31, 2018, at 12:19 AM, Dario Bozzali <Dario.Bozzali@ifmgroup.it> wrote:

> Am I missing some setting that has been changed among releases?

No, this is a bug.  Please report it on http://bugs.wireshark.org/.



------------------------------

Subject: Digest Footer

_______________________________________________
Wireshark-users mailing list
Wireshark-users@wireshark.org
https://www.wireshark.org/mailman/listinfo/wireshark-users


------------------------------

End of Wireshark-users Digest, Vol 147, Issue 1
***********************************************


[Attachment #3 (text/html)]

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body>
Unsubscribe
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" \
style="font-size:11pt" color="#000000"><b>From:</b> Wireshark-users \
&lt;wireshark-users-bounces@wireshark.org&gt; on behalf of \
wireshark-users-request@wireshark.org \
&lt;wireshark-users-request@wireshark.org&gt;<br> <b>Sent:</b> Wednesday, August 1, \
2018 8:00:01 AM<br> <b>To:</b> wireshark-users@wireshark.org<br>
<b>Subject:</b> Wireshark-users Digest, Vol 147, Issue 1</font>
<div>&nbsp;</div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send Wireshark-users mailing list submissions to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; wireshark-users@wireshark.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a \
href="https://www.wireshark.org/mailman/listinfo/wireshark-users">https://www.wireshark.org/mailman/listinfo/wireshark-users</a><br>
 or, via email, send a message with subject or body 'help' to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; wireshark-users-request@wireshark.org<br>
<br>
You can reach the person managing the list at<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; wireshark-users-owner@wireshark.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Wireshark-users digest...&quot;<br>
<br>
<br>
Today's Topics:<br>
<br>
&nbsp;&nbsp; 1. latest wireshark 2.6.2 won't install on \
my&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Windows 2008<br> \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; standard SP2 (Noel, Andre)<br> &nbsp;&nbsp; 2. Re: \
latest wireshark 2.6.2 won't install on my Windows 2008<br> \
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; standard SP2 (Pascal Quantin)<br> &nbsp;&nbsp; 3. Re: \
i4btrace issue using Wireshark 2.6 (Guy Harris)<br> <br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 31 Jul 2018 13:57:45 &#43;0000<br>
From: &quot;Noel, Andre&quot; &lt;andre.noel@bell.ca&gt;<br>
To: Community support list for Wireshark<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;wireshark-users@wireshark.org&gt;<br>
Subject: [Wireshark-users] latest wireshark 2.6.2 won't install on my<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Windows 2008 standard SP2<br>
Message-ID:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
                &lt;3f1ba278ef8f430e94c3d9e4fa990791@DG2MBX02-WYN.bell.corp.bce.ca&gt;<br>
                
Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
<br>
Hello,<br>
<br>
I am running a PC&nbsp; with&nbsp;&nbsp; Windows 2008 Standard SP2&nbsp;&nbsp; \
Wireshark 2.4.4&nbsp; run fine&nbsp; on it.&nbsp; But when I try to&nbsp; upgrade to \
the latest 2.6.2&nbsp; I do receive this message:<br> &quot; Windows Vista is no \
longer supported.&nbsp; Please install Wireshark 2.2 instead.&quot;<br> <br>
I am thinking maybe Wireshark is checking&nbsp; a registery key that returns a false \
information about the OS&nbsp;&nbsp; because really, it is not Vista.&nbsp; That \
machine&nbsp; is running<br> Windows 2008 Standard SP2...<br>
<br>
Is there a way to circumvent that ?&nbsp; Or do someone knows what is that registery \
key that is being checked ?<br> <br>
Regards.<br>
<br>
André Noël<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: &lt;<a href="https://www.wireshark.org/lists/wireshark-users/attachments/20180731 \
/5d95011a/attachment.html">https://www.wireshark.org/lists/wireshark-users/attachments/20180731/5d95011a/attachment.html</a>&gt;<br>
 <br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 31 Jul 2018 16:04:42 &#43;0200<br>
From: Pascal Quantin &lt;pascal.quantin@gmail.com&gt;<br>
To: Community support list for Wireshark<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;wireshark-users@wireshark.org&gt;<br>
Subject: Re: [Wireshark-users] latest wireshark 2.6.2 won't install on<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; my Windows 2008 standard SP2<br>
Message-ID:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
                &lt;CAGka-80THH5_TW2nwK4GagzjMzJ2AzXfyveDi=CuytP7hKGfxA@mail.gmail.com&gt;<br>
                
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
Hi André,<br>
<br>
Le mar. 31 juil. 2018 à 15:58, Noel, Andre &lt;andre.noel@bell.ca&gt; a écrit :<br>
<br>
&gt; Hello,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I am running a PC&nbsp; with&nbsp;&nbsp; Windows 2008 Standard SP2&nbsp;&nbsp; \
Wireshark 2.4.4&nbsp; run<br> &gt; fine&nbsp; on it.&nbsp; But when I try to&nbsp; \
upgrade to the latest 2.6.2&nbsp; I do receive<br> &gt; this message:<br>
&gt;<br>
&gt; “ Windows Vista is no longer supported.&nbsp; Please install Wireshark 2.2<br>
&gt; instead.”<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I am thinking maybe Wireshark is checking&nbsp; a registery key that returns \
a<br> &gt; false information about the OS&nbsp;&nbsp; because really, it is not \
Vista.&nbsp; That<br> &gt; machine&nbsp; is running<br>
&gt;<br>
&gt; Windows 2008 Standard SP2…<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Is there a way to circumvent that ?&nbsp; Or do someone knows what is that<br>
&gt; registery key that is being checked ?<br>
&gt;<br>
<br>
Windows server 2008 is based on the same kernel as Windows Vista. So indeed<br>
Wireshark 2.6.x is not supported on this OS (it looks like we did not<br>
differentiate the error string depending on whether you run a client or<br>
server version).<br>
<br>
Best regards,<br>
Pascal.<br>
<br>
&gt;<br>
&gt;<br>
&gt; Regards.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; André Noël<br>
&gt; ___________________________________________________________________________<br>
&gt; Sent via:&nbsp;&nbsp;&nbsp; Wireshark-users mailing list \
&lt;wireshark-users@wireshark.org&gt;<br> &gt; Archives:&nbsp;&nbsp;&nbsp; <a \
href="https://www.wireshark.org/lists/wireshark-users">https://www.wireshark.org/lists/wireshark-users</a><br>
 &gt; Unsubscribe: <a \
href="https://www.wireshark.org/mailman/options/wireshark-users"> \
https://www.wireshark.org/mailman/options/wireshark-users</a><br> \
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a \
href="mailto:wireshark-users-request@wireshark.org">mailto:wireshark-users-request@wireshark.org</a><br>
 &gt; ?subject=unsubscribe<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: &lt;<a href="https://www.wireshark.org/lists/wireshark-users/attachments/20180731 \
/ef1f28a0/attachment.html">https://www.wireshark.org/lists/wireshark-users/attachments/20180731/ef1f28a0/attachment.html</a>&gt;<br>
 <br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 31 Jul 2018 10:13:26 -0700<br>
From: Guy Harris &lt;guy@alum.mit.edu&gt;<br>
To: Community support list for Wireshark<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;wireshark-users@wireshark.org&gt;<br>
Subject: Re: [Wireshark-users] i4btrace issue using Wireshark 2.6<br>
Message-ID: &lt;43BA46F8-42F2-4AB1-8A63-A573BD16919F@alum.mit.edu&gt;<br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Jul 31, 2018, at 12:19 AM, Dario Bozzali &lt;Dario.Bozzali@ifmgroup.it&gt; \
wrote:<br> <br>
&gt; Am I missing some setting that has been changed among releases?<br>
<br>
No, this is a bug.&nbsp; Please report it on <a \
href="http://bugs.wireshark.org/">http://bugs.wireshark.org/</a>.<br> <br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Wireshark-users mailing list<br>
Wireshark-users@wireshark.org<br>
<a href="https://www.wireshark.org/mailman/listinfo/wireshark-users">https://www.wireshark.org/mailman/listinfo/wireshark-users</a><br>
 <br>
<br>
------------------------------<br>
<br>
End of Wireshark-users Digest, Vol 147, Issue 1<br>
***********************************************<br>
</div>
</span></font></div>
</body>
</html>


[Attachment #4 (unknown)]

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@wireshark.org?subject=unsubscribe

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic