HDTenEightyP/NetNews huggingface dataset:
From: pact_ltd@uhura.cc.rochester.edu (Blade)
Newsgroups: comp.periphs.printers
Subject: Panasonic 2123 and color option.
Summary: How to fix?
Keywords: Black and Red problems
Date: 27 Dec 92 05:02:26 GMT
Organization: University of Rochester - Rochester, New York


	This may or may not be a FAQ, apologies if it is because the FAQ
isn't available at my site.  (I know, for a month and all that, but I have a
screwy site it seems...)  Anyway, when I try to print color through this
printer, it refuses to print black.  It puts out blue instead.  Also, when I
print, I often get red bands appearing in the picture.  This looks horrible
and I'd like to know if there's any way to fix it.  If anybody has any
suggestions, I would appreciate e-mail at:  pact_ltd@uhura.cc.rochester.edu
Any help would be appreciated.  Thanks in advance,   Pete.
-- 
Pete Schott                    pact_ltd@uhura.cc.rochester.edu

I don't have to have a 4.0 GPA to succeed in life because I'm good enough,
I'm smart enough, and doggone it, people like me.
From: warren@CAM.ORG (Robert Warren)
Newsgroups: comp.periphs.printers
Subject: What is a brother printers?
Date: 29 Dec 92 21:46:00 GMT
Organization: Communications Accessibles Montreal, Quebec Canada

I need help here. I came accross a brother M-1109 printer. There is serial and
parallel port on it, along with 2 dip-switch blocks inside the printer. Trying
to hack the dip-switches has not yeilded any succes in making the paralle port
work. Can anyone out there with the owner's manual type-in the dip-switch
specification?

And is this beast epson/ibm proprinter/whatever compatible?

Regards,	
	Robert Warren
From: white@angmar.llnl.gov (Greg White)
Newsgroups: comp.periphs.printers
Subject: Request for thoughts on LJ4m ...
Date: 18 Dec 92 22:33:47 GMT
Organization: UC LLNL

I'm finally going to go out and buy my next generation printer....

I have (tentativly) decided on the HP laserjet 4m to connect to
my Mac, PC, and eventually a Unix box.

I have read all the reviews, read the specs, etc....but

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

the questions ... for those of you who have already got a LJ4
		  or LJ4m ...

1) Would you do it again?
2) Any gotcha's, problems, etc?
3) General comments ...


Thanks in advance,
Greg White
white@angmar.llnl.gov
Newsgroups: comp.periphs.printers
From: eng10056@nusunix1.nus.sg (LAU YIN CHENG)
Subject: HP LJ4 printing in windows -slow spooling
Organization: National University of Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Sat, 26 Dec 1992 02:11:47 GMT

I just got my LJ4 about 1 week ago,

	Besides the 'famous' paper curling and the splendid output,
	I find the spooling of files in windows 3.1 annoying slow.

Below are some statistics.

My system:  486dx-33 4MB Ram  

Under windows: +6 MB virtual memory

Spooling:  Under WFW v2.0
	Type of files	  		Time taken to spool to printmang

	plain text 600dpi		19-22 seconds /page
	text with graphics 600dpi
	avg 1 fig / 2 pg		60-66 seconds /page

Printing:

	Very fast - 8-9 ppm

	Anybody outthere got the same problems as me.  It pretty
annoying to wait half-an-hour to get a 27 page document to be spooled.


Any suggestions and advice?  Is it because of the printmang.  or my
system has too little memory? Any ideas about speeding the spooling
process urgently needed. 


Please help.

Merry Christmas and Happy New Year to all.
Newsgroups: comp.periphs
From: jeff@anthro.utah.edu (Jeff Thomas)
Subject: Re: Hard drive question,please read and reply
Organization: University of Utah, Dept. of Radiology
Date: Fri, 1 Jan 93 00:00:36 GMT

Your 8-bit WD controller should work in an AT. Just because some card is
only an 8-bitter doesn't mean that it won't work in an AT. The ATs were
designed to take all 8- and 16-bit cards designed for the ISA bus.
From: ah157@cleveland.Freenet.Edu (Rob Henry)
Newsgroups: comp.periphs
Subject: WD1002A ,how do i disable it's bios?
Date: 2 Jan 1993 16:35:48 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: ah157@cleveland.Freenet.Edu (Rob Henry)
NNTP-Posting-Host: slc10.ins.cwru.edu



I have an 8 bit westen digital 1002a hard drive controller and I
need to know how to disable it's bios to use it on my
machine.
Please leave mail.
There are only two jmpers on it so it must be one of those.
Newsgroups: comp.bugs.2bsd
From: bostic@VANGOGH.CS.BERKELEY.EDU (Keith Bostic)
Newsgroups: comp.bugs.4bsd.ucb-fixes
Subject: V1.99 (Dump/Restore Update)
Date: 22 Dec 92 18:30:30 GMT
Distribution: world
Organization: University of California at Berkeley

Subject: Dump/Restore Update
Index: sbin/{dump,restore} 4.4BSD-alpha

Description:
	A new version of dump and restore is now available which fixes
	several major bugs:

	In some instances, the NET/2 dump would fail to include unchanged
	intermediate directories making it difficult to extract files on
	the tape. For example, if /usr/src/sbin/dump/dump.h changed, but
	sbin had not changed, sbin might not be on the tape. The result
	would be that files and directories below sbin, though on the
	tape, could not be restored.

	Restore now fully supports POSIX 1003.2 glob'ing. This has been
	done by replacing the adhoc glob code in restore with use of the
	glob(3) function in the C library.  Note that the C-library glob
	function needed some minor (backward compatible) modifications to
	support restore.  Thus, the modified glob.{c,h,3} is included in
	this distribution. It can either replace the glob in your existing
	C library, or be compiled separately in the restore directory.

	Backward compatible changes have been made to dump and restore to
	support the added features in the 4.4BSD filesystems (including
	32-bit uid/gid, 64-bit file sizes, and file types in directories).

        Kirk McKusick

Fix:
	Copies of the new dump/restore package are available by anonymous
	ftp from ftp.cs.berkeley.edu:ucb/4bsd/dump.restore.tar.Z, or from
	okeeffe.cs.berkeley.edu:pub/dump.restore.tar.Z.
Newsgroups: comp.bugs.4bsd,comp.bugs.sys5,comp.bugs.misc,comp.sources.bugs
From: ray@Celestial.COM (Ray Jones)
Subject: Re: A serious bug in unix2dos/dos2unix
Organization: Celestial Software, Mercer Island, WA
Date: Mon, 21 Dec 1992 18:05:58 GMT

In <BzBF6H.3Au@mccc.edu> pjh@mccc.edu (Pete Holsberg) writes:

>In article <1992Dec12.224109.15621@cs.mcgill.ca> haiying@cs.mcgill.ca (Haiying ZHANG) writes:
>=
>=   I came across this bug a while ago. This has to do with using wild
>=card in file names with unix2dos/dos2unix.

>Where did you find these utilities?
I didn't have these utilities long ago (They came with the last update
though), so I wrote a couple of shell scripts that do the same thing.  Let
me know if you are interested.

-- 
INTERNET:  ray@Celestial.COM   Ray A. Jones; Celestial Software
UUCP:   ...!thebes!camco!ray   6641 East Mercer Way
             uunet!camco!ray   Mercer Island, WA 98040; (206) 947-5591
The probability of one or more spelling errors in this missive approaches
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: hansen@pegasus.att.com (Tony L. Hansen)
Subject: Re: Problem with mailx in ESIX 4.0.4
Organization: AT&T
Date: Mon, 28 Dec 1992 19:38:28 GMT
Summary: from problem fixed in SVR4.1

< From: hmc@cs.hw.ac.uk (Hugh Conner)

< We have several 486 based systems running ESIX 4.0.4. When using the mailx
< command to read mail messages a problem occurs if the first word on a line
< of the message is 'from'. I notice that when sending mail if the first
< word is 'From' with a capital F it replaces it with '>From' which I assume
< is meant to stop the mail reader treating it as the start of a new
< message. This does happen with 'from' and although /bin/mail reads the
< message ok, mailx decides that the line starting 'from' is a new message.
< Does anyone know a patch for this or should I just compile a decent mail
< reader and scrap mailx.

This was fixed in System V release 4.1 ES. The fix should be available from
your vendor.

					Tony Hansen
			    hansen@pegasus.att.com, tony@attmail.com
				att!pegasus!hansen, attmail!tony
Xref: sparky comp.bugs.sys5:159 comp.unix.sys5.r4:1058
From: pat@rwing.UUCP (Pat Myrto)
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
Subject: Re: Problem with mailx in ESIX 4.0.4
Date: 30 Dec 92 14:29:10 GMT
Organization: Totally Unorganized

In article <2B4061C0.3F79@telly.on.ca> evan@telly.on.ca (Evan Leibovitch) writes:
>
> [ ... stuff about support policies deleted ...]
>
>I, for one, will hardly mourn the departure of AT&T from USL's
>ownership (and thus, leadership). Novell may not be any better,
>but it can't possibly be worse.

It can if Novell refuses to re-license all the non-Novell vendors, or
increases the price to the levels associated with Netware.  That would
kill any derivatives of UNIX for all but a few corporate sites, and
would certainly kill any chance of being able to choose among vendors.
I sure hope Novell does't do that - I cannot afford 12 - 18K for a home
UNIX site.  And a 'reasonably' priced version that is crippled to only
3 to 5 logins, and/or by removal of other features (such as the networking
capability, compiler and libs, etc., unless many extra thousands of
dollars are paid) is not something that I would look forward to, either.

That is somnething I have not seen discussed (or heard of anything from
Novell indicating a policy) - will the price for OS software derived from
USL code remain the same, go lower, or be increased by a factor of 6?

Anybody know?  <while I sit here chewing on fingernails...>

-- 
pat@rwing.uucp                                  (Pat Myrto),  Seattle, WA
                      If all else fails, try:
         ...!uunet!{pilchuck, polari}!rwing!pat
WISDOM:    "Travelling unarmed is like boating without a life jacket" 
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: hansen@pegasus.att.com (Tony L. Hansen)
Subject: Re: Problem with mailx in ESIX 4.0.4
Organization: AT&T
Date: Thu, 31 Dec 1992 04:13:52 GMT
Summary: 4.2 contains everything in 4.1
Keywords: mailx, UNIX

< From: evan@telly.on.ca (Evan Leibovitch)
<< This was fixed in System V release 4.1 ES. The fix should be available
<< from your vendor.

< Version 4.1, eh?
<
< A version that nobody has, since everyone is either still at 4.0 (Dell,
< ESIX) or skipped to 4.2 (Consensys, Univel).

If you have 4.2, then you have the fixes put into 4.1 as well. Enough said.

					Tony Hansen
			    hansen@pegasus.att.com, tony@attmail.com
				att!pegasus!hansen, attmail!tony
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: nitin@kailash (Nitin Kaulavkar)
Subject: Re: Problem with mailx in ESIX 4.0.4
Organization: Indian Institute of Technology, Bombay
X-Newsreader: Tin 1.1 PL4
Date: Mon, 21 Dec 1992 10:08:00 GMT

hmc@cs.hw.ac.uk (Hugh Conner) writes:
: We have several 486 based systems running ESIX 4.0.4. When using the mailx
: command to read mail messages a problem occurs if the first word on a line
: of the message is 'from'. I notice that when sending mail if the first word
: is 'From' with a capital F it replaces it with '>From' which I assume is meant
: to stop the mail reader treating it as the start of a new message. This does
: happen with 'from' and although /bin/mail reads the message ok, mailx
: decides that the line starting 'from' is a new message. Does anyone know a
: patch for this or should I just compile a decent mail reader and scrap mailx.

	This indeed is one of the known problems with mailx. There is one more
problem with mailx while reading mail. If any of the mail messages have
non-text byte, then the mailx reading goes berserk. It for the reasons I
fail to fathom, appends the mail portion after that funny character at the
end of the mail box and the effect is that you see your mailbox growing
EXPONENTIALLY. You neither can delete the mail message which has this funny
byte nor delete the mail messages after that as mailx fail to recognize the
mail boubdaries. 

	No easy patch I suppose. We have switched to MH and we are very happy
with it.
 MH source :

  via anonymous ftp:
    FTP Site:		IP Address:	Path/File Name:		Size:
    -----------------------------------------------------------------
    ftp.ics.uci.edu	[128.195.1.1]	mh/mh-6.7.tar.Z		1.6MB
    louie.udel.edu	[128.175.1.3]	portal/mh-6.7.tar.Z	1.6MB
    ftp.uu.net		[137.39.1.9]	mail/mh/tar/mh-6.7.tar.Z-split/	256K*7
  					README, part01, ..., part07

Cheers,
nitin

--
----------------------------------------------------------------------
Nitin Kaulavkar, SysAdm, <nitin@cse.iitb.ernet.in>
S/W and Computing Laboratory, Dept of C.S.E. ,IIT, Bombay 400 076.
----------------------------------------------------------------------
Xref: sparky comp.bugs.sys5:158 comp.unix.sys5.r4:1045
From: evan@telly.on.ca (Evan Leibovitch)
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
Subject: Re: Problem with mailx in ESIX 4.0.4
Date: 29 Dec 92 14:33:35 GMT
Organization: Somewhere just far enough out of Toronto

In article <1992Dec28.193828.17739@cbnewsk.cb.att.com>
	hansen@pegasus.att.com (Tony L. Hansen) writes:

>< From: hmc@cs.hw.ac.uk (Hugh Conner)

>< We have several 486 based systems running ESIX 4.0.4. When using the mailx
>< command to read mail messages a problem occurs if the first word on a line
>< of the message is 'from'.

>This was fixed in System V release 4.1 ES. The fix should be available from
>your vendor.

Version 4.1, eh?

A version that nobody has, since everyone is either still at 4.0
(Dell, ESIX) or skipped to 4.2 (Consensys, Univel).

As I recall, a move up a release number from a vendor requires extra $$$
to USL. ESIX told me that part of the reason their 4.0.3 to 4.0.4
license fee is more expensive than they (ESIX) wanted was because of an
upgrade fee to USL.

Would USL offer bug fixes for individual problems in 4.0 without
requiring their licensees to move to 4.1? Most vendors like ESIX, Dell
and SCO have offered update patches at no cost other than the cost of
retrieving them. If only USL was as responsive to *its* customers.

Sigh.

I, for one, will hardly mourn the departure of AT&T from USL's
ownership (and thus, leadership). Novell may not be any better,
but it can't possibly be worse.

-- 
 Evan Leibovitch, Sound Software Ltd., located in beautiful Brampton, Ontario
         evan@telly.on.ca / uunet!utzoo!telly!evan / (416) 452-0504
         "IBM's three letters are probably EBCDIC for CYA" - Nik H.
Xref: sparky comp.bugs.sys5:160 comp.unix.sys5.r4:1064
From: cshaver@informix.com (Craig Shaver)
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
Subject: Re: Problem with mailx in ESIX 4.0.4
Date: 30 Dec 92 20:53:56 GMT
Organization: Informix Software, Inc.

In article <1850@rwing.UUCP> pat@rwing.UUCP (Pat Myrto) writes:
>In article <2B4061C0.3F79@telly.on.ca> evan@telly.on.ca (Evan Leibovitch) writes:
>>
>> [ ... stuff about support policies deleted ...]
>>
   [ ... more stuff deleted ... ]
>
>That is somnething I have not seen discussed (or heard of anything from
>Novell indicating a policy) - will the price for OS software derived from
>USL code remain the same, go lower, or be increased by a factor of 6?
>
>Anybody know?  <while I sit here chewing on fingernails...>
>
>-- 
>pat@rwing.uucp                                  (Pat Myrto),  Seattle, WA
>                      If all else fails, try:
>         ...!uunet!{pilchuck, polari}!rwing!pat
>WISDOM:    "Travelling unarmed is like boating without a life jacket" 

It should take them 6 months to figure out what they have (furniture, bodies,
liabilities, equipment).  They may have an idea on where they want to go
with it, but I doubt it is well thought out and will probably change in 6 months.
I think USL will look the same on the inside for the next year.  You may
see superficial changes on the outside.  This is my observation of typical
stupid mergers.  Look at the Borland takeover of Ashton-Tate.  

I recommend people start kissing up to Chairman (big potato) Bill.
-- 
Craig Shaver  (cshaver@informix.com for now) (415)390-0654 (415)926-6407
Productivity Group POB 60458 Sunnyvale, CA  94088
Xref: sparky comp.bugs.sys5:162 comp.unix.sys5.r4:1098
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
Subject: Can a script find out, under SVR4, the ABI to which a machine conforms?
Date: 1 Jan 93 22:10:54 GMT
Followup-To: comp.bugs.sys5
Organization: Auspex Systems, Santa Clara

The SVR4 documentation I have indicates that the "sysinfo()" routine
will, if given the "command" SI_ARCHITECTURE, return "a string
describing the instruction set architecture of the current system, e.g.,
'mc68030', 'm32100', or 'i80486'."

It also hints that said "command" is used by "uname -p" to return the
"processor type" string.

Unfortunately, as I read it, that *doesn't* correspond to the ABI to
which the machine conforms:

	there isn't a Motorola 68030 ABI - there's a Motorola 68K ABI,
	but machines with 68020's, 68030's, or 68040's all have the
	right instruction set for the 68K ABI;

	similarly, there isn't an Intel 486 ABI- there's an Intel i386
	ABI, but machines with 386's, 486's, or presumably
	586's^H^H^H^H^HPentia have the right instruction set for the
	i386 ABI, or simulate the missing instructions in software, e.g. 
	if the floating-point unit is missing;

	the same presumably applies to other ABIs for processors for
	architectures that have acquired new instruction over time.

A *program* probably doesn't have to care what the ABI is for the
machine on which it's running - if it's the wrong ABI, it won't run,
period - but a *script* might care.  In particular, Frame Maker has a
"fmarch" script that, at least on some platforms, is used to select the
directory from which executables are to be run.

If, in fact, "uname -p" returns a *detailed* processor type, rather than
an ABI type, "fmarch" and, conceivably, other scripts will have to know
all the detailed processor types that support a particular ABI, and may
thus have to change over time as new instructions are added to
instruction sets and new processor types are added.

Perhaps later SVR4.x releases have already done this, but if not:

	There should be a new SI_ABI "command" for "sysinfo()", that
	returns a string that indicates the ABI to which a system
	conforms; for example, it would return "i386", or something such
	as that, on 80386-based machines, 80486-based machines,
	Am386-based machines, Cyrix-chip-based machines, Pentium-based
	machines, etc..

	The string returned by SI_ABI for a particular ABI should be
	part of the ABI specification.

	There should be a "-b" flag to "uname" to write the string
	returned by SI_ABI to the standard output.
Newsgroups: comp.bugs.sys5,comp.unix.sys5.r4
From: scum@pcthree.com (Steve Monroe)
Subject: Re: Problem with mailx in ESIX 4.0.4
Organization: PC Three
Date: Tue, 29 Dec 1992 02:28:43 GMT

hansen@pegasus.att.com (Tony L. Hansen) writes:

>< From: hmc@cs.hw.ac.uk (Hugh Conner)

<mailx problem description deleted>

>This was fixed in System V release 4.1 ES. The fix should be available from
>your vendor.

Bah hah hah hah

>					Tony Hansen
>			    hansen@pegasus.att.com, tony@attmail.com
>				att!pegasus!hansen, attmail!tony
-- 
Steven C. Monroe            VOICE:(703)406-2082                PC Three, Inc.
scum@pcthree.com             FAX:(703)406-2078                  P.O. Box 1644
                                                              Herndon, VA 22070
Newsgroups: comp.realtime
Subject: Re: What's wrong with DOS in real-time?
From: Christopher Vickery <CCVQC@CUNYVM.BITNET>
Date: Wednesday, 30 Dec 1992 12:30:47 EST
Organization: City University of New York/ University Computer Center

If you use a kernel or real-time OS, the software can easily mask
any differences between processor architecture for real-time
performance.  The items to compare are the context switch and
interrupt response times.  The amount of processor state that
has to be saved/restored and the availability of special instructions
for doing so determine context switch times.  Interrupt response
time depends on amount of state, as above, plus the amount of time
that the processor is not interruptable.  The processor's instruction
set determines the amount of time the processor has to be non-
interruptable.  If an interrupt occurs on the 8086 as a divide
instruction starts, the processor will not respond for 100x as
much time as if one of the simple instructions had just started.
The real problem with trying to do real-time with DOS is that the
software disables interrupts for long periods of time.  Adding to
the woe induced by DOS itself is the possiblity that TSRs can muck
around with the interrupt enable flag at will.  There are real time
kernels and real time operating systems available for the 8086, but if
if you want to do real-time on a DOS machine, you have to use iRMX
for Windows.  That's a full-blown real-time OS that runs only on
an 80386 or above, undoubtedly too big for a small embedded app.

Somebody else can talk about the Moto chip...
-------
Christopher Vickery, Computer Science Department, Queens College (CUNY)
Flushing, NY 11367-0904  vickery@ipc1.cs.qc.edu (718)997-3500
Newsgroups: comp.realtime
From: d7932329@dec4.ncku.edu.tw (d7932329)
Subject: iRMX III real time OS
Organization: NCKU Tainan Taiwan
X-Newsreader: Tin 1.1 PL3
Date: Sun, 3 Jan 1993 04:46:01 GMT


Hi,all

	I am a new user in using iRMX III for Windows.
   As far as I known, it is a multi-task,multi-user and
   networkable OS. You can run batch jobs and iterative
   work at the same time. After <alt-sys_request> keypressed
   ,you can toggle between iRMX and DOS quickly. 

        On the one hand,you can excute your jobs in real time
  status ( Multi-task is allowable ). On the other hand, you 
  still can get all the data through semaphares or memory.Under
  DOS, you can show all the data which currently being processed
  in iRMX III jobs.

        If you are a iRMX III for Windows customer,too. Please
  E-mail me.Maybe we can exchange some informations and have fun
  in "iRMX III for Windows".


                                  Anthony Chen             
                                     1.3.1993 in Taiwan
From: mhuang@buast7.bu.edu (Maohai Huang)
Newsgroups: comp.realtime
Subject: Re: Lynx and Chorus
Date: 3 Jan 93 05:28:23 GMT
Organization: Astronomy Department, Boston University, Boston, MA, USA

In article <1992Dec31.181031.11309@umr.edu> quandt@mcs213c.cs.umr.edu (Brian Quandt) writes:
>
> it 
>can be (and frankly is) a pain!  Many of their tools such as
>compilers, linkers, etc are old and really need to be updated.  We
>dont understand why they don't upgrade this stuff to more current
>software when most of the stuff is already public domain (mostly

and device drivers ( network cards, display, SCSI adapters etc.) are
limitedly provided for PCs. 

maybe they are busy establishing Lnyx on different platforms.

>GNU stuff).  Here's a typical problem we have experienced with Lynx:
>	We would like to use the large amount of PD software out there
>	so we download it from the nets and then try to compile.  On
>	average less then 5% of the stuff we try will compile without
>	major screwing around.  Short list of failures: xf, tk, and even
>	tcl would not compile.
>

i've spent a lot of time compiling PD software on my 486 under Lynx, with
little success. Lynx seems to me a system which provids basic utilities for
real-time task development but far from a comfortable environment. no
wonder VENIX claim itself as "real unix" -- it makes sense.

mh