home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
pmnos11x.zip
/
readme.now
< prev
next >
Wrap
Text File
|
1993-09-19
|
4KB
|
82 lines
PMNOS -ver 930901 aka 1.1
Ok Folks, here it is. (Wheew)
I am including PMail since some users have reported problems that have been fixed.
Some bbs or ftp site is distributing an older version. I know there is a problem with some
of these sites distributing OS2NOSV4, which does not work under OS/2 2.1.
**************** For you new comers or others that might be interested ************
**************** PMail users perhaps ought to set this up ************************
I am including a "view"able intronos.inf, think of this as online nos documentation.
you can either type view intronos, from the dir that intronos.inf is in or,
create a new program object, set the name to view.exe and the command line to
x:\where\ever\it\is\intronos. This will create a permenant nos information reference
on your desktop. Note, this does not represent the ultimate in NOS documentation,
that would be difficult to do since it is such a moving target.
************************************************************************************
This represents my final version of NOS (as you know it)!!!!!!! Really, this is it!
I have fixed alot of bugs, both from my previous versions as well as those currently in the DOS
versions. The fact that the a DOS program doesnt program check doesnt mean its using valid
pointers.
Added stuff:
Split screen
Proper echoing/no echoing (well thats more a bug fix I guess).
Font management, for those with lower resolution screens you can now change fonts.
if you have high resolution screens you can still change fonts.
This version is loosely based on jnos 106. It is more like a 106 plus given the fixes made
that probably arent in the DOS versions. I am including txt from the jnos files that cover
fixes he did as well as mbox commands. Unfortunately they are from 107 so they might not all
apply.
nos.ini, that remembers the state of nos (kindof) over sessions.
state of means position, size and font, it doesnt restart sessions.
...
Control characters are now transmitted.
...
PMNOS is now fault tolerant, meaning that what users occationally saw as pmnos simply
disappearing wont happen. A msg will be provided that will state what PMNOS was doing
and where it took the exception. Users can then either fix the problem, ie a broadcast timer
with no broadcast text or avoid the problem code by not using that service.
...
I have included bootp and bootpd code. Refer to bootp documentation elsewhere for
a description of using this feature.
...
I know there's more, but they elude me at present.
I will be including the source for this version, it will most likely be called
PMNOS11S - s for source, as opposed to PMNOS11X - X for executables and doc,
So, have fun with it and good luck. I will see you all when I resurface with V2.
I hesitate to call it pmnos v2, 1 it wont be based on PM, per se and NOS is not
a good name, it implies a network operating system, which it isnt. Besides, nos has pretty
much come to mean Phil Karn's implementation of Berkeley tcp/ip, and my v2 wont be
based on Phil's code and perhaps not too much on UC Berkeley.
Should any thing major come up I can be reached via internet at kz1f@legent.com
or on CIS as 71204,1555.
One note: the main holdup on this release has been the operator page cmd.
This kinda works now but may force PMNOS into a loop upon exit. This may simply be
a result of testing it locally, it may work from a remote user. In the event it doesnt,
dont use it. I have spent several weeks working solely on it and frankly
I am tired of working on it. Tell your packet friends to use nos. The problem is not
with ttylink, that works fine, as does the mailbox proper and ax25 emulation.
Oh, Jack asked me to mention this. really observant people may notice that ping
takes a rather long time on a one shot or first in the series. This is not really
a bug, at the point in time when the icmp echo request gets set up, PMNOS is doing
that, servicing the other 20 task (or those that need servicing) building a PM win-
dow for the session, and later knocking it down. Plus starting up 2 subtasks
to handle the ping and responses. So there is a bit of a delay between when the
current time is put in the ICMP record and when the request actually gets out the
door. Non first pings will be accurate. I hope that helps explain it.