HDTenEightyP/NetNews huggingface dataset:
From: james@sam.contex.com (James McQueston)
Newsgroups: comp.sys.sgi
Subject: crimson hanging
Keywords: crimson ip17 irix bug
Date: 14 Aug 92 15:46:51 GMT

We have been working very hard for two weeks now to narrow a
knotty issue where irix gets hung after tape read operations.

No login or shell will work, user processes stop, the cursor moves when
you wiggle the mouse until you have done this for two or three seconds
and then the cursor freezes in place (I assume the interrupt service
routine finds that the input buffer is full).

We just got our official Iris Partner shipment of 4.0.5A, which contained
a letter from Carol J. Buckreus, Mgr CSD Software Distribution.

The letter contains the following:

	We are in the process of planning a revision of 4.0.5A
	which will address an NFS LockD bug which limits the number
	of locked files and a Crimson R4000 kernel bug...

Can someone explain the bug referred to at the end of that sentence so
that we can consider it a possibility or rule it out?  We are taking our
hang problem through the TAC (#115939) but the above quotation is
unsettling to us.

-----
James H. McQueston					james@contex.com
Xyvision Color Systems, Inc.				(617) 246-1776 x 5523
Wakefield, MA 01880					(617) 245-4471
Newsgroups: comp.sys.sgi
From: jrh@de.deere.com (John R. Howell)
Newsgroups: comp.sys.sgi
Subject: zip - 8 bit ascii?
Date: 12 Aug 92 12:27:58 GMT
Organization: Deere & Company

I would like to use some "special" characters in the 8 bit character set.

Does zip support 8 bit (as opposed to 7 bit) ascii characters?

How do I get them in (since the ALT key is for commands)?

Do other SGI editors, etc (vi, edge, CASEVision) support 8 bit ascii?
From: sd@chem.ucsd.edu (Steve Dempsey)
Newsgroups: comp.sys.sgi
Subject: Re: DPS extensions to X
Date: 21 Aug 92 16:41:46 GMT
Article-I.D.: network.1736caINNbb5
Organization: University of California San Diego, Chemistry
NNTP-Posting-Host: chedccf0.ucsd.edu

In article <orpb8p@twilight.wpd.sgi.com> bobg@rains.wpd.sgi.com (Bob Green) writes:
>In article <32139@adm.brl.mil>, englund@gdstech.grumman.com (Dave Englund) writes:
>|> I've recently tried to do some postscript previewing on my PI 4D/25. 
>|> Using "xspview" resulted in a FATAL ERROR and told me that a correctly
	...
>
>I would guess that you have newly installed "dps_eoe" and not restarted
>your X server.
>
>	OR
>
>You haven't installed "dps_eoe" yet.

You haven't installed dps_eoe because as an old loyal customer upgrading
your 4D/25 from IRIX 3.3 to 4.0 you have the privilege of having to pay
extra for 'dps_eoe', even though 'dps_dev' is included in the upgrade, and
even though 'dps_eoe' is bundled for free on new machines.

I've tried to use 'xpsview' on an Indigo that recently arrived here and
couldn't get many of our documents to display!

Instead I got the GNU 'ghostscript' via anonymous ftp from sgi.com and
it has never failed.  You can beat free software that works!

>The "dps_eoe" product contains the driver for viewing DPS while
>the development piece serves only the development needs.
> 
>|> Any help would be greatly appreciated! Thanks!
>|> 
>|> 
>|> 			Dave Englund | #include <stdio.h>
>|> 	 englund@gdstech.grumman.com | main() 
>|> 		       Grumman Corp. | {
>|> 	   Corporate Research Center | 	  printf("hello, world\n");
>|> 			Bethpage, NY | }
>
>Good Luck,
>Bob Green
Newsgroups: comp.sys.sgi
From: heiko@Groucho.Chemie.FU-Berlin.DE (Heiko Schlichting)
Subject: Re: 4.0.5 confusion (again, still)
Organization: Free University of Berlin, Dept. of Chemistry
Date: Thu, 20 Aug 1992 03:10:20 GMT

sysmark@helios.physics.utoronto.ca (Mark Bartelt) writes:

>Finally, one last question:  Of the various flavours of 4.0.5 releases
>(A,C,D), is it only the eoe1 and eoe2 subsystems which differ?  On my
>4.0.5A CD, only the eoe[12] subsystems have any sort of alphabetic suffix
>after the version number.

I didn't found any alphabetic suffix on my CDs at all. 'uname -a' says "4.0.5"
and 'versions eoe1' too. How can I check which release it is? (SGI Berlin
says it is 4.0.5A and we'll get 4.0.5C soon).

Heiko
-- 
Heiko Schlichting                     | Freie Universitaet Berlin
heiko@groucho.chemie.fu-berlin.de     | Institut fuer Kristallographie
Newsgroups: comp.sys.sgi
From: olson@anchor.esd.sgi.com (Dave Olson)
Subject: Re: bru filename length problem...
Keywords: sigh
Organization:  Silicon Graphics, Inc.  Mountain View, CA
Date: Thu, 20 Aug 92 04:43:42 GMT

In <acas.714179869@godzilla.cgl.citri.edu.au> acas@cgl.citri.edu.au (Andrew Cassin) writes:
| We do our backups (daily incremental, weekly incremental and monthly full
| backups) using bru. However, ever since we made the backup host an
| AppleShare server (courtesy of a Webster MPG, CAP and a little patience :)
| we have been unable to backup some people's files due to an excessive
| pathname length (> 127 chars). IRIX 4.0.1 is currently being used.
| 
| Question:  why is the max pathname length so short??? Will it be fixed in
| 	   a later release of bru/irix? Is there a workaround (apart from
| 	   not writing out the full pathname)?

Because at one time, 127 was a long file name...

A newer version of bru exists, which permits up to 1024
(MAXPATHLEN) chars, in a compatible fashion, but SGI has
chosen not to license that version (or invest the time to
make equivalent changes ourselves).  You'll have to complain
to your sales folks and the TAC to make it an issue.

There is no workaround, except to do multiple backups,
some of them further down the directory tree, and to
omit the 'bad' part of the tree on your main backups.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: dump and logical volumes
Date: 20 Aug 92 05:03:38 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <1992Aug19.134643.6347@gserv1.dl.ac.uk> ufe@dlva.dl.ac.uk writes:

| Attempts to use dump on a logical volume fail.
| eg dump 0uf /dev/tape /data1 hangs in Phase 1. (/data1 is a striped
|    partition)
| dump process is taking virtually all cpu and can't be killed
| Has anyone seen this ?

Dump and lv's (both striped and concatenated) have worked just
fine for us (including me personally) since 4.0.1 when dump
was first supported.

Can you force a core dump of dump (something like 'killall -ILL
dump')?  If so, and you contact the TAC, and can get the
core file to them, we can figure out where it was looping.

Other than that, I haven't any ideas.  Are there no kernel
or dump messages when this happens?
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Newsgroups: comp.sys.sgi
From: jeremy@classic.asd.sgi.com (Jeremy Higdon)
Subject: Re: CDC Drive Parameters
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Wed, 19 Aug 1992 03:44:37 GMT

In article <1992Aug19.011509.7427@iscnvx.lmsc.lockheed.com>, cunning@arthur.msd.lmsc.lockheed.com (Dave Cunningham) writes:
> My in-company computer repair folks replaced my failing 380 Mb system
> disk on a 4D20 with with a similar one last used on a sun.  It's the
> same model (CDC 94171-9) but with a different firmware rev. (0045).
> I formatted it with stand alone fx, using the "auto" command.  That
> went ok, but I notice that some of the drive parameters are different
> than on my SGI CDC 380s- specifically,  "Report recovered errors" is 
> enabled, "Auto bad block realloc. on read" is enabled, "Error retry attempts"
> is 16, and "Drive read-ahead" is enabled.
> 
> Are all of these changeable with fx, or are they jumpered ?
> If so, should I change them or assume fx did what was right ?

They are all changeable using fx, and fx won't change any of them
without specifically being told to.  Newer disks shipped by SGI
have the "Auto bad block realloc. on read" enabled and
"Drive read-ahead" enabled with "Report recovered errors" disabled
and "Error retry attempts" typically set to manufacturer default.
If the "Auto bad block realloc. on read" on the disk works (we've
seen bugs on some disk drives when this feature was enabled), it
should probably be enabled.  Same with "Drive read-ahead".
Unfortunately, you probably don't have a good way to know if the
features work.  If you weren't having any problems on the Sun,
you probably won't on the SGI, but you may, since disk access
patterns and usage may be different.

"Report recovered errors" should be enabled if you want to see
when your disk recovers from errors.  Since this is a relatively
common occurence, you may or may not need to know.  If you
leave it on, don't be surprised to see a "Read data recovered with
retries" message every now and then.  Finally, "Error retry attempts"
is between you and the manufacturer.  Generally, the higher the
number, the more the disk will try to recover your data when it's
having a hard time.  Only certain numbers are valid, typically.

Use the /label/set/param option of fx to play with these params
if you want to.  Remember to be careful and back up your data
beforehand.

jeremy

Newsgroups: comp.sys.sgi
From: ercolessi@uimrl7.mrl.uiuc.edu (furio ercolessi)
Subject: Re: Binary File: SGI <-> IBM
Reply-To: ercolessi@uimrl7.mrl.uiuc.edu (furio ercolessi)
Organization: MRL - UIUC
Date: Thu, 13 Aug 1992 05:36:16 GMT

In article <1157@deere.com>, jrh@de.deere.com (John R. Howell) writes:
|>I have a binary file created with C fwrites and read with C freads.
|>
|>If I create this on an SGI (IRIX) and read it with an IBM RS6000, I seem to
|>read everything ok, but my floating point numbers don't make sense. If
|>I go the other way (IBM -> SGI) a similar thing happens.
|>
|>Apparently the integers are read correctly ...
|>
|>OK ... I have apparently stumbled upon a difference in floating point
|>formats between the different machines.

Fortran 'unformatted' files (which are binary) are shared without
problems between IBMs, SGIs, HPs, Suns and DECstations (the 
latter only with a magic compiler option).  All these machines have
IEEE arithmetics.
So the source of your problem must be a more subtle one
(and I have no ideas).
furio
--
Furio Ercolessi
Materials Research Laboratory           |   Intl School for Advanced Studies
Univ. of Illinois at Urbana-Champaign   |   Trieste, Italy
furio@uiuc.edu                          |   furio@sissa.it
From: chuckb@milton.u.washington.edu (Chuck Bass)
Newsgroups: comp.sys.sgi
Subject: Remote backups using bru and vadmin?
Date: 14 Aug 92 19:50:01 GMT
Organization: University of Washington



SGI sysadims:

I am trying to do a remote backup using the visual administration
tools.  I keep getting the following message.  

" The system is unable to open the remote tape device"

This lead me to the man page on bru.  I apparently must have
a brutab entry to make this work.  My question is:  With this as
the "mt status" for the tape drive I want to go to what is the 
proper brutab entry? 

  woodsy:~/tmp  % mt status
        Controller: SCSI
        Device: ARCHIVE: VIPER 150  21247-005 VP1
        Status: 0x362
        Drive type: QIC 150
        Media : READY, writable, at BOT, QIC120 format, block 1

I can't quit figure out the correct format to make this work.  
Or what to type in the Remote Host line in the vadmin stuff.

Any ideas, or better yet is there a manual that I have
not looked at that will answer my question?

Incedently I can use tar with no problems to do remote backups using
the following line:

   blueox:# tar cvf woodsy:/dev/tape myfiles.c
   
   
Cheers,

Chuck Bass
Cooperative for Forest-Systems Engineering
University of Washington   
   
   
Newsgroups: comp.sys.sgi
From: yves@gvu1.gatech.edu (Yves Darly Jean)
Subject: Help: new OS  -> the colormap gets confused
Summary: Rectwrite and the colormap call act funny        
Organization: Georgia Institute of Technology
Date: Fri, 21 Aug 1992 18:12:54 GMT


I have some code that puts an image on the screen using the Rectwrite call.
The Rectwrite call is preceded by a series of colormap calls to set up
a grayscale in the colormap table.  This code worked on the previous OS
but on the new OS (ver. 4.01) it doesn't work correctly.

The image is put on the screen but the colors are way off.  When I Showcolormap
 I can't find my graycale ramp. But when I select the cinterp option
of Showcolormap and open the cinterp window the grayscale entries suddenly
appear both in the colormap and in my image.

Please help if you can.  Thanks in advance.

YDJ
JEAN,YVES DARLY
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!cc!gvu1!yves
Internet: yves@cc.gatech.edu
From: joseph.maddry@matrix.sbs.com (Joseph Maddry)
Newsgroups: comp.sys.sgi
Subject: list
Date: 13 Aug 92 22:26:21 GMT

Date:        Tue, Aug. 11, 1992
From:        Joseph Maddry  <joseph.maddry@matrix.sbs.com>
Newsgroups:  comp.sys.sgi

Please take me off the mailing list.

(This is request number eight; please acknowledge this message!  Thanks.)

Joseph Maddry
joseph.maddry@matrix.sbs.com
---
 . SLMR 2.1a . If at first you don't succeed, use BIG LETTERS!
From: emilia@natinst.com (Emilia Hezari)
Newsgroups: comp.sys.sgi
Subject: Re: Any possibilities for GPIB on an Indigo
Summary: There is a solution
Keywords: gpib
Date: 19 Aug 92 15:44:25 GMT
Followup-To: comp.sys.sgi
Distribution: comp.sys.sgi
Organization: National Instruments, Austin, TX

In article <1992Aug18.213605.29950@magnus.acs.ohio-state.edu> hshamans@magnus.acs.ohio-state.edu (Harry T Shamansky) writes:
>Hello again...
>
>Is there any hope for GPIB control from my new Indigo ??
>
>Any suggestions will be appreciated....
>
>Thanks
>  
>  Harry

(I hope this is not a repost. I don't think my first message made it.)

National Instruments makes a GPIB interface for the IRIS Indigo and
Personal IRIS platforms. For more information, call 1-800-IEEE-488 or
(512)794-0100 and ask about the GPIB-SG-S kit.

Emilia Hezari
National Instruments
emilia@natinst.com
Newsgroups: comp.sys.sgi
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: Using the Automounter
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Mon, 17 Aug 1992 03:15:02 GMT

> In article <4275@inca.comlab.ox.ac.uk> mjs@prg.ox.ac.uk (Michael Smith) writes:
> >Has anyone out there perfected use of this wonderful feature?
> >I have managed to set it up, but, for example, typing
> >cd /home/nmra and then pwd gives /tmp_mnt/home/nmra, which
> >is fine-ish, but makes things a bit more difficult to use.
> >Is there some way of setting it up so the look is the same
> >as with the ordinary mount?


What I do is include the following line in my ~/.cshrc:

set home = `cd; pwd`

That makes $HOME and ~ point to /tmp_mnt/home/whatever, and generally
makes things that want `pwd` from ~ to do obvious things.  The line is
generally handy whenever the home directory in /etc/passwd (and
substitutes like NIS) is really a symbolic link.


Vernon Schryver,  vjs@sgi.com
From: joseph.maddry@matrix.sbs.com (Joseph Maddry)
Newsgroups: comp.sys.sgi
Subject: list
Date: 13 Aug 92 22:37:08 GMT


Date:        Tue, Aug. 11, 1992
From:        Joseph Maddry  <joseph.maddry@matrix.sbs.com>
Newsgroups:  comp.sys.sgi




                 SOMEONE










Joseph Maddry
joseph.maddry@matrix.sbs.com
---
 . SLMR 2.1a . If at first you don't succeed, use BIG LETTERS!
                                                                
Newsgroups: comp.sys.sgi
From: keithk@milton.u.washington.edu (Richard Keith Kerr)
Subject: Need help with RPC on Indigo
Keywords: RPC
Reply-To: keithk@u.washington.edu
Organization: University of Washington, Seattle
Distribution: na
Date: Thu, 20 Aug 1992 21:11:12 GMT


I am trying to port some RPC code from a Sun to an Indigo and
having trouble with the RPC sections.  I would like to use
the C++ compiler and I have followed the advice in the
examples in Chap. 4 of SGI`s "IRIX Network Programming Guide",
but no luck.  I then tried their simple msg_server example,
and got compile warnings and core dumps.

Can someone please point me to RPC code I could ftp or
send a VERY SMALL example of correctly using RPC with 
the SGI (IRIX 4.0.1) system.  I would prefer it compiled
with C++, but anything would help.

Thanks,
From: C_X_Gladstone%MWCORP1@mwmgate1.mitre.org
Newsgroups: comp.sys.sgi
Subject: MULTIPOINT Z 3-D mouse
Date: 13 Aug 92 20:09:20 GMT


         Larry,

         I put my hands on one of those mice at SIGGRAPH.  It felt good and
         compared favourably to the Spaceball.  Of course that doesn't say
         anything about how hard it is to develop applications.   One point
         that might be a drawback, they appear to come only in a
         right-handed form, and many people prefer to control the mouse
         with the left hand.

         If you get one, post to the net to say how you like it.

         Regards,

         Carla Gladstone    (MITRE Corporation  703-883-6861)
Newsgroups: comp.sys.sgi
From: jigang@dale.ssc.gov (Jigang Yang)
Subject: Re: NFS really slow in 4.0.1
Organization: SSC Lab
Date: Sun, 16 Aug 1992 02:59:12 GMT

In article <nch46so@rhyolite.wpd.sgi.com>, vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:
|> In article <31430@adm.brl.mil>, root@roosta.ama.ttu.edu (Kim Andersen) writes:
|> > ...
|> > This is a software patch to a hardware bug. The software patch
|> > is part of 4.0.5, so call SGI and get on their list to get 4.0.5
|> > when 4.0.5a ships. SGI also has fixed the chip for future systems.
|> > 
|> > This only works on IP12 and IP17 machines (Indigo, PI, Crimson).  ....
|> 
|> The problem that is affected by running in promiscuous mode affects
|> only IP12's, 4D/35's and Indigos.  It has nothing to do with Crimson.
|> Running this program on a Crimson on a busy network is a good way to
|> waste a lot of CPU cycles and do absolutely nothing good.  The problem
|> is related to interactions between the SEEQ ethernet chip and a custom
|> chip in the IP12.  The IP17 has neither of those chips.
|> 
|> 
|> Vernon Schryver,  vjs@sgi.com

    Is there any patch available for 4D/35 right now? The NFS is 
ridiculously slow, time out frequently. I hope I don't have to go
back to old version.

-- 
Jigang Yang, jigang@dale.ssc.gov, jyang@sscvx1.bitnet
2550 Beckleymeade Ave. MS 4011  Tel: 214-708-3498
Dallas, TX 75237                Fax: 214-708-4898
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: Crimson, symmon, kp scsi 0
Keywords: irix debugging symmon
Date: 21 Aug 92 02:18:14 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <2887@contex.contex.com> james@sam.contex.com (James McQueston) writes:
| I have installed setup my kernel to make symmon available
| according to the instructions in "IRIX Device Driver Programming Guide,"
| Document Number 007-0911-020, 3/92.
| 
| When I enter symmon by typing ^A and then type:
| 	kp scsi 0
| I get:
| 	WD93A controller at 0xb7f08007
| 	AUX 0x0 ...
| 	.
| 	.
| 	.
| 	CMD 0x8 DATA 0xff <and then it hangs right here>
| 
| What I mean by <and then it hangs right there> is that the cursor
| is left at then end of "0xff" and no newline seems to be output.
| Not only that, but now symmon is dead, and ^A will not bring it back.

Sounds like somebody didn't test symmon adequately (or more accurately,
the code in idbg.o that prints scsi data structures).  I guess you
are out of luck.  For all I know, the same happens in 4.0.5, although
I *do* know it isn't a problem on r4k indigos with 4.0.5D.

| Is this a known problem on Crimson, or is there something
| wrong with my IO3 board?

It isn't an i/o board problem.  It is almost certainly a software
bug.

| We have a timing - related problem that may be a bug in IRIX or
| in our specific hardware that is evidenced by a temporally tempramental
| set of: 6 x read(80 bytes), ioctl(forward space file), n x read(8192 bytes),
| ioctl(forward space file) 6 x read(80 bytes).  And that is why I want
| to know whether "kp scsi 0" is supposed to work.

kp scsi 0 is somewhat risky, in that it can cause you to lose SCSI
interrupts, since reading the chip status register is what clears
them (AUX register having bit 7 set indicates an interrupt was pending).

kp scsi 0 isn't likely to help much with target type problems anyway,
it is mainly an aid to people working on the driver.  "kp scsi 1", or
"kp scsi 2" is far more likely to be helpful.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
From: williams@agomoda.asd.sgi.com (Eric Williams)
Newsgroups: comp.sys.sgi
Subject: Re: xwsh -vt100
Date: 22 Aug 92 02:17:55 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <32156@adm.brl.mil> MIKE@scripps.edu (Mike Whittaker) writes:
> Number 1, I'd like to change the font in the windows, but I can't 
> figure out the -xrm flag. 

The -fn flag will do what you want.  Try something like this:

xwsh -fn -schumacher-clean-bold-r-normal--14-140-75-75-c-80-iso8859-1


If you want to use -xrm then try something like this:

xwsh -xrm '*font: -schumacher-clean-bold-r-normal--14-140-75-75-c-80-iso8859-1'

I think you need a full X font name.  I got this one using the font browser
(by clicking the right mouse in an xwsh and selecting Font...).  The -xrm
option allows you to pass X resources to xwsh.  See the man page for all
the different resources you can set.  e.g. just to see how multiple resources
could be set I tried:

xwsh -xrm '*font: -schumacher-clean-bold-r-normal--14-140-75-75-c-80-iso8859-1\
*foreground: yellow\
*background: blue'

It's easier to deal with resources if you use a .Xdefaults file.  See the
4Dgifts account for an example.  The xprop program is also very handy when
you start playing around with resources.



> Number 2, I'd like the
> backspace key to actually act like a backspace key. Currently only the
> delete key works like a backspace key when logged into the remote Vax.

I suspect this is the "fault" of the VAX and is more a difference in
default keyboard.  On SGI keyboards the backspace key (which sends a
control H) is more convenient than the delete key (control-?), so try
this:

	stty erase '^H'

to tell UNIX to use backspace instead of delete.  This could be put in
your .login file on the VAX to make it the default.


Good luck,
Eric Williams