[Jason House <jhouse@xxxxxxxxx>]

Shortly after discovering some timing problems with Ethereal and
NetXray, I tried to verify the timing factors listed.  Unfortunately,
the supplied correction factors were still off by about 10 seconds per
day.  Calculations yielded a value of 0.8382229.  Currently I don't know
much about what it was captured with other than "It was captured on a
Dolch machine running Windows ??"  A filtered portion of the capture
file is attached.

--- Begin Message ---

From: Shawn Duffalo <sduffalo@xxxxxxxxx>

Date: Thu, 08 Feb 2001 14:52:47 -0500

the factor appears to always be 0.8382229, which is about 10 sec per day off of
the numbers you have below.  not sure i know why but it would get close enough
for any analysis we would want to do


Jason House wrote:
> 
> There are two candidate bases in the mailings sent out.
> A numerical based estimate is 88/105 (=.8380952...) correction factor.
> Another guess is .838096.  That number is based on similarity to
> something else...
> 
> I don't expect you to differentiate the two, just see if what you have
> appears to match.  The two estimates will diverge from each other by a
> second on a 2 week capture file.

begin:vcard 
n:Duffalo;Shawn
tel;work:732-389-6542
x-mozilla-html:FALSE
org:MITRE Corporation;W072
adr:;;12 Christopher Way;Eatontown;NJ;07724;
version:2.1
email;internet:sduffalo@xxxxxxxxx
title:Systems Engineer
fn:Shawn Duffalo
end:vcard

--- End Message ---

Attachment: NtdrTesting_Dasb_Wed_1803-1859.cap
Description: application/unknown-content-type-capfile