You're right. Trust me, I understand insufficient problem
descriptions =) But in this case it's probably 98% guarantee that the
problem has already been identified and solution given. If he still
has problems, he can give more info.
On Thu, Apr 8, 2010 at 1:31 PM, Kok-Yong Tan <ktan@xxxxxxxxxxxxxxxxxxx> wrote:
> True enough. But if he provides more details, we can zero in on the
> problem and identify it (along with a definite solution) for sure
> instead of conjecturing. "It doesn't work" as a problem description
> doesn't quite cut it for me but then I'm a professional consultant...
>
> On Apr 7, 2010, at 18:17, Ian Schorr wrote:
>
>> It's a very common problem - chances are that the answer to his
>> question has already been given. He just hasn't responded.
>>
>> On Wed, Apr 7, 2010 at 8:01 PM, Kok-Yong Tan
>> <ktan@xxxxxxxxxxxxxxxxxxx> wrote:
>>> It might help if you tell us the exact steps you're taking to
>>> start up
>>> wireshark. Without that information, anything we come up with is
>>> conjecture.
>
> --
> Reality Artisans, Inc. # Network Wrangling and Delousing
> P.O. Box 565, Gracie Station # Apple Certified Consultant
> New York, NY 10028-0019 # Apple Consultants Network member
> <http://www.realityartisans.com> # Apple Developer Connection member
> (212) 369-4876 (Voice) # My PGP public key can be found
> at <https://keyserver.pgp.com>
>
>
>
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe
>
