HDTenEightyP/NetNews huggingface dataset:
From: ignatz@chinet.chi.il.us (Dave Ihnat)
Subject: Re: How to get Merge to see DOS partition?
Organization: Chinet - Public Access UNIX
Date: Sat, 19 Dec 1992 08:30:18 GMT

In article <1992Dec16.041341.0601110@locus.com> peet@locus.com (J. David Peet) writes:
>In article <Bz9ptE.I7H@chinet.chi.il.us> ignatz@chinet.chi.il.us
>  (Dave Ihnat) writes:
> <<my explanation of starting MERGE on my box>>

>This is not quite correct.  The default is "+amouse +ae:=/dev/dsk/dos".
>(Which is held in the /etc/dosenv.def file, and you use the "dosopt"
>utility to view and change the settings in this file.)
>The "+amouse" causes the mouse to be used via the UNIX console driver,
>thus it automatically follows the current VT.  Using "+adcom1" is not
>recommended for using the mouse.

Ok, but I'm not running a bus mouse--I rarely use it, and it's hanging off
a COM port.  A bit of clarification would be welcome--or, as I asked before,
where can I get the current manuals for MERGE?

>As long as /dev/dsk/dos is linked
>properly to the DOS partition device, then it will be automatically
>available.  Unless these defaults have been changed by the user, the mouse
>and DOS partition should be automatically available without needing to
>use the command line parameters.

Perhaps they were changed by Dell?

>>More, although /dev/dsk/dos and /dev/dsk/0s5 have the same major,minor
>>numbers, I can't access the partition from /dev/dsk/dos; it has to be the
>>0s5 special device.  This latter may well be a configuration problem,
>>however, as none of the MERGE manuals are available from Dell, and the
>>online manuals are one rev out of date.
>> (Any ideas how to get the latest version of the manuals?)
>
>It sounds like the permissions are wrong on /dev/dsk/dos.  If they
>have the same major and minor numbers, then they connect to the same
>device.  The actual name does not matter, but the permissions do.

I agree, conceptually.  They're linked together, in fact.  Empirically,
however, I can't get to e: if I just run 'dos'; or, if I
run 'dos +ae:=/dev/dsk/dos'.  Works fine with 'dos +ae:=/dev/dsk/0s5'.
In the former case, dos comes up, hesitates, rapidly flashes the 'Bad
command or filename' message, and aborts.

As another item, I find some programs can't use ems.  Are there any known
problems with this under MERGE?

Cheers,
		Dave Ihnat
		ignatz@homebru.chi.il.us (preferred return address)
		ignatz@chinet.chi.il.us
Xref: sparky comp.unix.sysv386:17520 comp.unix.programmer:5737
From: jim@visionware.co.uk (Jim Musgrave)
Newsgroups: comp.unix.sysv386,comp.unix.programmer
Subject: Accessing clone devices on SCO Unix
Date: 18 Dec 92 16:26:21 GMT
Organization: VisionWare Ltd., Leeds, UK

Hi everyone.

I Have SCO Unix Release 4.1.  I would like to make use of the 
clone device driver (/dev/ptmx) to access the STREAMS based
pseudo-tty's.  

Issuing an open on a clone device gives you the file descriptor
of the master side which you can then use to get back the name of the slave.
On SVR4 there are routines such as ptsname, unlockpt and grantpt, which,
when given the file descriptor of the master, will return the name of
the corresponding slave device, unlock it and change the ownership.

Does any one know if there are any equivalent routines under SCO.

Getting the name of the slave side is not too painful because you can take
the minor number of the master side.  The naming convention of the slave
device is such that the minor number forms the suffix, e.g. /dev/pts000 is
the slave device which corresponds to the master with minor number 0.  No
problem.  Unlocking the slave and granting permissions becomes a little more 
involved.

The STREAMS documentation I have for SCO is very thin on the ground, in
fact non-existent, can anyone give me any pointers on this one.

Thanks,

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" -------------
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: ISC: ESDI & SCSI in one host ?
Organization: American Micro Group, Ft. Lee  NJ
Date: Sun, 13 Dec 1992 19:12:43 GMT

In article <4rdi65TM7y@DATA-HH.DATA-HH.ComLink.DE> chk@data-hh.comlink.de writes:
>
>
>       Hi,
>
>       is ISC able to handle ESDI & SCSI devices at the same time ?
>       I'm thinking about plugging another SCSI in one of my machines.
>
>       Thanks in advance..
>
>       Regards,
>             Christian
>
>--
>Christian Kuhtz,  Gruener Weg 69c,  D-2000  Norderstedt,  FRG,  planet  Earth
>UNIX-Entwicklung im ftz Hamburg e.V., chk@{data-hh.comlink.de,mcshh.hanse.de}
>

Yes.

-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386
From: davis@chrysanthemum.cs.odu.edu (Mark Davis)
Subject: WordPerfect 5.1 for Unix is available
Followup-To: mark@taylor.twuug.com
Organization: Lake Taylor Hospital Computer Services
Date: Fri, 18 Dec 1992 16:50:10 GMT


Dateline: Friday, December 18, 11:00am EST

OK, I just talked to WordPerfect again.  They just started shipping WordPerfect
for Unix, Version 5.1  *Last Night*.  Don't know about anyone else, but our
purchase order should be on their desk tomorrow!! (We're upgrading from WP4.2)

FYI:  WordPerfect 5.1 is a complex and powerful word processing program which
originally became popular under MS-DEAD.  It has been ported to a number of
operating systems.  The Unix version seems to be slated tword the SCO platform,
but I think it will work under most flavors.  The new version not only
supports text terminals (like 4.2) but also runs with full GUI/WYSIWYG
under X Windows (console, X-terminals, etc).

WordPerfect has VERY good upgrade pricing and policies to take care of their
customers.  Out total upgrade for a 20 user floating licence from 4.2 will
be around $1384 COMPLETE.  I have also heard that if you have any MS-DEAD
version lying around, this can be upgraded the the a Unix version for not
much $$$.  (Although, WP for Unix CAN be expensive for a first-time buyer :< )

We are in the process of a hardware upgrade to an Altos 15000, so it won't
be loaded immediately.  But if there is interest, send me E-Mail and I will
give you an overview of our experience with the new software.  If there is
enough interest, I will post it to the net.

- mark@taylor.twuug.com

/------------------------------------------------------------------------------\
| Mark A. Davis---> Lake Taylor Hospital  ..!uunet!chrysanthemum!taylor!mark   |
| Systems Admin.    Computer Services---> mark@taylor.UUCP / @taylor.twuug.com |
\------------------------------------------------------------------------------/
Newsgroups: comp.unix.sysv386
From: cen@sactoh0.sac.ca.us (Charles E. Newman)
Subject: XBBS
Organization: Sacramento Public Access Unix
Date: Thu, 17 Dec 92 04:30:16 GMT


     Is XBBS Public Domain or Shareware?

-- 
#############################################################
# When I discover this file,  #     sactoh0.SAC.CA.US       #  
#     I will change it!       # UUCP=..ames!pacbell!sactoh0 #
################## default .signature file #############*****
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL -> Re: ISC: ESDI & SCSI in one host ?
Date: 16 Dec 92 17:09:39 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <Bz9x3p.Aqw@ra.nrl.navy.mil>, solsman@ra.nrl.navy.mil (Mark Solsman) writes:
| >>       is ISC able to handle ESDI & SCSI devices at the same time ?
| >>       I'm thinking about plugging another SCSI in one of my machines.
| 
| 
| 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.

  Dell will handle a mixture of SCIS, IDE, MFM, RLL, ESDI, etc, with one
caveat: the system will boot off the non-SCSI drive. Now, it's not
*totally* impossible to boot off the SCSI, but you have to do some
tricks to get there from here. As long as you're willing to boot
non-SCSI you should have no problem. Just install on the boot disk and
then create the stuff for the 2nd following the manual on "adding a 2nd
hard drive or controller."

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: root@candle.uucp (Bruce Momjian)
Newsgroups: comp.unix.sysv386
Subject: Re: What public domain (or otherwise free) ISC device drivers exist?
Date: 18 Dec 92 04:56:38 GMT
Organization: a consultant's basement
X-Newsreader: TIN [version 1.1 PL6]

Several drivers for generic SysV are available in pub/micro/sysv-386 on
gatekeeper.dec.com, or in pub/sysvX86 on ftp.win.tue.nl.
-- 
Bruce Momjian                          |  830 Blythe Avenue
root%candle.uucp@bts.com               |  Drexel Hill, Pennsylvania 19026 
  +  If your life is a hard drive,     |  (215) 353-9879(w) 
  +  Christ can be your backup.        |  (215) 853-3000(h)
Newsgroups: comp.unix.sysv386
From: udalski@astro.Princeton.EDU (Andrzej Udalski)
Subject: Disappering xterm
Originator: news@nimaster
Organization: Princeton University
Date: Fri, 11 Dec 1992 20:18:35 GMT


We are running Roell's X386 (1.1b) server on ISC 2.2.1. Everything
works fine except that occasionally xterm window disappears spontaneously
with no clear reason. This happens specially often when running telnet
in such a window, also in MicroEmacs in C-mode, when showing the
matching fence ( {,[,( etc. ). The latter problem can be fixed if the time
for which the editor "switches" to the matching fence is set low.
Now after we have changed to tcsh shell ver. 6.03, it happens that
during X Windows startup (usually we have two xterm windows to open in
.xinitrc) one of these windows disappears a few seconds after it is
opened.

Any ideas about that?

Andrzej Udalski
Princton University Observatory

udalski@astro.princeton.edu
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: How to get Merge to see DOS partition?
Date: 16 Dec 92 17:21:40 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <Bz9ptE.I7H@chinet.chi.il.us>, ignatz@chinet.chi.il.us (Dave Ihnat) writes:
| 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.

| >I created the DOS partition after I installed UNIX, so I
| >can see how this would be a problem. However, I can't seem
| >to find a way to get Merge to find it now. dosadmin seems
| >to be of no help. Any ideas? Sorry if this is in the Merge
| >docs, I couldn't find it.
| 

  I have put Dell on six machines, five with DOS partitions, and all
worked fine with Merge or booting the DOS partition when desired. The
older release (2.1) has DOS 3.3 or so, and doesn't seem to work with a
DOS partition larger than 32MB. I don't know if that relates to your
problem, I just throw it out.

  Also the DOS partition must be entirely in cylinders 0-1023, so if you
installed the DOS later I trust you didn't put it "up too high" on the
disk.

	[ really nifty workaround deleted ]

  I haven't had any problem with everything working just as it comes out
of the box, so I can't say that what might cause the problem. I did
notice that if I built DOS with one floppy offline it made a DOS image
with that device missing... if you didn't have the DOS partition when
you built your DOS images, you might try rebuilding them again and see
if that helps. See your manual for forcing this, I get it as a side
effect of rebuilding the kernel all the time ;-)

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: solsman@ra.nrl.navy.mil (Mark Solsman)
Newsgroups: comp.unix.sysv386
Subject: Xauth problem when using xdm
Date: 17 Dec 92 19:51:46 GMT
Organization: Naval Research Lab, Washington, DC


Hello-

I am having a problem running xdm on Dell 2.2.

Now that I finally got xdm to run, it seems that it is using Xauth for authorization of my X clients.

There are two problems that I have encountered:
1) When rlogged onto another machine, I cannot get the remote machine to
   connect to my server.  How do I do this??

2) when trying to run xloadimage, it cannot connect to the server.

Now, let me state that I am not really intrested in security here, I just want
to have other clients connect to my server as easiest as possible.

Any ideas?
-- 
Mark Solsman                                 Building 1, Code 5160
United States Naval Research Laboratory      solsman@ra.nrl.navy.mil
Washington, DC                               (202) 767-5769
Xref: sparky comp.unix.sysv386:17479 comp.unix.sys5.r4:858
From: andrew@uel.co.uk
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
Subject: bison-1.14.tar has been uploaded to US4BINR
Date: 17 Dec 92 01:12:46 GMT
Organization: us4binr


bison 1.14 -  the GNU Compiler Compiler (yacc replacement)

author:  Bob Corbett and Free Software Foundation, Inc.
compiled by: Andrew Josey, andrew@uel.co.uk
status: Free software : 
	Copyright (C) 1984, 1989 Bob Corbett and Free Software Foundation, Inc.
upload by: idem


Short description.
Bison is a parser generator in the  style  of  yacc(1).   It
should  be upwardly compatible with input files designed for
yacc.

Example parsers are included in the package
     /opt/lib/bison.simple   simple parser
     /opt/lib/bison.hairy    complicated parser

The  Bison  Reference   Manual,  (in Tex source) is  included  as the  file
/opt/lib/bison/bison.texinfo in this package.

A manual page is provided as part of the package

To download bison-1.14.tar, mail the FOLLOWING 3 LINES to request@us4binr.uucp
or to request%us4binr.uucp@uunet.uu.net

    reply your_email_address
    get prog/tools/bison-1.14.tar
    quit

To get help on uploads and downloads, email

    reply your_email_address
    help
    quit
-- 
----------------------------------------------------------
Jacques Gelinas
Maintainer of US4BINR. Archive site for UNIX SVR4 (386/486) binaries.
jacques@us4binr.login.qc.ca
Newsgroups: comp.unix.sysv386
From: tsh@lesti.hut.fi (Timo Hyv|nen)
Subject: Re: What's Happening to ISC UNIX?
Organization: Helsinki University of Technology, Finland
Date: 16 Dec 92 09:36:02 GMT

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

How about 3.0 users? I heard a rumour about some cheap price and something
that it wouldn't regard users who have migrated to 3.0 from some older version.

Facts anyone?

-- 
I					/ tsh@hut.fi   Timo Hyvonen	I
I	You don't exist! Go away!!      / Vuorikatu 22B44 Hki Finland	I
I   					/ +358-0-654 062		I
I					/ +358-49-704 424		I
Newsgroups: comp.unix.sysv386
From: dwex@cbnewsj.cb.att.com (david.e.wexelblat)
Subject: Re: configuring xdm on Dell 2.2
Organization: AT&T
Date: Wed, 16 Dec 1992 17:21:20 GMT

In article <BzBMr3.9En@news.rn.com> larry@news.rn.com (Larry Snyder) writes:
> dwex@cbnewsj.cb.att.com (david.e.wexelblat) writes:
> 
> >One note for xdm users - unless Dell has fixed a rather nasty little bug
> 
> Dell did fix something in xdm -- at least there was an patch out
> for those on support --
> 
> -- 
> Larry Snyder                                    internet: larry@gator.rn.com
> keeper of the Gator                                  uucp: uunet!gator!larry

I'm pretty sure that the patched xdm fixes a different bug.  The one I think
they fixed had to do with failure to open the mouse if you used xqueue.
This is also fixed in XFree86.  The one to which I referred above is VERY
subtle; I doubt that they found it (SGCS didn't find it either; I told 
them :->).

--
David Wexelblat <dwex@mtgzfs3.att.com>  (908) 957-5871
AT&T Bell Laboratories, 200 Laurel Ave - 3F-428, Middletown, NJ  07748

"The meaning of life?  That's simple.  Try to be happy, try not to hurt
 other people, and hope to fall in love."  -- Mallory Keaton
Xref: sparky comp.unix.sysv386:17422 comp.unix.xenix.sco:3497
From: clayh+@MUDLHEAD.NETWORK.COM (Clayton Haapala)
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
Subject: Re: Will SCO Xenix/Unix/ODT work with Tseng video?
Keywords: SCO, tseng
Date: 15 Dec 92 19:53:50 GMT
Organization: Network Systems Corporation

In article <1992Dec15.073543.6831@griffin.itc.gu.edu.au>, rosser@kraken.itc.gu.edu.au (Brad Rosser) writes:
|> 
|> Will Xenix 2.3.4, SCO Unix (versions 2.0 & 4.0) and SCO ODT 2.0 support
|> the Tseng card?
Xenix 2.3.4 runs fine with my ET-4000 with 1MB. I have run SCO X Windows for Xenix
on it.  (Got a grafinfo file for the Orchid Prodesigner-II to make it work.)  I
also run mgr.  Oh, the X I ran in 800x600 mode.  16 colors, of course.
-- 
Clayton Haapala	(clayh@network.com)	
Network Systems Corp.			Life needs more blue furry monsters.
7625 Boone Ave N MS10
Minneapolis, MN 55428-1099
Newsgroups: comp.unix.sysv386
From: steve@compunet.uucp (Steve Snow)
Subject: Re: Problem with ICS 3.0 and TEXEL CDROM
Organization: CompuNet Systems, Louisville KY (502-231-5908 & 5910)
Distribution: usa
Date: Thu, 17 Dec 1992 12:48:32 GMT

mittag@megatek.com (Larry Mittag) writes:

>In article <584@rri.UUCP> tim@rri.UUCP (Tim Buck) writes:
>>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
>>

>I just spoke to the tech support guy at Texel, and he says he already has a
>fix. He said it would be available next week, but I reminded him that there
>was some holiday or other during that period, so he amended that to the week
>after. The number for Texel is 1-800-886-3935. I'll let you know how it works
>out.

>Larry Mittag
>mittag@megatek.com

Thats good news but its a little too late. I also talked to tech support at
TEXEL and all they told me was sorry they couldn't help and good luck. I also
talked to Sunsoft who told me they did not support the drive. After no help
from either vendor I returned the drive and ate the $70 restocking charge. I
have since then ordered a Toshiba drive that Sunsoft assured me would work
with ISC 3.0. 

I am very unhappy with TEXEL tech support and will not be buying any more of
there drives.

  -- Steve Snow

-- 
|---------------------|----------------------|---------------------------------|
| Steve Snow          | CompuNet Systems     | Public Access UNIX System       |
| steve@compunet.uucp | 8412 Berea Dr.       | 300-19200 baud, V.32 & HST      |
|                     | Louisville, KY 40228 | 502-231-5908 & 502-231-5910     |
Newsgroups: comp.unix.sysv386
From: tkevans@fallst (Tim Evans)
Subject: Re: Dell Unix, 14.4Kb, and DigiBoards, HELP!
Reply-To: tkevans@eplrx7.es.dupont.com
Organization: Tim Evans
Distribution: usa
Date: Sat, 19 Dec 1992 14:01:13 GMT

sterling@oldcolo.com (Bruce Sterling Woodcock) writes:

>In article <1992Dec8.225638.29523@dms.agames.com> yaturner@dms.agames.com (James M. Turner) writes:
>>I have the following configuration:
>>Dell Unix SVR4.2.2 running on a 486/50
>>DigiBoard multi-port controller
>>Telebit T3000RM modem
>>sometimes the T3000's get screwed up and the DTE speed gets set to 14400
>>baud, my problem is that I can't find anyway in Unix to open a serial
>>line at that baud rate. Any ideas??

>We use Dell SVR4 here as well, and also found that the system did not "support"
>14.4K speeds.  According to what was told to me, 14.4 is a "standard" RS-232C
>baud and so you couldn't use it.  The solution?  Tell the system to use
>38400 (which is a standard speed) for the 14400 modem.  The modem will still
>talk over the phone line at 14.4, but it will communicate with the serial
>port at 38.4.  Everyone is happy.

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.  To take advantage of the compression
feature, you need to feed the modem data at a faster rate than it
transmits it so the compressin can happen.  Thus, you set your "rate"
at 38400 (or higher, if you can).
-- 
UUCP:		{rutgers|ames|uunet}!mimsy!wb3ffv!fallst!tkevans
INTERNET:	tkevans%fallst@wb3ffv.ampr.org
Tim Evans	2201 Brookhaven Ct, Fallston, MD 21047
Organization: Penn State University
Date: Wed, 16 Dec 1992 00:56:23 EST
From: Jeff Wolfe <JTW106@psuvm.psu.edu>
Newsgroups: comp.unix.sysv386
Subject: x3270 for dell svr4?

I hate to ask this, 'cause I suspect it is a FAQ, but ...
Does anyone have a copy of X3270 that will compile under Dell sVr4?
I'm not much of a programmer, but I know my way around makefiles somewhat.. :)

-Thanks...
-Jeff
From: shih@ohm.berkeley.edu (Sun-Inn Shih)
Newsgroups: comp.unix.sysv386
Subject: Re: UHC SVR4 + ARCHIVE XL  URGENT HELP NEEDED!!
Date: 19 Dec 92 21:36:29 GMT
Organization: U.C. Berkeley -- ERL
NNTP-Posting-Host: ohm.berkeley.edu

Hi again,

Sorry, I don't know how to be more specific. However, I
did reboot after installing the driver. After reboot, Sysadm 
tries to access a dev: '/dev/rmt/c0s0' and this device does not
exist. Any info is greatly appreciated.

Thanks in advance.

Alan


--
=======================================================================
God's Last Msg:

        We Apologize for the Inconvenience.
Newsgroups: comp.unix.sysv386