public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Emily Woodberry <ewoodberry@airnetcom.com>
To: "'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Subject: Startup problem
Date: Tue, 01 May 2001 07:19:00 -0000	[thread overview]
Message-ID: <07BB842D3E28D411804900508BAC02BDC4D220@ams1.aircom.com> (raw)

My name is Emily Woodberry.  I work for AirNet Communications in Melbourne,
Florida.

We had purchased Source Navigator 4.2 a number of years ago.  We purchased
additional licenses and an upgrade to 4.5 last year just prior to it
becoming a FREE product.  We also purchased a year of support, which is
still current.

I am having a problem that I cannot solve.  I have one user who can bring up
4.2 just fine but when he attempts to run the new version, 4.5, he is
getting an error that the reads: "error getting working directory name: no
such file or directory"   

I have not been able to find any error message information on the tool.

He is the only user who has experienced this problem.  How do I resolve it?

Thanks,

Emily


THIS TRANSMISSION, INCLUDING ANY ATTACHMENTS OR FILES, 
CONTAINS AIRNET COMMUNICATIONS CORPORATION CONFIDENTIAL 
AND PROPRIETARY INFORMATION WHICH MAY BE OTHERWISE EXEMPT 
FROM DISCLOSURE. 
The information is intended to be for the exclusive use of the individual 
or entity named above. If you are not the intended recipient, 
be advised that any disclosure, copying, distribution or other use 
of this information is strictly prohibited.  If you have received this 
transmission in error, please notify us by telephone at 1-321-984-1990 or 
by email to postmaster@aircom.com immediately and do not read, print 
or save this information in any manner. 

             reply	other threads:[~2001-05-01  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  7:19 Emily Woodberry [this message]
2001-05-01  7:36 Mills, John

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07BB842D3E28D411804900508BAC02BDC4D220@ams1.aircom.com \
    --to=ewoodberry@airnetcom.com \
    --cc=sourcenav@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).