HDTenEightyP/NetNews huggingface dataset:
From: po87553@cs.tut.fi (Pasi 'Albert' Ojala)
Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin
Subject: Re: Summary: colorstation doesn't power up
Date: 31 Dec 92 21:47:59 GMT
Distribution: comp
Organization: Tampere University of Technology
NNTP-Posting-Host: kaarne.cs.tut.fi

This is a forwarded message from: Juha Tuominen

>as the total opposite of a hardware freak i am not able to check 1) so
>i tried first to check 2) the proper operation of the battery. Pasi 
>'Albert' Ojala <po87553@cs.tut.fi> suggested to measure the voltage of
>the battery between the shield of the ethernet tube (ground) and pin 6
>of the monitor outlet (without power cord connected). there were the
>correct 2.5 V or more - the battery was ok! now i performed the final

To be honest, I made a mistake. If your NeXT doesn't boot, check the
voltage between system ground and pin 6 on the monitor D connector. 
Ethernet ground tube IS NOT CONNECTED to the system digital ground - directly.
If you look your NeXT cpu board in front of a light, you can see that the
power and ground layers inside the board are cut around the ethernet stuff.
That's because ethernet wires are often connected and disconnected when system
is up and running. The potential differences between the NeXT and etherenet
shield (and hot wire, too) may otherwise damage the cpu board. That's why
ethernet stuff is separated of the other system and signals and
ground is connected to it via a converter. (A blue little tube, made by SONY,
about 10 cm from the ethernet connector). OK, the monitor D-connector
pins from 13 to 19 are connected to ground (check Q&A for futher information,
they all work for measurements to find out if the battery is dead or not),
so if you have to check the battery condition, take ground one of those
pins WHEN THE SYSTEM IS NOT ON AND NOT EVEN WIRED TO THE WALL OR THE 
MONITOR!.
-Juha
-- 
Pasi 'Albert' Ojala     The other author of AXsh
po87553@cs.tut.fi	albert@cc.tut.fi
Newsgroups: comp.sys.next.hardware
From: ag@nextcube.in-berlin.de (Andreas Gradert)
Subject: Re: Help Wanted: External SCSI Disk (From SUN)
Organization: Privat
Date: Sat, 02 Jan 1993 22:25:12 GMT

nzhang@umiacs.umd.edu (Ning Zhang) writes:

> I was wondering if there is any difference between the SCSI on NeXT
> and the one on SUN Sparc? Or, did I do something wrong? FYI, I used
> the SCSI cable from SUN for connecting the disk to the NeXT box.

This worked for me. But don't forget the Schwarzenegger, rsp. terminator.

I took the drive directly from an IPX an formatted it under NS 3.0.

Works fine.

mfg, Andreas
-- 
Andreas Gradert | fon  +49 30 6923946 | email ag@nextcube.in-berlin.de
Bluecherstr. 15 | fax  +49 30 8825421 |   andreas@unlisys.in-berlin.de
D1000 Berlin 61 | leave INtel OUTside |  unido!fub!unlisys!nextcube!ag
Newsgroups: comp.sys.next.hardware
From: iwelch@agsm.ucla.edu (Ivo Welch)
Subject: SCSI Treatment
Organization: UCLA, Anderson Graduate School Of Management
Date: 28 Dec 92 11:01:44 PST

After  my  twentieth problem with   connecting/disconnecting SCSI disk
drives, I am   wondering   about  the proper "protocol"  of   handling
connecting/disconnecting/transporting them.

	[1] I understand that first the host should be synced and halted.
	Question: Does the host also need to be powered down, or is the
	ROM Monitor sufficient.

(then)	[2] Should the hard disk be powered down before it is removed
	from the SCSI chain, or can I unplug it from the SCSI chain with
	power on?

(then)	[3] Is it safer to move the hard disk with power on or with power
	off? A repair man once told me that the air pressure from a running
	disk is a better warranty that the head won't touch the disk.

Oh, I own an Imprimis 94601-15 and a Seagate ST41650 disk.

/ivo
From: bohlkejh@nextwork.rose-hulman.edu
Newsgroups: comp.sys.next.hardware
Subject: AAAAAARRRRRRRGGGGHH!!!! scsitools
Date: 4 Jan 1993 04:24:14 GMT
Organization: Computer Science Department at Rose-Hulman
Reply-To: bohlkejh@nextwork.rose-hulman.edu
NNTP-Posting-Host: cornflower.nextwork.rose-hulman.edu

Hey,
   Do the scsitools on the purdue archives work on NeXTSTEP 2.2 or 3.0?  I have
yet to get changes I have made to appear on the disk!!!!!!!!!!

Help   ;-(

Jon
From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Newsgroups: comp.sys.next.hardware
Subject: Re:   Multi Line BBS
Distribution: world
Date: 22 Dec 92 20:33:24 PST
Organization: Not an Organization

In article <1992Dec20.152822.29515@wam.umd.edu> rsrodger@wam.umd.edu (Yamanari) writes:
>In article <dillon.0t21@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US (Matthew Dillon) writes:
>>
>>    * If you fill up the disk and the NeXT runs out of swap it crashes
>>	hard.
>>    * No resource limits (NeXT ignores everything but the stack size limit)
>>    * No process/thread limits
>	  ^^^^^^^^^^^^^^ ^^^^^^
>
>	Surely you jest.  Surely, certainly, the OS of the future is
>	not so threadbare that it lacks features that most versions
>	of UNIX have these days..?

    What I mean to say is that the NeXT will gladly allow you to fork
    processes and threads until it runs out of table space or memory, then
    it crashes.

					-Matt

>	     Rule 1:  "Don't have more children than you can feed."
>		  Nuclear redevelopment for a better world!

--

    Matthew Dillon		dillon@Overload.Berkeley.CA.US
    1005 Apollo Way		uunet.uu.net!overload!dillon
    Incline Village, NV. 89451	ham: KC6LVW (no mail drop)
    USA 			Sandel-Avery Engineering (702)831-8000

Newsgroups: comp.sys.next.hardware
From: brunkhorst@mayo.edu (Geoff Brunkhorst)
Subject: Re: Flickering in new 17" Trinitron monitor
Reply-To: brunkhorst@mayo.edu
Organization: Mayo Foundation, Rochester MN. Campus
Date: Mon, 21 Dec 92 13:40:43 GMT

In article <1992Dec20.081910.15987@cs.yale.edu> nathan@laplace.csb.yale.edu  
(Nathan F. Janette) writes:
> I don't know, but I just wanted to toss in a comment about
> how *great* the new monitor is in comparison to the
> previous piece of junk NeXT was peddling.  It's now as good
> as it should have been in the first place!  Top notch!  Love
> it!

I agree.  It is definitely first rate, especially with the focus knobs on the  
bezel.  

Since I moved my ADB/Trini into the target office and the flicker went away on  
my system.  Seems the office where the flicker was (soon to be my office  
again), has a step-down transformer (some huge voltage -->480V3ph) directly  
above it.  The higher scan rate must more adversely affected by the noise this  
device puts out.

Also, the ADB keyboard, once you're used to it, is definitely a plus.  Now a  
command-C doesn't tunnel my carpals.  

--
- Geoff
-----------------------------------------------------------------
Geoffrey Brunkhorst                           brunkhorst@Mayo.edu
Research Computing Facility, Guggenheim 10         (507) 284-1805
Mayo Foundation, Rochester MN, 55905, USA      fax (507) 284-5231
From: bill@mathnx.math.byu.edu (Bill Smith)
Newsgroups: comp.sys.next.hardware
Subject: Re: SCSI Treatment
Date: 29 Dec 1992 17:43:31 GMT
Organization: Brigham Young University
Distribution: world
NNTP-Posting-Host: mathnx.math.byu.edu

In article <1992Dec28.110145.11642@mic.ucla.edu> iwelch@agsm.ucla.edu (Ivo  
Welch) writes:
> After  my  twentieth problem with   connecting/disconnecting SCSI disk
> drives, I am   wondering   about  the proper "protocol"  of   handling
> connecting/disconnecting/transporting them.
> 
> 	[1] I understand that first the host should be synced and halted.
> 	Question: Does the host also need to be powered down, or is the
> 	ROM Monitor sufficient.
> 
> (then)	[2] Should the hard disk be powered down before it is removed
> 	from the SCSI chain, or can I unplug it from the SCSI chain with
> 	power on?
> 
> (then)	[3] Is it safer to move the hard disk with power on or with  
power
> 	off? A repair man once told me that the air pressure from a running
> 	disk is a better warranty that the head won't touch the disk.
> 
> Oh, I own an Imprimis 94601-15 and a Seagate ST41650 disk.
> 
> /ivo

Well, I can tell you that our hardware guy would wince at the very
thought of doing anything without a complete power down of external
drive and machine.  Then power up drive, then machine.  
-Bill
--

       _ _|_______====___H____/===_====_====_====_====_===\____H___====_____ 
        |_______| [[[[    \### &&&&&&&&&&&&||&&&&&&&&&&&& ###/     [[[[     |
  _______| [][] |____  """         UNION |  | PACIFIC        """            |
  |o ____|  UP  |__| \___________________|_ |____________________/\_________|| 
|_| /    |__74__|   \_|  |  |  |  |  |  ||  |  |  |  |  |  |  | /  \|   |  |||
|_|=|====|======|===|===\/=================================|=\/=|======|===|_|
|_|  [(o)=(o)=(o)=(o)]|_________________||________________[(o)=(o)=(o)=(o)]|_| 
==============================================================================
]    []    []    []    []    []    []    []    []    []    []    []    []   []
                           5000 H.P. Track Staightener
Newsgroups: comp.sys.next.hardware
From: ulrich@canberra (Nathan Ulrich)
Subject: Re: Flickering in new 17" Trinitron monitor (image off-center)
Keywords: off-center image
Reply-To: ulrich@canberra.whoi.edu
Organization: Woods Hole Oceanographic Institution
Date: Tue, 22 Dec 92 01:06:00 GMT

In article <1992Dec20.182151.3909@lilliput.fdn.org> joseph@lilliput.fdn.org  
(Joseph Goldstone)  
writes: 
>Apparently it works pretty well.  As was told to me maybe 6 weeks ago, if you  
>have an Olde Systeme like mine, Olde '040, Olde ND, Olde SoundeBoxe, Olde  
>Keyboarde, &c, the display works but with the following quirk: the active area  
>of the display is shifted offcenter, I forget exactly howmuch, maybe 3/16" if  
>memory serves, and I forget to which side.

I'm using one of the new 17" monitors with an old ND and cube setup.  The image  
starts approximately 8 mm from the bezel on the right and 13 mm from the bezel  
on the left.  It is not at all distracting, and in fact I hadn't noticed it  
until the subject came up on this thread.  (5 mm is slightly more than 3/16")

My flickering--really more the image shaking--problem still recurs occasionally  
(it was quite bad earlier today, but barely noticeable now).  From my  
experimenting, it appears to have nothing to do with the position or  
orientation of the monitor, nor with its proximity to my MegaPixel mono or  
cube.  It seems to be related to the building power in some way.  The main feed  
for the building runs right under my floor--this has been suggested as a cause,  
though there really shouldn't be unbalanced magnetic fields with an AC feed.  I  
also plan to put a line conditioner in as soon as possible and see if that  
cleans up the problem....

--
Nathan Ulrich
Deep Submergence Laboratory
Woods Hole Oceanographic Institution
ulrich@canberra.whoi.edu
From: jimb@access.digex.com (Jim Brooking)
Newsgroups: comp.sys.next.hardware
Subject: Help with Fujitsu Hard Drive
Date: 31 Dec 1992 22:09:02 GMT
Organization: Digicon
Distribution: usa
NNTP-Posting-Host: access.digex.com

We have a Fujitsu M2652SA hard drive mounted externally on
a cube.  The Fujitsu is 2.0 gb (unformatted), and is acting
as a network server disk.

There is a recurring problem wherein the cube panics without
warning.  No one needs to be logged in to the cube for the panic
to happen.

When rebooting, fsck fails, so we run it manually.  The Fujitsu
winds up with a ton of duplicate INodes and other problems which
wind up causing a loss of data.

Does anyone know why this is happening?  We're running 3.0, and
the cube is rebooted daily.  I realize the explaination is sort 
of sparse, but it's all we can get at the moment.

Any assistance would be appreciated!  8^)

Thanks
-- 
jimb@access.digex.com  | (Cage) 1991 323se     ZCP-710   |     Comus Road
Merry Land (MD) U.S.A. | (Bike) 1986 GSXR750    (sold)   |     ClarksBURG
------------------------------------------------------------------------------
Newsgroups: comp.sys.next.hardware
From: verket@venice.sedd.trw.com (Paul Verket)
Subject: Re: CD-ROM causes system panic
Organization: TRW Systems Engineering & Development Division, Carson, CA
X-Newsreader: TIN [version 1.1 local 1 PL6]
Date: Thu, 24 Dec 1992 16:55:06 GMT

Mark T. Dornfeld (mark@cyantic.com) wrote:
: I have tried reading several CD's for Sun with no success.  The Workspace
: just spits them back out with no information as to why.

Most Sun CDs are encoded in their own ufs format which the NeXT doesn't
understand. (Neither does the Mac) 

It's good for Sun users because they have to _explicitly_ tell their
mount command which format disk was inserted and ufs is the default.
It's only bad for EVERYONE ELSE(!) or those who have other brands
in addition to their Suns (blastphamy!).

The funny thing is that the first CD put out by Sun, the original CDROM
demo disk was a nice standard format that the Sun, NeXT and Mac could
all read.

Paul Verket (NeXTmail ok)
Xref: sparky comp.sys.next.hardware:3136 comp.sys.next.sysadmin:7254
From: brueck@inm.uni-sb.de (Stefan Brueck)
Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin
Subject: Summary: colorstation doesn't power up
Date: 31 Dec 92 12:46:48
Organization: Institute for New Materials (INM), Saarbr"ucken, Germany.
Distribution: comp
NNTP-Posting-Host: inmsol.inm.uni-sb.de
In-reply-to: brueck@inm.uni-sb.de's message of 25 Dec 92 14:07:06

thank you for your help! the problem is solved with your help and the 
computer is running again. 

the received answers to my problem 'computer doesn't start again when
i press the power key' mentioned three possible causes:

1) the power supply is dead
2) the battery is dead or has bad contact
3) damaged data in non-volatile ram buffered by the battery

as the total opposite of a hardware freak i am not able to check 1) so
i tried first to check 2) the proper operation of the battery. Pasi 
'Albert' Ojala <po87553@cs.tut.fi> suggested to measure the voltage of
the battery between the shield of the ethernet tube (ground) and pin 6
of the monitor outlet (without power cord connected). there were the
correct 2.5 V or more - the battery was ok! now i performed the final
check 3^) i opened the next (oh so many nice little pieces!) and re-
moved the battery for about 30s then i inserted it again (check the
proper direction!). several answers said that this would destroy the 
eventually bad data buffered in the non-volatile ram. the answers said 
that doing this does destroy correct data (boot parameters, hardware 
password) too. after assembling the computer together again (service 
friendly - one screw!) i pressed the power key... ... ... WHOW the
computer is starting!!! it tried first to check for ethernet to boot
from - ok this was caused by the default boot parameters and could
be fixed by setting the correct boot device according to the sysadmin
manual...


thank you very much!
      stefan

--

##############################################################################
Institut fuer Neue Materialien (INM) #  
Universitaet des Saarlandes, Geb. 43 # Phone: +49 681 302 5086
Stefan Brueck                        # E-Mail (Internet): brueck@inm.uni-sb.de
W-6600 Saarbruecken (Germany)        #
##############################################################################
From: Jim_Laredo@transarc.com
Newsgroups: comp.sys.next.hardware
Subject: Device Block Size
Date: 28 Dec 92 06:02:29 GMT
Article-I.D.: transarc.IfDmIJD0Bwx5I1_r4u
Organization: Carnegie Mellon, Pittsburgh, PA

I installed the 1.23GB HD, and found that it came with a device block
size of 512Bytes. The original Seagate was formated with a 1024Bytes
block size.

Do you have any idea what the performance impact is? Should I try to
reformat the disk to get a block size of 1024Bytes?


How hard is to reformat the HD to set the block size to 1024, can I do it
or is it a manufacturer's job?


thanks in advance,
Jim.
Newsgroups: comp.sys.next.hardware
From: kimman@magnus.acs.ohio-state.edu (Kim Richard Man)
Subject: How to adjust monitor?
Organization: The Ohio State University
Date: Tue, 29 Dec 1992 20:41:33 GMT

Hi,

I saw a discussion on how to adjust the internal setting of the mono monitor a
while ago. Would anybody have that article forward it to me?

Thanks in advance.
From: arrigo@cube.sublink.org (Arrigo Benedetti)
Newsgroups: comp.sys.next.hardware
Subject: Re: CD-ROM causes system panic
Date: 24 Dec 92 11:12:22 GMT
Reply-To: arrigo@cube.sublink.org
Organization: Arrigo Benedetti

In article <Bz64Lt.9z1@world.std.com> ferguson@world.std.com (Jon E  
Ferguson) writes:
> When I mount the Jewel of the Matrix CR-ROM, the Workspace refuses to
> show me any of the files.  When I look at it from a terminal window,
> I can get directory listings, but they are messed up: There is no
> ".." directory, instead there is a directory named "?". The rest
> of the files in a directory are all lowercase, and truncated after
> a dozen characters or so.
> 
> The fun part is, if I try to read any of the files in any way, I
> get a system panic.
> 
> At first I though it was just a messed up disk (though I found this hard
> to believe).  Then I tried mounting an old Next Demonstration Software
> CD-ROM (Q3 1991), and as soon as the system mounted it, I got a system
> panic.
> 
> I am able to read my 3.0 and Educational Software Sampler CD-ROMs
> just fine, so I am inclined to believe it has something to do with
> the format of the other two disks (Rock-Ridge extensions perhaps?).
> 
> Has anyone else been having trouble reading specific CD-ROMs?
> Has anyone else ordered the Jewel of the Matrix CD-ROM, and were
> you able to read it?
> 

Yes, and I had no problems at all.

> I'd really love to get this working so I can remove all the stuff on
> my HD which overlaps with the Jewel o' the Matrix.
> 
> -Jon
> 
> ferguson@world.std.com
> "If Casper is a friendly ghost, where did they bury the body of
> Casper the Friendly Dead Kid?"
-- 
Arrigo Benedetti             e-mail: arrigo@cube.sublink.org (preferred)
University of Bologna                benedett@deis01.cineca.it
undergraduate student (EECS)         
Via S. Agata, 11               Tel:  (home)   +39 59 224929
41100 Modena - Italy                 (office) +39 59 216688 (fax) +39 59 220727
Newsgroups: comp.sys.next.bugs
From: kenny@netcom2.Netcom.COM (Ken Smith)
Subject: Workspace 3.0 doesn't eject floppies
Organization: Netcom Online Communications Service
Distribution: comp
Date: Tue, 29 Dec 1992 21:17:24 GMT

Since upgrading from 2.1 to 3.0, the Workspace Manager can no longer
eject floppy disks.

The only way I can eject a floppy is with /usr/etc/disk, which is a
pain because I still have to su root and umount it.

Has anybody else had this problem?  I searched the NeXT FAQs and 
NextAnswers but found no mention of it.

Thanks in advance.
_______________________________________________________________________
Kenny Smith                                            kenny@netcom.com
--
_______________________________________________________________________
Kenny Smith                                Software Engineer/Consultant
kenny@netcom.com                                           310/447-1190
-- 
_______________________________________________________________________
Kenny Smith                                Software Engineer/Consultant
kenny@netcom.com                                           310/447-1190
From: madler@cco.caltech.edu (Mark Adler)
Newsgroups: comp.sys.next.bugs
Subject: Re: Workspace 3.0 doesn't eject floppies
Date: 29 Dec 1992 21:47:32 GMT
Organization: California Institute of Technology, Pasadena
Distribution: comp
NNTP-Posting-Host: sandman.caltech.edu


The fix is at the anonymous ftp site next.com in pub/Binaries as
DiskEjectFix.compressed.

Mark Adler
madler@cco.caltech.edu
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer
From: mrb@earth.wustl.edu (Mike Bray)
Subject: help needed:  dbkit and/or oracle adaptor bug
Organization: Washington University, St. Louis MO
Date: Thu, 31 Dec 1992 19:23:59 GMT

DBKit - Oracle Adapter Bug

There are two, possibly related, problems with the DBDatabase delegate 
"db:notificationFrom:message:code".  I am in great need of a work around for 
problem #1.

1.  When doing a fetch, and Oracle discovers an error during the parse phase, 
db:notificationFrom:message:code generally returns the proper error code (see 
#2 below for a time when it doesn't).  If an error occurs during the fetch 
phase, no notificationFrom: message is generated, and the "db:log:" delegate 
prints the message "selectData:  succeeded".  However, no data is available, 
and dependent display objects show blanks.  This is very bad, because I need 
access to Oracle's error number.

Here's an example that works properly:

From SQL*DBA, "select garbage_column_name from dual" correctly returns:
ORA-00904:  invalid column name

Creating a DBExpression with the string "garbage_column_name" and then 
fetching it causes the notificationFrom delegate to be called, yielding the 
proper error code number, -904.

Now for the example that doesn't work right:

From SQL*DBA, "select to_date('asdf') from dual" returns:

TO_DATE('
---------
ORA-01858:  a letter was found in a date where a number was expected

This is proper behavior.  Notice that a column heading was printed, 
"TO_DATE('",
indicating that the statement parsed ok, but Oracle found an error during the 
evaluation of the statement.  This differs from the first example, where no 
column heading is printed, since it doesn't get as far through the 
parse/evaluation process.

Creating a DBExpression with the string "to_date('asdf')" and then fetching it 
DOES NOT generate a notificationFrom: event.  This is a major problem.  
Watching the results of "db:log:", a "selectData:  succeeded" message goes by, 
but the number of records fetched is zero.  Checking for zero is the only 
indication we have that an error occurred.  

How can I get the error message from Oracle?  I'm assuming that this bug is 
some problem in interpreting the error codes returned by Oracle OCI.  I really 
need some sort of work around for this problem.


2.  When attempting to insert a duplicate value into an index defined as 
unique, 
oracle version 6 generates "ORA-00001:  duplicate key in index", which is the 
proper code.  When attempted through DBKit, the notificationFrom: code is 9, 
which is not a valid V6 error number.  However, consulting the Oracle OCI 
manual, the value 9 is the value returned by Oracle Version 2!  It is still 
provided for backward compatibility in the OCI cursor data area, called the V2 
Return Code.  Is this somehow being accessed by mistake?  I can work around 
this problem, since it consistently returns the same value, but it seems that 
this might be a problem related to #1 above.

Thanks,
Mike Bray  307-332-6973 x279
From: bungi@stein.u.washington.edu (Timothy J. Wood)
Newsgroups: comp.sys.next.bugs
Subject: Bug in the realpath(3) function
Date: 27 Dec 92 10:17:53 GMT
Article-I.D.: u.1992Dec27.101753.16648
Organization: University of Washington


  I believe that the following code exhibits a bug in the NeXT
  implementation of the realpath(3) function.  I am running NS3.0.

#import <sys/param.h>
#import <stdio.h>

/*
 * usage: realpath [filelist]
 */

int main (int argc, char *argv[])
{
        char *file_name;
        char resolved_name[MAXPATHLEN];
        int i = 1;

        while (i < argc) {
                if (!realpath(argv[i], resolved_name))
                        perror(argv[i]);
                else
                        puts(resolved_name);
                i++;
        }
}


   The problem involves the clipping of the prefix of some paths, for
   example:

% cd /
% realpath tmp
rivate/tmp
% realpath /tmp
/private/tmp
%

  Notice that in the first case the leading "/p" was stripped from the
  output.  This happens in various other cases as well.
Newsgroups: comp.sys.next.bugs