[Thread Prev][Thread Next][Thread Index]
Re: PilotManager v1.006_01 available
- To: pilotmgr@xxxxxxxxxxxxxxxxxxx, Mark.Hapner@Eng
- Subject: Re: PilotManager v1.006_01 available
- From: kurt.horton@Central (Kurt Horton)
- Date: Tue, 29 Apr 1997 13:12:59 -0600
- Sender: owner-pilotmgr@shadow
While trying to get this working on my 2.5.1 system yesterday I was
fiddling with the environment variables. I often use env(1) to empty
the environment and see what happens... :-)
The PERL scripts seem to rely on the envvar PWD and if it is not set
I got this same error. Try:
at your shell prompt -- if you don't get the current working directory
that may be the problem. ksh and csh seem to maintain this envvar --
sh doesn't seem to do so.
> From owner-pilotmgr@xxxxxxxxxxxxxxxxxxx Tue Apr 29 12:54 MDT 1997
> Date: Tue, 29 Apr 1997 11:40:51 -0700
> From: Mark.Hapner@Eng (Mark Hapner)
> To: pilotmgr@xxxxxxxxxxxxxxxxxxx
> Subject: Re: PilotManager v1.006_01 available
> I'm a new user of PilotMgr and have run into a couple of problems.
> 1. When I run either the 1.006 or 1.006_01 versions on my Ultra 1 it
> fails with:
> Sorry, but PilotManager does not currently support
> your architecture (sun4-solaris)
> This does not happen with 1.005.
> 2. I'm using a male to male 9 to 25 pin adaptor and when I run hotsync I
> get a loopback detected error on the pilot. The Ultra 1 has three 25
> pin connectors; I'm assuming the one on the bottom row is the serial
> port. I tried the others and they don't work either.
> -- Mark Hapner