HDTenEightyP/NetNews huggingface dataset:
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Dell support?
Organization: The Gator Conferencing System 219-289-3745 
Date: Sun, 13 Dec 1992 16:18:09 GMT

richard@pegasus.com (Richard Foulk) writes:

>>>What's the current status of support and development for Dell Unix?
>>
>>I talked with Dell support yesterday evening around 6PM EST.  Dell
>>had 3 support gurus on the telephone, and other 2 took off for the
>>day earlier -- so I can assume they have 5 on the phones -- with
>>staggered shifts covering the east and west coasts..
>>

>Didn't they lay some people off or shift them to other tasks some
>time ago?  Or are all the folks that built the initial system with all
>the extra bells and whistles still in place?

I heard that rumor on the net, but never heard anything else.  The unix.faq
mentions a support team of 5, and according to my support call -- they
still had 5.  Now they could have replaced 4 of those, but not the support
person I talked to -- since I've talked to her before (months ago)..

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: SCO automount
Date: 17 Dec 92 21:25:40 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY


  I'm having a bit of trouble getting SCO automount to work. I've set up
automount on SunOS, Dell, and HP-UX, so I'm not without experience doing
this, and I have copied an automount file directly off another system
which works (and verivied that the documentation agrees it should work).

  When I start automount I get no error messages, quick terminate with
exit status 1, and no daemon running.

  If this is just broken I'll give up on it and do a workaround. If
there's some "value added" which keeps standard files from working I'd
like to know what it the workaround is.

  I talked to several other people at the local UNIX User's meeting last
night, and they both agreed that it didn't work, so I am willing to
believe that it's broken, but I'd really like to avoid going out to get
a third party soluution if I don't need to.

  Sorry for posting to the net, but I just don't have the patience to
talk to SCO this month. 
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.sysv386
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: What's Happening to ISC UNIX?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Fri, 11 Dec 1992 16:19:12 GMT

In article <1992Dec10.152342.2185@rwwa.COM>,
 witr@rwwa.COM (Robert Withrow) writes:

| In article <1g61anINN1o6@stp.West.Sun.COM>,
|  karenro@smaug.West.Sun.COM (Karen Rodriguez) writes:
| 
| | When Solaris 2.0 for x86 Platforms is released we will migrate ISC SVR4 users
| | to Solaris for *FREE*!!! If in the mean time the user needs a full development
| | system, we can migrate them to our current SVR3.2 product as well. 
| | 
| | If anyone has any questions regarding their individual situation, they can      contact our TeleSales Dept. Please do identify yourself as an ISC SVR4 user so
| | we can give you the appropriate information. 
| 
| Karen:
| 
| If you will examine <1992Dec9.215101.670@rwwa.COM> you will see that I did
| just that and got completely different information.  This posting contains
| a summary of my conversion with Sunsoft teleservices..

An update:

I have gotten mail from Karen, and a call from Anthony, stating that Anthony
was incorrect about the $195 ``migration'' offer.  She maintains that the
``migration'' will be free.  She also states that only about 5% of the 
purchasers of ISC SVR4 actually registered the product.  I can see that this
would raise a problem in notifying licensees about the migration policy for
those who purchased SVR4 through a distributor.  It seems like Sunsoft could
get the records for those who purchased directly through ISC, however.  I
don't know what proportion of the customers did this...

I wonder if other customers share my ambivalence about this offer:

PLUS:

1) Sunsoft certainly wasn't required to offer this, and (assuming that
continuity of multiuser licensing is maintained), I think that the offer
is generous.

2) Those who use SunOs like it.  This will probably be true of Solaris.

3) Support and quality is likely to be vastly superior to that offered
by ISC.

4) The free migration certainly beats the ``competitive'' upgrades currently
offered by other SVR4 vendors...

MINUS:

1) The development system ``thing''.  Still with the Cygnus/Gnu system
this is not a large minus.

2) Lack of dos merger in the migration.  This means nothing to me, but it
might be important to others.  Besides, considering the price, buying the
new version should not be a big deal.

3) The 8 month lead time.  I think this is a real problem.  Destiny is
available now.  So are other ``improved'' SVR4s.  Is solaris that much
better to be waiting for?

I've followed the bumpy unix road from ``Old'' Microport (rip), to 
BellTech (rip), to Intel(SVR4 rip), to Interactive (SVR4 rip).  Is
Sunsoft next?   Hmmm...
From: jim@visionware.co.uk (Jim Musgrave)
Newsgroups: comp.unix.sysv386
Subject: Pseudo-tty pairs on SCO V.3.2R4
Date: 15 Dec 92 10:28:05 GMT
Organization: VisionWare Ltd., Leeds, UK

Hello everyone,


I have a simple application which has two processes.  One opens the master side
of a pseudo-tty and issues a read.  The other opens the slave side.  The 
master side has the O_NONBLOCK flag set, the read on the master side 
returns 0 when there is no data (EOF?), and 0 when the slave side is closed.

When I issue a select on this file descriptor, it returns implying it is 
readable, when I issue a read, it returns 0.  This somewhat defeats the
object of using select.

How can I tell the slave side has been closed?  

(I have the same piece of code running on Interactive 386ix, read and select
behave as you would expect, thus I can tell when the slave side is no longer
open and I can determine whether there is data available or not)
 
Any ideas?

Jim.
-- 
         VISIONWARE LTD, 57 Cardigan Lane, LEEDS LS4 2LE, England
    Tel +44 532 788858.  Fax +44 532 304676.  Email jim@visionware.co.uk
-------------- "VisionWare:   The home of DOS/UNIX/X integration" -------------
From: bson@gnu.ai.mit.edu (Jan Brittenson)
Newsgroups: comp.unix.sysv386
Subject: Re: UHC SVR4 + ARCHIVE XL  URGENT HELP NEEDED!!
Date: 18 Dec 92 11:38:39
Organization: nil
NNTP-Posting-Host: nutrimat.gnu.ai.mit.edu
In-reply-to: shih@ece.ucdavis.edu's message of 17 Dec 92 20:15:54 GMT

In article <20357@ucdavis.ucdavis.edu> shih@ece.ucdavis.edu (The Nomad) writes:

 > I have UHC Unix SYSV4.0.2 and I bought a Archive XL 9250i.  I install
 > the Archive driver but cannot access the tape drive from OA&M. I try
 > to add device but /dev/rmt/c0s0 does not exist.

   You give us very little info. Did you reboot? Did the installation
procedure successfully rebuild your kernel? Any errors or warnings
during the installation?

						-- Jan Brittenson
						   bson@gnu.ai.mit.edu
--
						-- Jan Brittenson
						   bson@gnu.ai.mit.edu
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: What's happening to ISC UNIX?
Organization: American Micro Group, Ft. Lee  NJ
Date: Sun, 13 Dec 1992 00:02:27 GMT

In article <1992Dec12.001751.16715@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>>>| You know, there were no commercial releases of the ISC
>>>| V4 product, and although Kodak/Interactive promised there would be, but
>>>| no one who bought ISC V4 was told they were getting anything other
>>>| than a pre-release product. 
>>>
>>>This is baloney.  There is nothing in the ISC V4 package that stated that
>>
>>It's not baloney. Every authorized vendor, and ISC themselves, told
>>prospective buyers and were told to tell buyers, that the version
>>of V4 available was a pre-release version. It was tough to miss.
>>If you did miss it...I sympathize.  
>
>... is so! ... is not! ... is so!
>
>My we're adamant today, aren't we.
>
>Assuming it was a pre-release version, that presupposes that a *real*
>version is in the works.  When no *real* version was made available
>a refund should have been made available (unless it was made clear
>at purchase time that it might not happen).
>
>I suspect that any holder of one of these packages wouldn't have too
>much trouble convincing ISC to make good.  A few well-placed letters
>to the right government agencies should do the trick.  After all, most
>states have laws against this kind of thing.
>
>So there!    :-)

Where? Where? Remembering back, which is not necessarily a crystal clear
view, I recall the V4 versions were called "real" developer's releases
but not "real" commercial releases. If that difference is significant
to you, it may not be, the idea was that developers could get a jump
on V4, before its commercial release.

Of course, there is no ISC anymore, as far as PC Unix goes, there is
only the Interactive product and the former employees of Interactive/
Kodak now at SunSoft. 

Do you think SunSoft is legally liable, or morally, for the ISC V4
product, or for continuing it, and that ISC Kodak misled V4 purchasers
fraudulently? Or maybe Kodak is liable for selling the x86 product
to SunSoft?

When people get dead-ended with a product they are likely to be un-happy
certainly, but when you say a "holder of one of these packages wouldn't
have too much trouble convincing ISC to make good," and "most states
have laws against this kind of thing," what does that mean? What would
making good be? And what kind of thing is it here that states have
laws against?

I mean these questions in a nice way, and I'm not trying to anger
anyone--Id like to know what people think SunSoft owe holders of
Interactive V4 licenses and why.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
From: simon@mimosa.unice.fr
Newsgroups: comp.unix.sysv386
Subject: Pb with mounting a remote filesystem
Date: 10 Dec 92 18:21:13 GMT
Organization: University of Nice - Sophia Antipolis, France
NNTP-Posting-Host: mimosa.unice.fr
Originator: simon@mimosa.unice.fr

under Unix SCO when i try to mount a remote FileSystem under SCO with
mount -f NFS remote_host:/usr /newusr
i get the following message :
mount : remote_host:/usr : no such device

i get the same message on the remote_host with
exportfs -a

I think that the problem is coming from the remote host.

Thanx for help

simon@mimosa.unice.fr
From: raymond@es.ele.tue.nl (Raymond Nijssen)
Newsgroups: comp.unix.sysv386
Subject: do SVR4.* SCSI drivers support LUNs ??
Date: 15 Dec 92 09:44:08 GMT
Distribution: comp
Organization: Eindhoven University of Technology, Eindhoven, The Netherlands


We're trying to hook up a second ESDI drive to an Emulex MD21 SCSI<->ESDI
convertor in a system running ESIX 4.0.4. 

This convertor supports 2 ESDI drives while occupying only one SCSI target
address: it uses Logical Unit Numbers (LUNs) to address drive 0 and drive 1.

It seems however that the ESIX SCSI driver does not support any other LUN than
LUN 0 for each target. The scsi disk device names, c?t?d?s?, suggest the
contrary because of the d? field.

Looking at the minor device numbers of the corresponding devices, it 
appears that the format of the minor device numbers is:

......cc.tttssss

Note that this leaves no room for addressing LUNs through minor device
numbers, and what's more, it completely contradicts the format given in eg.
/usr/include/sys/aha.h:

 * the host adapter minor device number is interpreted as follows:
 *
 *           MAJOR           MINOR      
 *      -------------------------------
 *      |  mmmmmmmm  |  ccc  ttt ll   |
 *      -------------------------------
 *      
 *         m = major number assigned by idinstall
 *         c = Host Adapter Card number (0-7)
 *         t = target controller ID (0-7)
 *         l = logical unit number (0-3)


Needless to say, all this leaves me quite confused.

Please help me with this, or should I just forget about using LUNs under SVR4?

-Raymond
--
Raymond Nijssen             | Eindhoven University of Techology
       phone: +31-40-473373 | Department of Electrical Engineering
       fax:   +31-40-464527 | Design Automation Section (ES),  room EH 7.16
"WP is for morons"          | PO. Box 513, 5600 MB Eindhoven, The Netherlands
Newsgroups: comp.unix.sysv386
From: forestie@dxcern.cern.ch (Jean-Philippe Forestier)
Subject: Looking for a card+driver for SCO UNIX
Organization: CERN European Laboratory for Particle Physics
Date: Tue, 15 Dec 1992 08:55:43 GMT

Hi everybody,

We would like to buy a card to be connected to a SCO Unix PC.
This card will be use for data acquisition.
The card must have at least 16 data acquisition lines (with a gain 1-2-5-10),
2 DAC (Digital Analogic Converter) (+ - 10v),
1 paralell input-ouput port,
the data acquisition rate must be around 100 HZ.

What we would like to do is to be able from Unix to communicate with
this (or those) card (s). We would like to be able to select a value 
on a given input line, to specify a gain on the acquisition line, to
read the DACs, to programm the DACs, to programm the timer and the paralell
port.

If you have any idea of the availability of such card and of the corresponding
driver, please let us know.

Many thanks in advance.

Jean-Philippe Forestier

PS: Please respond by email :

forestie@dxcern.cern.ch
From: bmyers@shyguy.lonestar.org (bob myers)
Newsgroups: comp.unix.sysv386
Subject: HELP!!!  can't ping/telnet own SVR4 system!
Date: 11 Dec 92 04:05:51 GMT
Organization: 3-B Technology

'm starting to get into MUDs (Multi-User-Dungeons).  In order for me
to do this on my Consensys V4 (an AT&T SVR4 unix), I need to be able to
telnet back into my own system.  However...

Right now I do not have a WD8003 card (but, I've found a supplier for them).
Since I do not have the WD package loaded, I get the following msg in my
inet.start file in the /tmp directory:


The following commands were run from /etc/inet/rc.inet
/usr/sbin/ifconfig lo0 localhost up
/usr/sbin/ifconfig emd0 shyguy up -trailers
ifconfig: ioctl (SIOCGIFFLAGS): Invalid argument
  
Apparently the last statement above is due to not having the WD driver
loaded up (at least i think?).  

Can anyone tell me what I can do to allow pinging/telnet'ing back into
my own system?  Do I really need to purchase one of the WD8003 cards?

-bob

-- 
-----------------------------------------------------------------
Bob Myers                        | You gotta watch out for those
Shyguy's AT&T SVR4 Unix/Uniboard | shy guys....you never know 
Email:bmyers@shyguy.lonestar.org | what they're thinking..:)
Newsgroups: comp.unix.sysv386
From: dlparker@dlpinc00.rn.com (David L. Parker)
Subject: Re: Tape drive streaming magic for ISC
Organization: Automated Data Management Services
Date: Thu, 17 Dec 1992 01:12:58 GMT

In article <1992Dec14.153909.9982@rocker.uucp> doug@rocker.uucp (Doug Luecke) writes:
>I have recently added a Jumbo 250 tape drive to my 386/40 running ISC 2.0 
>Unix (SVR3), using the Colorado Unix/Xenix tape driver and jtape software.
>The Jumbo 250 is a QIC-80 tape drive that uses 2120 tapes.
>
>Everything works fine except the tape drive doesn't seem to be streaming, 
>causing the backups and restores take from five to ten times as long as the 
>time estimate indicates they should.  (This is also about five to ten times 
>as long as the equivalent backup takes on my DOS machine with the same 
>drive.)  The darn thing spends more time repositioning than reading or
>writing data.
>
>The manual says nothing about tuning the software to get the drive to stream.
>I've tried nice'ing the jtape program with -20, but it made no difference.
>There's basically nothing else going on when I'm doing the backup.
>
>Is there some way to tweak the driver or something magic to do to get the
>drive to stream?  I'd really appreciate any help on this.
>
>doug
>-- 
>Doug Luecke                      UUCP:      uunet!iex!rocker!doug
>Terzon Systems, Inc.             INTERNET:  iex!rocker!doug@uunet.uu.net
>Richardson, Texas                MABELL:    214/234-8222

I'm not familiar of any method of improving the performance of these drives
other than using the TC-15 h'ware compression controller.  If you're running
off the floppy controller, you'll notice a dramatic improvement.  Wish I had
figures to give you, but I no longer run my DJ-20/TC-15 under UNIX, and didn't
save any comparative data.  The FC-10 controller is quite an improvement over
the floppy interface, too, but again, no hard data.
-- 
Dave Parker
Automated Data Management Services, Pleasant Hill, MO 64080-1331
(816) 987-5167/5218 voice/fax     -     dlparker@dlpinc00.rn.com
Newsgroups: comp.unix.sysv386
From: witr@rwwa.COM (Robert Withrow)
Subject: Using Postgres on SVR4?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Thu, 17 Dec 1992 16:48:51 GMT

If anyone out there is/has built/used Postgres on SVR4, I'd like to hear
about your experiences...  Please mail, I'll summarize...

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
From: debra@wsinis07.info.win.tue.nl (Paul De Bra)
Newsgroups: comp.unix.sysv386
Subject: Re: can't write 8 bit chars to printer with Esix 4.0.4
Keywords: Esix, 8-bit chars
Date: 16 Dec 92 12:35:37 GMT
Reply-To: debra@info.win.tue.nl
Organization: Eindhoven University of Technology, the Netherlands

In article <4808@svin09.info.win.tue.nl> debra@info.win.tue.nl writes:
>...
>The problem is that writing chars with the 8th bit set does not work with
>Esix 4.0.4 but does work with AT&T. The patch that was posted some time ago
>to fix the 8th bit problem with uucp and serial lines for Esix 4.0.3
>(replacing a jge by jmp in clist/Driver.o) does not fix the problem.
>...
>Is there a trick to write chars with the 8th bit set to the printer with Esix?

Found the problem, thanks to a pointer from wswietse (Wietse Venema).

The infamous fubyte bug has *not* been fixed in the 4.0.4 version of Unix.
(it was apparently introduced in 4.0.3).

The fix for 4.0.4 is the same as for 4.0.3 but the addresses are different.
Following are the diffs between /etc/conf/pack.d/kernel/vm.o as it should
be (top) vs the vm.o that was shipped (bottom).
The bug is in lfubyte i believe. The problem is that an unsigned char
is treated as signed.

***************
*** 22,28 ****
  	1167c:  85 c0                 testl  %eax,%eax
  	1167e:  75 09                 jne    0x9 <11689>
  	11680:  8b 45 08              movl   8(%ebp),%eax
! 	11683:  0f b6 00              movzbl (%eax),%eax
  	11686:  89 45 fc              movl   %eax,-4(%ebp)
  	11689:  c7 05 d8 13 00 00 00 00 00 00 movl   $0x0,0x13d8
  	11693:  83 3d dc 13 00 00 00  cmpl   $0x0,0x13dc
--- 22,28 ----
  	1167c:  85 c0                 testl  %eax,%eax
  	1167e:  75 09                 jne    0x9 <11689>
  	11680:  8b 45 08              movl   8(%ebp),%eax
! 	11683:  0f be 00              movsbl (%eax),%eax
  	11686:  89 45 fc              movl   %eax,-4(%ebp)
  	11689:  c7 05 d8 13 00 00 00 00 00 00 movl   $0x0,0x13d8
  	11693:  83 3d dc 13 00 00 00  cmpl   $0x0,0x13dc

Paul.
From: pcg@aber.ac.uk (Piercarlo Grandi)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL -> Re: ISC: ESDI & SCSI in one host ?
Date: 18 Dec 92 22:52:11 GMT
Reply-To: pcg@aber.ac.uk (Piercarlo Grandi)
Organization: Prifysgol Cymru, Aberystwyth

On 15 Dec 92 15:33:15 GMT, shane@cs.sunysb.edu (Shane Bouslough) said:

shane> Mark Solsman (solsman@ra.nrl.navy.mil) wrote:

>>       is ISC able to handle ESDI & SCSI devices at the same time ?

: Anyone know if DELL can do the same?  I am intrested in adding a
: second drive, but I want to slowly make the transition to SCSI.

shane> I tried to get my old DOS disk (IDE) to co-exist with my UNIX
shane> SCSI disk to no avail. I don't know about ESDI, but the manual
shane> sure *claims* it's possible.

I will repeat this: yes, you can have SCSI and ESDI/IDE/whatever at the
same time.

No, you cannot boot from a SCSI drive with an Adaptec controller if
there are any other disk controllers; as soon as the Adaptec BIOS sees
that there are other drives configured in the CMOS, it refuses to boot.

So, it's possible, as long as the (first) non SCSI disk is the boot disk.
--
Piercarlo Grandi, Dept of CS, PC/UW@Aberystwyth <pcg@aber.ac.uk>
  E l'italiano cantava, cantava. E le sue disperate invocazioni giunsero
  alle orecchie del suo divino protettore, il dio della barzelletta
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: ISC capabilities
Organization: American Micro Group, Ft. Lee  NJ
Date: Fri, 18 Dec 1992 04:36:21 GMT

In article <9235309.21919@mulga.cs.mu.OZ.AU> pickup@ee.mu.OZ.AU (Simon John Pickup) writes:
>I am hoping to port a commercial graphical application to ISC UNIX,
>probably SVR3, and need the following capabilities:
>
>	X with support for an editable colormap of 256 colours
>		(with appropriate hardware)
>	ANSI C compiler
>	C++ compiler
>
>We hope to use ISC's X, but will it support 256 colours?  Or do we need
>to use a different X server?  And any suggestions for VGA cards?
>
>ISC's LPI C compiler could be ok, but last time I used it, it was very
>buggy.  But I don't think ISC has a C++ compiler?
>
>How about gcc, g++ and libg++, have they been run successufully under SVR3?
>
>Or should we look at SVR4?
>
>Any suggestions appreciated, by email or news.
>
>Simon Pickup
>
>__________________
>Simon Pickup
>pickup@ee.mu.oz.au

There are 256 color 8bit 1024X768 SVGA servers, and there are other
8 bit higher res servers as well.

Liant C++ is available and has the C++/Views Class libraries as well
and gcc. g++, and libg++, don't have to be ported--they compile
just fine as is.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
From: shane@cs.sunysb.edu (Shane Bouslough)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL Filesystem type?
Date: 19 Dec 92 05:19:24 GMT
Organization: Dept of Computer Science, State U of NY at Stony Brook
X-Newsreader: Tin 1.1 PL5

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

: I'm upgrading a customer from Dell to SCO [...]

This sounds backwards to me :-).

: The Golden Gryphon 				gryphon@openage.COM

-Shane

--
Shane Bouslough       | #include <stddisc.h>
shane@sbcs.sunysb.edu | #include <happy.rhodes>
Xref: sparky comp.unix.sysv386:17455 gnu.misc.discuss:4003
From: steve@prd.co.uk (Steve Blinkhorn)
Newsgroups: comp.unix.sysv386,gnu.misc.discuss
Subject: groff for sysv386
Summary: Binaries wanted for groff
Keywords: groff,ISC
Date: 16 Dec 92 17:23:38 GMT
Organization: Psychometric Research & Development Ltd


Does anyone out there have binaries for groff that will run under ISC
2.0.2?  Getting g++ going is on my list, but getting [tg]roff to print
via Postscript is much more urgent.   Thanks in advance for any offers
or pointers.   Replies by email please to steve@prd.co.uk.

---
Steve Blinkhorn (steve@prd.co.uk)
Newsgroups: comp.unix.sysv386