TIP: Click on subject to list as thread! ANSI
echo: muffin
to: ALL
from: David_Nyquist@f2000.n106.z1
date: 2005-10-26 21:13:05
subject: Re: Maximus 3.03b for Linux

Path: number1.nntp.dca.giganews.com!local01.nntp.dca.giganews.com!nntp.adelphia.com!news.adelphia.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 26 Oct 2005 21:13:05 -0500
Newsgroups: fidonet.muffin
From: David_Nyquist@f2000.n106.z1
Date: Sat, 22 Oct 2005 17:14:32 -0400
Subject: Re: Maximus 3.03b for Linux
Message-ID: 
References: 
Organization: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671
 124/5009 5025
 3634/12
Lines: 23
NNTP-Posting-Host: 24.48.121.215
 properly
Xref: number1.nntp.dca.giganews.com fidonet.muffin:35

DN> 
DN> ! 22 Oct 14:48:01 MAX  MEX:  can't read file 'm/headmsg'.

 AI> Are you using an amd64 by chance? I get the same thing here using

No just a regular AMD 1.7 Ghz CPU.  I did figure it out though.  I had to
manually recompile the headmsg.mex files.  Then chown and chgrp all the files in
the /opt/max/m directory to the 'bbs' linux user and group.  Then it seemed to
work.

 AI> I have done that before with inetd although I forget exactly how I did
 AI> it. Have you tried with what is at the bottom of the QUICKSTART file?
 AI> I can't remeber if that is for telnet/dialup or both.

I tried looking at the bottom of the QUICKSTART file.  But it didn't provide
any insight.  I did however try executing the command ./max -n1 -pt2323 -w.  It
brought up the waiting for caller window.  I tried telnetting into it on the same
box max was setup on.  But it wouldn't connect.

Cheers,
David Nyquist

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.