Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!greg
From: greg@ccwf.cc.utexas.edu (Greg Harp)
Newsgroups: comp.sys.amiga.datacomm
Subject: WEIRD bug in DNet
Keywords: DNet, ENV:, SAS/C
Message-ID: <46071@ut-emx.uucp>
Date: 23 Mar 91 08:30:14 GMT
Sender: news@ut-emx.uucp
Reply-To: greg@ccwf.cc.utexas.edu (Greg Harp)
Organization: The University of Texas at Austin
Lines: 23
Originator: greg@pooh.cc.utexas.edu

I have been experiencing a disconcerting number of gurus (most with no complaints
out of GOMF!) recently when using DNet.  I back-tracked over what I had done with
my system and I think I've traced the problem to the fact that I have configured
SAS/C!  It writes the file SASCOPTS to ENV:, and since ENV: is in RAM on my
system I copied it to a directory that gets copied to ENV: on bootup.  

I removed the SASCOPTS file from the ENV: directory and DNet hasn't crashed
since.  I haven't tested this with just any file being in ENV: (Previously I
had nothing in ENV:.  DNet creates some of its own environment variables when
it's running.) yet, so I can't be sure if this is a conflict with SAS or
what.

I am running DNet 2.10L.10, in case some later version has fixed this.  Has 
anyone else experienced this problem?

Thanks...

Greg
-- 
       Greg Harp       |"How I wish, how I wish you were here.  We're just two
                       |lost souls swimming in a fishbowl, year after year,
greg@ccwf.cc.utexas.edu|running over the same ground.  What have we found?
  s609@cs.utexas.edu   |The same old fears.  Wish you were here." - Pink Floyd