HDTenEightyP/NetNews huggingface dataset:
From: fontenot@ravl.rice.edu (Dwayne Jacques Fontenot)
Subject: Hercules CHROME
Organization: Rice University
Date: Wed, 7 Oct 1992 00:22:00 GMT

Hello,

Has anyone any information on the new Hercules CHROME video card?
There is an add for it on the back cover of the October Computer Graphics
World.

Add claims:

------------------------------------------------------------------------------

* Fastest - 24-bit graphics at 8-bit speed.

* No Compromise - 16.7 million colors at up to 1152x900 resolution.

* Dual Page - readable type on a two page spread.

* Highest Refresh - up to 90Hz for a comfortable workout.

* True color graphics - all gain, no pain!

picture of a card with that looks like 5 SIMM slots.

800-532-0600

------------------------------------------------------------------------------

no price though. sigh.

anyone heard anything?

Dwayne Fontenot
Newsgroups: comp.unix.bsd
Subject: Re: AHA1542B vs Sysgen SC4000 controller under BSD386
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Mon, 5 Oct 1992 17:52:59 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Oct5.100219.28945@tfs.com> julian@tfs.com (Julian Elischer) writes:
>In article <1ao4umINNaua@network.ucsd.edu> brian@ucsd.edu (Brian Kantor) writes:
>>I managed to score a Sysgen SC4000 SCSI-to-QIC-02 controller, an Adaptec
>>Stand-Alone-Tape-Controller QIC-02-to-QIC-36 board, and an Archive 5945C 
>>drive.  This bizarre combination is what Sun used to use in their really
>>old (Sun-2/68010 days) tape backup boxes.
>>
>>When I connect this mess up to my Adaptec controller and try to bood
>>386BSD with Julian's SCSI package, the error light on the SC4000 comes
>>on, and the computer just keeps telling me that command timed out.
>>The light on the Adaptec just stays on.
>>
>
>I wonder if the SC4000 is really compatible with modern scsi.
>Does the BIOS find the tape controller? (do you have the BIOS enabled?)
>just for laughs, try the old scsi system and let me know
>what happens.

I think you're right.  I believe that the SC4000 is a SASI controller,
which is a subset of SCSI.

Also, the Archive SAC controller is notorious for being finicky.

>I'm sorry that that is not much help.
>But it sounds as if the low level protocols are failing.
>Something is wedging the scsi bus.
>That's not something the software can easily do.
>
>(If it makes you feal better I'm having the same problem
>with a particular disk and the aha1742 card (aha1542 loves it).
>
>
>>Has anyone gotten this or a similar setup to work?  What firware
>>revisions are in your controllers, and what jumper/switch settings did
>>you use?
>>	- Brian
>
>julian
>
>+----------------------------------+       ______ _  __
>|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
>|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
>| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
>+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
>          v
>
>


-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Newsgroups: comp.unix.bsd
Subject: Re: device 0/0 0/1
Date: 6 Oct 92 12:27:26 GMT
Organization: Ascom Autelca AG, Guemligen, Switzerland

andrick@sun.rhrk.uni-kl.de (Ulf Andrick [Biologie]) writes:

>nbladt@autelca.ascom.ch (Norbert Bladt) writes:
>: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
>: 
>: 
>: >I'm running 386bsd on a ah1542b with as0a as root, as0b swap, as0h /usr.
>: >Yesterday I installed Julian Elischers (thank you, Julian), scsibeta2.1
>: >release because my DAT tape (DEC TLZ04) was never recognized by the as
>: >driver. With the above SCSI driver it is recognized.
>: 
>: 
[ text about error message: "sd0: device not configured" deleted - NB. ]

>I have no experience with that, but I wonder whether one
>shouldn't have a look at /etc/fstab in such a case. That file
>should be decisive for what devices are used as swap space,
>shouldn't it?
Yes but savecore doesn't look at it !
Savecore (or whatever the name of the program is) does a
nlist for the current unix and looks for the entry "dumpdev".
There must be "sd0b" (or device 4,1) in it, which is usually the swap area,
unless configured differently, i.e. not using "install" for installing 386BSD.
I don't know how it proceeds from then, but I looked in the
code and found this call to "nlist".

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
From: phk@data.fls.dk (Poul-Henning Kamp)
Newsgroups: comp.unix.bsd
Subject: 386bsd: 1.2 Mb we could do without in the src01 distribution
Date: 28 Sep 92 10:40:54 GMT
Organization: FLS Data A/S, Valby, Copenhagen, Denmark.

I have found the following files in the src01 distribution, which I belive
should have been left out or may have a problem.  I imagine most of them
are indications of Makefile problems.  If I am wrong please correct me.

They total around 2.5 Mb before compression so we might have saved a floppy.

I Hope my input is usefull...

/* Probably patch/emacs leftovers */
./usr.sbin/sendmail/cf/sitedep/uucp.proto.m4~
./usr.sbin/sendmail/cf/sitedep/uucp.id.m4~
./usr.sbin/sendmail/cf/m4/uucpm.m4~
./usr.sbin/sendmail/cf/m4/localm.m4~

/* zero size */
./usr.bin/gas/as.1:	empty
./sys.386bsd/i386/include/mtpr.h:	empty

/* file {} | grep -v text */
./usr.bin/fgrep/fgrep:	demand paged pure executable not stripped
./libexec/uucp/uuxqt:	demand paged pure executable not stripped
./libexec/uucp/uustat:	demand paged pure executable not stripped
./libexec/uucp/uuname:	demand paged pure executable not stripped
./libexec/uucp/uulog:	demand paged pure executable not stripped
./libexec/uucp/uucp:	demand paged pure executable not stripped
./libexec/uucp/uucico:	demand paged pure executable not stripped
./libexec/uucp/uuchk:	demand paged pure executable not stripped
./libexec/uucp/tstuu:	demand paged pure executable not stripped
./libexec/uucp/uux:	demand paged pure executable not stripped
./sys.386bsd/i386/stand/wdboot.x:	data
./sys.386bsd/i386/stand/wdboot.old:	data

-- 
phk@data.fls.dk		  || 			$HOME
Poul-Henning Kamp	  ||	
FLS DATA A/S		  ||			sweet
Phone: (+45) 36 18 12 35  ||
Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: I'm a dud...and need help!
Keywords: cdrom
Organization: Pix Technologies -- The company with no adult supervision
Date: Sun, 27 Sep 1992 07:57:30 GMT

In article <greg.717567006@coombs> greg@coombs.anu.edu.au (Greg Price) writes:
>This is my confession!
>
>I bought a CD-ROM drive (Sound Galaxy CR-522-B with a Panasonic Drive).
>There is a dos driver (fine), but I wanted to get programming info and
>the retailer has been unable to get it. The interface is the AT type,
>ie proprietary. Apparently the drive can be used on Sound Blasters, any
>way, I want the low level programming info so I could work on a driver
>for 386BSD, but I appear to be stuck. I have asked for help in alt.cd-rom
>and a pc group, but got no responses, so I ask two things.

As far as I know the "CR-ROM port" on the Sound Blaster is just a non-standard
SCSI conector.  So what you need is a SCSI cable to connect your CR-ROM to a
SCSI controler (which you also need one of).  Then you can try assuming that
the SCSI CD-ROM you have acts like most others and just try the pre-existing
driver that comes with Julian Elischer's SCSI driver (assuming you have
one of the supported controlers, which as far as I know the Sound Blaster is
_not_).

>1) Does anyone know how/where I could get programming info I need, or

Ask them what the diffrence between this and the "normal SCSI" version is.

>2) If I could get it swapped for the SCSI version of the panasonic drive
>   what types of scsi controller could/should I get for it. The Adaptec
>   1542 costs as much as the drive alone! I don't mind working on the
>   drivers for a different type of controller, but I would need info for
>   it (ie the scsi controller and possibly some stuff about the drive,
>   although the scsi should be standard). Is it anticipated more scsi
>   controllers will be supported, etc?

It is (anticipated that more SCSI controllers will be supported).
Hunt through the last week or so of news and find the new SCSI drivers and
look them over.  I don't know what SCSI controler is best for you, if all you
want is the CD-ROM then even the slowest SCSI controler should be much faster
then the drive, just get the least expensiave one that is supported, or has
the docs you need.  If you want to put a disk drive, or tape backup on someday
you should start looking at the speed...
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
Newsgroups: comp.unix.bsd
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: fixing apropos (from FAQ, and then...)
Organization: University of Michigan ITD Consulting and Support Services
Date: Sun, 27 Sep 1992 04:21:07 GMT

So I added the | col -b | to the Makefile in /usr/othersrc/share/man
without any trouble.  Now when I go to "make" it returns:

make: obj: No such file or directory
*** Error Code 2 

Stop.
*** Error Code 1


Paul Southworth                    |     ftp redspread.css.itd.umich.edu
Consulting and Support Services    |        Anonymous Political Archives
Information Technology Division    |                     100% 386BSD 0.1
University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org

  <Representing myself.  Everything I say is for educational use only.>
Newsgroups: comp.unix.bsd
From: u009@csx.cciw.ca (G. Stewart Beal)
Subject: Re: BEWARE:  stupid placement of swap space...
Organization: Canada Centre for Inland Waters
Date: Wed, 30 Sep 1992 13:41:21 GMT
Keywords: (or:  Don't be stupid like me :-)

In article <47897@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>Just a word of caution to anyone who installs swap space on extra
>disk drives.  I learned this the hard way and don't want anyone
>to be as stupid as I am ;-)
>
>I borrowed a 1.0GB SCSI drive so that I could build X11R5 and have some
>
>...... deleted
>
>Everything is now fine.  By the way, the reason for not putting swap
>first was given to me by a gentleman from Germany (sorry I've forgotten
>your name :-(  It turns out that the first few sectors of a SCSI drive
>are used for partition information.  A filesystem will not use the first
>few sectors of it's partition (knowing about the reserved blocks).  But
>a swap space will eventually overwrite the partition information,  thus
>causing strange things to happen.
>
Does this mean even if the swap partition is specified to start at cylinder
1 or 2? Does the swap creep, or just want to use block 0 of the partition
starting at cyl 0? If so, it sounds like an "off by one" boundary bug.
 
Regards, Stu Beal, VE3MWM, U009@CS.CCIW.CA,
National Water Research Institute, Burlington, Ontario, Canada.
 
"We'd made it through yet another nuclear winter and
 the lawn had just trapped and eaten it's first robin." - Kyle J. Spiller
From: caveh@spartacus.csl.sri.com (Caveh Jalali)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd]Wanted:PC Diagnostic reporting bad BLOCKS (not track/head)
Date: 5 Oct 92 18:07:21
Organization: Kernel Labs.  NOT!
NNTP-Posting-Host: spartacus.csl.sri.com
In-reply-to: u009@csx.cciw.ca's message of Thu, 1 Oct 1992 17:31:09 GMT

In article <1992Oct1.173109.5869@csx.cciw.ca> u009@csx.cciw.ca (G. Stewart Beal) writes:

the interleaving will not change your block number or sector numbering.
it does determine their physical order on the disk, but not their sector
numbers.  each sector has it's sector number recorded on the disk
(ie. "soft sectoring").

i have the same problem that you describe.  all the formatters i've used
will mark every sector on a track as bad (this can be done in the sector
header) for every track that has a bad spot (sector) on it.  in other
words they do bad-tracking rather than bad-sectoring.  BSD likes to do
bad-sectoring.

you will have to enumerate every bad sector in the bad144 table that corresponds
to the track containing a bad sector.

note that you will have to verify that your driver *correctly* supports
sector remapping.  the original 386BSD driver does not.  i've beaten mine
into submission so that it works for me.  i think there are patches
which claim to fix sector remapping as well.  my version of wd.c is
has significant changes, so i don't think i can send diffs at this point.

another enhancement i made was to introduce the convention that sector
#255 is a wildcard sector, such that the entire track is marked as remapped.
this is somewhat consistent with the SCSI convention, but more importantly
cuts down the size of your bad144 table by a factor of 17!  this is significant
since the table needs to be scanned (linearly right now!) for every disk
transfer (generally 8K).

one question i have about the current wd.c driver is whether it handles the
case correctly, where a disk transfer starts on a "normal" sector, but
either has a bad sector in the middle of the transfer or at the end.
is the driver smart enough to split the transfer into the required 2 or 3
sub-transfers???  could someone familiar with the current driver let me
know, please?

00c
--
00c -- caveh@csl.sri.com
"X is not a letter, it's a sentence."
Newsgroups: comp.unix.bsd
Subject: X386 & ViewSonic 5e
From: cse0935@desire.wright.edu
Date: 2 Oct 92 19:39:27 EST
Organization: Wright State University 

I have Xwindows up and running on my 386-40 with 386BSD, and I can get it
running in 640x480 but can't mange to get it to work in 1024x768 mode.
I have a ViewSonic 5e monitor
with the following freq.
Hor. freq: 31-60KHz
Ver. freq: 50-90Hz

If anyone has a ViewSonic 5e up and running in SVGA modem PLEASE let me
know your Xconfig file.
From: guido@wzv.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: xdm hangs after a while
Date: 30 Sep 92 07:38:46 GMT
Organization: Eindhoven University of Technology, The Netherlands

Hi, after succesfully installing XFree, some time ago, my machine now
has enough memory to be able to use it a normal way. I put:
nohup /usr/bin/X11/xdm in my rc. 
All works fine, but whne I logout and dont login for a few hours, then
my keyboard doesnt seeem to work anymore. I didnt look (yet) if you even
cant't logon from other systems..
I also experienced that when I start x with startx, then after finishing,
the console still works, but you dont get to see anything on it. Do I have
to run some kind of program to put the console back or so? 

-Guido
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: Corruption in BIN01.56?
Date: 1 Oct 92 11:36:21 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <adam.717861382@marsh> adam@cs.curtin.edu.au (Adam Sawyer) writes:


>Has anyone else had problems when trying to extract the BIN01.(1-56) 
>distribution?

>When I go to extract the files (after mread b:*.* /tmp) for all 56 BIN01.X
>files, I am always getting the error :

>Corruption in BIN01.56

>And I've already b) recopied the file onto a new disk
>                 c) re-ftped the file from kirk.bu.oz.au
>                 d) (re-ftped ensuring that I was in BINARY mode)
>                 d) re-ftped from agate.berkeley.edu


>And now I'm lost for ideas, its only this one last file *sigh*


>Adam!

This question appears on-and-on again. It should get into the FAQ.

Check whether the bin01.56 file (the last one) has exactly 227717 bytes.
You had to copy this to a MSDOS disk. Some DOS COPYs like to append 
CTRL-Z and other nasty stuff to a file, which of course modifies the checksum
and the size.

Check whether the Manifest file is corrupt. This file contains the checksums
for the distribution. Get a new one from a site which has the whole bin tree
unpacked (e.g. agate.berkeley.edu). If this still fails, do the necessary
things manually:
	cd /tmp (provided you have the distribution files in /tmp)
	cat bin01.* | uncompress | cpio -idalmu
	sh /tmp/install.bin01

If cpio fails shortly before the end with "invalid data" or so, bin01.56 is
indeed defective. If it does not fail, you have just repeated what extract
does.

Hope that helps

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 26 Sep 92 06:07:50 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes:

>  You repeatedly attempt to disassociate yourselves from this suit. I wonder
>why? Surely you realize that if a verdict is reached that Net-2 contains USL
>proprietary material, you will have to cease distributing 386BSD?

While this is certainly a logical view, it may not be true.  I asked
one of our faculty, who is a lawyer with some knowledge of
intellectual property issues, to look at the complaint and a copy of
our ATT license.  He thinks the suit is going to turn on how the
courts interpret the details of the relationship between ATT and
Berkeley.  It is not impossible that BSDI could end up being
prohibited from using BSD, but that non-commercial BSD-based software
would be unaffected.  I thought the theory that would lead to this was
pretty bizarre.  But so far the evidence suggests that when lawyers
get involved in software, anything is possible (except bug-free code).
Newsgroups: comp.unix.bsd
From: chuck@coplex.com (Chuck Sites)
Subject: The Compile from HELL!
Organization: Copper Electronics, Inc.
Date: Tue, 6 Oct 1992 07:42:23 GMT
Summary: Difficult time compiling Xview3
Keywords: 386BSD GCC compiler Xview3



    Recently when trying to port XView3 to 386BSD and XFree, I ran into a
brickwall of a performance problem.  There are some files which start 
compiling but they just don't stop.  One file, attr_char.c, I let compile
over the weekend only to come back and find the system apparently frozen.
Frozen may be a misnomer though.  While trying to telnet into the system 
during the early stages of the compile, I can access the system, but slowly
the perfomace degrades to the point of printing 1 line/min for an ls, and it
gets worse to the point of not responding at all.  I assumed it was swapping,
but the severity that other process are excluded from thier share of the
clock makes me think this is a kernel problem. 

    Well in fairness, this may not be a kernel problem alone. GCC maybe
partially to blame.  On large structure arrays I've seen it go 'all
consuming' before on OS2 and SYSV,  but both resulted in an out of
memory error at the user prompt after several hours. Neither had the
multitasking performace degradation like I got with 386bsd.  (I was
trying to port the fax portion of the TIFF package on uunet fyi.) 

    So, my question is: has anybody seen this type of problem and is this
symtom fixed by the latest beta patches?  Second, if the beta patches do
fix this problem, could someone direct me to a site that has the collected
binaries of the beta patchs.        


Thanks,
Chuck Sites         
chuck@coplex.com    (502)-9688495
Newsgroups: comp.unix.bsd
Subject: [386bsd] What does this message mean?
From: <AI4CPHYW@MIAMIU.BITNET>
Date: Monday, 5 Oct 1992 10:11:33 EDT
Organization: Miami University - Academic Computer Service

I have noticed that every time I reboot my machine (recompiled kernel with
most of Terry Lambert's patchkit applied) I get a message in the boot manifest
along the lines of "wd0a overlaps partition (b)" or something like that.
Also, once in a while I get the following messages in my /var/log/messages
file as well:
 
Sep 30 13:53:49 continuity /386bsd: wd0a: overlaps open partition (b)
Sep 30 13:53:50 continuity /386bsd:
Sep 30 13:53:50 continuity /386bsd: warning: no swap space present (yet)
 
[note the blank error message]
 
Now, I know what the "no swap space" message means, I just included it
because it shows in the exact same place each time I get the overlap
message.  My HD has been completely given over to 386bsd, a look at the
disklabel (disklabel -r wd0a) doesn't seem to indicate that any partitions
share the same space on the disk (except for the one partition that contains
all the others).  So, I'm now kinda stymied. :)
 
If you have seen this message, and know what it means, please let me know.
(Mostly I'm wondering if I can ignore it, or if it is a precurser to 386bsd
lunching itself.)
 
 
                      -Alec D. Isaacson
                       AI4CPHYW @ miamiu.acs.muohio.edu
                       isaacson @ rogue.acs.muohio.edu (NeXt Mail)
                       Miami University, Oxford, OH
-------------------------------------------------------------------------
Only a barbarian would eat chive cream cheese and blackberry jam on the
same bagel.                          -Spenser
Newsgroups: comp.unix.bsd
Subject: Re: How to format UNIX floppies under 386BSD
From: levinson@vax.sonoma.edu
Date: 29 Sep 92 16:50:42 -0800
Organization: Sonoma State University

In article <1a7hksINNhfe@maverick.ksu.ksu.edu>, brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
> In <rcskb.717489070@minyos.xx.rmit.OZ.AU> rcskb@minyos.xx.rmit.oz.au (Kendall Bennett) writes:
> 
>>BTW, if I finally get mtools working on 386BSD, it has an mformat command
>>to format an MSDOS floppy right? So you could write a shell script that
>>would use mformat to low-level format the floppy, then newfs to put a
>>file system on it. Or is mformat only a high level format program (like
>>the MSDOS 5.0 format without /U?)...
> 
> All mformat does is write the MS-DOS filesystem (ha ha) info to track 0.
> Stuff like the FAT and the root directory for the disk.  It does not low
> level format the disk.  BTW, this is a really quick way to reformat a disk
> for MS-DOS that's been used for a tar file or some such.  MS-DOS always
> want's to reformat the entire disk in these cases.  mformat will do the
> job in about 5-10 seconds.
> 
> ++Brett;
-- 
well, there is format /q in MSDOS which just overwrites the root directory.
--
Eric Levinson
rcisnet2!root@moon.nbn.com	|  Home computer (UUCP)
levinson@vax.sonoma.edu		|  Vax
I can also be reached on my BBS system, Color Galaxy Milky Way (415) 883-0696

Newsgroups: comp.unix.bsd
From: peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller)
Subject: Xfree86 New Release-Date ??
Organization: University of Salzburg / Austria
Date: Tue, 6 Oct 1992 07:35:07 GMT

Hi folks!
I wonder if anybody know the official (probably new) release-date
of Xfree86? I've a bunch of students in my neck who are desperatly 
waiting for that stuff. (I told em that I won't install any beta-releases
'cause the official release is on the way)
So WHEN is the official release?
--
/-------------------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience			    |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
| "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
\-------------------------------------------------------------------/