HDTenEightyP/NetNews huggingface dataset:
From: q78262@pbhrzx.uni-paderborn.de (James Bond 007)
Newsgroups: comp.unix.sysv386
Subject: HELP NEEDED ! My 386 Unix does not boot !!!
Date: 15 Apr 92 11:56:19 GMT
Organization: Uni-GH Paderborn

Hello folks !!!

Hope that someone can help me !!!!

Always when I try to boot a new 386 unix from floppy disk , the system
crashes before a single harddisk operation is done.

That would be usually a disk failure... but the SAME floppy works
perfectly on the computer of a friend of mine. SO:

WHAT IN HELL IS WRONG WITH MY COMPUTER ????

...because with the SAME disk i managed to install unix on MY computer
three days before...and now...with the same (working) disk and the SAME
computer there only is a system crash.

HELP ME ... EMAIL ME ... PLEASE !!!!!

Dirk 007 Vogelsang

--
________________________________________________________________________________
| email :                            ___  ___  ___     IRCnick :               |
|                                   /  / /  /    /                             |
| q78262@pbhrzx.uni-paderborn.de   /  / /  /    /      JamesBond               |
Newsgroups: comp.unix.sysv386
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: Cyrix CX486SL
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Fri, 10 Apr 1992 09:42:04 GMT

In article <3147@wzv.win.tue.nl> rob@wzv.win.tue.nl writes:
+----- [heavily edited] ----------
| I read in a magazine lately that Cyrix has announced a new processor,
| the CX486SL, a clone of the Intel i486...
| the Intel 386SX. This made me wonder:
| - 386SX is surface-mounted?
| - 386SX has 16-bit databus, CX486SL is also only 16 bits external ?
| - Does it have a coprocessor, like a real i486 ?
+---------------

- Don't know about the surface-mount issue, would have thought PLCC, though.
  But it doesn't matter [see below].
- Yes, it's 16 bits external.
- Yes, it has the 486's "internal 487". (Cyrix also makes external 487 clones.)

+---------------
| The concept isn't as interesting as I first thought, almost all
| SX boards and PC's are 16 or 20 Mhz, 25 Mhz SX'es are rare, so
| why go for this strategy ?
+---------------

They aren't aiming for end users to swap out their 386SX's. My guess
is they feel they can get a lot of laptop manufacturers to buy their
chip as an easy upgrade path, while staying with the form factor and
power consumption of the 386SX.


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)335-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94039-7311
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: gcc 2.0 for ISC 2.2.1?
Date: 15 Apr 92 16:00:20 GMT
Organization: Private system -- Orlando, FL

In article <1992Apr14.005455.20531@mav.com> stu@mav.com (Stu Donaldson) writes:
>Since then, I have rebuilt X386 1.1b with the new gcc2.1, and have
>encountered a bug that I also had with the 1.39 version of gcc.
>I haven't been able to track this down other than to something with
>the floating point code that is generated.

Yes, I've seen instances of gcc 1.39 generating bad floating point
code.  I ran into it just yesterday at the office.  I've found that
compiling with -O sometimes resolves the problem, but not always.
Yesterday, it didn't, and I had to recompile the program with cc to
get it to work right.

>the server will crash on some
>functions such as in miWideSegment with a Floating Point Exception
>error.

I don't recall seeing exceptions generated by the bad code, just
incorrect results.  Usually floating point comparisons or assignments
fail.
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)
Newsgroups: comp.unix.sysv386
From: mark@cyantic.com (Mark T. Dornfeld)
Subject: Disk Mirroring
Organization: CYANTIC Systems
Date: Fri, 17 Apr 1992 02:17:42 GMT

Is there any disk mirroring technology available that will work with any or
all of the existing Intel Unix OSs including Sys Vr3 and Vr4.  The
application is standard: high availability accounting system.

I'd like to keep the database simple and let the hardware or OS do the hard
work.

Thanks
-- 

Mark T. Dornfeld                              Voice: (416) 234-9048
CYANTIC Systems                               Facsimile: (416) 234-0477
101 Subway Crescent Suite 2103                Email: mark@cyantic.com
Xref: sparky comp.unix.sysv386:8724 comp.unix.xenix.sco:1921
From: cbuckley@unix1.tcd.ie (Colm Buckley)
Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
Subject: Free X11 for SCO?
Date: 16 Apr 92 16:14:22 GMT
Organization: Trinity College, Dublin

This may be a FAQ, but I don't see it on the FAQ list...

Has some kind soul managed to port X11r5 (or even r4) to SCO UNIX? I'm
getting a 486 with SVGA, and putting SCO 3.2.4 on it (for pro development
work; I'd personally prefer BSD386, but business is business :( ), and I'd
love to see it running X. I could splash out on the ODT Devsys, but I find
SCO's prices a bit excessive; considering the bulk of X is free, somebody
may have written suitable display drivers for VGA/SVGA? I seem to recall
that Per Lindqvist (spelling?) had done this for Xenix - is there an
equivalent Unix port?

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: comp.unix.sysv386,comp.sys.ibm.pc.hardware
From: rfarris@rfengr.com (Rick Farris)
Subject: Re: ATI Graphics Ultra vs. 8514 Ultra
Organization: RF Engineering, Del Mar, California
Date: Fri, 10 Apr 92 02:45:15 GMT

In article <1992Apr8.183411.23336@loop.uucp> keithl@loop.uucp (Keith Lofstrom;;;520-1993) writes:


> ATI offers two very fast boards, the Graphics Ultra and the 8514 Ultra.

> I haven't had much luck getting information from ATI on
> the relative merits of the two approaches for a SVR4
> system (ESIX); a posting about the relative merits of the
> two cards would be appreciated.

There's an article in the February 1992 issue of UNIXWORLD
magazine called "Maximizing Your PC for Graphics" that
addresses the two most effective accelerated graphics
solutions for PC-Unix: ATI's 8514-based cards and TIGA
cards.

I think it does a pretty good job of describing the
strengths and weaknesses of each, why not check it out?

--
Rick Farris  RF Engineering POB M Del Mar, CA 92014  voice (619) 259-6793
rfarris@rfengr.com     ...!ucsd!serene!rfarris      serenity bbs 259-7757


Newsgroups: comp.unix.sysv386
From: keith@dinosaur.lonestar.org (Keith Cantrell)
Subject: Sugestions on a good/fast X11R* video card
Organization: Private system, Dallas Tx
Date: Wed, 08 Apr 1992 04:34:30 GMT


Well I gave up on my Diamond SpeedStar after being TOTALLY disappointed with
the performance.  Not to fault Diamond SpeedStar or X11R4, but the fact that
256 colors at 1024x768 over a 16 bit bus is just not going to work.  So
my question is, what is a good VGA compatible card that will allow me to
down load the X11R4 (or X11R5) server to it so that the performance will
not be hampered by the 16 bit bus, or the CPU.  I don't want to say that
money is no object, but I think I have learned my lesson about trying to
get a cheap solution, but at the same time cannot justify speed thousands
of dollars on a video card.

My current setup:
Gateway2000 25MHz 386 with 32k cache
80387 Co-Processor
ATI's VGA wondercard with 512k ram.
CrytalScan1024 1024x768 interlaced 14 inch color monitor.
ISC's X11R3 version 1.2 or X11R4 patchlevel 18 if it will run better.
Microsoft 3 button serial mouse.
heavy VPIX usage (ie. the new video card MUST support virtual terminal
                      switching to a VPIX session)

Thanks,

Keith

P.S.  If I get enough responses I will summarize and post back to the net.

-----------------------------------------------------------------------
Keith Cantrell                    Phones:  hm: 214-492-1088
                                           wk: 214-699-2509 
USMAIL:                          EMAIL:
2100 Sonata Ln                   keith@dinosaur.lonestar.org
Carrollton TX 75007                           or
                                ...!uunet!digi!dinosaur!keith
-----------------------------------------------------------------------
Newsgroups: comp.unix.sysv386
From: bruno@thunder.mcrcim.mcgill.edu (Bruno Hall)
Subject: Re: SVR4 DAT users: Questions about restoring your system
Organization: McGill University, McRCIM
Date: Fri, 17 Apr 92 02:15:36 GMT

In article <336@wmms.UUCP> david@uucp (David R. Mayne) writes:
>[...]
>BTW, is anyone using a DAT with ESIX SVR4 ?

How about with Dell SVR4?
-- 
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Bruno Hall  |  VE2HUM  |  bruno@mcrcim.mcgill.edu         
McGill Research Centre for Intelligent Machines - Controls Group
New systems generate new problems -- Join the Flat Earth Society.
From: wiesel@ipf.bau-verm.uni-karlsruhe.de (Joachim Wiesel)
Newsgroups: comp.unix.sysv386
Subject: Re: New viking sparc processor?
Date: 10 Apr 92 09:50:56 GMT
Reply-To: wiesel@ipf.bau-verm.uni-karlsruhe.de
Organization: IPF, University of Karlsruhe

This is a figure for a SPARC-2 clone (OPUS 5000) with a Fujitsu 420MB 3 1/2 inch
disk (2623SA):

   time dd if=/dev/rsd1g of=/dev/null bs=10240k count=1
    1+0 records in
    1+0 records out
    
    0.0u 1.0s  0:06  16% 0+4708k 0+1io 0pf+0w
                ^^^^  6 (six) seconds ...
                 about 1700KB/s   not too bad 

Joachim
---

Joachim Wiesel, Institut fuer Photogrammetrie und Fernerkundung,
Universitaet  Karlsruhe, Englerstr. 7, D-7500 Karlsruhe, Germany
Phone: +49 721 608 2316                      Fax: +49 721 694 568
Internet: wiesel@ipf.bau-verm.uni-karlsruhe.de
From: pak@eng.ufl.edu (Philip A. Kufeldt)
Newsgroups: comp.unix.sysv386
Subject: 386BSD soucre
Date: 9 Apr 92 16:30:26 GMT
Article-I.D.: eng.1992Apr9.163026.28223
Followup-To: pak@eng.ufl.edu (Philip A. Kufeldt)
Organization: College of Engineering, University of Florida

Does anyone know of site that has the source to 386BSD in an unpacked or tar
form.  I'ld like to take a look at the source but I dont have a spare PC laying
around to unpack everything as it distributed.

Any help would greatly appreciated.


pakman
pak@eng.ufl.edu
Engineering Computing Services
University of Florida
Newsgroups: comp.unix.sysv386
From: rhill@pulse.spacecoast.org (Russ Hill)
Subject: Problem getting 2150s SCSI tape drive working with ISC2.2.1.
Organization: Private System -- Melbourne, FL
Date: Wed, 08 Apr 1992 00:27:53 GMT

How do you get an Archive 2150s to work on a with the following
configuration:

80386 processor
ISC2.2.1 OS without HPDD configured (see other posting ;-)
Adaptec 1542b  controller
Maxtor LXT213  disk drive
Archive 2150s  tape drive

After I installed the tape drive I enabled the 'tape' driver by putting a
'Y' in the second field in /etc/conf/sdevice.d/tape file and rebuilt
the kernal.  After that I built a device file for the tape drive using:

mknod /dev/tape c 41 8

Unfortunately though all that didn't work, because when I try
to access the tape drive I get the following error:

tar: cannot open /dev/tape.

I wrote a little program to see what the real error was by just trying to
open the device with an fopen() and calling perror().  It reported:

fopen: No such device or address

Has anybody ever seen this?  And if so how did you fix it?

Thanks in advance,

Russ Hill
-- 
Russ Hill                     rhill@pulse.spacecoast.org
                              rhill@dale.ksc.nasa.gov
From: hoven@etek.chalmers.se (Hans-Ove Frimodig)
Newsgroups: comp.unix.sysv386
Subject: Anyone using SVR4 as a boot server for diskless DOS machines ??
Date: 15 Apr 92 13:57:30 GMT
Organization: Chalmers University of Technology, Gothenburg, Sweden

I want information about how to boot diskless PC:s from an SVR4 machine.
I have got the bootp.2.1 but nothing there seems SVR4 specific. I have
not tried to compile it yet. I don't have a diskless PC with bootproms
so I cannot test these things. I will not buy new hardware before I know
it will work.
If the bootp works, what kind of files must be on the server ??
Standard DOS files ??
I use ESIX 4.0.3.

Please send email if you have any info.

Thanks in advance!

/Hans-Ove Frimodig
hoven@cd.chalmers.se
From: debra@wsinis07.info.win.tue.nl (Paul De Bra)
Newsgroups: comp.unix.sysv386
Subject: Re: Is there life after Bell Tech?
Date: 13 Apr 92 13:24:29 GMT
Reply-To: debra@info.win.tue.nl
Organization: Eindhoven University of Technology, the Netherlands

In article <1992Apr11.064529.259@timesink.spk.wa.us> kew@timesink.spk.wa.us (Keith Walker) writes:
>After years of working with a 386 box with only a monochrome
>screen, I just bought a new 386/40 with a VGA (Trident 8900C
>chipset, I believe) screen. Unfortunately, Bell Technologies
>Unix R3.2.1u doesn't know what a vga card is, much less how
>to deal with it.

I don't believe that's the problem. AT&T added vga support in
release 3.2u (aka release 3.2 version 2.1).
One way to notice this is to look in the kd.h include file.
(it should have VGA modes)

The support added by AT&T was for the VDC-600. It recognizes the presence
of other VGA boards, but does not necessarily know how to deal with them.

>When the system boots, the screen goes inverse (black chars
>on a white background), and some of the features like color
>and underlines don't work. Otherwise, it is working -- I
>mean, at least I can use the machine.

This is the same behavior as with AT&T 3.2u. A Paradise or Tseng Labs
based video card does not suffer from this problem.

>Is there an easy fix to this problem? Like a new console
>driver or something? I hasten to point out that after
>purchasing the computer, I have little money left, so the
>cheapest solution may be the best for me.

Try to exchange your video card for a card with Paradise or Tseng Labs
chipset.

Note that up to release 3.2 version 2.0 there was no VGA support,
meaning you don't get any output on the screen when booting.
An obvious difference from the behavior with 3.2 version 2.1.

Good Luck.

Paul.
From: bill@bilver.uucp (Bill Vermillion)
Newsgroups: comp.unix.sysv386
Subject: Re: low-level SCSI formatter for unix.
Date: 12 Apr 92 15:08:51 GMT
Organization: W. J. Vermillion - Winter Park, FL

In article <1992Apr09.135127.819@ibmpcug.co.uk> dylan@ibmpcug.co.uk (Matthew Farwell) writes:

>In article <1992Apr3.194038@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:

>>Scott does mention one good point that a lot of people ignore when doing
>>normal backups, to their considerable peril:  After you write a tape, read
>>it back to be sure it can be read without error at least once.  Don't
>>assume that the write was successful just because it didn't report any
>>errors.

>Can I just add thats its even better to try and read the tape on another
>machine with another tape drive, if possible.  We discovered not so
>recently that our tape drive was out of alignment, and all of our
>backups are nearly useless.

And one horror story here. (At least it was a horror story to me).

About 6 years ago I was installing a 3b2/310.  We started the install
on the morning of Dec 24.  About 1pm we found that the vendor had
swapped the CPU boxes and we had one with a 35Meg drive and not the 70
meg drive.  Vendor had gone home for the holiday.  Call them on the
26th.  They had swapped the boxes on the loading dock.  Someone got our
box, and we got theirs.  Air freight another unit in.

In the meantime I was doing install and software transfer and
conversion from a previous system.  I would make a tape and run the
verify of the tape.  I foolishly did not try to read the tape back in.
So by the time we got the new box in and set up and ready to install it
was 7pm on Friday night.   No tapes would read back in.    Wrote tape,
verified tape, but they would not read in.

Went to another similar machine - 60 miles away - and found that the
first machine had a defective drive.  It wrote nothing to tape, and
verified that!!!!!.
 
 Argh!   So back to square one!   Re-install and re-transfer everything
 again.   


-- 
Bill Vermillion - bill@bilver.uucp 
                - ..!{peora|ge-dab|tous|tarpit}!bilver!bill
Newsgroups: comp.unix.sysv386
From: cpcahil@virtech.uucp (Conor P. Cahill)
Subject: ISC UNIX 3.0 & SYSADM menus
Organization: Virtual Technologies Inc.
Date: Mon, 6 Apr 92 11:44:17 GMT


As several people have noted, ISC UNIX provides a new set of system
administration menus that sometimes appear to escape to never-never land.

This happened to us the other day and I tracked it down to the fact that we
had added a new module to the system (therefore requiring a rebuild of the
menu files) and the next time we entered sysadm, all we got was the Help
and Quit selection items.

The gist of the problem is that we had installed GNU-grep as /bin/grep on
our system and there is one option in particular that conflicts between
the ISC grep and the GNU grep.  Of course, this option is used by the 
sysadmin interface.  The option is -s.  In GNU-grep this means run silently,
in ISC grep this means supress error messages about missing files.  

The sysadmin menu building shells were using grep -s to obtain menu entries
without having to deal with any missing files and they weren't seeing any
of the output since GNU-grep ran silently.

Since GNU-grep is measureably faster than ISC grep we didn't want to install
the old version of grep.  So our solution was to install grep in /usr/admin/bin
which is setup by the sysadm .profile (in /usr/admin) to be the first search
path for executables.

Once you do that, remove /usr/admin/sysadm.hlp and /usr/admin/sysadm.mnu 
and then re-enter sysadm and you should see the other entries magically 
reappear.

-- 
I guess these are the views of VTI - since it is my consulting company.

Conor P. Cahill              (703)430-9247              uunet!virtech!cpcahil 
Virtual Technologies, Inc.  46030 Manekin Plaza            Sterling, VA 22170
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: svr4 asy, uucico and ttymon hints (was: Sys V R4, Async problems...)
Date: 11 Apr 92 19:39:39 GMT
Organization: Private system -- Orlando, FL

In article <JHPB.92Apr7230655@sarto.budd-lake.nj.us> jhpb@sarto.budd-lake.nj.us (Joseph H. Buehler) writes:
>I don't know about CD, but my observation is that ttymon will fork on
>just plain data bits without any CD at all.  This is extremely
>annoying, because my modem sends
>
>	RING
>
>whenever someone calls.

I was wondering how ttymon was monitoring for CD on multiple ports.  Is
it just doing a poll() on all the ports, waiting for data?  What if the
modem doesn't generate any data on connect?  Does SVR4 have some new
STREAMS message that gets sent on CD detection that you can poll() for?
How does ttymon know what baud rate each port it's monitoring is using?
Can it parse CONNECT messages from modems?  How does it deal with
devices that aren't wired for CD, like terminals?  (I don't have SVR4.)
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)
Newsgroups: comp.unix.sysv386,comp.unix.misc
From: orville%weyrich@tnet.com (Orville R. Weyrich)
Subject: Re: Use of "crashme"
Reply-To: tnet.com!weyrich!orville
Organization: Weyrich Computer Consulting
Date: Sun, 12 Apr 92 22:24:38 GMT

In article <id.R7PO.SI4@ferranti.com> peter@ferranti.com (Peter da Silva) writes:
>In article <00348@meph.UUCP> gsarff@meph.UUCP writes:
>> Nealy every company that came out with a machine running unix,
>> ported the code, bugs and all, and presumably did not fix the bugs because of
>> the fear of being struck by a lightning bolt from the unix gods.
>
>One company has been fixing the bugs. The problem is, they get panned for it.
>
>The problem is that if you fix the bugs you need to KEEP fixing them in every
>release because AT&T (or USL) never bothers to fold any fixes back into the
>source release. So either you give up fixing them or you give up picking up
>every new release of UNIX.
>
>Can you figure out which company I'm talking about now?

Obviously a company that is slow to release new versions :-)

But I can't seem to think of any company that is noted for not having
the same old bugs release after release -- I hear complaints about them 
all (haven't tried them all, though -- nobody values my opinion enough
to give me review copies, and I am still running release 3.0 for financial
reasons).

But seriously, wouldn't cdiff's and the patch utility do most of the work?

And if you know that you are going to have to do regression testing in the
next release, wouldn't you carefully document your test cases and/or
make them at least partially automatic?


orville

--------------------------------------           ******************************
Orville R. Weyrich, Jr.                           Weyrich Computer Consulting
Certified Data Processor                         POB 5782, Scottsdale, AZ 85261
Certified Systems Professional                        Voice: (602) 391-0821
Internet: orville%weyrich@tnet.com                    Fax:   (602) 661-0660
Internet: orville%weyrich@uunet.uu.net                  Yes! I'm Available
--------------------------------------           ******************************
From: pim@cti-software.nl (Pim Zandbergen)
Newsgroups: comp.unix.sysv386
Subject: Re: Bi-directional Parallel driver
Date: 13 Apr 92 19:43:46 GMT
Organization: CTI Software BV, The Hague, The Netherlands

swispl@solomon.technet.sg (SW International) writes:

>Greetings from one of the worlds greatest 24 hour suana !!!

>I am looking for either or both of the following items,

>i. a bi-directional parallel driver (esp for SCO Unix - if at all
>   possible). Its purpose is to be used for a image scanner.

>ii. sources to a bi-directional parallel driver (esp for SCO Unix 
>    - if at all possible).

The ISC lp(7) man page says the lp device driver will allow
one read/write open and multiple read-only opens.

This would suggest this driver is bidirectional.

I would be interested in using the parallel port
for fast communication with a UNIX laptop without
all the overhead involved with a pocket ethernet adapter.

If the ISC driver is truly bidirectional, could one
just use cat as a communication program ?

What kind of cable would be required ?
-- 
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: comp.unix.sysv386