HDTenEightyP/NetNews huggingface dataset:
From: coco@cbnewsl.cb.att.com (felix.lugo)
Subject: Re: Recovering ROM monitor password
Organization: AT&T
Date: Wed, 7 Oct 1992 19:00:49 GMT

In article <1992Oct7.181323.7221@news.media.mit.edu> lacsap@plethora.media.mit.edu (Pascal Chesnais) writes:
>In article <1ask66INN2ga@ustores.ustores.missouri.edu>  
>usbill@ustores.ustores.missouri.edu (Bill Canning) writes:
>> 	Put the battery in the opposite way for 2 or 3 seconds. (Or simply
>> 	leave it out for a while.)
>
>
>DO NOT DO REVERSE THE BATTERY!!!!  Name me one NeXT document
>that states this should be done.
>
>pasc

	Would you care to expand on your comment?  Name me one NeXT document
that states this should NOT be done?  8^)

--Felix

BTW,
	I've performed this procedure several times (count 7), and I've
NEVER experienced any problems with doing this.  Luck?  Maybe, but it works!

Newsgroups: comp.sys.next.misc
From: nevin@dtint.dtint.com
Subject: Appsoft Draw/Allegro Lisp - $150 ea.
Reply-To: nevin@dtint.dtint.com
Organization: Digital Technology, International
Date: Sat, 10 Oct 92 20:34:50 GMT

Appsoft Draw - $150.  Transfer the registeration.
Franz Allegro Common Lisp - $150.  Never installed.

Buyer pays shipping.

Email at: nevin@dtint.dtint.com, or call: (801) 224-7574 x220


--
NeXTmail preferred, but ONLY at my REAL email address: nevin@dtint.dtint.com

-- 
---
root	                               root@dtint.dtint.com
Digital Technology Int.                (801)226-2984	
500 W. 1200 South, Orem UT, 84057      FAX (801) 226-8438
Newsgroups: comp.sys.next.misc
From: verket@venice.sedd.trw.com (Paul Verket)
Subject: Re: Printing Book
Organization: TRW Systems Engineering & Development Division, Carson, CA
Date: Sun, 11 Oct 1992 17:26:02 GMT

In article <1992Oct9.125258.1436@ccsvax.sfasu.edu>  writes:
> I have a book I'm working on in FrameMaker. All of the pages
> are 5.5"x8.5". I would like to print it out so that instead
> of getting one page in the center of each 8.5"x11", I can
> get two of them on a sheet. I'd also like to be able to print
> them double sided.
> 
> Does anyone know of a program that could separate the
> saved PostScript from the print panel into two files that
> look like: 
> ...

I'm only a light user of Framemaker but couldn't you just define an alternate  
set of page definitions/flows and let frame do the work for you?

Paul Verket (NeXTmail ok)
From: pcnot4me@cs.montana.edu (Craig Pratt)
Newsgroups: comp.sys.next.misc
Subject: Re: How to get local man pages show up like NeXT's in DL?
Date: 9 Oct 92 02:58:02 GMT
Article-I.D.: coe.1992Oct9.025802.18740
Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717

In article <Bvu0AF.6FA@news.cso.uiuc.edu> jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
>I've installed a number of man pages for local applications in /usr/local/man
>(that's the root of the local manpage tree, that is) and built a 'whatis' file
>there describing the manpages found there.
>
>I wanted to use Digital Librarian to search through them, and I can get it to 
>build the index (3.0 DL builds the index whereas 'ixbuild' doesn't due to a bus  
>error) but the titles come out like:
>
>man1/blah.1
>man8/sample.8
>
>instead of with the descriptions built in the whatis file like the NeXT  
>manpages do:
>
>blah - prints "blah" to the screen
>sample - prints "sample" somewhere else
>
>All I'm doing to get these two examples above is clicking on the local man page  
>or ManPages (NeXT-supplied) icon and then clicking on "List Titles" (first and  
>second example, respectively).
>
>I thought it might have something to do with the dot files in  
>/NextLibrary/Documentation/ManPages so I linked all of them to my local man  
>page location and rebuilt the index from scratch.  Still, the listing comes up  
>as "man1/blah.1" lines instead of "blah - does something wonderful".
>
>What should I do to make my local man pages listing show up all pretty and nice  
>in DL like NeXT's man page listing does?
>
>Thanks.
>-- 
>-- Jeff (jeffo@uiuc.edu)
>-- NeXTmail ok

I think I tried each of these with no success as well.  What finally worked 
was copying all the index files from the /NextLibrary/Documentation/ManPages 
directory (yes, the .index.store too) to the LocalLibrary/Documentaion/ManPages
directory.  Then, just do an update on the local man pages and all will be
fine.  For some odd reason, copying everything but the .index.store didn't
do the trick.  The above did.

Anyone know why?

-- 
  Craig Pratt                                          pcnot4me@cs.montana.edu
  Montana State University, Bozeman MT            gcp1070@msu.oscs.montana.edu
   What's the difference between a used-car salesman and a computer salesman?
       A used-car salesman knows when he is lying. - Andrew Loewenstern
Xref: sparky comp.sys.next.misc:20966 comp.sys.next.software:2152
From: anwar+@cs.cmu.edu (Anwar Mohammed)
Newsgroups: comp.sys.next.misc,comp.sys.next.software
Subject: OCR Software
Date: 15 Oct 92 16:12:17 GMT
Article-I.D.: cs.Bw67oH.6yn.2
Organization: School of Computer Science, Carnegie Mellon


I know of HSD's OCR servant, but are there any other OCR 
software packages available for the NeXT?  Any shareware,
free, or PD implementations?

Thanks,
anwar
-- 
Anwar Mohammed                FREE       Graduate Student
anwar+@cs.cmu.edu              THE       School of Computer Science
Voice: +1 412 268 3043     KUWAITI       Carnegie-Mellon University
Fax:   +1 412 681 5739        POWS       Pittsburgh, PA  15213-3890
From: izumi@pinoko.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next.misc
Subject: Re: Workspace Disk Eject bug: Workaround available from NeXT
Date: 12 Oct 1992 09:17:05 GMT
Organization: University of California, Berkeley
Distribution: world
Reply-To: izumi@pinoko.berkeley.edu
NNTP-Posting-Host: moomin.berkeley.edu

In article <HARDY.92Oct9215303@golem.ps.uci.edu> hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy))  
writes:
In article <1b5874INNok@gap.caltech.edu> madler@cco.caltech.edu (Mark Adler) writes:

>
>!So, you can put it in /usr/local/bin or maybe
>!/LocalApps, but you have to have every user run it once to set the
>!Workspace default.
>
>Would launching the daemon from rc.local be a solution? (I would guess
>not, since it affects the Workspace.app --- or whatever it's called). 
>Alternatively, could one put it in every users .login? 

If DiskEjectFix.daemon is installed in /usr/local/bin, you have to
do the following for each user:

   dwrite Workspace LaunchPaths /usr/local/bin/DiskEjectFix.daemon

It appears that items specified as LaunchPaths are launched before
autolaunched apps on the dock.
You can specify multiple apps on the above dwrite by listing them
separated by a ';' as in:
   dwrite Workspace LaunchPaths path1;path2;path3

It shouldn't be hard to write a script which goes through passwd
database and do the above dwrite for each user.


--
Izumi Ohzawa             [ $BBg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: (510) 642-6440     Fax:  (510) 642-6341
Internet: izumi@pinoko.berkeley.edu (NeXT Mail OK)
ollowing for each user:

   dwrite Workspace LaunchPaths /usr/local/bin/DiskEjectFix.daemon

It appears that items specified as LaunchPaths are laun
Newsgroups: comp.sys.next.misc
From: emerson@hadrosaur.cis.ohio-state.edu (R. Matthew Emerson)
Subject: elmer fudd's been in my spell checker!
Organization: The Ohio State University Dept. of Computer and Info. Science
Date: Fri, 16 Oct 1992 05:22:04 GMT

While spellchecking a document with the word "raytracer" in it, my NeXT
suggested that the correct spelling was "raytwacer." (no kidding!)
-matt
From: anwar+@cs.cmu.edu (Anwar Mohammed)
Newsgroups: comp.sys.next.misc
Subject: Fax Cover Pages
Date: 16 Oct 92 16:36:16 GMT
Article-I.D.: cs.Bw83GH.9zq.2
Organization: School of Computer Science, Carnegie Mellon


The 2.0 documentation seems a little out of date wrt fax cover pages.
I don't want to pay $40 or whatever to get this little piece of info,
so could someone e-mail me a brief of how to set up cover pages under
3.0?

thanks,
anwar
-- 
Anwar Mohammed                FREE       Graduate Student
anwar+@cs.cmu.edu              THE       School of Computer Science
Voice: +1 412 268 3043     KUWAITI       Carnegie-Mellon University
Fax:   +1 412 681 5739        POWS       Pittsburgh, PA  15213-3890
Newsgroups: comp.sys.next.misc,comp.sys.next.marketplace,comp.soft-sys.nextstep
From: piro@bnlux1.bnl.gov (SdlS)
Subject: NeXTStep for the Iris??
Organization: Brookhaven National Laboratory, Upton, NY 11973
Date: Tue, 13 Oct 1992 23:32:42 GMT

I've been told the rumor that Silicon Graphics would be
porting/licensing NeXTStep for their platforms. Is There any truth at
it?

Regards.
Ores.
From: sowa@amdew.llnl.gov (Erik C. Sowa)
Newsgroups: comp.sys.next.misc
Subject: Re: HiddenWords, sndMucker, and artillery...
Date: 8 Oct 92 18:49:31 GMT
Organization: LLNL Chemistry and Materials Science
In-reply-to: tim@rri.UUCP's message of 8 Oct 92 13:07:03 GMT

>>>>> "Tim" == Tim Buck <tim@rri.UUCP> writes:

Tim> In article <1992Oct7.125957.12258@dartvax.dartmouth.edu> fermat@fermat.dartmouth.edu (Michael Glenn) writes:
>
>These three were recently posted to nova/sonata as .tar.Z files.  However,  
>when I try to uncompress them, it seems to go for awhile, make a file  
>about 5-6 megs big, then die for some strange (unpredictable) error.  Has  
>anyone else had any problems uncompressing these files?  Any idea what is  
>going wrong for me?
>
Tim> It sounds to me like you forgot to use BINARY when you FTPed them.

Well, I ftp'ed them in binary mode and got the same problems. Perhaps
they were uploaded by the author in ascii mode by mistake?

--
erik sowa (sowa@amdew.llnl.gov)
From: rab@cs.cmu.edu (Robert Brennan)
Newsgroups: comp.sys.next.misc
Subject: 486 NeXTStep and DOS
Date: 8 Oct 92 13:17:23 GMT
Article-I.D.: cs.Bvt0x2.Fqz.2
Organization: School of Computer Science, Carnegie Mellon

Is it possible to configure a 486 system to have partitions for both DOS  
and NeXTStep486; and at boot time either boot one or the other?  I am just  
ready to uncrate my Gateway 486 and would like to enjoy the best of both  
worlds without having two machines.  Please don't flame my DOS usage--some  
apps in the world still only run under DOS.

Thanks,
Bob Brennan
rab@cs.cmu.edu
Newsgroups: comp.sys.next.misc
From: paul@seer.demon.co.uk (Paul Lynch)
Subject: Re: BUG: Font Panel's font list is broken under 3.0
Organization: P & L Systems
Date: Sat, 10 Oct 1992 13:42:38 GMT

In article <1992Oct10.021134.23139@cbnewsl.cb.att.com>  
coco@cbnewsl.cb.att.com (felix.lugo) writes:
> BTW,	In 3.0, the system scans for new fonts whenever the Font Panel is
> ordered front;  In 2.x, this was only done the FIRST time the panel is
> brought in.  This also happens when an application uses certain Font  
methods,
> but I don't have a list handy (check TFM).
> 
On 2.1, it would rebuild /LocalLibrary/Fonts, but you had to delete the  
cache files manually first.

Paul
-- 
Paul Lynch
P & L Systems                   (NeXTmail) paul@seer.demon.co.uk
Tel: (0494)671501                      paull@cix.compulink.co.uk
Fax: (0494)680228                       76711.451@compuserve.com
Newsgroups: comp.sys.next.misc
From: Michael_Pizolato@afs.com (Michael Pizolato)
Subject: Re: A Modest Proposal
Reply-To: Michael_Pizolato@afs.com
Date: Thu, 8 Oct 1992 14:08:16 GMT

In article <tlm.718249912@scl1.al.iastate.edu> tlm@iastate.edu (Dr. T.L.  
Marchioro II) writes:
> At the risk of seeming ignorant (or, even worse, proving what 
> everyone already suspects :-) I thought I might offer a "modest
> proposal" about a subject which has been banging around  this group
> for a couple of weeks now.  Specifically, starting with Louis Mamakos'
> post about "gee, they unbundled WriteNow and then dropped the read-only
> version. What should I make my documentation in?" we now have arguments
> running about bundled versus unbundled software, the value of said
> things versus those things added to 3.0, etc.  
> 
> Personally, I find the unbundling of a read-only right now rather 
> strange, but would guess it has something to do with (1) keeping the
> 3.0 distribution smaller and (2) (from my cynical side) giving Appsoft
> a boost.  
> 
> Sadly, there's little to do about it now (except complain, which we're all
> quite good at :-) but perhaps I can offer a better solution to Louis' original
> question --- i.e. a solution with pagenumbering, headers, etc. which runs on 
> any NeXT --- which at least "calms the waters" on one aspect of this 
> question.  Why not have everyone put their documentation in troff??
> [rest deleted]

A standard that is available to everyone is absolutely necessary.  In fact, when NeXTMailing documents, we've taken to telling the print panel to save the postscript from whatever word processor we wrote the doc in (we use, roughly equally, Edit, WriteNow, and WordPerfect) and sending that in NeXTMail.  Everybody has Previewer, right? :-)

I'm sure I'm worse at troff than Dr. Marchioro is, although I'm not completely unfamailiar with that style of word processing.  But this is the 90's (though it seems that they're almost over already, since to me they started in about 1987 :-), and lots of us demand WYSIWYG.  Why doesn't someone bite the bullet and make Edit a full-function RTF word processor, with page numbering, styles (still waiting for the new Stylist beta...), and all the other goodies?  Or, better yet, take that functionality out of E


dit and write a separate RTF word processor?  Even NeXT converts their on-line docs from Frame (I think that's right) to RTF.  On the assumption that eventually no one will want paper copies of the docs (that's flame bait if I ever saw it), even page numbering doesn't matter.  As for compatibility with other systems, RTF is something of a standard, and anyway we're talking about the One True OS here, so sooner or later everyone will junk what they have now for NeXTSTEP, right? ;-)

I vote for RTF, if we can get a real RTF word processor.  I'm not a word processor guy, and I don't have the time to become one, or I'd do it myself.

Michael

--
Michael_Pizolato@afs.com
~18 kyu
Q16
NeXTMail appreciated
Newsgroups: comp.sys.next.misc
From: datec@gagme.chi.il.us (Charles Robinson)
Subject: Re: Problems with 3.0 and FrameMaker
Organization: GAGME - Public Access UNIX of Chicago, Illinois, USA, Earth
X-Newsreader: TIN [version 1.1 PL6]
Date: Sun, 11 Oct 1992 06:56:29 GMT

Randy Judd (judd@nosc.mil) wrote:
: 
: I have had 3.0 installed for about 3 weeks and I have noticed a couple of 
: problems I would like some comment on.  I have an upgraded Cube with a 600 meg
: Maxtor disk, 28 Meg of RAM, a PLI Floppy, and the NeXT CDrom drive.  I also
: have a NeXT printer.
: 
: (1)
: FrameMaker does not seem to be as robust as it was under 2.1, and has crashed
: on me 5 or 6 times out of about 4 hours of use.  Three or four of these crashes
: have come with the following error scrolling contiuously on the console
: 
: Oct  5 20:59:38 localhost WindowServer[125]: Event discarded: window 160: 
: 5 @ (2.017613e+19,4.709765e-307), 0.
:
We have also noted that FrameMaker is more fragile under v3.0
Our symptom seems to be related to processor load (for example,
if someone is using the Next printer via the net on the same
station that the Framemaker user is typing on --- then occassionally
an endless spinning disk or sometimes a "postscript error").

In the latter case, the FrameMaker software is "aware" of the problem ---
a panel comes up suggesting that you "save" your document immediately
and reload FrameMaker. With much trepidation, the first time, we did
and it recovered.

Would anyone from FrameMaker care to comment? 
Newsgroups: comp.sys.next.misc
From: roettig@ifi.unizh.ch (Thomas Roettig)
Subject: Re: ND memory question
Organization: University of Zurich, Department of Computer Science
Date: Tue, 13 Oct 1992 09:00:37 GMT

In article <1992Oct13.004840.9117@leland.Stanford.EDU> m@crito.stanford.edu (M  
Carling) writes:
> In article <1992Oct7.215224.11582@eagle.lerc.nasa.gov>  
> jim@ljkiraly.lerc.nasa.gov (L J "Jim" Kiraly) writes:
> > If I replace my 100ns NeXTDimension memory with 70ns memory, will it  
> make any  
> > difference?  e.g. Does the ND board register the memory speed, or does  
> it  
> > presume a 100ns memory interface?
> 
> It makes no difference. You can, however, use 8MB SIMMs, though this is   
> not supported by NeXT.
> 
> M Carling
> Director, Bay Area NeXT Group
> General Manager, NetForce Inc.
> --
> "High tech is potent, precise, and in the end, unbeatable. The truth is,  
> it reminds a lot of people of the way I pitch horseshoes. Would you  
> believe some of the people? Would you believe our dog? Look, I want to  
> give the high-five signal to high tech."
>                           George Bush, 4/25/89

What does it give to use 8 MB SIMMs? 8 x 8MB = 64 on the ND?

Gruss 
Tom
_____________________________________
Thomas Roettig - Forchstrasse 194
8032 Zuerich - voice +41/1 382 31 64
NeRD
Email: thomas@nice.usergroup.ethz.ch
Newsgroups: comp.sys.next.misc
From: smb3u@kiptron.psyc.virginia.edu (Steven M. Boker)
Subject: Re: Call for Volunteers *warning*
Organization: University of Virginia, Department of Psychology
Date: Thu, 15 Oct 1992 17:51:12 GMT

In article <16027@umd5.umd.edu> matthews@oberon.umd.edu (Mike Matthews) writes:
>In article <1992Oct10.235001.3605@pencom.com> ricardo@chuy (Ricardo Parada) writes:
>>I was doing part 2 and had to stop for a while and when I wanted to come  
>>back to it to finish it the app had dissappeared.  I wasted about 40 min.
>
>I ran it, and it froze in the between-section countdown.  When into gdb and
>attached the process, and it's stuck forever and ever in sigpause() so I
>don't think they're using signals very wisely.
>

Perhaps someone with more wisdom than myself can tell me why this
loop occasionally freezes for some people.  I haven't been able to
observe the phenomenon myself.

for (i = seconds; i > 0; --i) {
	minutes = i / 60;
	sprintf(tempstring, "%d:%02d", minutes, (i - (minutes * 60)));
	[[restObject theRestTextField] setStringValue:tempstring];
	NXPing();
	usleep(950000);
}

Steve Boker

-- 
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#
 #  Steven M. Boker            #          "Two's bifurcation           #
 #  boker@virginia.edu         #           but three's chaotic"        #
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#
From: jmd@cube.handheld.com (Jim De Arras)
Newsgroups: comp.sys.next.misc
Subject: Re:  Recovering ROM monitor password
Date: 12 Oct 92 03:12:00 GMT
Organization: Hand Held Products, Inc.

In article <dillon.0p24@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US  
(Matthew Dillon) writes:
> >It works, but I have heard a couple of NeXT SEs say that this will
> >void your warranty.  You never know when the diode that prevents
> >reverse current will fail and fry who knows what.
> 
>     IF there is an inline diode there preventing the reverse current it
>     will never fail.  The reverse breakdown voltage for most standard
>     diodes is a hellofalot larger then anything a battery puts out. No
>     current == no heat.  For example, diodes are often used in battery
>     charging circuits like this:
> 
> 	+12V from supply ----*DIODE*----x----> system power
> 					|
> 	+!2V from battery --------------/
> 
>     When AC is available it charges the battery.  When AC is not available
>     the battery does not try to feed the supply, the diode is reverse
>     biased by 12V when the supply DC is at 0V.	This is standard  
operation
>     and the diode will never break down for this case.

Where did you get this dangerous mis-information!!  Do not EVER, repeat, EVER  
attempt to charge a standard lithium cell.  You are looking at a nasty mess at  
BEST, if the seals blow, and a VERY REAL, blow a hole in the board and you,  
explosion if the seals fail to blow.  Lithium cells do not take a joke!

	Now, shorting
>     system power to ground is a different case... in that case the diode is
>     forward biased and dissipates W=Ix0.7 (usually) in heat. Any diode can
>     handle large forward currents for a short while, how long they last
>     depends on their current rating but usually the solder melts on the PC
>     board before the diode dies.  Diodes are usually rated 500mW, 1W, or 5W
>     the smallest being applied to glass diodes.
> 
>     I presume that NeXT is using a similar circuit to power the real time
>     clock and prevent the battery from trying to power the system +5.
> 
Let's hope not!

> 					-Matt
> 
> >MUCH safer to let the capacitor sit and discharge for a few hours on
> >its own.
> >What's your hurry?
> >:-)
> >--
> >David Lemson						     (217) 244-1205
> >University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin
> >Internet : lemson@uiuc.edu		   UUCP :...!uiucuxc!uiucux1!lemson
> >NeXTMail accepted				    BITNET : LEMSON@UIUCVMD
> 
> --
> 
>     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

(Will this topic ever end?  :-) )  I cannot let dangerous misinformation remain  
as the final word, though.  When it comes to putting batteries in ANYTHING  
backwards, "Just say no!"

Jim
Newsgroups: comp.sys.next.misc
From: sherwood@space.ualberta.ca (Sherwood Botsford)
Subject: Fat Binaries Diet?
Organization: University Of Alberta, Edmonton Canada
Date: Fri, 16 Oct 1992 16:29:21 GMT

Charles Robinson writes
> Fat binaries (like those planned for NextStep 486) should solve your  
concern.
> Basically the (incompatable) binaries are packaged together and  
NextStep
> figures out which one to load. Developers will, as I understand the  
current
> situation, be forced to compile on each native system (no cross  
compilers
> will be available for the 486).
> 

In many ways the ideal would be to sell the packages as Fat Binaries,  
but then have a standard diet command that could strip out the binaries  
that you didn't want.

Thus if you bought a 6 unit FrameMaker license, and had it on a network  
with both 486's and Classic Slabs, but no Next Risc Workstations you  
would run 
diet -d 88110 app-folder,
and diet would strip out the 88110 stuff. 
and it would go through that folder looking 
Newsgroups: comp.sys.next.misc
From: robinc@jhunix.hcf.jhu.edu (Robert Delucca)
Subject: Workspace Manager error
Organization: Johns Hopkins University - Homewood Academic Computing
Date: Sun, 11 Oct 1992 11:53:38 GMT


I increased my buffer size to 64 in the ROM monitor using sd- nbu=64. 
To do this, I entered single-user mode. I got to the ROM monitor by
doing an su to root, using the "shutdown now" command, and then "halt". At ROM
prompt I typed "p" and then changed the buffer size.

Now I can't log in as root. I get "Workspace Manager error just 
after logging in and must log in to my account. I CAN su to root.

What must I do? Rebuild system? :-(

Robert de Lucca

Followup-To: 
Distribution: 
Organization: HAC - Johns Hopkins University, Baltimore
Keywords: 


Newsgroups: comp.sys.next.misc
From: thf@zelator.in-berlin.de (Thomas Funke)
Subject: Re: How Slow is NeXTSTEP 3.0 w/ 8 megs ram?
Reply-To: thf@zelator.in-berlin.de (Thomas Funke)
Organization: NNU Corp. - NeXT is Not UN*X
Date: Fri, 9 Oct 1992 19:02:38 GMT

In article <2131@deadmin.ucsd.edu> bense@heart3.ucsd.edu (Booker C. Bense)  
writes:
> 
> - Some people have reported using as high a number as 1000. I use 64
> since the rom will only remember 12 chars. I tried 99 for a while,
                           ^^^^^^^^^^^^^^^^

Try 

	nbu=999

just leave out the 'f'. 


-- 
------------------------------------------------------------------
Thomas Funke  ** E-mail: thf@zelator.in-berlin.de
NeXT-Developer * Unix-Consultant
------------------------------------------------------------------