HDTenEightyP/NetNews huggingface dataset:
From: bilse@login.dkuug.dk (Per G. Bilse)
Newsgroups: comp.unix.sysv386
Subject: Help: g++ & V.4
Summary: Need help w .section for C++ on V.4
Keywords: g++ c++ V.4 gnu assembler 386
Date: 24 Jul 92 20:46:33 GMT
Organization: ``bilse''

I have a V.4 system (Consensys, to be specific) and have problems
with the assembler output from g++.  For constructors and destructors,
g++ outputs special sections ...

  .section .dtors,"a",@progbits .long <address>

... (and with .ctors for constructors).  However, the assembler distinctly
dislikes anything following the ``"a"''.  I've tried unsuccessfully
to fiddle about with the output from g++, trying to use .rodata etc,
but with no success.  Now, the question is if the assembler on
Consensys is out of line, or if the method of handling C++ information
is different on '386 V.4 from that on other V.4s.

Any pointers would be greatly apprecia
Any pointers would be greatly appreciated as I'm sort of in dire
straits with this one (I need to get groff running before the end of
the month and groff is written in C++).  If possible, cc to my regular
account (bilse@dkuug.dk) as well as posting.

In advance, thanks.
--
Per G. Bilse:   bilse@dkuug.dk   bilse@login.dkuug.dk  per@bilse.dk
work DKUUG, Universitetsparken 1-3, 2100 Copenhagen OE  +45 31 39 73 22
priv Dannebrogsgade 35, DK-1660 Copenhagen V.  +45 31313971
      "It's spaghetti, Jim, but not as we know it"
From: jack@dsl.pitt.edu (john p. nelson)
Newsgroups: comp.unix.sysv386
Subject: asy device uses 2 IRQs?  any way to free them?
Keywords: asy drivers IRQ Starlan NAU
Date: 24 Jul 92 01:50:22 GMT
Organization: Decision Systems Laboratory, Univ. of Pittsburgh, PA.
Originator: jack@cadre.dsl.pitt.edu


  In trying to set up an AT&T 6386 to run WINTCP/386, I seem to be out
of IRQ's.  I have a PC Starlan NAU already at IRQ2, cartridge tape
drive at IRQ5, and IRQ6 seems to be used by kd driver (keyboard) and
LPD has IRQ7.  The Starlan-10 NAU I want to use for tcp uses on
2,3,4,5,7 as does the Starlan NAU.
  IRQ3 and IRQ4 seem to be assigned to asy driver, I guess to control
the remote boot feature.  This seems a high price to pay, unless I
can find an NAU with IRQ10 or some further flexibility.
  Am I understanding this correctly?  Is there any way to get rid of
the asy 'feature', or to free up at least one of the IRQ's?
  Thanks for any help.
  Jack Nelson
-- 
John P. Nelson, M.D., U. of Pittsurgh, Dept of Psychiatry
(412) 624-4802, 3811 O'Hara St, Pittsburgh PA 15213
jack@nelslab.wpic.pitt.edu jack@cadre.dsl.pitt.edu jpn@med.pitt.edu 
Newsgroups: comp.unix.sysv386
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: >>An example of Dell's product 
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Thu, 23 Jul 1992 16:54:01 GMT

In article <1992Jul18.142650.24227@virtech.u>, cpcahil@virtech.uucp writes:
| That isn't what was said.  What was said was [...]

Sorry, but that *isn't* what was said either.

What was said was:

| Bull.  [...] your complaint is unjustified.  We're familiar with your
| problem - even in development we've heard your whining, [...] IT'S NOT
| DELL'S PROBLEM that someone else's printer and cable doesn't work with
| our machine/software.  We have no obligation or commitment to make your
| particular (and peculiar) setup work [...] I *personally* wish you would
| find out what Compaq is selling these days.

and

| Give us a frigging BREAK! [...][Dell] sales people are notorious 
| for knowing little about software and quick to dispose of callers
| who waste their time asking about it.

I don't care who is right or wrong on the technical issue.  I
don't care whether the customer is an asshole or not.  I don't care
whether dell has any obligation to make *anything* work.

What I care about is what the vendor's representative said (publicly)
to a *customer*.  (And BTW, his disclaimer is meaningless, considering
he was talking about a *business* issue concerning Dell and a *customer*.
In this topic, he *is* acting as Dell's representative.  It is reasonable
to take his statement, lacking any authorative denial, as Dell's position
on this issue.  If this is *not* Dell's position, then I think Dell should
tell us what their position is.)

In my company, some things you *never* tell a customer are:

  1) Bull.  Your complaint is unjustified.  (even if it is).

  2) Give us a frigging BREAK! (even if that is what you really want).

  3) We're familiar with your whining.  (even if we are).

  4) It's not our problem.  (even if it isn't).

  5) We have no obligation to make your system work (even though you don't).

and especially

  6) We hope you go to the competition (even if you do).

I have very little sympathy with those in this forum who attempt to
appologize away these sentiments.  That is because I suspect that these
same people are the first to complain when a sales person is rude, or when
a product fails to perform, or when *their* complaints are poorly handled.

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
Xref: sparky comp.unix.sysv386:12456 comp.os.linux:6720 comp.sys.ibm.pc.hardware:20320
From: shite@sinkhole.unf.edu (Stephen Hite)
Newsgroups: comp.unix.sysv386,comp.os.linux,comp.sys.ibm.pc.hardware
Subject: Re: Mis-convergence vs mis-registration (Was: What the 17" monitor reviews)
Date: 26 Jul 92 13:21:42 GMT
Organization: University of North Florida, Jacksonville


   In case anyone missed my followup posting to the problem I was having
with the new Nanao F550i I bought, the monitor is fantastic.  It turned
out that the new Diamond Speedstar 24 card I got at the same time *has*
to be setup correctly to work with your monitor by a DOS program called
vmode.com.  Diamond Computer is now using a new method to program their
graphic card dot clocks (the DS 24 and Stealth use it...smode.com is the
setup program for the Stealth).  Several on the net are trying to get
Diamond Computer to give out the information on how to program the dot
clocks.  So far, they haven't given a definitive answer.  Some /have/ been
"turned away" by their staff, but others appeared to have gotten to 
higher ranks in the company.

Back to the my monitor confusion....

  Since the DS 24 timings sent to the monitor before I used vmode.com were
not correct for 1024x768, the result was a severe moire' problem. 
Lesson learned...RTFM. ;-)


P.S.  Bob Diez (sp?) in tech support at Nanao is one of most patient,
      knowledgable (about what he's supporting) and helpful people you'll 
      ever meet.  I wish all of my software/hardware vendor 
      experiences could be so positive.  


Steve Hite
shite@sinkhole.unf.edu
From: mtcusa@tigger.jvnc.net (Multilingual Technogies Corporation)
Newsgroups: comp.unix.sysv386
Subject: SCO Unix - getting version level - uname doesn't work
Date: 27 Jul 92 20:25:08 GMT
Distribution: usa
Organization: JvNCnet, Princeton University, NJ
Originator: mtcusa@tigger.jvnc.net

HELP:

I need to determine if I'm on a SCO 2 or SCO 4 box from software.
One would think that the obvious solution would be 'uname(2)'.

Think again.

******************

Here is program A:

#include <stdio.h>
#include <sys/utsname.h>

main()
{
struct utsname x;

	uname(&x);

	printf("release: %s\n", x.release);
	printf("version: %s\n", x.version);
	printf("machine: %s\n", x.machine);
}

On a SCO 2 box It produces:

	release: 3.2
	version: 2
	machine: i386

On a SCO 4 box It produces:

	release: 3.2
	version: 2
	machine: i386

Not much help here.
***********************

Here is some output of uname -X on a SCO 2 box

Release = 3.2v2.0
KernelID = 90/06/10
Machine = i80386
BusType = AT

Here is some output of uname -X on a SCO 4 box

Release = 3.2v4.0
KernelID = 92/01/20
Machine = i80486
BusType = ISA

**********************

AHA! you say, just use the same calls!!!

But what are those calls?  Where are they documented?

God!! I HATE guru software!!!!!   @#%&$%@&&%#!%!@&%$#$!!!!!!!!!!


George Bogatko - mtcusa@tigger.jvnc.net
From: mah@parrot.prv.univie.ac.at (Michael Haberler)
Subject: Re: adding SLIP to sVr4 (Dell archive)
Reply-To: mah@ic.co.at
Organization: Vienna University
Date: Tue, 28 Jul 1992 22:54:16 GMT

In article <1992Jul28.183910.26898@crd.ge.com>, davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
|> In article <8160@orbit.cts.com>, dougm@pnet51.orb.mn.org (Doug Mcintyre) writes:
|> | What is needed to add SLIP to sVr4? I take it I need a bootp client/server of
|> | some kind, and someway to add the SLIP commands into the existing TCP/IP
|> | implementation?
|> 
|>   There's a public domain version floating around, or maybe you can get
|> something off the Dell archives, SLIP is part of their V.4.


Unfortunately, at closer inspection it turns out that neither of the
two slip packages on dell*.dell.com are the base of the code 
distributed by Dell. I found out because I wanted to add VJ compression.


-michael

-- 
Michael Haberler 		mah@ic.co.at,  mah@awiwuw11.bitnet
A-1070 Vienna, Austria, Mariahilferstrasse 126
Tel: +43 (1) 961-679 (voice & fax) D-Netz/Cell Tel: +43 (663) 811-056
From: ddewolfe@dragon.acadiau.ca (Dave DeWolfe)
Newsgroups: comp.unix.sysv386
Subject: Crisp 2.2e on Esix
Keywords: crisp,esix
Date: 29 Jul 92 11:05:53 GMT
Organization: Acadia University

I have installed the Crisp esitor on Esix 4.0.4.  Everything works fine
except that a few keys like cntl-rightarrow , keypad * - + are not
recognized.  I have installed the editor on SCO, Microport with no
trouble.

Can the problem be in /usr/lib/keyboard/keys?  Any suggestions would
be appreciated.

Thanks



--
Dave DeWolfe                    |  e-mail:
Acadia Center for               |  dave.dewolfe@acadiau.ca 
       Estuarine Research       |  (902) 542-7988  FAX (902) 542-1454
Acadia University               |  "Practice random kindness and senseless
Wolfville, N.S.  B0P 1X0 Canada |  "acts of beauty . ." - Anne Herbert
-- 

--
Dave DeWolfe                    |  e-mail:
Acadia Center for               |  dave.dewolfe@acadiau.ca
Newsgroups: comp.unix.sysv386
Subject: FTP sites for SVR4 code? any there?
From: bmyers@mcopn3.dseg.ti.com
Date: 21 Jul 92 09:46:33 CST
Organization: Texas Instruments Defense Systems & Electronics Group

Are there any anon FTP sites that have or support ported code to
SVR4?

could someone please post them or send me a message?

thanks
-bob

Newsgroups: comp.unix.sysv386
Subject: Re: Dell Unix..
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Fri, 24 Jul 1992 18:21:44 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Jul22.174516.22924@compu.com> fr@compu.com (Fred Rump from home) writes:
>rmk@rmkhome.UUCP (Rick Kelly) writes:
>>Sure, you can buy a less polished version of SVR4, and spend your time at
>>church keeping it running.
>
>Whatever V4 has to do with running a UNIX system at a church escapes my sense 
>of logic. We have over 200 such systems running in churches without any 
>sysadmins or general computer knowledge etc - just your ordinary 
>volunteer/secretary/housewife/minister/priest type of user who wouldn't know 
>an operating system from a prompt as they never see either.
>
>They all run on that nasty SCO environment which we've all heard so much about 
>here in past times (it's Dell's turn today).

SCO, warts and all, is a fairly stable environment.  I have clients who
use SCO systems for database applications.  They know how to log in and
start up the app, and how to use email.  A pc running SCO with 5 or 6
terminals seems to be a good reliable office machine.

>And by the way, these non-computer types read news (our own cdi.* groups), 
>write and read email, and generally feel at home with their systems as if they 
>were designed for churches - which they were, of course. It makes for all the 
>difference in the world to let a vertical VAR handle all that computer stuff 
>and let users be users and do their church thing. We've spent around 20 
>man/years at the back end so that life would be easy at the front end. 
>
>Personally, I've never believed in teaching users about computers and 
>operating systems - confuses the hell out of them. It's tough enough 
>remembering all the things you can do with the application. :-)

Which is why you give them a stable UNIX product.  You could run your
stuff with Dell SVR4 and expect as good or better reliability.  If you
were to give your clients Consensys SVR4, you might have to spend a lot
more time dealing with os flakes and bugs.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.unix.sysv386
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: RFD: comp.unix.* reorganization
Organization: Kithrup Enterprises, Ltd.
Date: Sat, 25 Jul 1992 03:23:41 GMT

In article <14q9hvINNgbd@smaug.West.Sun.COM> Richard.Mathews@West.Sun.COM (Richard M. Mathews) writes:
>But that it just what Merge does (I haven't looked at the internals of
>VP/ix, so I can't say for certain what it does).  

But you're willing to claim you know it does...

>Your code (DOS) executes
>an outb instruction.  But the instruction is not executed by the hardware.

Wrong.  At least in some cases.

The x86 (x > 2) can allow a task to have IO privileges (I know I misspelled
it, sorry 8-)).  This is how X works under UNIX on an SCO machine, for
example:  the X server is granted io priv's for a range of io ports, and can
then, merrily, go about at full speed.  DOS Merge works the same way (or,
rather, it *can*:  you want, in general, to explicitly allow some addresses,
and you never really want to give others, to the process).

>You trap to the kernel which decodes the instruction and executes it's
>own instructions to perform what you would have expected that instruction
>to do.  The instruction executed by the kernel is not necessarily the
>same one executed by the DOS process -- for example an "outb immediate"
>executed by the program ends up being emulated by an "outb dx" somewhere
>in the kernel.  

Completely not true, for UNIX and for DOS-under-UNIX.  If the io port is not
allowed for that process, then Merge -- which is a user-level program
(although it does have some kernel hooks) -- will "decide" what to do, and
how best to proceed.  For the disk addresses, for example, it will emulate
them, but it won't do an "outb" at all; instead, it will read, using the
UNIX kernel, the appropriate block, or will lie and act as if it had
actually done the work when it's actually done nothing at all.  For others,
it will just fail completely, with a trap.

-- 
Sean Eric Fagan  | "My psychiatrist says I have a messiah
sef@kithrup.COM  |  complex.  But I forgive him."
-----------------+              -- Jim Carrey
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.sysv386
From: krs@ardvar.moundst.mn.org (Kent Schumacher)
Subject: CD-ROM drives and SCO
Organization: Ardvar Research
Distribution: usa
Date: Fri, 24 Jul 92 01:02:07 GMT

I am planning on purchasing a CD-ROM drive to be used on a 486-25 ISA
bus computer running SCO UNIX SVR3.2.2 (soon to be upgraded to release
3.2.4).  The computer has the standard cards - SVGA, 2S1P + IDE +
Floppy as well as a Marstek hand scanner and Digiboard PC8 serial port
board.  I also run DOS and Windows on this machine so compatability on
the DOS side is necessary.

I am looking for any info that will help me make an intelligent
purchase.

Specific questions that come to mind are:

Do I need to purchase a SCSI card?  What are the issues here?

Is drive performance something to worry about (i.e.  600ms as opposed
to 300ms)?

What features do you consider important?

Are there any specific CD-ROM Drives to recommend?

Any email or posts will be appreciated - I'll summarize email and post.

Thanks,
Kent Schumacher


-- 
---
I've spent so much on this computer, I can't afford a signature
Kent Schumacher
Newsgroups: comp.unix.sysv386
From: slangley@constant.demon.co.uk (Simon Langley)
Subject: esix 4.0.4 experiences 
Distribution: world
Organization: home
Date: Thu, 30 Jul 1992 23:00:08 +0000


In article <3658@randvax.rand.org> edhall@rand.org writes:

>freeware SLIP is an improvement.  I suspect that the ESIX code would be
>good enough for a simple point-to-point setup if the connection was
>stable. (I've been beta-testing Marc Boucher's PPP driver (marc@cam.org);
>it's 99 and 44/100% solid at the moment--I hope it gets released soon.
>So I've not played much with SLIP.)

The Esix slip is not that much use for a point-to-point setup as it requires
three totally separate network addresses.  I wanted to connect my machine
(158.152.8.12) to a gateway machine (158.152.1.65) and the Esix slip cannot
do this.  This came from Esix tech support BTW.

I am also beta testing Marc's port and it has worked perfectly.

     ----------------------------------------------------------------------
       Simon Langley                 email: slangley@constant.demon.co.uk
     ----------------------------------------------------------------------
From: edhall@rand.org (Ed Hall)
Newsgroups: comp.unix.sysv386
Subject: Re: esix 4.0.4 experiences
Date: 31 Jul 92 00:05:48 GMT
Organization: RAND Corporation.

In article <712539230snx@constant.demon.co.uk> slangley@constant.demon.co.uk (Simon Langley) writes:
>The Esix slip is not that much use for a point-to-point setup as it requires
>three totally separate network addresses.  I wanted to connect my machine
>(158.152.8.12) to a gateway machine (158.152.1.65) and the Esix slip cannot
>do this.  This came from Esix tech support BTW.

That's how I used it.  The SLIP connection was its own Class C network.
A waste, I know; my current setup (with Marc Boucher's PPP) doesn't use
any such nonsense.

		-Ed Hall
		edhall@rand.org
Newsgroups: comp.unix.sysv386,comp.os.linux
From: cummings@hammer.Prime.COM (Kevin Cummings)
Subject: Re: Warning about Diamond Speedstar 24
Organization: Prime Computer R&D
Date: Fri, 24 Jul 1992 18:37:54 GMT

In article <1992Jul23.133104.18681@Informatik.TU-Muenchen.DE>, roell@informatik.tu-muenchen.de (Thomas Roell) writes:
> Diamond has a new programmable PLL syntesizer on the newer board. The
> Stealth VRAM BIOS Rev 2.0 and newer are examples of these cards. You
> have to programm this chip before it will give you a new frequency
> output besides those two standard clocks.

Does anyone know how to do this?  Or is it time to start disassembling
the Stealth BIOS?

=================================================================
Kevin J. Cummings                       PrimeService
20 Briarwood Road                       A Computervision Company
Framingham, Mass.                       500 Old Connecticut Path
					Framingham, Mass.
Work:  cummings@primerd.Prime.COM
Home:  cummings@kjc386.framingham.ma.us

Std. Disclaimer: "Mr. McKittrick, after careful consideration,
		  I've come to the conclusion that your new
		  defense system SUCKS..."   --  War Games
=================================================================
From: ilan343@violet.berkeley.edu (Geraldo Veiga)
Newsgroups: comp.unix.sysv386
Subject: Destiny X Dell, Esix, Microport etc.
Date: 25 Jul 1992 16:30:08 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: violet.berkeley.edu

I've just read a review of USL's SVR4.2 in this week's  OST.  They seem
to confirm some of pre-release hype about Destiny. (And this comes from
a magazine that fell head over heels for NT). Does anybody have
an informed guess regarding other SVR4 vendors release plans for
products based on  SVR4.2?  It looks like they will be facing stiff
competition from Univell both in price and in features.

Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Dell SVR$ (and Dell hardware) total lack of success on Postscript
Organization: The Gator Public Access Unix Site - 219-289-3745
Date: Tue, 28 Jul 1992 11:22:07 GMT

gram@aim1.aztec.co.za (Graham Wheeler) writes:

>marketing strategy, it is clear that Dell UNIX is rapidly becoming a product
>in its own right. Dell could make the most of this success by dropping their
>attitude of `if your hardware isn't ours, we're not interested', and instead
>marketing Dell UNIX as a competitive product to SCO, ESIX, etc, and providing
>better support to those of us who already had the hardware and just wanted the
>software.

Well I can speak as well as others on the ability of Dell Unix to run on
non Dell hardware.  I've had 4 different motherboards over the last year 
running Dell SVR4 -- all without any hardware problems.  Dell Unix is very
stable and solid.

-- 
Larry Snyder                                    internet: larry@gator.rn.com
4950 Estero Blvd, Ft. Myers Beach, FL            uucp: uunet!rde!nstar!larry
Newsgroups: comp.unix.sysv386
From: gec@admiral.uucp (George E. Cabanas)
Subject: ODT and startx problem
Reply-To: gec@admiral.uucp (George E. Cabanas)
Organization: The Grid/Waffle BBS, 203-661-2873, -1279, -0450, -2967
Date: Tue, 28 Jul 1992 01:34:49 GMT

Hello all,

I'm encountering a new problem when I start X under SCO-ODT 1.1.
It did work a while ago, but I haven't used it in some time.

To the best of my knowledge, I haven't changed any config files
and I haven't deleted anything.  This error occurs to any user,
including root.

This is the result of executing "startx."

==========
$ startx
Open event driver failed:: No such file or directory
                                                    giving up.
xinit:  Invalid argument (errno 22):  unable to connect to X server
Open event driver failed:: No such file or directory
                                                    Open event driver 
failed:: N
o such file or directory
                $

==========

Any help would be greatly appreciated.

Thanks.

George

--
gec%admiral.uucp@yale.edu (George E. Cabanas) <yale!admiral!gec>
The Admiral's Public UNIX - Greenwich, CT - System Administrator: Doug Fields
(HST/V32) (203)661-2873 -- (PEP/V32) -1279 -- (V32) -0450 -- (V29/MNP6) -2967
>FREE!< Unix shell accounts, Usenet access, and Internet-style mail available
From: bilse@login.dkuug.dk (Per G. Bilse)
Newsgroups: comp.unix.sysv386
Subject: Re: I need Help..!
Date: 27 Jul 92 16:28:42 GMT
Organization: bilse

>	I did buy a 386sx recently..., can i run a Unix sistem on my computer?
>	How i do this??.., and how can i obtain the software ?..

You can run UNIX on a 386SX, but it will be a bit on the heavy side
to work with (depending on clock-speed, 25MHz should be reasonable,
this is simply a linear scale).  However, you'll need at least 4Megs
of memory (8 if you want to run X) and 80-200 Megs of harddisk.  Also,
many cheaper motherboards are a bit flakey and don't run well in 32-bit
protected mode.  Generally, hardware compatibility is a critical issue,
much more so than for DOS.

As for _getting_ a UNIX system, and which UNIX, I can't really help
you ... follow the group, ask around, buy the apropriate computer
mags ... spend _at least_ 2-3 months and try to understand as much
as possible about the issues (hardware, version [V.4 vs V.3], etc)
before making a decision, and try to ensure you get it from somebody
who will give proper support.
--
Per G. Bilse:   per@bilse.dk  bilse@dkuug.dk   bilse@login.dkuug.dk
work DKUUG, Universitetsparken 1-3, 2100 Copenhagen OE  +45 31 39 73 22
priv Dannebrogsgade 35, DK-1660 Copenhagen V.  +45 31 31 39 71
      "It's spaghetti, Jim, but not as we know it"
Newsgroups: comp.unix.sysv386
From: wittesa@reks.uia.ac.be (Willy Wittesaele)
Subject: kermit
Organization: U.I.A.
Date: Wed, 22 Jul 1992 15:21:04 GMT

hello ,

yes the C version of kermit can be compiled for SCO UNIX
(I have it running under SCO 3.2.2) and the package can be
obtained via ftp from Columbia university (have no exact
address here available).


willy

wittesa@reks.uia.ac.be