Re: Unable to open filelist

1999-12-07 Thread Earl Hood

On December 3, 1999 at 15:22, Alycia Eck wrote:

 No. But I did try installing it on my personal site (on Linux) which I can
 telnet into and I still get the same Unable to open filelist. Thought I
 could follow how it installed itself and copy the same setup on my NT site.
 I change my directory so that I'm in the folder with the install.me, I type
 perl install.me and I get the same message. Do I need to change permissions?
 
 Do you see what Windoze has done to me?

If the file contents of the MHonArc tar bundle does not match what
is listed at http://www.oac.uci.edu/indiv/ehood/MHonArc/ then re-download
MHonArc.  Letter case is important in filenames.

You should provide a copy of the commands you run and the output
generated to provide use with better information.  Under Unix/Linux,
you can use the "script" command to record a terminal session.

--ewh



Re: Unable to open filelist

1999-12-03 Thread Earl Hood

On December 3, 1999 at 08:50, Alycia Eck wrote:

 So basically if I don't have access to the NT command shell (remote hosting
 my site) then I have to manually install this?

I believe so unless you can get your service provide to install it
for you.  Manual installation is described in the documentation, but it
may be troublesome since it appears you have no easy way to edit the
files.  You'll probably have to pre-edit the files on your system
before uploading to the remote site.

Do you have anyway to telnet to the site?

--ewh



Re: Unable to open filelist

1999-12-02 Thread Earl Hood

On December 2, 1999 at 18:01, "Steve Pacenka" wrote:

 It will not work to do something like:
 
perl d:\tmp\install.me
 
 with the current drive/directory set to something other than d:\tmp .

From the documentation:

IMPORTANT   You must be in the same directory as the install.me
program when you run it. 

So Steve is correct.  You need to install from a shell prompt.  I
recommend installing the Cygwin package for a (free) decent shell
and Unix tool environment for Win32.  But NT's command shell will
work.

Read the installation documentation for more information and usage
notes for Win32 systems.

 I recently erased my only NT workstation installation but I believe that
 Earl uses NT now so he will probably reply.

I only use NT if I am paid to do so.  I run Linux at home, and at my
current paying workplace, I do not have easy access to an NT box.  I
have a Sun running Solaris 2.6, a Dell running Lose98, and an old HP
Vectra running RH Linux 6.0.

I used an NT box (mostly as an X terminal) at my previous place
of employment.

--ewh