HDTenEightyP/NetNews huggingface dataset:
From: pizzi@nervous.com (Riccardo Pizzi)
Subject: looking for color Xterm (X11R5)...
Followup-To: poster
Reply-To: pizzi@nervous.com (Riccardo Pizzi)
Organization: The Nervous XTC Public Access Unix System, Rimini, ITALY
Date: Thu, 05 Nov 92 14:20:34 GMT

Hi there!
I remember, some time ago, an xterm capable to displaying ANSI colors much
like a normal 386/486 unix console would do... I am desperately seeking
such beast in order to compile it here under X11R5 (ISC 2.2.1/SVR3).

Does anybody know where to get it (maybe via ftp) ?

Many thanks in advance,

Rick
-- 
Riccardo Pizzi @ the Nervous XTC Public Access Unix System, Rimini, ITALY
E-Mail -> pizzi@nervous.com        <*>      Bang-path -> uunet!nervous!pizzi
Nervous XTC, the home of the UniBoard package * Data: +39-541-27135 HST/PEP/V32
Xref: sparky comp.unix.sysv386:16267 comp.unix.bsd:8490 comp.os.mach:1520 news.answers:3842
From: shj@login.dkuug.dk (Stig Jacobsen)
Subject: Re: ISC 3.0: Where did user rlogin/telnet from!?
Keywords: isc,telnet,rlogin
Organization: Asis Electronic Intl., Copenhagen, Denmark
Date: Thu, 12 Nov 1992 16:29:20 GMT

andy@homebase.vistachrome.com (Andy Finkenstadt) writes:

>>After logging into an ISC system via rlogin/telnet, how do I find
>>out the IP-address from which the rlogin or telnet originated? 

>>Any ideas? I need it to set the terminaltype automaGically for
>>terminals that won't respond to the ANSI inquire string.

>Perhaps I'm stupid - but when I rlogin/telnet across the network between
>Sun and ISC and vice versa, my current TERM variable comes with me.

I'm happy to tell you that you're not stupid :-)  It is so that
the rlogin/telnet software I'm using, does not look at the TERM
variable and does not pass it on to the remote host.

So I'm still looking for a way to get to the IP-address..
--
Stig Jacobsen
shj@login.dkuug.dk
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
From: fr@compu.com (Fred Rump from home)
Subject: Re: Everex Step MP anybody?
Organization: CompuData Inc.
Date: Fri, 13 Nov 1992 09:23:09 GMT
Keywords: MP

gryphon@openage.openage.com (The Golden Gryphon) writes:

>john@jho.com (John Ho) writes:

>>Anybody has experience with the Everex Step MP multi-processor
>>486s running SCO-MPX software?

>us out the door.  Now it looks like the whole project is going to hell in a
>hand basket.  I would recommend you look elsewhere for MPX boxes.  There are a
>lot of them like the Compaq and DEC machines that are better.

Just for information - we are installing a 250 user Altos 15000 on Monday in 
NY. I think this 8 Gig SCO UNIX box would kick both the Compaq and DEC 
machines into smithereens. But then Altos may not have the required label on 
the box, it simply screems symmetrical performance.

fred
-- 
W. Fred Rump 	office:	   fred@COMPU.COM     'mans feet have grown/so big 
26 Warren St.   home: fred@icdi10.compu.com  that he/forgets his littleness'
Beverly, NJ. 08010                          		Don Marquis 
609-386-6846    bang:uunet!cdin-1!icdi10!fr
From: tim@rri.UUCP (Tim Buck)
Newsgroups: comp.unix.sysv386
Subject: Re: Latest Fixdisk for ISC3.0
Date: 6 Nov 92 03:25:04 GMT
Organization: Recognition Research Inc., Blacksburg, VA

In article <Bx4FsG.Dv@maxed.amg.com> ed@maxed.amg.com (Ed Whittemore) writes:
>
>Just upgrade to 3.01. It's only $95.
>-- 
>Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
>American Micro Group, Inc.   201-944-3293

Can someone post a list of things that ISC 3.01 fixes from ISC 3.0 so I
can decide how important it is to upgrade?  Thanks.

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
 Borger King:  Special orders are irrelevant. You will have it our way.
From: berger@castor.cs.uga.edu (Chilli Willi)
Newsgroups: comp.unix.sysv386
Subject: TCP/IP and NetBIOS under SCO ODT 1.0
Keywords: TCP/IP, NetBIOS
Date: 12 Nov 92 19:41:50 GMT
Organization: University of Georgia, Athens
Originator: berger@castor

I am trying to use SCO for a gateway in my network to bridge between
NetBIOS and TCP/IP Ethernet networks.   I have a server process on my
SCO box which takes requests from TCP clients, calls other server processes
on the NetBIOS side of things, and returns results to the TCP clients.

I am attached to one network full of NetBIOS nodes and one network full
of TCP nodes.  I am using two 3COM EtherLink boards.  Everything seems to
work fine with the TCP network, including FTP, Telnet, and my program with
its socket calls.  However, I am unable to make a NetBIOS connection.  I
can successfully add a network name, but my "call" always fails.

Has anyone used TCP/IP and NetBIOS simultaneously on their SCO box?  I
specify that I want to use TCP with a particular network card, but I can't
seem to find out how to tell NetBIOS to use the second card.

Any help would be most appreciated, and could even earn you a complete set
of Desert Storm trading cards.  Please send reponses to michael@infoman.com.
Thanks in advance for your help.

Willi Berger
willi@infoman.com
Newsgroups: comp.unix.sysv386,comp.windows.x,comp.windows.open-look
From: smith@compound.se (Bjorn Smith)
Subject: SVR4 system hangs when running XView3 !?
Organization: Compound Systems AB
X-Newsreader: Tin 1.1 PL5
Date: Thu, 5 Nov 1992 07:53:30 GMT

We have successfully compiled and installed XView3 (as from the X11R5 contrib
tape) with the following patches:
-rw-rw-rw-   1 smith    other      37426 Oct 19 07:54 xview3.diff.01
-rw-rw-rw-   1 smith    other        949 Oct 19 07:53 xview3.diff.02
-rw-rw-rw-   1 smith    other       1218 Oct 19 07:53 xview3.diff.03
-rw-rw-rw-   1 smith    other        745 Oct 19 07:53 xview3.diff.04

The environment is USL SVR4.0.3 (Consensys) and X11R5 pl17 + XFree86-1.1.diff.

Everythings seems to work fine but after a while the system freezes !?
(The pointer cannot be moved av the X386 server cannot be restarted.)
Only pressing reset button on the machine helps.

Has the problem been observed elsewhere ?
Are there any other patches that should be applied ?

Many thanks in advance for any kind of help !

-- 
Bj|rn Smith	Compound Systems, phone +46 8 7923689
UUCP:	 	{uunet,mcsun}!seunet!comsys!smith
Domain Address:	smith@compound.se
Newsgroups: comp.unix.sysv386
From: dmq6899@tamsun.tamu.edu (D. Querin)
Subject: Help with Modem on ttymon with IPC
Organization: Texas A&M University, College Station
Date: Thu, 12 Nov 1992 00:44:46 GMT

I am attempting to install an indial modem on an ATT Starlan
with SVR4/2.1.  The configuration includes IPC (intelligent
port connector I believe) branches.  These branches are using
10 pin modular.  There seems to be a problem between the modem
and the IPC.  However, I have successfully hooked a terminal
and a notebook up via a modular->serial connector.  The modem
just will not fly.  If anyone could give me some input here,
I would much appreciate it!  Thanks.

-David
 dmq6899@tamsun.tamu.edu

/* this is for my own good.  the previous was my opinion. */
From: lenneis@statrix1.wu-wien.ac.at (Joerg Lenneis)
Newsgroups: comp.unix.sysv386
Subject: Re: DTK BIOS/Chipset systems...
Date: 26 Oct 1992 16:15:36 GMT
Organization: University of Economics and Business Administration Vienna
Distribution: usa
Reply-To: lenneis@wu-wien.ac.at
NNTP-Posting-Host: statrix1.wu-wien.ac.at

In article <Bw8yJw.Ayn@booth.uucp>, roger@booth.uucp (Roger Abrahams) writes:
|> In article <1569@b1.babss.UUCP> wadswort@babss.UUCP (John H. Wadsworth) writes:
|> >In article <1992Oct09.174320.11511@attics.rn.com> rdr@attics.rn.com (Dean Riddlebarger) writes:
|> >>For 386 UNIX and/or Windows 3.1 installations, has anyone noticed any
|> >>major compatibility problems with systems based on the DTK BIOS and
|> >>chipset?  Especially 486 machines?
|> >
|> >There have been some problems with dtk machines. Usually they are fine
|> >for dos but may be flaky when pushed to run windows or unix-like os's.
|> >I prefer to use Technology Power motherboards.
|> 
|> Well, I keep hearing this, but my DTK FEAT-3331 33mhz 486 doesn't seem
|> to agree.  There may have been a time when this was true.  DTK was one
|> of the first companies to start designing ALL their stuff in Taiwan,
|> founded about 1980.  Certainly there have been machines in the past 
|> that were problematic, the 20mhz 386DX KEEN-2000 comes to mind, but
|> current DTK machines run various flavors of Unix just fine.
|> 
                        < stuff deleted >

I am currently looking into clone PCs and also have an offer for a
DTK machine (FEAT 5031, 50 MHZ 486). Prompted by the remarks in the 
386 buyers guide I tested this machine in the following configuration:
8 MB Ram, DTK Bios, Symphony chipset, 120 MB IDE harddisk, Tseng ET4000 video 
controller, WD8003 ethercard plus, Microsoft mouse. I installed ISC Unix 3.2
version 2.2. I left the machine running overnight copying files over the network,
doing screen updates and pinging it from various other machines. The only 
problem I encountered was the initial setup for the WD8003. It was jumpered to
use interrupt 3 which is also used by the second serial port. This worked
fine for OS/2 2.0 (which I also installed successfully) but not for Unix. After 
changing to interrupt 5 the problem went away. After that I did not run into
any other problems. I also installed and ran X386 1.3E. OS/2 2.0 ran 
okay as well. So, to conclude, they seem to have got their act together with 
respect to the motherboard problems mentioned in the 386 buyers guide.  

-- 
Joerg Lenneis

University of Economics and Business Adminstration
Department for Applied Statistics and Data Processing
Augasse 2-6, 1090 Vienna, Austria

Tel. *43/222/31336 4758
email: lenneis@wu-wien.ac.at
Newsgroups: comp.unix.sysv386,biz.sco.opendesktop
From: steveh@zentronics.ca (Steve Haller)
Subject: Re: Problems with fsck root disk
Organization: Zentronics Head Office, Mississauga, Ontario, CANADA
Distribution: comp
Date: Thu, 12 Nov 1992 18:51:12 GMT

In article <1992Nov11.024057.22835@cognos.com> maklinm@cognos.com (Max Maklin) writes:
>I have recently down an upgrade (not an install) from 
>ODT 1.1 to ODT 2.0.  I was running Digital's enhanced
>MPX (DEC MPX 1.2) and upgraded to SCO MPX 2.0.  This
>update was applied to an applicationDEC 433MP.
>
>Everything seemed to go well, except the machine hangs
>just before printing out the maintenance mode prompt.
>I believe this is where it issues an fsck /dev/root.
>If I hit DELETE (SIGINT key) I finally do get the prompt.
>The problem is that I can not fsck the root disk.
>
># /etc/fsck -b  /dev/root
>
>just hangs.  No wonder I am hanging on reboots.  The
>device entry for the root disk is:
>

Max, see my previous posting (just posted) about an ODT 1.1 --> ODT 2.0
upgrade I did on a 433MP where the root disk was on the CPU SCSI 
and not on the adaptec.  

Hope this helps.
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Haller           steveh@zentronics.ca / uunet.ca!zentron!steveh
Systems Engineer,      Zentronics Toronto,  "Authorized SCO APC"
Tel: (416) 507-2600
Newsgroups: comp.unix.sysv386,biz.sco.opendesktop
From: maklinm@cognos.com (Max Maklin)
Subject: Problems with fsck root disk
Organization: Cognos Incorporated, Ottawa CANADA
Distribution: comp
Date: Wed, 11 Nov 1992 02:40:57 GMT

I have recently down an upgrade (not an install) from 
ODT 1.1 to ODT 2.0.  I was running Digital's enhanced
MPX (DEC MPX 1.2) and upgraded to SCO MPX 2.0.  This
update was applied to an applicationDEC 433MP.

Everything seemed to go well, except the machine hangs
just before printing out the maintenance mode prompt.
I believe this is where it issues an fsck /dev/root.
If I hit DELETE (SIGINT key) I finally do get the prompt.
The problem is that I can not fsck the root disk.

# /etc/fsck -b  /dev/root

just hangs.  No wonder I am hanging on reboots.  The
device entry for the root disk is:

br--r-----   1 root     backup     1, 40 Oct 29 17:49 /dev/root

The idea of not being able to fsck my root disk does not sit
very well with my stomach.  Note that the system runs fine otherwise,
at least for now.

Max
-- 
Max Maklin                                                P.O. Box 9707 
Technical Analyst	                           3755 Riverside Drive
Cognos Incorporated                              Ottawa, Ontario CANADA
Internet: maklinm@cognos.COM                 UUNet: maklinm@cognos.UUCP
Newsgroups: comp.unix.sysv386
From: mikebo@timesink.chi.il.us (Michael Borowiec)
Subject: Re: ISC 3.0 multiple FDISK partitions?
Organization: HAM Radio Station N9EUZ, Naperville, IL
Date: Thu, 12 Nov 1992 06:23:26 GMT

In article <BxKEKD.v0@ad4su1.rsre.mod.uk> druid%caercn@ajax.rsre.mod.uk (ad4su1) writes:
>On my hard disk I have three *real* partitions---i.e., created with FDISK.
>The first is for DOS, the second for ISC 3.0, the third is spare.
>I would also like to use the third partition for ISC, as a home partition.
>
>Is this possible?

Yes, use /dev/dsk/0p3

>
>It seems to me that ISC only ever looks at the first UNIX partition,
>which it divides into several of what it calls partitions. I am not
>able to re-FDISK at this stage and thus merge the second and third
>partitions.
>
>Can anyone suggest how I can make use of my third partition from UNIX?
>
>	Regards and thanks,
>		Mark.

Here is the poop on using DOS fdisk partitions in ISC UNIX >= 2.2 from
the 2.2 release notes:
/dev/dsk/...
np0	Entire physical drive n
np1	1st fdisk partition on drive n
np2	2nd "
np3	3rd "
np4	4th "
np5	1st extended DOS partition on drive n
np6	2nd "
... etc, etc, through
np15	11th extended DOS partition on drive n

Additional info:
ns0	Entire UNIX system partition on drive n
	(not the entire disk as it meant in 1.x releases of 386/ix)
ns1	1st "soft" UNIX partition in the UNIX fdisk "hard" partition
	(usually root)

The spec changed from 2.2.x to 3.0.x in that:
/dev/dsk...
c0d0s3	<= 2.2.x syntax for Controller 0, Disk 0, Slice 3 (usually /usr)
c0t0s3	>= 3.0.x syntax for Controller 0, Target 0, Slice 3

I had configured my 2nd fdisk partition as a 64MB DOS partition. Since
I didn't need it as a DOS parition any longer, I simply did a mkfs,
labelit and mount and, voila... I have a new 64MB UNIX partition I
mount as /dev/dsk/0p2. Works like a champ... 
- Mike

PS> Get 3.0.1 or 3.0 Update disk FD3.0S.3 to be able to mount DOS 4/5
    (or Compaq DOS 3.31) partitions greater than 32MB under UNIX like:
    mount -f DOS /dev/dsk/0s? /dos

--------------------------------------------------------------------------
Michael Borowiec  -  HAM Radio Station N9EUZ  -  mikebo@timesink.chi.il.us
  >>> Dedicated to the Pursuit of Computer Assisted Time Dissipation <<<
The Timesink Organization  -  121 Thrush Lane  -  Naperville, IL 60540 USA
--------------------------------------------------------------------------
From: duane@intermec.com (Duane Charron)
Newsgroups: comp.unix.sysv386
Subject: Help on ISC 3.2 v301
Date: 5 Nov 92 01:27:04 GMT
Article-I.D.: intermec.1979
Reply-To: duane@intermec.com ()
Distribution: world
Organization: Intermec Corporation, Everett, Wa.


 Hello Net,

  I have ISC and am trying to get it up to full potential.  I have
had numerous problems with it, and boy am I getting frustrated!  The
latest problem is my Kconfig Program won't run!  it keeps getting a
memory fault and then core dumps when I try to save the paramaters
when I change something.  It appears it saved everything, but when
I try to build it, the System Chokes.  Sunsoft Tech support had me
reinstall the Kconfig Program.  This changed all of my Tuneable
params, and now I am getting kernel panics.  Also My looking glass
License server keeps getting a "Broadcast Not Received" error and
exits.  It appears I might have to reinstall my system from scratch
again!!    H E L P!!!

				Duane
Newsgroups: comp.unix.sysv386
From: kevin@kosman.uucp (Kevin O'Gorman)
Subject: Got SAS working on ESIX
Organization: Vital Software Services, Oxnard, CA
Date: Thu, 12 Nov 1992 18:33:48 GMT

I got SAS (Streams Asynchronous Solution, a freeware goodie) working on
my ESIX 4.0.3 system.  It was mostly easy.  Just one gotcha.

I have been using a Telebit 2500 for my UUCP work.  The way things were
set up, using the FAS driver, I set the 2500 with s131=2, to have carrier
on all the time.  This defeated the two-device method of handling
bidirectional lines, because the getty open would complete immediately.
No sweat, so I set s131=1, for a more normal behavior from the modem.

Still, the UUCP chat script would fail at the point early on where it
would set CLOCAL, to ignore carrier during the dialing sequence.  This
had never caused trouble before, so I had not changed it.

I have no idea why, but it turned out to be necessary to take the \M
out of the Dialers file.
-- 
Kevin O'Gorman ( kevin@kosman.UUCP, kevin%kosman.uucp@nrc.com )
voice: 805-984-8042 Vital Computer Systems, 5115 Beachcomber, Oxnard, CA  93035
Non-Disclaimer: my boss is me, and he stands behind everything I say.
Newsgroups: comp.unix.sysv386
From: aburt@mnemosyne.cs.du.edu (Andrew Burt)
Subject: 9-track SCSI tape drives?
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Fri, 6 Nov 92 18:19:15 GMT

I'm in need of a 6250bpi 9-track tape drive for my Dell (never mind
how disgusting they are -- it's how the data will be coming, off an
IBM mainframe).  Dell has no clue what (if anything) will work with their
scsi tape driver... (SCSI seems the way to go on this, since the drive may
eventually be moved to a non-intel platform).

Surely someone must have faced this out there?

Anything relating to any kind of 9-track on an intel SVR4 platform
is probably relevant, if you know anything...
-- 

Andrew Burt 		   					  aburt@du.edu

      "And that, my liege, is how we know the Earth to be banana-shaped"
Newsgroups: comp.newprod
From: manbir@softwords.bc.ca (Manbir Prihar)
Subject: CoSy Conferencing System with CoSyPlus GUI
Followup-To: poster
Keywords: cosy conferencing cosyplus gui
Organization: Softwords
Date: Tue, 10 Nov 1992 19:25:42 GMT

                             PRODUCT ANNOUNCEMENT
                 * * * * THE COSY CONFERENCING SYSTEM * * * *  
                                    from
                     Softwords Research International Ltd.

The CoSy Conferencing System, one of the most widely used and powerful
conferencing systems in the world, is now available through Softwords
Research of Victoria, B.C., Canada.

Originally developed in 1984, CoSy enjoys the commercial support of a
professional software house.  CoSy has clients in Europe, Asia and North
America and literally tens of thousands of users access CoSy sites
worldwide.  Byte Information Exchange, CIX (U.K.), MIX (Japan), Telecom
Finland, NSA (a Division of British Telecom) are examples of major CoSy
sites.  

In the past three years, Softwords has set up businesses who have
discovered the benefits of electronic conferencing for client support,
office communications, marketing, product development, employee training,
and conferencing's unique ability to bring physically remote offices
together.

So what makes CoSy unique? 

  - Professional support for installation and on-going upgrades

  - A powerful conferencing system that has been refined over the past
    eight years

  - A full mail system built into CoSy for one to one messaging

  - System managers routines for in-house maintenance

  - Graphical User Interfaces with serial or TCP/IP connectivity 

  - GUI's are available for MAC, DOS and Windows systems

  - GUI's with a built-in communications package and full screen editors  


If you would like to take a look at CoSy, and discover how it can benefit
your office or help you deliver courses, e-mail Softwords at:

          blair@softwords.bc.ca

or phone us at: +1 (604) 727-6522

or fax us at:   +1 (604) 727-6418

We can arrange to provide you with an account on our CoSy system, and send 
you a demonstration copy of our Graphical User Interface, CoSyPlus.


See how the CoSy Conferencing System will be your next step in electronic
messaging.
-- 
Manbir Prihar
Senior Systems Analyst
CoSy Conferencing Systems                 //     manbir@softwords.bc.ca
Newsgroups: comp.newprod
From: edeline@ans.net (Edeline Cantave)
Subject: ANS CO+RE EXPANDS FAMILY OF SECURITY SERVICES
Followup-To: poster
Organization: Advanced Network & Services, Inc. - Elmsford, NY
Date: Tue, 10 Nov 1992 19:23:31 GMT

Contact:  Susan Eldred
	  eldred@ans.net

		ANS CO+RE EXPANDS FAMILY OF SECURITY SERVICES

	Elmsford, NY . . . . . ANS CO+RE Systems, Inc., has announced
that it is expanding and enhancing its InterLock family of IP network
security services.  InterLock (a servicemark of ANS CO+RE) is an array
of application-level security services that controls all network
access between the Internet and a private IP network and/or between
segments of an organization's private IP network.

When InterLock was introduced in October 1991, it was comprised of
security-enhanced versions of TELNET, file transfer protocol (FTP) and
simple mail transfer protocol (SMTP) services.  With the most recent
announcement, InterLock services now include security-enhanced
versions of X window system and network news transfer (NNTP)
protocols, plus the support for end-to-end encryption on all services.
The encryption is based upon DES, and it is available between two or
more InterLocks.

Access to each of the InterLock services is controlled via a rules
base, which is configured by the InterLock administrator at the
enterprise network's location.  Use of a particular service, including
encryption, can be granted or denied based on any combination of
userid, time of day, day of the week, private/public network address
and private/public host address criteria designated by the
administrator.  Once a user is authenticated, communication to and
>From both sides of the InterLock occurs transparently.  Each service
provides login tracking, audit and reporting features.

InterLock services are not only effective, they also are easy to
integrate into a private IP network, because ANS CO+RE designed them
as a true turnkey package.  Installation of hardware and software is
provided to the customer, as is the initial configuration of services
and 24-hour-a-day, seven-day-a week maintenance and support.  ANS
CO+RE also offers training for InterLock administrators.

InterLock services are leased on a yearly basis; prices range from
$18,500-$29,000, based on the configuration of services selected.  The
enhanced version of the InterLock family will be demonstrated at this
week's InterOp conference and will be available November 30.

For more information contact info@ans.net
Newsgroups: comp.newprod