Problem Initiating The Debuger From Code 400 -- CODE400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Problem Initiating The Debuger From Code 400
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Mon, 27 Jan 2003 13:22:22 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/code400-l>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

Xuan Chen,

just out of interest I followed the %USERPROFILE% route you suggested to see
what "odd" files I might have there.  I notice that although I don't have a
cfg file named CLIPPER, I _do_ have a couple that I never created, including
one called "working8-5.cfg" and another called "working9.cfg".  There are
also a number of (Anne?) WILEY's files liberally scattered around.  Are you
guys by any chance leaving your own server info in the install directories?

Jon Paris
Partner400

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.