HDTenEightyP/NetNews huggingface dataset:
From: jonr@bigsky.dillon.mt.us (Jon Robinson)
Newsgroups: biz.sco.general
Subject: Re: 3.2 4 system reports 3.2 2
Date: 31 Aug 92 14:35:37 GMT
Article-I.D.: bigsky.1992Aug31.143537.4682
Organization: Big Sky Telegraph
X-Newsreader: Tin 1.1 PL5

Geoffrey Welsh (geoff@zswamp.UUCP) wrote:
: mike@pacsoft.com (Mike Stefanik) writes:
: 
: > In an article, geoff@zswamp.UUCP (Geoffrey Welsh) writes:
: > >[...] but why does SCO UNIX SysV R3.2v4 report that it is SysV R3.2v2?
: > 
: > If it's so important to have the correct version number, then by all
: > means, change it yourself (an exercise for the determined reader :-)
: 
:    I'm curious more than anything.
: 
:    Also, it reports i386, even when running on a 486.

Ok, here's how I understand it (anyone feel free to correct me).
It's reporting 3.2.2 because it's OFFICIAL release (meaning AT&T/UNIX)
is 3.2.2, it wouldn't matter if SCO chose to name it SCO UNIX 9.3.7,
as long as it is based on the UNIX release named 3.2.2, that is what
it will report.  (unless you change it like Mike suggests).

Likewise, the OFFICIAL AT&T/UNIX labs release was designed for, ported
to, or otherwise officially designated as being for the Intel 80386
chip.  That you run the i386 version on a 486 isn't important.

Hope this helps.
-jon

-- 
Jon Robinson @ Big Sky Telegraph       "Sometimes yes, sometimes no.  
Western Montana College of the         The staff usually forgets." - Fletch
University of Montana, Dillon MT                    
INTERNET: jonr@bigsky.dillon.mt.us     Disclaimer:  Don't blame my employer,  
VOICE:406-6837870 /FAX:406-6837493     my fingers are the guilty party.
From: cronejp@bnr.ca (Jonathan P. Crone)
Newsgroups: biz.sco.general
Subject: Re: ODT Dos Merge
Date: 2 Sep 92 16:03:45 GMT
Organization: Bell Northern Research
X-Xxdate: Wed, 2 Sep 92 17:06:05 GMT
X-Useragent: Nuntius v1.1.1d9

Subject: ODT Dos Merge
From: xenitec.on.ca News Administrator, news@xenitec.on.ca
Date: Sun, 30 Aug 1992 10:43:01 GMT
In article <1992Aug30.104301.14225@xenitec.on.ca> xenitec.on.ca News
Administrator, news@xenitec.on.ca writes:
>I just started to use Merger under ODT 2.0.  I would like COM2 to appear
>as /dev/ttyac.
>
>I looked it up in the manual.  I disabled the /dev/ttyac, I changed the
>chmod to 666, and then I did
>
>
>Script started on Sat Aug 29 11:56:19 1992
># dos +acom2[=/dev/ttyac]
>TOKEN_NF: dos: ERROR: Could not find token 'com2[' of the needed type.
># 
>script done on Sat Aug 29 11:56:44 1992
>

You're using the [], don't....

dos +acom2=/dev/ttyac

>
>I am trying to assign COM 2 to /dev/ttyac, could someone tell me what I
am
>doing wrong?
>
>I want to use PCPlus and I need to use com2, the mouse is on com1 and the
>mouse is working under merge.

I think that you'll find that you're out of luck... Unless I'm misreading
the situation, it looks like you're trying to map a multi-port
card serial port to a COM device in Merge....

(what specifically is your multiport card? ( it sure looks like the 
tty mapping for a Consensus PowerPorts...) )

I've been trying to do this for a week with Merge and a Digiboard,
and finally found out from SCO that its because they didn't get
the developer documentation out to the multiport vendors that
they need to support additional IOCTL calls in the serial
card driver to allow merge to attach to the serial port....

(for example, a digiboard supplies ttyi1a through ttyi1d on my 
four port card.... any attempt to mount the port

dos +acom2=/dev/ttyi1a  

would fail with the VM86 process dying, and with Merge
complaining that it couldn't initialize /dev/vcom2=/dev/ttyi1a .
(INIT_DEV_FAIL was the return from DOS) 

I've asked Digiboard when I can expect this to be working....  I
have hopes, but not great expectations...

(Yes, the card works perfectly from the Unix side of operations.) 


>
>I am doing this from the root prompt as well.
>

Doesn't matter from whether you use the root id or a regular user, its
toast... 


>thanks.
>
>steve
>

Good luck...

JpC

Jonathan P. Crone	613-763-8624	Fax 613-763-2803	ESN:393-8624
BNR Audio Conformance			cronejp@bnr.ca
BNR pays me to design and test telephone systems, not to have a
net.opinion.
Newsgroups: biz.sco.general
From: dean@world.std.com (Dean S Banfield)
Subject: Timeouts in TCP/IP processes
Organization: The World Public Access UNIX, Brookline, MA
Distribution: biz
Date: Thu, 3 Sep 1992 18:38:18 GMT

Hi,

We are running SCO TCP/IP runtime 1.1.3 and are suffering long delays in 
initiating TCP/IP socket connections.  This happens to my Telnet users when
logging in and to inbound SMTP mail.

My Telnet users just wait about 1 min and eventually get a prompt, then log
in.  When SMTPD is fired up by inetd to service the inbound mail request
poor smtpd just times out before it really can get started.  Inetd just fires
up another one because there is still an outstanding mail request.

The problem seems to reside in the named nameserver.  When it is not running
access is quick.  Is there a bug fix for named?  We are getting the upgrade
to TCP/IP 1.2.0 (our supplier assures us that there IS a bug).  While I
wait, is there any way to let smtpd be more lenient.  There are NO man pages
on smtpd!

Thanks.

-dean
-- 
Dean S. Banfield			Voice: (203) 656-1500
Real Decisions Corporation		FAX  : (203) 656-1659
22 Thorndal Circle			email: dean@world.std.com
Darien, CT 06820
Xref: sparky biz.sco.general:3075 comp.mail.headers:271
From: ronald@gate.demon.co.uk
Newsgroups: sanet.list.sco,biz.sco.general,comp.mail.headers
Subject: Re: Reply receipt from MMDF
Date: 28 Aug 92 11:23:51 GMT
Distribution: sanet
Organization: Demon Internet Services.
X-Conv: Automatic mail-->news conversion at olsa99


john@chance.gts.org wrote:

> Write a script to generate return receipts, and put it in the global
> maildelivery file

As far as I can remember, SCO MMDF deconfigured the system deliver file.

Really, MMDF needs at least the "link kit" approach -- supply ld -r'd
binaries and link them on installation so I can diddle the things in conf.c.

--
Ronald Khoo <ronald@demon.co.uk> <ronald@ibmpcug.co.uk> <ronald@robobar.co.uk>
BTNet: +44 71 229 7741                    | Brambles are the order of the day.
From: paul@openage.COM
Newsgroups: sanet.list.sco,biz.sco.general
Subject: RE: FOXPRO FOR SCO WHEN????
Date: 24 Aug 92 22:59:14 GMT
Distribution: sanet
Organization: [resent by] The SCOGEN gateway and Propagation Society
X-Conv: Automatic mail-->news conversion at olsa99




>Has anyone heard when FoxPro for SCO Unix might ship.  I have had
>many customers interested, but there is no news of availability.

>Microsoft purchased FOX and I wonder if it will ever be a real
>product for SCO users.


I called the 800 number for Fox and MS after the merge.  I never got a reply.
The rumor I heard is that Foxpro for SCO is dead.  Qbase is out.  Does anyone
have any info on that?

--------------------------------------------------------------------------------
Independent SCO support and service provider in the D.C. metro area.
No Incumbents in '92. Get the crooks out of office. Vote & Send a Message
Paul A. Fischer           | Open Age Inc.  | paul@openage.com
Sr. UNIX Sys. Consultant  | (301) 948-6422 | (301) 948-9644 Fax
From: fengstad@alpha.uleth.ca
Newsgroups: sanet.list.sco,biz.sco.general
Subject: Re: FOXPRO FOR SCO WHEN????
Date: 25 Aug 92 00:13:11 GMT
Distribution: sanet
Organization: University of Lethbridge
X-Conv: Automatic mail-->news conversion at olsa99


In article <9208241859.aa06135@openage.COM> paul@openage.COM (Paul A. Fischer, Sr UNIX Sys Consultant) writes:
>
>>Has anyone heard when FoxPro for SCO Unix might ship.  I have had
>>many customers interested, but there is no news of availability.
>
>>Microsoft purchased FOX and I wonder if it will ever be a real
>>product for SCO users.
>
>
>I called the 800 number for Fox and MS after the merge.  I never got a reply.
>The rumor I heard is that Foxpro for SCO is dead.  Qbase is out.  Does anyone
>have any info on that?
>

At the upcoming FoxPro Developers Conference in Phoenix, AZ, FoxPro has
the FoxPro for DOS 2.5, FoxPro for Windows 2.5 and FoxPro for Unix 2.5
on the agenda.  My sources tell me that FP Unix 2.5 is in limited Beta
at this time (on the SCO platform).

--
#====================================================================#
# Grant M. Fengstad		     E Mail: fengstad@alpha.Uleth.CA #
# Manager, Network Operations	     Voice:     (403) 382-6724       #
# Canadian Regional Airlines Ltd.    FAX:	(403) 327-1229       #
#====================================================================#
From: watson@carssdf.uucp
Newsgroups: sanet.list.sco,biz.sco.general
Subject: bug in memc.. intrinsic
Date: 26 Aug 92 18:16:20 GMT
Distribution: sanet
Organization: John Watson (Self Employed System Integrator)
X-Conv: Automatic mail-->news conversion at olsa99


Everyone probably knows this, but I thought I should post it,
just incase SCO didn't know it yet.

There is a BUG in the intrinsic version of memcpy and similar
routines.  It is ok as a subroutine, but the intrinsic version
does not type cast the lenght to a long.  If you call it with a
short, it will use whatever junk you had most recently in the
high order 16 bits of the register.

It can be fixed with a define, but not the (long)(len) that you
would first expect.  That has problems, but just using len+0, will
force the complier to think about it with some arithmetic, and
then it gets the right answer.  Only a statement or two of extra
code is generated, if any.

John Watson ... a non-profit re-seller, maby next year I can make some money!
From: mikes@vivanet.UUCP (Michael Shea)
Newsgroups: biz.sco.general
Subject: Sco Days '92
Keywords: Sco
Date: 31 Aug 92 18:10:39 GMT
Distribution: na
Organization: VIVATRON Corporation




        September 16, 1992 - VIVATRON Corporation is proud to announce:

                        *****************************
                        *       SCO DAYS '92        *
                        *****************************


                            Holiday Inn - Downtown
                       Genesee Plaza, Rochester New York
                            Mini-Ballroom  1-5 pm.



     Presentations on:                        Seminars on:
    X-Windows by Tektronix                   Introduction to Unix by VIVATRON
    DOS-UNIX Connectivity by Esker           Contact Management by Telemagic
    SCO Open Desktop 2.0 by SCO              Disaster Preparation by Maynard


   Other demonstrations include:
                            Multi-Media Computing
                            Office Automation
                            and much more...


                Call VIVATRON for more information or to
                 reserve your space (limited seating!)
                   (716) 272-0820   (800) 836-UNIX




Newsgroups: biz.sco.general
From: hart@cp4.cp.bell-atl.com (Rod Hart - Director Minicomputer Techn. Support)
Subject: need jumbo 250 driver
Organization: C & P Tel. Co. - Minicomputer Techn. Support Dist.
X-Newsreader: Tin 1.1 PL5
Date: Tue, 25 Aug 1992 23:50:54 GMT


Newsgroups: biz.sco.general
From: nikki@trmphrst.demon.co.uk (Nikki Locke)
Distribution: world
Subject: Front end menu systems
X-Mailer: cppnews $Revision: 1.14 $
Organization: Trumphurst Ltd.
Date: Thu, 3 Sep 1992 17:28:41 +0000

Can anyone suggest and P.D. front-end menu systems for SCO Unix 3.2.4 ?
You know the sort of thing - to present a user with a pick list of 
things to do, and run shell scripts and programs for them.

Or is there even one that comes with SCO ? It occurs to me that sysadmsh 
might be written using something like this.
---
Nikki Locke              |                        | nikki@trmphrst.demon.co.uk
Trumphurst Ltd.          | Tel: +44 (0)691-670318 | nikki@cix.compulink.co.uk
PC and Unix consultancy  | Fax: +44 (0)691-670316 | nikki@kewill.co.uk
trmphrst.demon.co.uk is NOT affiliated with ANY other sites at demon.co.uk.
Demon.co.uk is a dial-up subscription access point to the Internet.
Newsgroups: biz.sco.general,comp.unix.sysv386
From: Petri.Wessman@hut.fi (Petri Wessman)
Subject: Mysterious SCO 3.2.4 lockups
Reply-To: Petri.Wessman@hut.fi
Organization: La Gata Encantada
Date: Wed, 26 Aug 1992 08:37:33 GMT

I'm having some problems with the new SCO 3.2r4.1, and would
appreciate some help. The system works fine normally *if I'm running
something*, but if I log out from all the multiscreens (leaving just a
getty on each screen), the systems locks up totally in a few minutes.
By "locks up" I mean that nothing happens, the keyboard is quite dead
(I don't have a serial terminal so I can't check whether it's just the
multiscreens that zonk). I tried the keyboard lockup fix found in the
Troubleshooting section of the SysAdm manual -- no effect. This is
getting to be really annoying, so far I've "solved" it by running
something, usually u386mon, in one of the multiscreens.

Some info about the system:

- "generic" 386/33 box, 8MB RAM, 64k cache, 330 MB ESDI disk,
  Paradise 1024 VGA, serial/parallel I/O card.
- MS4.1 installed.
- TCP/IP 1.1.3 installed, but not active at the moment
- Development system 3.2.4 installed
- Some kernel parameter modifications, including screen blanker on
  (in 15 mins), ETRUNC 1, etc. All well within the /etc/conf/cf.d/mtune
  limits.
- Getty running on only the first 4 multiscreens.


I've also had some type 0xE panics now and then, but fortunately rarely.

The thing is, this same system ran 3.2.2 for about a year without any
problems or a single panic/lockup!

Is anyone else having similar problems with r4.1?
Any and all help appreciated.

//Petri
From: mike@pacsoft.com (Mike Stefanik)
Newsgroups: biz.sco.general
Subject: Re: 3.2 4 system reports 3.2 2
Date: 31 Aug 92 08:50:26 GMT
Organization: Pacific Software Group, Riverside, Ca.

In an article, geoff@zswamp.UUCP (Geoffrey Welsh) writes:
> I'm curious more than anything.
> Also, it reports i386, even when running on a 486.

The command uname(1) is a simple program that calls uname(2), which is a
simple system call that copies the contents of a structure called "utsname"
in the kernel to a local buffer.  In it's simplest form, the structure
contains the following members (I say "in it's simplest form" because this
is one of the things that UNIX vendors absolutely love to screw around with.)

        struct utsname {
        	char	sysname[9];
        	char	nodename[9];
        	char	release[9];
        	char	version[9];
        	char	machine[9];
        };

In this structure, release is defined as "3.2", version as "2" and
machine as "i386".  There is no magic here -- they are just strings.
Now, changing the version from 2 to 4 would probably be innocuous
enough... however, changing the machine type to "i486" would probably
break any software or shell scripts that check this value against "i386"
to make sure that it's running on the correct machine type.

-- 
Mike Stefanik  mike@pacsoft.com  ...!uunet!pacsoft!mike
Pacific Software Group, Riverside, CA
Newsgroups: biz.sco.general
From: dthomas@mcl.bdm.com (David Thomas)
Subject: Autosensing of floppy formats
Date: Fri, 04 Sep 92 19:03:15 GMT
Organization: BDM International, Inc.

In the manual for SCO Unix 3.2.2 (and 3.2.4), the fd(HW) manual page
says, "Format specification is mandatory when opening the device for
formatting.  However, when accessing a floppy disk for other operations
(read and write), the format field specification can be omitted.  In
this case, the floppy disk driver will automatically determine the
format previously established on the diskette and perform the requested
operation."  The example given is:

	cpio -itv </dev/rdsk/f0

But when I try this on a disk that was formatted and written as a low
density disk (/dev/rdsk/f05d9), it doesn't work.  Upon further examination,
I see that /dev/rdsk/f0 has the same major/minor numbers as /dev/rdsk/f05h
(5.25" high density).  What am I missing here?  Has anyone else out there
gotten the floppy driver to automatically determine the format?

David Thomas
dthomas@mcl.bdm.com
Newsgroups: biz.sco.general
From: rdr@attics.rn.com (Dean Riddlebarger)
Subject: Re: 3.2 4 system reports 3.2 2
Organization: Ameritech Information Systems
Date: Thu, 27 Aug 92 04:18:36 GMT

"Brian J. Murrell" <brian@ilinx.wimsey.bc.ca> writes:

>A client just installed 3.2.4, however a uname -a reports that it is 3.2 2.
>What's going on here??

What's going on is that the uname is reporting the AT&T SVID version
number, and 3.2.2 is accurate in this respect.  SCO's numbering scheme
for this particular OS flavor happens to be 3.2.4, even though the
OS as such bears only a passing resemblance (stretch!) to System V
Release 4 (which is also undergoing some version growth, but that's
another story...:-)  SCO says that it is simply coincidence that their
version 4, which is really SysV 3.2.2 with "enhancements", happens to
suggest SysV R4 in the general marketing material.  Cynical folk
might think instead of a marketing department conspiracy, but I for
one would never suggest that.........


   
<*>  Dean Riddlebarger                   Once in a while              <*>
<*>  Ameritech Information Systems        You get shown the light,    <*>
<*>  rdr@attics.rn.com                   In the strangest of places   <*>
<*>  317-488-3067 (w)                     If you look at it right.    <*>
From: paul@openage.COM (Paul A. Fischer, Sr UNIX Sys Consultant)
Newsgroups: biz.sco.general
Subject: RE: SCO 3.2.4/ODT 2.0 Filesystem Types
Date: 25 Aug 92 17:55:51 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

>Could someone tell me what filesystem types are supported with
>SCO ODT 2.0 (which I believe is 3.2.4).

>In particular, I want to know if the BSD 4.2 filesystem type is supported.

>3.2.2 supports only AFS, and S51K.
                And XENIX and DOS

>                                               Thanks


Add EAFS to the above.

--------------------------------------------------------------------------------
Independent SCO support and service provider in the D.C. metro area.
No Incumbents in '92. Get the crooks out of office. Vote & Send a Message
Paul A. Fischer           | Open Age Inc.  | paul@openage.com
Sr. UNIX Sys. Consultant  | (301) 948-6422 | (301) 948-9644 Fax
Newsgroups: biz.sco.general
From: davidf@golem.uucp (David J. Fiander)
Subject: Re: Mailing lists with MMDF
Keywords: MMDF MAIL MAILING LIST
Date: Thu, 03 Sep 1992 22:37:14 GMT

According to dlucy@sandr.COM (Douglas Lucy):
>
>The SCO ODT System Admin Guide (ODT-NET section, somewhere around page
>188-190) tells you to use one of two formats for the list-of-recipients:
>
>	list-outbound:	":include:/usr/list/of/addresses"
>
>	or
>
>	list-outbound:	</usr/list/of/addresses
>
>I've found only the second of these two formats work. At least with
>3.2.2 and the patches & kludges (read as SLS/EFS) I've added here.

That's odd, I always use the first form, and I've never had a
problem.  The second form may be eliminated in a future
release, owing to RFC 1123.

Secondly, there has never been an MMDF SLS or EFS.  There has
been 1 (one) MMDF TLS, which is a complete drop-in replacement
for the entire MMDF subsystem that came with 3.2.2.  Since I
was the person that packaged the TLS (and half of the people
responsible for the contents), I resent the implication that it
is a collection of patches and kludges.  The MMDF TLS (which is
also the MMDF shipped with ODT 2.0) is a much better product
that the MMDF that SCO initially shipped with UNIX and ODT.

>Okay, I'll tell you how I got mine set up, regardless of whether or
>not it's SUPPOSED to be done like this.

Well, the good news is that this is _exactly_ how it is
supposed to be done.

>
>	5. Now, you've still got the MMDF deliver program running, and
>	since I'm not convinced the thing EVER reads the database when
>	it should, I look for the program "deliver" in a ps listing,
>	kill it, and then re-execute the deliver command just as it
>	looks in the boot script /etc/rc2.d/S*mmdf. It'll be the line
>	that su's to mmdf and then executes "deliver".
>

FYI, the _only_ time the deliver daemon needs to be restarted
is after you have added or deleted channels.  It probably
wouldn't be too difficult to modify deliver to keep track of the
modification time of the mmdftailor file, and reload it on
demand, but channels don't get changed often enough for it to
matter.

Also, if you do kill and restart the deliver daemon, make sure
you do this _logged_in_ as mmdf.  Otherwise the accounting
information recorded by the C2 security system will be wrong
(if you care).

>Are you confused yet? Well, the above steps worked for me. The only
>addition I put in was an additional address in the list of mailing
>list members. I put in "blue-sky-archive" in the list and then added
>this line to /usr/mmdf/alias.list:
>
>	blue-sky-archive:	"mmdf//mail/archives/blue-sky"
>
>After following the same re-build steps for the MMDF database above in
>steps 3-5, this additional line told MMDF to keep a copy of all
>incoming mail to the list in the file /mail/archives/blue-sky.

The other option is to just add the line

	mmdf//mail/archives/blue-sky

to the mailing list file, but having a separate archive alias
means that it is easier to modify the behaviour of the archive
process.

- David
Newsgroups: biz.sco.general,comp.mail.headers
From: davidf@golem.uucp (David J. Fiander)
Subject: Re: Reply receipt from MMDF
Distribution: sanet
Date: Wed, 26 Aug 1992 02:36:10 GMT

According to john@chance.gts.org (John R MacMillan):
>|So the answer is "upgrade"
>
>If I can go off on a rant for a moment, Return-Receipt-To is
>misleading in name, and people should not considered a returned
>receipt to indicate that the person has actually received the message,
>and especially not assume the recipient has read it or even had a
>chance to.  Think of it as Return-MTA-Coniders-Delivered-But-Who-
>Really-Knows-Receipt-To.

Yes, but at least the SCO mmdf rrt says that the message was
delivered to the user or his agent (which is a polite way of
saying that MMDF ran it through his .forward file, which may
have trashed it).

At least RRT is better than the so-called "Read-Receipt" which
is implemented by a particular _User_ Agent.  This caused no
end of grief for a secretary at the last place John and I
worked.  She always requested this, and believed it.  She was
particularly confused by the fact that we would reply to a
message, but three days later she would get a mail message
telling her that the message had not yet been read.

- David
Xref: sparky biz.sco.general:3048 comp.unix.sysv386:13671
From: fengstad@alpha.uleth.ca
Newsgroups: sanet.list.sco,biz.sco.general,comp.unix.sysv386
Subject: DOS/Merge under SCO ODT 2.0 and NFS filesystems
Date: 25 Aug 92 00:08:07 GMT
Followup-To: fengstad@alpha.uleth.ca
Distribution: sanet
Organization: University of Lethbridge
X-Conv: Automatic mail-->news conversion at olsa99



My question is quite simple....

I understand that with ODT 1.1, it was not possible to assign DOS Drive
letters to NFS mounted file systems.

Can ODT 2.0 do this?  I want to be able to use an ODT 2.0 Server as a
potential X Server, call a DOS Session using Merge and have the
flexibility to assign drive letters to point to various locations on the
Unix Filesystem, to also include NFS mounted filesystems.

Please email responses and I will summarize...
--
#====================================================================#
# Grant M. Fengstad		     E Mail: fengstad@alpha.Uleth.CA #
# Manager, Network Operations	     Voice:     (403) 382-6724       #
# Canadian Regional Airlines Ltd.    FAX:	(403) 327-1229       #
#====================================================================#
Newsgroups: biz.sco.general