Date: Wed, 7 Jul 93 04:30:10 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #173
To: tcp-group-digest
TCP-Group Digest Wed, 7 Jul 93 Volume 93 : Issue 173
Today's Topics:
Go figure
NOS log files
NOS on T1000 (2 msgs)
T1000 nos problems
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Tue, 6 Jul 93 11:23:24 -0700
From: chuckb@babbage.ecs.csus.edu (Chuck Bland)
Subject: Go figure
To: tcp-group@ucsd.edu
Correction ! I'm not sure why the mailer dropped a character. The first
entry in my results should read "TMP=d:\".
Sorry....:-&
Chuck
chuckb@babbage.ecs.csus.edu
------------------------------
Date: Wed, 7 Jul 1993 14:33:00 +1000 (EST)
From: Adam Robertson - Network Officer DIT <aroberts@csunb.mit.csu.edu.au>
Subject: NOS log files
To: Gateways Mail List <gateways@mpg.phys.hawaii.edu>,
Hi all, Just doing some cleaning on the gateway, and decided to remove my
old nos log file (its over 1Mb now).
I have decided to do some processing on it to find out some stats about my
gateway. (Number or starts, number of SMTP sent jobs etc)
My main quere is about the NOS load info: line.
The numbers that appear in this line, what do they mean, and are they
allways meant to be the same etc. What usefull things do they tell me??
Also does anyone else do anything like this and what other usefull info can be
obtained.
Thanks in advance for any help. (My new log file is now over 600K since i
removed the old one.)
de vk2xra
Regards ---------------------------------------------------------------------
| Adam Robertson - Network Officer - Div. of Information Technology |
| Charles Sturt University - Mitchell Campus |
| Location - Bldg S1, Panorama Drive, Bathurst, NSW. AUST. 2795 |
| Charles Sturt University - Mitchell |
---------------------------------------------------------------------
| E-mail : aroberts@csu.edu.au Phone : +61 63 332-782 |
| AMPRnet: vk2xra@gw.vk2xra.ampr.org Fax : +61 63 332-181 |
---------------------------------------------------------------------
------------------------------
Date: Tue, 6 Jul 93 08:32 CDT
From: cusla!raviho@cuuxb.att.com
Subject: NOS on T1000
To: cuuxb!att!att.com!ucsd.edu!tcp-group
I sent this Friday to Gary Sanders in response to his question about
running NOS on a T1000 laptop. I am posting this to the group for anyone
else's benefit.
=====
Original T1000 does run DOS out of a ROM "drive C:". I've successfully run G1EMM
11/90 NOS on my 2 T1000 (vintage 1987) machines for 3 years. I made DOS 3.3
boot floppies for them that have the NOS on the floppy. NOS ran fine on the
ROM 2.11 DOS except for Bdales Messy Mailer which needed ansi screen capability,
so I chose to use a later DOS, thus 3.3. The ugly trade-off was that DOS 3.3
boot floppies don't recognize the ROM C: or RAM D:, so operation is slow
and limited to the floppy "poorformance." It's a concession I've lived with
and have thus been able to run mobile TCP/IP and portable TCP/IP. (At least I
always have a floppy backup of all files in case the battery fades out!)
I have no idea how well, or if at all, newer versions of NOS would do
on the original T1000.
Hope this info helps.
73,
Peter Richey
N9HDW
cuuxb.att.com
------------------------------
Date: Tue, 06 Jul 1993 12:00:21 -0400
From: "Brandon S. Allbery" <bsa@kf8nh.wariat.org>
Subject: NOS on T1000
To: tcp-group@ucsd.edu
In your message of Tue, 06 Jul 1993 08:32:00 EDT, raviho@cuuxb.att.com forwards from Gary Sanders:
+---------------
| boot floppies for them that have the NOS on the floppy. NOS ran fine on the
| ROM 2.11 DOS except for Bdales Messy Mailer which needed ansi screen capabili
ty,
| so I chose to use a later DOS, thus 3.3. The ugly trade-off was that DOS 3.3
| boot floppies don't recognize the ROM C: or RAM D:, so operation is slow
+---------------
Two comments here:
(1) Toshiba sells a modified DOS 3.3 which recognizes the ROM drive. I don't
know if later DOS versions are available from them with this modification.
(2) ANSI.SYS is on the ROM drive, if you want to modify the CONFIG.SYS stored
in NVRAM to use it.
Neither of which addresses the question of whether later NOS versions will
work. I *can* say that I ran the kb7yw_ss version of PA0GRI 2.0f for about a
month, and aside from the usual lack of memory (I only have 512K) and a
tendency to not maintain the date, it worked fine.
++Brandon
------------------------------
Date: Tue, 6 Jul 1993 13:57:53 -0500 (CDT)
From: P.Adisoemarta@ccwf.cc.utexas.edu, N5SNN <yono@ccwf.cc.utexas.edu>
Subject: T1000 nos problems
To: MIKEBW@ids.net (Mike Bilow)
According to Mike Bilow:
>
>I also have a T-1000 laptop, and I was never actually able to get NOS to
>run on it. The error message I received was "Panic: Interrupts were off!"
>My guess was that the laptop was going to sleep, which is not conducive to
>correct operation by communication software.
I never can make a T-1000-SE (newer than the original T-1000)
can work with a NOS (I tried with PA0GRI 2.0m last year).
NOS can run, but after several second it will trash the disk
where the nos was started.
I tried to run both from RAMdisk or disket, both failed and
the disket needs to be reformatted.
I gave up after several evenings trying to fix it and
sell the laptop to the net and now I'm happy with a Compaq Contura.
I'm using the laptop mainly for mobile IP (to grab my mails
using POP from our gateway).
73 de Paulus, N5SNN
paulus@nextover.pe.utexas.edu
yono@ccwf.cc.utexas.edu
------------------------------
End of TCP-Group Digest V93 #173
******************************
******************************