I concur...I tested this leaving LOTS of time
between exchanges on the two computers, and the
serial #'s still got hosed.
"Lots of time" = 30 seconds +/-.
--- "Violette, Daniel R"
<Daniel.Violette@West.Boeing.com> wrote:
> I don't believe the computers are an issue. Each
> computer believed it was
> giving #518 because the other computer hadn't
> notified it yet that the
> number was used. Once computer A got notified that
> the other used #518 it
> had already sent #518. They were a 386 and a 486
> computer with minimum
> settings (not even sure if we have SMARTDRV on).
> They are club machines and
> we set up quickly. We just decided to so this last
> week.
>
> Dan KI6X (@K6NX)
>
> > ----------
> > From: Guy Olinger, K2AV[SMTP:k2av@contesting.com]
> > Reply To: k2av@contesting.com
> > Sent: Monday, November 08, 1999 10:24 AM
> > To: Violette, Daniel R
> > Cc: dawley@execpc.com; 'geoiii@kkn.net';
> trlog@contesting.com;
> > Balmforth, Kevin D; 'Don McDoniel N4EA'
> > Subject: Re: [TRLog] Serial #, Pathological
> behavior in a network
> >
> > Sounds like a grab interval problem. What
> processor/speed/SMARTDRV was
> > being used in each case? A faster machine, or one
> running with a
> > different cache size/option in SMARTDRV, might
> slip by the problem.
> >
> >
>
>
>
=====
Please direct any replies to
dawley@execpc.com
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|