Re: Interpreter startup problem

Subject: Re: Interpreter startup problem
From: Ray <rehenry-at-up.net>
Date: Thu, 1 Nov 2001 18:19:16 +0000
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <3BE1A244.D50F7629-at-btconnect.com>
References: <3BE070BF.AD6CB507-at-btconnect.com> <01103122195202.05165-at-localhost.main> <3BE1A244.D50F7629-at-btconnect.com>
Reply-To: rehenry-at-up.net



Chris

Fantastic.  Glad that you got it working.

Ray


On Thursday 01 November 2001 19:45, you wrote:
> Ray
>
> Thanks for the suggestion I made the change you suggested and everything
> now works fine. I knew it would be something simple.
>
> Chris
>
> Ray wrote:
> > Chris
> >
> > I wonder if this could be as simple as 5220 not being 1.0000 in the
> > var file.  There were some problems with the file not being saved or
> > transfered correctly when first started up.  Might check.
> >

References:
- Interpreter startup problem
  - From: Chris Galloway <chris.galloway-at-btconnect.com>
- Re: Interpreter startup problem
  - From: Ray <rehenry-at-up.net>
- Re: Interpreter startup problem
  - From: Chris Galloway <chris.galloway-at-btconnect.com>

Prev by Date: Re: Interpreter startup problem
Next by Date: Remote tkemc
Prev by thread: Re: Interpreter startup problem
Next by thread: New York Security Services/Quantum

Date Index | Thread Index | Back to archive index | Back to Mailing List Page
Problems or questions? Contact