HDTenEightyP/NetNews huggingface dataset:
From: yeh@cs.purdue.edu (Wei Jen Yeh)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL -> Re: ISC: ESDI & SCSI in one host ?
Date: 18 Dec 1992 21:50:42 -0500
Organization: Department of Computer Sciences, Purdue University
NNTP-Posting-Host: jessie.cs.purdue.edu
Summary: Both SCSI and MFM in a system

In article <PCG.92Dec18225211@decb.aber.ac.uk>, pcg@aber.ac.uk (Piercarlo Grandi) writes:

> 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.

With help from support@dell, I was able to boot up from my SCSI hard
drive (a Microplis) and mount the other two MFM drives.  The trick is
to leave the MFM disks out in the cmos settings and have the working
hd dev drivers.  It's nice to have an extra 110 mb (an st251 and a
miniscribe 4085) to store the gnu sources.

That was Issue 2.1.  I was told that the same should work for 2.2 too.

Wei Jen Yeh                      yeh@cs.purdue.edu
                                 Department of Computer Science
                                 Purdue University
                                 West Lafayette, Indiana
Newsgroups: comp.unix.sysv386
From: richardf@teal.csn.org (Richard Forbin)
Subject: CMS Tape Drives
Organization: Colorado SuperNet, Inc.
X-Newsreader: Tin 1.1 PL4
Date: Fri, 11 Dec 1992 18:56:53 GMT


Has anyone in this group used a Colorado Memory Systems tape drive under
UNIX??  I'm thinking about getting one, but I figured I better check
here before i buy one. Any input would be a BIG help.
Thanks in advance!
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.sysv386
Subject: Re: What's happening to ISC UNIX?
Date: 12 Dec 92 00:17:51 GMT
Organization: Pegasus,  Honolulu

>>| 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!    :-)


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.sysv386
From: fred@genesis.demon.co.uk (Lawrence Kirby)
Subject: Need status of DSR (Carrier Detect) on serial device 
Distribution: world
Organization: BT
Date: Wed, 16 Dec 1992 00:29:03 +0000


In article <1992Dec8.231259.8433@njitgw.njit.edu> tod@eies2.njit.edu writes:

>
>We have an Epson serial printer hooked upto an Onboard Systems Stallion
>multiport serial board, and it signals the printer is not ready by 
>dropping DTR. As I understand it, this translates into the DSR signal
>(or carrier detect) on the other end. Does anyone know a way through
>the tty interface, or something else, to detect a drop in this signal?
>

This is almost a week old but you don't seem to have a reply (not in this
newsgroup anyway!)

There are 2 possible routes you can take:

1. Use hardware flow control. The printer is essentially using the DTR pin
as a 'ready to receive' signal. I don't Know the Stallion board as such but
you should connect the printer's DTR pin to the flow control input on the
board (usually CTS, sometimes RTS on boards which pretend to be a DCE
device). Make sure the board supports hareware flow control and enable it.

2. Use XON/XOFF flow control. Most printers will support sending XON/XOFF
control codes down the return data line to the computer. Since this is the
only data that goes down this line there are no problems. Just make sure that
both the port and printer are set up for XON/XOFF.

Fred

-----------------------------------------
Lawrence Kirby | fred@genesis.demon.co.uk
Wilts, England | 70734.126@compuserve.com
-----------------------------------------
From: Frank.Tarczynski@launchpad.unc.edu (Frank Tarczynski)
Newsgroups: comp.unix.sysv386
Subject: Source For  FAS 2.10
Date: 18 Dec 92 04:06:35 GMT
Distribution: na
Organization: University of North Carolina Extended Bulletin Board Service

Can someone point me in the direction of the source for 
FAS version 2.10?

Thanks,
Frank
--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  laUNChpad.unc.edu or 152.2.22.80
From: tim@rri.UUCP (Tim Buck)
Newsgroups: comp.unix.sysv386
Subject: Re: Problem with ICS 3.0 and TEXEL CDROM
Date: 11 Dec 92 14:16:30 GMT
Distribution: usa
Organization: Recognition Research Inc., Blacksburg, VA

In article <1992Dec8.121935.5483@compunet.uucp> steve@compunet.uucp (Steve Snow) writes:
>I have just purchased a TEXEL DM-3024 CDROM drive to use with my ISC 3.0
>unix system. The problem I am having is that when I attempt to mount the
>drive I get a "PREVENT MEDIA REMOVAL failed" error and ISC refuses to mount
>the drive. I have used an NEC CDR-74 in past which worked fine. The only
>difference in the two drives is that The NEC has a motorized eject button
>and the TEXEL has a mechanical eject. Does anyone have a work around or
>patch for ISC. 
>
>Thanks,
>
>Steve Snow

Here's a workaround:  Return your Texel drive and buy a different one that
has an electronic eject.

Seriously, I don't think there's any way around the problem -- the Texel
drive simply doesn't recognize the Prevent Media Removal SCSI command, which
is required by the ISC 3.0 High Sierra driver.  We also tried Micro Designs
SCSI Express driver, with the same result.

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
The first sign of maturity is the discovery that the volume knob also turns
 to the left.
Newsgroups: comp.unix.sysv386
From: dold@unislc.uucp (Clarence Dold)
Subject: Re: How to get Merge to see DOS partition?
Organization: Unisys Corporation SLC
Date: Tue, 15 Dec 1992 18:26:47 GMT

From article <Bz9ptE.I7H@chinet.chi.il.us>, by ignatz@chinet.chi.il.us (Dave Ihnat):
> In article <1992Dec9.165909.19109@sbcs.sunysb.edu> shane@cs.sunysb.edu (Shane Bouslough) writes:
>>I have Dell UNIX on a disk which also has a bootable DOS
>>partition. According to the Merge docs, the DOS partition
>>should appear as e:. Unfortunately it doesn't.
> 
> Nope.  Not as it comes from the installation scripts.
[  .....   lots of stuff deleted  ... ]

Wow.  What an answer! ;-)

I looked in the merge default file (I think /etc/dos*), where it said:
       dos +adcom1 +ae:=/dev/dsk/dos

I noticed that there was no /dev/dsk/dos, so I linked the appropriate
/dev/dsk/xxx to it, and all was well, after I opened up the permissions.

You might need to look at fdisk to determine the proper /dev/dsk entry.


-- 
---
Clarence A Dold - dold@unislc.slc.Unisys.COM
               ...pyramid!ctnews!tsmiti!dold
From: mbarkah@slate.mines.colorado.edu (Ade Barkah)
Newsgroups: comp.unix.sysv386
Subject: Compiled EMACS anyone ?
Date: 15 Dec 92 17:04:30 GMT
Organization: Colorado School of Mines

If you've compiled EMACS on your svr4/386, please tell
me what options/changes you used. The make dies very
quickly on mine with error after error. I'm using
the m-intel386.h and the svr4 rel 4 s- file. The
complier is the standard cc; the options were 
DEBUG, and I have NO_SIOCTL_H defined. I've also 
tried using gcc with the '-traditional' flag.

I'm sure there are tons of people who have done this,
so any help is appreciated.

The system is Microport SVR4.0 version 4.1 unlimited;
X is installed (this is USL's Dev. Graphics.) I'd like
to compile both emacs and xemacs.

-Ade.
-- 
Internet  : mbarkah@slate.mines.colorado.edu    (NeXT Mailable)
CompuServe: 74160,3404
Newsgroups: comp.unix.sysv386
From: larry@news.rn.com (Larry Snyder)
Subject: Re: DELL Filesystem type?
Organization: Gator Communications - Feeds-R-Us 219-289-3745 
Date: Sat, 19 Dec 1992 15:13:48 GMT

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


>I'm upgrading a customer from Dell to SCO, and I want to mount the old Dell
>file systems under SCO, without having to do the mkfs under SCO.  Is this
>possible?

SCO is based on old technology and likewise doesn't support ufs
filesystems.  You could make a s5 filesystem on the Dell box, which
is outdated technology like used with SCO, and it should work.

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: doug@rocker.uucp (Doug Luecke)
Newsgroups: comp.unix.sysv386
Subject: Tape drive streaming magic for ISC
Date: 14 Dec 92 15:39:09 GMT
Organization: Terzon Systems, Inc.,   Richardson, Texas

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
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: comp.unix.sysv386
Subject: Re: Demise of Starserver line?
Keywords: AT&T Starserver SYSVR4
Date: 20 Dec 92 21:35:22 GMT
Organization: W. J. Vermillion - Winter Park, FL

In article <1992Dec16.231617.39888@spillman.uucp> bruce@spillman.uucp (Bruce Hunsaker) writes:
>I heard a rumor that AT&T was discontinuing it's Starserver line of
>UNIX computers in favor of NCR hardware.  Is this true? Will AT&T 
>no longer have a line of  80386/80486 based UNIX machines?

The NCR machines are now primarily 80386/80486 boxes.  (There
are some Motos left, but all new boxes are Intel oriented).

The NCRs have some pretty impressive specs too!  
-- 
Bill Vermillion - bill@bilver.oau.org  bill@bilver.uucp
                - ..!{peora|tous|tarpit}!bilver!bill
Newsgroups: comp.unix.sysv386
From: gerg@netcom.com (Greg Andrews)
Subject: Re: Dell Unix, 14.4Kb, and DigiBoards, HELP!
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Distribution: usa
Date: Mon, 21 Dec 1992 02:55:10 GMT

tkevans@eplrx7.es.dupont.com writes:
>
>Just to expand on this:  the whole point of V.32bis modems is that they
>use dynamic data compression to make the effective baud rate 14,400
>when they're really talking at 9600.  
>

That's not true, Tim.  V.32bis modems actually transmit at 14,400 bps.
That's why they have a different name for their modulation than 9600 bps
modems do.  9600 bps modems use V.32, 14400 bps modem use V.32bis.

Perhaps you've been confused by the similarity in name between V.32bis
(transmission at 14400 bps) and V.42bis (data compression).  The names
are similar, but they are completely different things.

-- 
:::::::::::::::::::  Greg Andrews  gerg@netcom.com  :::::::::::::::::::
ObGuindon:  The correct way to bunt with a carp is head first.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Newsgroups: comp.unix.sysv386
From: vanmol@tokyo.seri.philips.nl (Peter van Mol)
Subject: Re: What is best was to run DOS and Unix on same box?
Organization: SERI-CEN Network Services, Philips C&P, Eindhoven, The Netherlands
X-Newsreader: Tin 1.1 PL4
Date: Sun, 13 Dec 1992 20:37:49 GMT

booloo@framsparc.ocf.llnl.gov (Mark Boolootian) writes:
: I am about to take the plunge and purchase a 486 box.  My wife will likely
: be using the machine more than I to run a few DOS applications.  When I work
: on the machine, I want to run Unix.  How can I best accomplish this?
: 

You might check the LINUX newsgroup(s). A very interesting development of a free UNIX!

--
NAME		Peter van Mol
ORGANIZATION	Philips Semiconductors Automation
EMAIL		vanmol@sce.philips.nl
SERIMAIL	vanmol:nlsce1
ADDRESS		P.O. Box 218, Building BAE-4, 5600MD Eindhoven, the Netherlands
PHONE		+31-40-723836
FAX		+31-40-722581
From: Lucian_Dancanet@transarc.com
Newsgroups: comp.unix.sysv386
Subject: IDE + SCSI, ESIX 4.0.4 problems
Date: 21 Dec 92 01:39:08 GMT
Organization: Carnegie Mellon, Pittsburgh, PA



Setup:

EISA 486DX50 with 16 MB, AMI BIOS dated 12/12/91
Floppy/IDE Adapter
Internal IDE Fujitsu M2624T, 520 MB, drive C:
Adaptec 1542B (BIOS V3.10), floppy disabled, everything else factory default
(resistor pack removed)
Internal SCSI HDD Toshiba MK-538FB (1.2 GB formatted, 1172 cyl), ID 0
Internal SCSI Tape Drive Wangtek 5150ES (resistor pack installed), ID 2
External SCSI CD-ROM Drive Toshiba TXM-3301B (resistor pack installed), ID 4
ATI Graphics Ultra with the InPort Mouse
2 Serial, 1 Parallel, 1 Game Ports

DOS 5.0 and OS/2 2.0 (GA+SP) installed on C: (dual boot), OS/2 HPFS partitions
on Fujitsu and Toshiba, Extended DOS partition on Toshiba. DOS sees only
1024 MB on Toshiba, OS/2 sees the whole disk (1172 MB).

Everything seems to work fine, except for Windows 3.1 if installed on Toshiba;
it will start only in standard mode (win /s). win, win /3, win /d:x, win /d:v
do not work. If installed on Fujitsu, Windows 3.1 works fine.

Anyway, when installing ESIX 4.0.4, only the Fujitsu drive is seen, the SCSI
hard disk is not recognized at all.

All SCSI devices are terminated properly, have the parity checking enabled,
and there are no IRQ conflicts (that I know of).

Once in a while, I saw a "Timeout Error: Error on port I/O with host adapter",
at boot time. I don't know if it was related to this, but I've changed now
the BUSCLK from CPUCLK/4 TO 7.159 MHz.

What is wrong with my setup? How can I install ESIX on both the IDE, and the
SCSI hard disks? What's the problem with Windows 3.1 on the SCSI drive?

Any help will be greatly appreciated.

Lucian
Newsgroups: comp.unix.sysv386
From: deano@areyes.com (Dean Carpenter)
Subject: Re: SCSI controller board inquiry
Reply-To: deano@areyes.areyes.com (Dean Carpenter)
Organization: Areyes, Inc.
Date: Sun, 13 Dec 1992 05:08:23 GMT

In article <1992Dec10.183131.19791@fcom.cc.utah.edu> jeff@anthro.utah.edu (Jeff Thomas) writes:
>What's a good brand of SCSI controller that's ASPI compliant that will
>work with both DOS5 and ISC UNIX? This is gonna go into a 386 ISA machine.
>I'm planning to hook up an Archive 2150S SCSI tape drive and possibly a
>SCSI disk.

  Go with either a BusLogic 542 (used to be BusTek) or an Adaptec 1542.
I use a BusTek 742A, the eisa version, and have had absolutely no
problems with it.  BusLogic upgraded the firmware for me for free when I
called, and I wasn't even the original owner.

  Some people think the BusLogic cards are faster than the Adaptecs, but
since I haven't done a head-to-head test, I can't really say.  On the
eisa bus, copying a multi-megabyte file from one filesystem to another
(on different disks) twice *flies*.  That is, from disk1 to disk2 and
from disk3 to disk4, all at the same time.

  I'm running ISC 3.2 V3 here, soon to be moving to Destiny.  Booted
under DOS5, aspi compliant software works just fine.

-- 
Dean Carpenter		uunet!areyes!deano		(203) 847-6003
Areyes, Inc.		deano@areyes.com

"No matter where you go, there you are"  sayeth Buckaroo 								 across the Eighth Dimension
Xref: sparky comp.unix.sysv386:17492 comp.unix.sys5.r4:860
From: tener@cs.widener.edu (Stuart Tener)
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
Subject: Re: gawk-2.14.tar has been uploaded to US4BINR
Date: 17 Dec 1992 15:30:32 -0500
Organization: Widener University CS Department, Chester PA
NNTP-Posting-Host: pebbles.cs.widener.edu

Jacques Gelinas:

	Everytime something new is added to the US4BINR server, you
	seem to feel the need to publish a bulletin. This is a teribble
	waste of resources. To make things worse you seem to also have
	the neeed to make these bulletins quite wordy. Why not just list
	all new software available on the server each week or month?
	Is it really necessary to publish all this information everytime
	you get a new binary?

	Why not just publish a monthly list of new updates? All these
	constant news articles do is jam up the network more. As

	thank you,

	stuart b. tener
	tener@cs.widener.edu


Newsgroups: comp.unix.sysv386
From: bruce@spillman.uucp (Bruce Hunsaker)
Subject: Demise of Starserver line?
Summary: Can someone confirm/deny this rumor?
Date: Wed, 16 Dec 1992 23:16:17 GMT
Organization: Spillman Data Systems
Keywords: AT&T Starserver SYSVR4

I heard a rumor that AT&T was discontinuing it's Starserver line of
UNIX computers in favor of NCR hardware.  Is this true? Will AT&T 
no longer have a line of  80386/80486 based UNIX machines?

--
Bruce   bruce@spillman.com     ...!uunet!spillman!bruce
From: chris@alderan.sdata.de (Christoph Splittgerber)
Newsgroups: comp.unix.sysv386
Subject: Re: ISC 2.0.2 and SCSI primary controller/drive
Date: 9 Dec 92 23:22:45 GMT
Organization: C. Splittgerber Datentechnik, Denkendorf, Germany

In article <Byt7DC.B3n@maxed.amg.com> ed@maxed.amg.com (Ed Whittemore) writes:

>What makes you say that? Do you know it for a fact? The first ISC ver.
>without broken, or completely broken SCSI was 2.2, as I remember.

Please don't tell this my ISC 2.0.2 Box ! It does not know this - and because
it doesn't know about this it's running and running and running and ....
running ......... ;-)

>-- 
>Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
>American Micro Group, Inc.   201-944-3293

          Chris


-- 
******************** It's not a bug, it's a feature !!! ********************
Replies-To:  chris@alderan.sdata.de    UUCP: uunet!mcsun!unido!alderan!chris 
Phone:       +49 711 344375            Fax:  +49 711 3460684
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: XBBS
Date: 17 Dec 92 20:49:44 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Dec17.043016.4761@sactoh0.sac.ca.us>, cen@sactoh0.sac.ca.us (Charles E. Newman) writes:
| 
|      Is XBBS Public Domain or Shareware?

  Since Sandy didn't answer on this one, I believe the answer is no.

  I believe it is freely licensed copyrighted software, like UNaXcess.
This means you can use it, but you don't have to pay for it and it's not
public domain. I *believe* there's a restriction against selling it or
distributing modified copies.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Xref: sparky comp.unix.sysv386:17381 comp.unix.sys5.r4:825
From: debra@wsinis07.info.win.tue.nl (Paul De Bra)
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
Subject: can't write 8 bit chars to printer with Esix 4.0.4
Summary: works with AT&T, not with Esix
Keywords: Esix, 8-bit chars
Date: 14 Dec 92 10:11:45 GMT
Reply-To: debra@info.win.tue.nl
Followup-To: comp.unix.sysv386
Organization: Eindhoven University of Technology, the Netherlands

I have a 486 system with AT&T sVr4 2.1a, sas 1.25 and a polling printer driver.
A friend just got Esix 4.0.4 for a similar system, and also installed sas 1.25
and the same polling printer driver.

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.
Furthermore, the AT&T clist driver has the jge and does not have the
problem.

Is there a trick to write chars with the 8th bit set to the printer with Esix?
(With AT&T sVr4 there is no trick, it works out of the box)
Or is it (as i suspect) a bug in some kernel routine?
Does anyone have a fix for this? It seems hard to believe that we are the
only people who want to send 8-bit chars to a printer.

Note that the problem is *not* in the printer driver which works fine with
AT&T sVr4.0.2.1a. The printer driver doesn't get the chars with the 8th bit
from whatever kernel routine is supposed to call the driver's write function.

Any help much appreciated.

Paul.
(debra@win.tue.nl)
Newsgroups: comp.newprod
From: rich@pluto.dss.com (Rich Rupp)
Subject: Datability Announces Terminal Server Management System
Followup-To: poster
Organization: Datability, Carlstadt, NJ
Date: Thu, 17 Dec 1992 01:52:08 GMT

                  NEW UNIX BASED SOFTWARE DELIVERS
              COMPREHENSIVE TERMINAL SERVER MANAGEMENT

CARLSTADT, N.J. -- November 19, 1992 -- Datability today announced
the availability of a new software management tool targeted at UNIX
sites that utilize DEC compatible or TCP/IP terminal servers.  Called
VSM, the new software is a functional replacement for Digital Equipment
Corporation's popular TSM terminal server management software,
providing comprehensive management of terminal servers.

While SNMP management programs are capable of managing many types
of devices including terminal servers, VSM has been specifically
engineered to manage terminal servers and the particular configuration
process governing them.  VSM allows site administrators to store server
configurations (profiles) on host systems, where they can be centrally
maintained and updated.  Updated server profiles can then be applied
easily and automatically to a single server or a group of servers as
required.

Unlike TSM, which runs only on DEC hosts, Datability's VSM runs on
UNIX hosts, allowing site managers to migrate server management away
from DEC systems to UNIX systems.  Users familiar with DEC's TSM
product will automatically know how to use VSM because the product is
command for command compatible.  Like DEC's TSM product, VSM
interprets DCL format command files when interacting with a remote
server, allowing users to customize supplied procedures to support any
DEC compatible or TELNET terminal server.  DEC users can even utilize
their existing DCL procedures to manage DECSERVERS with VSM.

VSM/UNIX will be priced at $799 per copy.  On an introductory basis,
the software is available immediately for $499.  All Datability products
are covered by a 100% satisfaction guarantee return policy.  Standard
reseller discounts are available.

For more information, please contact Esti Weissman, VSM Product
Manager, at esti@doc.dss.com or 1-800-456-7844 x 339.
Newsgroups: comp.newprod