On Apr 5, 2007, at 3:19 AM, [EMAIL PROTECTED] wrote:
> The problem has been resolved with the inclusion of the emem.h> for 64 bit environment.
Code should *always* include the appropriate headers for any functions
it calls, to import the proper declarations for those functions;
otherwise, y
Hi,
Thanks for your inputs.
The problem has been resolved with the inclusion of the
for 64 bit environment.
Yes, the dissector is a proprietary one.
Regards,
Bhavani.
The information contained in this electronic message and any attachments to
this message are intended for the exclusive
On Mar 27, 2007, at 6:36 AM, [EMAIL PROTECTED] wrote:
> We are using a 32 bit machine and dissector is working fine. The
> same dissector when used in a 64 bit m/c is giving problems.
Is this a dissector you've written?
If so, are you
1) calling routines without including the appropr
Hi ,
We are using a 32 bit machine and dissector is working fine. The same
dissector when used in a 64 bit m/c is giving problems. I would like to
know how is it going to get affected in the change of environment,
because initially it did not even compile properly .While testing in a
64 bit ma
Is this a proprietary dissector or a dissector you plan to contribute
to wirehsark?
On 3/27/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>
>
> We are using a 32 bit machine and dissector is working fine. The same
> dissector when used in a 64 bit m/c is giving problems. I would lik
Hi,
We are using a 32 bit machine and dissector is working fine. The same
dissector when used in a 64 bit m/c is giving problems. I would like to
know how is it going to get affected in the change of environment,
because initially it did not even compile properly .While testing in a
64 bit mac
