HDTenEightyP/NetNews huggingface dataset:
From: belal@sco.COM (Bela Lubkin)
Newsgroups: biz.sco.general
Subject: Re: SCO UNIX System Performance
Date: 28 Aug 92 23:36:39 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Cc: scogen@xenitec.on.ca
Precedence: bulk

Geoffrey Welsh wrote:

> Bela Lubkin <belal@sco.COM> writes:
> 
> > Question: when you upgraded from 64K to 256K of cache, did you have to
> > replace the *tag RAM*?
> 
>    I believe that we did.  However, the tag RAM, like the cache RAM, was 
> upgraded from 8K by 8 chips to 32K by 8 chips... and I would think that 
> keeping longer tags would require an increase in tag RAM greater than 1:1 with
> the increase in cache RAM.

Indeed.  That shoots that theory...

>    I also wouldn't mind knowing why, in this day of a multitude of memory-
> hungry operating systems and applications, there doesn't seem to be any real 
> understanding of this problem among net.users.  I'm guilty as anyone - and my 
> excuse is that I don't do work with big systems and that my experience is 
> purely self-funded - but I would have expected that we'd have tripped over the
> 16MB limit on PCs long ago, thanks to XENIX, Novell Netware, Windows, OS/2, 
> QNX, etc... surely these systems are as vulnerable to the problem as UNIX?

I dunno about the others; no version of SCO XENIX has ever supported
more than 16MB RAM, so you couldn't have run into a hardware limit
there.

I think, in practice, the number of >16MB PC-based systems has been
vanishingly small until recently.  Furthermore, this problem isn't fatal
-- it only causes a mysterious glitch in performance.  Finally, not all
machines behave this way -- it's totally dependent on cache design.
Lastly, SCO UNIX 3.2v4 makes the problem much more apparent by loading
the *kernel* into high memory, thus making the entire machine slow if
high memory is slow.

>Bela<
From: paul@openage.COM
Newsgroups: sanet.list.sco,biz.sco.general
Subject: Re: SCSI II
Date: 25 Aug 92 16:56:35 GMT
Distribution: sanet
Organization: [resent by] The SCOGEN gateway and Propagation Society
X-Conv: Automatic mail-->news conversion at olsa99


>fr@compu.com (Fred Rump from home) writes:

>>If I would like the fastest and meanest I/O combination between disk, tape
>>and controller, what does the combined net wisdom recommend for a SCO UNIX
>>environment?

>Check if your setup works before you buy it. We are  just  having
>trouble  getting  SCO  to install on (probably too fast HP-) SCSI
>disks.

I had this problem with my HP SCSI-2 disk.  HP was aware of the problem and
they Federal Expressed me a new set of HDD ROMs.  It's worked flawless since
then.


--------------------------------------------------------------------------------
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: paul@openage.COM (Paul A. Fischer, Sr UNIX Sys Consultant)
Newsgroups: biz.sco.general
Subject: RE: ODT Dos Merge
Date: 31 Aug 92 16:40:20 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

>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


>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 am doing this from the root prompt as well.

The problem is that the multiport serial board is not supported by Merge!  SCO 
should have released a developers guide to the multiport vendors so that they 
can include this in their drivers.  VP/ix had such a guide and you will notice 
that all multiport vendors support VP/ix.  When Locus had the Merge product 
they did not have such a guide, but now that SCO has the product hopefully they 
understand the product well enough to make this a reality.  Then and only then 
will you be able to access multiport cards from within merge.  


NOTE:  You can still login on a terminal and run merge, you just can't make DOS 
COM1=/dev/ttyA23 so you can access the device on the port.

--------------------------------------------------------------------------------
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: geoff@zswamp.UUCP (Geoffrey Welsh)
Newsgroups: biz.sco.general
Subject: Re: 3.2 4 system reports 3.2 2
Date: 31 Aug 92 05:27:29 GMT
Organization: Izot's Swamp

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.

Geoffrey Welsh, 7 Strath Humber Court, Islington, Ontario, M9A 4C8 Canada
geoff@zswamp.uucp, [xenitec.on.ca|m2xenix.psg.com]!zswamp!geoff (416)258-8467
"Feel for the winter but don't have a cold heart" - Little River Band, "Lady"
Newsgroups: biz.sco.general,comp.unix.sysv386
From: cbuckley@unix1.tcd.ie (Colm Buckley)
Subject: Wyse-120 to Specialix SI8 wiring for h/w flow control?
Organization: Trinity College, Dublin
Date: Mon, 31 Aug 1992 11:06:34 GMT

Can anyone tell me what the correct wiring for a connection between a Wyse
120 terminal and a Specialix SI8 multiport (on a 486 with SCO UNIX) is, to
use hardware flow control?

The Wyse uses pin 20 (DTR) to indicate a full buffer, and the Specialix
docs say that pin 4 (RTS) is used for this purpose. So I'm going to try the
following :

	Wyse                    Specialix
	----                    ---------
	Pin 2  (TxD) ---------> Pin 2 (RxD)
	Pin 3  (RxD) <--------- Pin 3 (TxD)
	Pin 7  (GND) ---------- Pin 7 (GND)
	Pin 5  (CTS) <--------- Pin 5 (CTS) *** this isn't necessary...
	Pin 20 (DTR) ---------> Pin 4 (RTS)

On the Wyse, I'll put it in DTR handshaking mode (DTR assert when buffer
full), and I'm going to try RTSFLOW CTSFLOW in gettydefs on the PC. I'm
using SCO UNIX 3.2.4 with a Specialix SI/8 version 2.0. The CTS pin is used
in theory to give flow control from the terminal to the PC, but this is
unlikely to be necessary, and I'll gladly sacrifice it if the rest of the
stuff works ok. I need hardware flow control, as I'll have a printer
attached to this Wyse, but the terminal will need to have XON/XOFF
disabled...

That is, unless someone tells me differently. Any help would be
appreciated. Oh - do I use the modem control port (ttyA1 etc.) or the
normal port (ttya1 etc.) for the above to work?

Thanks.
-- 
Colm.
+-------------------------------------+----------------------------------+
| Colm Buckley                        | "My program doesn't work."       |
| Computer Science,                   | "You forgot the semicolon."      |
| Trinity College, Dublin 2, Ireland  | "But..."                         |
|                                     | "Line 376. Check."               |
| cbuckley@unix1.tcd.ie               | "But..."                         |
| CBUCKLEY@vax1.tcd.ie                | "Trust me."                      |
+-------------------------------------+----------------------------------+
From: watson@carssdf.UUCP (- Self Empl. Sys.Integrator)
Newsgroups: biz.sco.general
Subject: bug in memc.. intrinsic
Keywords: memcpy memset memcmp
Date: 26 Aug 92 18:16:20 GMT
Organization: John Watson (Self Employed System Integrator)

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: andrew@airs.com
Newsgroups: sanet.list.sco,biz.sco.general
Subject: Problem with rwhod on SCO UNIX V/386 3.2.2 & TCP/IP Runtime 1.1.1b
Date: 19 Aug 92 20:58:54 GMT
Distribution: sanet
X-Conv: Automatic mail-->news conversion at olsa99


I'm running an Intel '486 box with SCO UNIX V/3.2.2 and TCP/IP 1.1.1b
runtime system installed.  I've got two other systems on the ethernet.
One is a DECstation 3100, the other is a VAXstation II/GPX - both are
running Ultrix.  Anyhow, I recently set all the machines up to start
rwhod when they boot.  From both Ultrix machines, ``rwho'' shows all
users logged in and active on all three systems.  The SCO system is
oblivious to the two DEC boxes, however - users logged into those
machines do not appear in the output of the rwho command.
Additionally, there are no /usr/spool/rwho/whod.* files for the remote
machines.

This means that either (1) rwhod is never seeing the broadcasts, or
(2) it is invalidating the broadcasts from the Ultrix machines.  I
think that (1) is pretty remote given that the other machines are
picking up the SCO machine's broadcasts.  The supporting evidence I
have for (2) is that in the Ultrix machines' /usr/spool/rwho
directories, I see these files:

-rw-r--r--   1 root     rsrv3         108 Aug 19 16:50 whod.bugs
-rw-r--r--   1 root     rsrv3          84 Aug 19 16:52 whod.comton.airs.com
-rw-r--r--   1 root     rsrv3          60 Aug 19 16:52 whod.elmer.airs.com

Notice that our domain (airs.com) is present on the files for the
Ultrix machines (comton and elmer), while no domain name is given for
the SCO machine (bugs).  Since the SCO rwhod manpage states that
incoming broadcasts are validated, and that only broadcasts from
within a local network are permitted, I believe that the ``airs.com''
domain in the broadcasts from the Ultrix machines is being interpreted
as a broadcast from another network, and hence the packets are
discarded.  Anyone able to confirm/refute this?

I looked for a way to tell rwhod the local domain name, so that it
will accept broadcasts from *.airs.com, but there doesn't seem to be
any way to do that.  Any secrets I should know?
--
Andrew Evans (andrew@airs.com) - Infinity Development Systems - Waltham, MA
Newsgroups: biz.sco.general
From: jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE)
Subject: vt100 emulation?
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Distribution: usa
Date: Mon, 31 Aug 1992 19:43:00 GMT

  Anybody know of a vt100 or similar emulation package for sco available
by ftp? I've got xcmalt and kermit(old) and neither are doing vt emulation.

Thanks, jason.

Newsgroups: biz.sco.general
From: pim@cti-software.nl (Pim Zandbergen)
Subject: Re: Have ESDI need SCSI
Organization: CTI Software BV, The Hague, The Netherlands
Date: Wed, 2 Sep 92 20:00:15 GMT

watson@carssdf.UUCP (- Self Empl. Sys.Integrator) writes:

>I installed a pair of 670 mb ESDI disks at a customer over the last couple
>of years, using a cacheing disk controller that work ok under Xenix, but
>now on UNIX with EISA I would like to upgrade to 1742 mode.  Is there some
>kind of box/board that would make the ESDI look like an SCSI?  The investment
>is just to great to ignore.

I've used an ESDI-SCSI bridge controller made by Emulex
with success on an Adaptec 1542B.

The bridge contoller came from an AT&T 3B2 computer
that had its defective ESDI disk replaced by a SCSI disk.

I've used a Micropolis 1558 and a CDC 150 MB disk
(can't remember the type). I had to reformat the
disk on the 3B2, as the Adaptec firmware could
not figure out how to format the ESDI disks.

The Emulex will map up to four ESDI disks on one
SCSI ID, with different LUN's.
-- 
Pim Zandbergen                      domain : pim@cti-software.nl
CTI Software BV                     uucp   : uunet!mcsun!sun4nl!ctisbv!pim
Laan Copes van Cattenburch 70       phone  : +31 70 3542302
2585 GD The Hague, The Netherlands  fax    : +31 70 3512837
Newsgroups: biz.sco.general
From: gerg@netcom.com (Greg Andrews)
Subject: Re: 3.2 4 system reports 3.2 2
Date: Sun, 30 Aug 92 21:46:03 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <5sw9PB10w165w@zswamp.UUCP> geoff@zswamp.UUCP (Geoffrey Welsh) writes:
>
>   Reporting version 3.2.4 is *not* the same as reporting SysV R4!  Both 
>versions are reporting SysV R3.2, but why does SCO UNIX SysV R3.2v4 report 
>that it is SysV R3.2v2?
>

I can't answer that one, but I can say that 'uname -X' listed the
desired number in the "Revision" line...

I found 'uname -X' in the man page for 'uname'...


-- 
 .------------------------------------------------------------------.
 |  Greg Andrews   |       UUCP: {amdahl,claris}!netcom!gerg        |
 |                 |   Internet: gerg@netcom.COM                    |
 `------------------------------------------------------------------'
From: root@candle.uucp (Bruce Momjian)
Newsgroups: biz.sco.general
Subject: What causes modem to hang system?
Date: 1 Sep 92 01:24:06 GMT
Article-I.D.: candle.1992Sep1.012406.3364
Organization: a consultant's basement
X-Newsreader: Tin 1.1 PL5

Runnning SCO 386 Unix V 3.2 with a Hayes 2400 modem, I have found that
sometimes both the console and connected terminals slow to a crawl.  You
wait for each character to echo.  At these times, no one is using the
modem.

If I turn off the modem, the problem is corrected.  I heard someone else
had this problem.  I would like to know how to correct it.
-- 
Bruce Momjian                      |  830 Blythe Avenue
root%candle.uucp@bts.com           |  Drexel Hill, Pennsylvania 19026 
                                   |  (215) 353-9879(w)  853-3000(h)
Newsgroups: biz.sco.general
From: avg@litwin.com (Anil Gokhale)
Subject: Re: Second or alternate swap files
Organization: Litwin Process Automation
Date: Mon, 31 Aug 1992 13:20:30 GMT

karl@robots.in-berlin.de (Karl-P. Huestegge) writes:

>fraserh@eismv3.dofasco.ca (Hugh Fraser) writes:

>>I've gone through the manuals and haven't found the answer to my
>>question: can I create a second swap file on another disk.

>Just type "man boot" ;-)
>or edit the file /etc/default/boot and enter the line:


I thought the question was have a second swap area, that is in addition to
the primary swap.  If so, the following might help.

Using divvy a partition needs to be setup on your second disk for this
purpose.  Let' call it swap2.   When you exit divvy by saying yes to the
question 'Install the above division' or something similar, you will
now have a device called /dev/swap2 

During divvy, make sure to remember the starting block number and the
ending block number you assigned to this area.

Now you may either replace the primary swap by this second one by 
changing the boot string as described by the previous poster, or 

In /etc/rc2.d/  look for the sample script starting with S88

Make a file for yourself to look like that.  Lets call it S88SWAPADD
Edit it and to it add the appropriate command as
swap -a ####  ########
The two numbers are starting block and length of the swap space.
Look up the man page on swap

There seems to be a lot of confusion here.  Remember two things.
The block numbers shown by divvy are 1k blocks.  The swap command
wants blocks in 512Byte size.  So the length number will be 
double of what you think.  Furthermore, the starting block number
has nothing to do with the starting block number in divvy.  This is
because in the swap command, you are giving the first block of the
/dev/swap2  area.  So this number is always 0.

Anyone out there correct me on the above if necessary; especially on the
second point I made above.

If I confused you enough, sorry, but I went through this exercise with
a lot of pain myself.  Thanks to Bela Lubkin at SCO, I think I know what
I am doing now.  I haven't read the ODT2.0 manual yet, but the ODT1.1
manuals are very poor in explaining all this.

Good Luck
-------------------------------------------------------------------------
                               Dr. Anil Gokhale
Litwin Process Automation                          avg@dynsim1.litwin.com
1250 W. Sam Houston Pkwy. South          ...!uunet!dynsim1.litwin.com!avg
Houston, Texas 77042, U.S.A.                               1-713-268-8209
-------------------------------------------------------------------------
Newsgroups: biz.sco.general
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Subject: Re: SCO 3.2.4/ODT 2.0 Filesystem Types
Date: Wed, 26 Aug 1992 01:02:34 GMT
Organization: The Programmer's Pit Stop, Ann Arbor MI

In article <9208251355.aa16809@openage.COM> paul@openage.COM (Paul A. Fischer, Sr UNIX Sys Consultant) writes:
>>3.2.2 supports only AFS, and S51K.
>                And XENIX and DOS
[...]
>Add EAFS to the above.

Read closely.  That was for 3.2v2.0, not 3.2v4.0.

3.2v2.0 supports S51K, S52K, Xenix, DOS, and AFS (the Acer Fast
Filesystem, not to be confused with the neat super-NFS that's also
called AFS).  3.2v4.0 adds EAFS (Extended Acer Fast Filesystem), which
has support for symlinks and long filenames.  I don't know if they
changed the allocation or seek schemes any.

There is no version of SCO Unix that supports the BSD FFS.  SVR4,
which is not offered by SCO, supports the UFS filesystem, a derivative
of the BSD FFS.  The UFS filesystem is also used by later versions of
SunOS, and perhaps by things like Ultrix and HP-UX.

-- 
Marc Unangst                | Real men don't make backups.  Real men never
mju@mudos.ann-arbor.mi.us   | accidentally delete files that they're going
                            | to need later.
Xref: sparky biz.sco.general:3086 comp.unix.sysv386:13769
From: dan@cedb.dpcsys.org (Dan Busarow)
Newsgroups: biz.sco.general,comp.unix.sysv386
Subject: Credit Card Authorization
Keywords: credit card auth
Date: 29 Aug 92 19:37:10 GMT
Followup-To: biz.sco.general
Organization: DPC Systems, Monrovia, CA

Hi all,

I have a client who wants to do credit card authorizations using their
UNIX box (SCO) as an auth server for multiple workstations.

What I envision is a daemon which can handle the details of dialing
(or a dedicated line) the authorization network and communicating with
my app via IPC.

Can anyone recommend a solution?

Thanks in advance.

Dan

-- 
+                                                                            -
   Dan Busarow             dan@cedb.dpcsys.org              uunet!cedb!dan
   DPC SYSTEMS                Monrovia, CA                  (818) 305-5733
-                                                                            +
Newsgroups: biz.sco.general
From: peet@locus.com (J. David Peet)
Subject: Re: ODT Dos Merge
Organization: Locus Computing Corp, Los Angeles
Date: Mon, 31 Aug 1992 19:38:09 GMT

In article <1992Aug30.104301.14225@xenitec.on.ca> news@xenitec.on.ca (xenitec.on.ca News Administrator) 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
># dos +acom2[=/dev/ttyac]
>TOKEN_NF: dos: ERROR: Could not find token 'com2[' of the needed type.

Use "dos +acom2=/dev/ttyac"

The brackets are meta characters.
The documentation uses the brackets to donote something optional.
You don't use them in the command itself.
Related Note: Don't use the quote characters in the above 'Use "dos ... "'
because they are meta characters also.  Also don't use 'Use'. :-)

-David Peet
From: fr@compu.com (Fred Rump from home)
Newsgroups: biz.sco.general
Subject: Re: FOXPRO FOR SCO WHEN????
Date: 1 Sep 92 14:50:46 GMT
Organization: CompuData Inc.

fengstad@alpha.uleth.ca (Grant Fengstad) writes:


>Fox Software was developing FoxPro 2.0 for Unix, but the project was
>scrapped.  Microsoft felt it was better to position all products on the
>2.5 platform.  From what I've been able to ascertain, Microsoft is not
>fully commited at this time.

The September issue of DBMS contains an interview with the MS DB dream team. 
They do not hesitate to reinforce their comittment to FoxPro for UNIX. They 
say that these things always follow two to three months after the more general 
DOS/Windows release. Obviously, there will also be an NT version.

The SQL Server connectivity is also worthwhile reading about.

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   
Xref: sparky biz.sco.general:3077 comp.unix.sysv386:13746
From: cbuckley@unix1.tcd.ie
Newsgroups: sanet.list.sco,biz.sco.general,comp.unix.sysv386
Subject: SCO Unix drivers for Wyse-995 multiport adaptor?
Date: 26 Aug 92 12:20:32 GMT
Distribution: sanet
Organization: Trinity College, Dublin
X-Conv: Automatic mail-->news conversion at olsa99


Does anybody know of drivers for the above serial card for SCO UNIX? I have
a few of these cards, which I used to use on some SCO Xenix machines a few
years ago, but I could not get drivers for UNIX when I upgraded. I now use
Specialix multiport cards, but the Wyse ones would be handy to have...

My local distributor says that the range is discontinued, and that drivers
are not available - does anyone else know differently?

Thanks for any help,

--
Colm.
+-------------------------------------+----------------------------------+
| Colm Buckley                        | "My program doesn't work."       |
| Computer Science,                   | "You forgot the semicolon."      |
| Trinity College, Dublin 2, Ireland  | "But..."                         |
|                                     | "Line 376. Check."               |
| cbuckley@unix1.tcd.ie               | "But..."                         |
| CBUCKLEY@vax1.tcd.ie                | "Trust me."                      |
+-------------------------------------+----------------------------------+
Newsgroups: biz.sco.announce