HDTenEightyP/NetNews huggingface dataset:
From: sowa@amdew.llnl.gov (Erik C. Sowa)
Newsgroups: comp.sys.next.misc
Subject: Re: Foreign languages for BackSpace on purdue
Date: 19 Nov 92 16:48:42 GMT
Organization: LLNL Chemistry and Materials Science
In-reply-to: coco@cbnewsl.cb.att.com's message of 17 Nov 92 02:56:21 GMT

In article <5890@rosie.NeXT.COM> sam_s@NeXT.com writes:
|I just put French, German, and Kanji interfaces for BackSpace 3.0 on  

>>>>> "felix" == felix.lugo  <coco@cbnewsl.cb.att.com> writes:

felix> 	Thanks, but ...
felix> 	How about providing a "fix" <blah blah blah>

Back off, felix. BackSpace began as one of Sam's personal "fun"
projects, not an official NeXT thing. Have you forgotten the history
already? Please don't discourage him or he'll keep his cool stuff to
himself. Just because he works for NeXT does not mean he works for them
24 hours a day.

--
erik sowa (sowa@amdew.llnl.gov)
Newsgroups: comp.sys.next.misc
From: golden@cady.stanford.edu (Miriam Golden)
Subject: testing
Reply-To: golden@cady.stanford.edu
Organization: DSO, Stanford University
Distribution: na
Date: Thu, 19 Nov 92 23:54:11 GMT

Just a test.
Newsgroups: comp.sys.next.misc
From: fischer@iesd.auc.dk (Lars Peter Fischer)
Subject: Re: Ejecting a disk from Terminal?
Organization: Mathematics and Computer Science, Aalborg University
	<1992Nov21.111324.25931@pilhuhn.ka.sub.org>
Date: 23 Nov 92 21:37:17


>>>>> "Heiko" == Heiko W.Rupp (hwr@pilhuhn.ka.sub.org)

Heiko> As root do 'disk -e /dev/rfd0a'  
Heiko> Read the manual page for disk !

Or install mtools -- it comes with an "eject" program. You'll need
mtools anyway, unless you really *enjoy* waiting for your floppy
driver to get something done.

Oh, and you can get rid of the "root" business by setting a more
sensible mode on /dev/rfd0a.

/Lars
--
Lars Fischer, fischer@iesd.auc.dk | It takes an uncommon mind to think of
CS Dept., Aalborg Univ., DENMARK. | these things.  -- Calvin
From: gmiller@next.com (Gary Miller)
Newsgroups: comp.sys.next.misc
Subject: Re: Help in Edit.app -- the end of the line (command)?
Date: 16 Nov 92 22:45:08 GMT

In article <21OCT199212494808@mpx2.lampf.lanl.gov>  
silbar@mpx2.lampf.lanl.gov (Dick Silbar) writes:
> Someone yesterday asked about line numbers in Edit (and I sort of  
mis-answered
> his question, it turns out).  Today I looked at the Help package that  
comes
> with Edit (use <alt-ctl-click> to get the question-mark cursor).   
Amazing,
> there is nothing there about the line and character range panel (which  
is
> invoked by <cmd-l>, just as before in 2.x and 1.x.
> 
>    Dick Silbar

Help in Edit only covers the commands and features found in (the new in  
3.0) User Mode.  For information about additional Developer Mode commands  
such as Line Range, you can look at the online developer documentation  
(the Edit documentation is in the Development Tools target of the  
NextDeveloper bookshelf).  This bookshelf, rather than online Help, is  
where you should always look first for developer documentation.

Admittedly, this is a confusing and unfortunate state of affairs, but it's  
just symptomatic of a more general problem:  due to resource, time, and  
budget constraints, online help in 3.0 isn't available at all for  
applications in /NextDeveloper/Apps and /NextAdmin, and is available for  
only about half the applications in /NextApps (not to mention the lack of  
localized help, except in 3.0J).  Edit is the only app which -- due to its  
two modes -- has Help for only one half of itself. 

NeXT maybe could have spared itself some embarrassment and criticism by   
deciding not to release what little Help was ready for 3.0, but we felt  
that it was important to provide developers with at least some  
applications that demonstrate the Help facilities that we're finally  
beginning to provide for them.  After seeing the complete, consistent, and  
conforming Help systems that have already appeared with several 3rd-party  
3.0 apps, I believe that this was the right decision.

-Gary Miller
 NeXT Publications


Newsgroups: comp.sys.next.misc
From: sherwood@space.ualberta.ca (Sherwood Botsford)
Subject: Re: su File Viewer
Organization: University Of Alberta, Edmonton Canada
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 17 Nov 1992 19:45:25 GMT

Allen B (ab@nova.cc.purdue.edu) wrote:
: In article <BxLvqp.B5o@newcastle.ac.uk> S.A.McIntyre@durham.ac.uk writes:
: > 
: > Since I, like no doubt many others, don't like logging in as root more  
: > often than necessary...
: > 
: > Is there any way of launching a FileViewer with setuid root privs?
: > 
: > If it doesn't exist, maybe it should.
: 
: It certainly should.  I might be the numero uno complainer
: in this field.  Everytime I get a program that tells me to
: log in as root to install it, it drives me crazy.  Since I
: actually have installed >every< program in the Archives
: on my machine at one time or another, this comes up a lot. :-)
: 

While at times useful, it's not necessary.  Open a Stuart window,
su to root then type
/NextAdmin/Installer.app/Installer &
Installer comes up, as root, and you carry on.  It is a nuisance.

This is why I prefer programs that are tar.Z's or zips to those that
are packages.  I can start one or more gnutars or unzips and stuff in
background.  Installer has a raft of mouse clicks and dreck.
   
--
=> Sherwood Botsford                   sherwood@space.ualberta.ca <= 
=> University of Alberta         Lab Manager, Space Physics Group <=         
=> tel:403 492-3713                             fax: 403 492-4256 <=         
Newsgroups: comp.sys.next.misc
From: vhs@rhein-main.de (Volker Herminghaus-Shirai)
Subject: Re: su File Viewer
Reply-To: vhs@rhein-main.de
Date: Wed, 18 Nov 92 20:57:03 GMT

In article <1992Nov17.001020.18066@athena.mit.edu> robert@amo.mit.edu(Robert Lutwak)  
writes:
> In article <BxtDwG.4L7@mentor.cc.purdue.edu> ab@nova.cc.purdue.edu (Allen  
> B) writes:
> > In article <BxLvqp.B5o@newcastle.ac.uk> S.A.McIntyre@durham.ac.uk  
> writes:
> > > 
> > > Is there any way of launching a FileViewer with setuid root privs?
> > > 
> > > If it doesn't exist, maybe it should.
> > 
> > It certainly should. 
> 
> O.K. I'm going to throw a little TNT onto this fire:
> 
> Disclaimer:  I am not responsible for anything you type into your machine.
> 
> Try this (PLEASE do not do this as root):
> 
> Type into a terminal window:
> 
> /usr/lib/NextStep/Workspace.app/WM.app/WM -NXAutoLaunch YES &
> 
> I clipped this from a "ps ax" and added the "&" so that I could keep my  
> terminal window useful.
> 
> This creates a new workspace on top of the old one (move it and see).
> Except for moving or copying from the old workspace to the new one,  
> everything seems to work fine (you can still create multiple viewers,  
> etc.).
> 
> So far, I can get out of it by choosing "logout" from either WorkSpace's  
> menu, which generates an error and logs you off ungracefully, or by doing  
> a "kill PID" which generates an error and logs you off ungracefully.
> Neither is satisfactory.
> 
> I checked the online docs with DL and found no mention of command-line  
> arguments for WM.  Maybe there's some argument which will make it exit  
> gracefully when you hit logout without killing everything in sight.
> 
> Maybe now that I've got people around the planet crashing their  
> Workspaces, someone who really knows will pipe up.  :-)

The next obvious thing to try would be to `kill -HUP <PID>` it.
I'm not going to do it, though (got same serious work to do).

--
Volker Herminghaus-Shirai (vhs@rhein-main.de)

Computer industry: Industry in which the number of units sold of any
given product is inversely proportional to its technical excellence.
See also: MS-DOS, Windows, IBM-PC, X, QWERTY,
          80x86, TrueType, Survival of the shittest.
Newsgroups: comp.sys.next.misc
From: matt%mattcube@concert.net (Matthew M. Stecker)
Subject: Re: Stolen NeXT Station Color
Reply-To: matt%mattcube@concert.net
Organization: UNC School of Law, CC for NeXT Computer, Inc.
Date: Tue, 17 Nov 1992 14:43:53 GMT


[ response to all of the talk about what a security breach it is that
  someone who steals a machine can, given the right knowledge get
  access to the system's data ]

All of this discussion boils down to one simple truth - namely that
once a culprit has physical access to the machine, they can 
reset the ROM, get access to root, and get at the system's data.

Even if the system were structured in such a way that this were
impossible, (say a hardwired ROM password that was unchangeable), 
the culprit can always remove the SCSI drive and mount it up on 
a machine that he does control, thereby getting at the system's data.

I was just wondering if this 'fault' (and it's not necessarily a fault -
consider that for every thief that uses this process, probably hundreds
of folks legitimately forget their passwords and need these procedures)
could be alleviated by some sort of password lock built into the 
hardware of the drive itself - that is, the drive itself would not
become active, no matter what system it was attached to, unless it 
received a password at boot time.  The password would be hard-wired
into the drive (so you couldn't reset it by killing the battery), and
could be retrieved only by calling the drive manufacturer who would
give it away in the same manner that banks give out PIN numbers - they
would only mail it to the address on file.

The system would be set up to prompt for this at boot time, so that 
it couldn't be discovered by poking around the system.  I suppose that
this would work like the security code on my car radio - if the system
loses power, it needs an id code to be useful again.  

I realize that this would be a minor inconvenience, but considering that
most (many? I have no real data on this) people keep their machines
running continuously, it shouldn't pose too much of a problem - it also
doesn't seem like it'd be very difficult to implement.

This might not make sense for many sites, but for those who hold extremely
sensitive data, it could provide some peace of mind.

Just an idea,

matthew

-- 
matt stecker			|	This is my NeXT Computer
NeXT Campus Consultant,		|	There are many like it,
UNC School of Law		|	but this one is mine.

Newsgroups: comp.sys.next.misc
From: Young Yang Boy
Subject: How to configure system
Originator: boyiny@kovalevskaya
Reply-To: yangboy@math.ntu.edu.tw
Organization: MIT, Department of Mathematics
Date: Sat, 21 Nov 92 03:51:19 GMT


Greetings!
	I have a problem.  Having purchased a hard disk some time ago,
I have been meaning to upgrade to NeXT Step 3.0.  Well, I finally took the
trouble of having it installed on my external disk.

	Now the question is, how do I switch between booting from the
in-built drive (SCSI #0) and the external drive (SCSI #1)?

	I understand that there is some kind of boot-time switch where
one can change the parameters so as to boot from a different drive?

	Any information will be appreciated.


Newsgroups: comp.sys.next.misc
From: dan@ennex1.eng.utsa.edu (Daniel Shelton)
Subject: UTSANUG meeting
Reply-To: dan@ennex1.eng.utsa.edu (Daniel Shelton)
Organization: Univ of Texas at San Antonio
Date: Mon, 23 Nov 1992 01:15:20 GMT

All and everyone,

	The University of Texas at San Antonio NeXT Users Group will be
having a meeting on Friday, the 4th of December, at 6:30 p.m.  The meeting
will be held at UTSA, exact location to be determined.  Demonstrations
will include :

	1. co-Xist : X-windows for the NeXT

	2. Knowledge Tool : a multimedia presentation program that is
still in beta

	3. ObjectWorks\Smalltalk and VisualWorks from ParcPlace Systems -
a pure OO development environment which is being ported to the NeXT

Also, we will have four NeXT machines for people to "play" on.  There will
be food and drink afterwards.  

Note : This and all meetings are informal so people wearing suits and ties
will be shot.

For additional information, send e-mail to Daniel Shelton
(dan@ennex1.eng.utsa.edu).
From: milionis@shannon.ee.wits.ac.za (Taki Milionis)
Newsgroups: comp.sys.next.misc
Subject: Upgrade from 1.0 to 3.0 - It worked ;-)
Keywords: upgrade
Date: 19 Nov 92 06:52:00 GMT
Organization: Electrical Engineering, University of the Witwatersrand

This is just a note to thank all those people who did e-mail me with help
in upgrading 1.0 to 3.0 NextStep.

My problem was, I did not have a stiffy drive and I had to use the OD to get
the CD-ROM working. The solution has been posted before... 

\usr\lib\disk -B \usr\standalone\boot.cdrom \dev\rod0a

will place the new boot blocks onto the OD which, when booted will allow the
CD-ROM to boot.

BEWARE however, I remembered too late that the -B option in the `disk' 
command does a BULK ERASE (AAARRRGGHH!) under version 1.0 NextStep. In this
version, \usr\lib\disk -b \rod0a will move the \usr\standalone\boot onto
the boot block. I have seen mention of this problem before but I think it 
should be FAQ. 
Never before has RTFM meant so much to me (about 2 weeks ;-)). I must
have diagnosed every other potential problem on my NeXT but this one!
					      
Cheers,

-- 
                         *    H     * . 
Taki Milionis        . ( .   HHH  .   ___  milionis@odie.ee.wits.ac.za
Network Manager          ___  H ____  |.|  (..011) 716-5423
Wits Elec Eng        O __|.|_ H |. | _|.| "I still put my panties on 
Joburg               | |.|..| H | .| | .|    one leg at a time ..." 
Newsgroups: comp.sys.next.misc
From: nevin@dtint.dtint.com
Subject: Re: NeXT Trinitron Monitor
Reply-To: nevin@dtint.dtint.com
Organization: Digital Technology, International
Date: Mon, 23 Nov 92 01:15:46 GMT

In article <1992Nov22.053020.29596@cs.yale.edu> nathan@laplace.csb.yale.edu  
(Nathan F. Janette) writes:
> In article <1992Nov22.000006.1888@leland.Stanford.EDU>  
> m@crito.stanford.edu (M Carling) writes:
> > In article <1992Nov19.080022.24667@cs.yale.edu>  
> > nathan@laplace.csb.yale.edu (Nathan F. Janette) writes:
> > > Support for 1024x768 on a 15" color display, as I imagine
> > > NS486 will include, would live up to that claim of a reasonable
> > > price even better.  Now when will NeXT get around to supporting
> > > it for their own hardware?  Not to mention the lack of 1280x1024
> > > for 21" displays...
> > 
> > NeXTSTEP 486 supports resolutions ranging from 600x400 to 1280x1024.
> 
> Then there will be no excuse for NeXTstep 3.1 to not do the same ;-)
> 
> --
> Nathan Janette
> PPP link from hilbert.csb.yale.edu
> 
> Please reply to: nathan@laplace.csb.yale.edu (NeXT)



NeXTSTEP 3.0 does it today.  It's adjustable/available through (if I remember  
correctly) the defaults database.  I've played with it and "shrunk" my  
NeXTSTEP-recognized screen size before (to recover an off-screen window, before  
I got VirtSpace).

It's NeXT's hardware that's currently "locked" into the maximum of 1120 X 832.

--
Nevin Pratt, Digital Technology, Int'l    Orem, Ut
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: gbrown@raven.ctr.columbia.edu (Glenn Brown)
Subject: Re: MATLAB (the missing piece)
Organization: J. Random Misconfigured Site
Date: Wed, 18 Nov 1992 03:49:22 GMT
Reply-To: gbrown@raven.ctr.columbia.edu (Glenn Brown)
X-Posted-From: raven.ctr.columbia.edu
NNTP-Posting-Host: sol.ctr.columbia.edu


> What I'm trying to say here is that the glass is not half empty, it's
> half full.

	Agreed... and filling... Slowly.

>  As an engineering/scientific user and developer, I can
> testify that the scientific and engineering community would prefer to
> use and develop under NeXTSTEP rather than other environments; however,
> the X window "inertia" is fairly difficult to overcome.  This must
> be countered by persistence.

	And NeXTSTEP ported to those machines that are already on  
scientists desktops.  Suns, especially.
	If NeXTSTEP itself was developed on Sun3's before the first NeXT  
prototypes (as one source has told me), then this is not a giant leap.  Or  
even a small one.  But I'm sure the guys at NeXT are all way ahead of us  
already on this score.  They're no bozo's.

--Glenn
Newsgroups: comp.sys.next.misc
From: corson@eng.umd.edu (Mathew Scott Corson)
Subject: NeXTSTEP486/Cost?
Originator: corson@csplserv.eng.umd.edu
Organization: College of Engineering, Maryversity von Uniland, College Park
Date: Mon, 23 Nov 1992 22:04:02 GMT


Does anyone know the expected cost of NeXTSTEP486 ?

Thanks...

-Scott
 
Xref: sparky comp.sys.next.misc:22255 comp.sys.next.hardware:2792
From: izumi@pinoko.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next.misc,comp.sys.next.hardware
Subject: Re: NeXT DSP memory
Date: 24 Nov 1992 02:37:09 GMT
Organization: University of California, Berkeley
Distribution: world
Reply-To: izumi@pinoko.berkeley.edu
NNTP-Posting-Host: moica.berkeley.edu

In article <1992Nov23.225548.16414@ringer.cs.utsa.edu> dan@ennex1.eng.utsa.edu (Daniel Shelton)  
writes:
>In article <1992Nov23.172959.3855@pencom.com> ph@pencom.com (Patrick  
>Hester) writes:
>> Does anyone know about adding DSP memory to a (non-turbo) 68040 cube?
>> I've checked the FAQ but no mention of DSP memory.
>> I'd like to pump up the DSP so I can have lots of synthesis going on at
>> the same time.
>> So if anyone knows how much memory can be added, what kind, where to
>> get it, prices or any other clues, please let me know. Also if you
>> happen to have an idea how extra memory will change the limits...
>
> You can add another 32K of memory, they will say 96K, but the DSP
>memory is 24 bits wide so it is only 32K, to the DSP via a SIMM module
>from NeXT for $195.  Call them at 1-800-848-NeXT for details. Part
>#N7013. 

It will NOT ADD 32kwords of memory -- N7013 will REPLACE the existing
8kwords of DSP RAM with 32kwords on a SIMM.  So you end up with the
total of 32kwords (96kbytes) after installation of N7013, not
40kwords = 8 (existing) + 32 (N7013).  I suppose the 8k on the CPU
board is disabled.


Also, current 3.0 MusicKit from CCRMA will NOT use the expanded DSP RAM
automatically.  It is hardcoded for 8kwords (It has always been for
previous releases).  Therefore, installing N7013 will not automatically
increase synthesis capacity of a NeXT.   I believe you must obtain the
MusicKit sources and change the hardcoded DSP RAM size (8k) and re-make
the kit.  Doc mentions that auto-detection of DSP RAM size is an item
on the to-do list for future, but not yet supported.

It is pretty simple to determine whether a NeXT has 8k or 32k of DSP
RAM at run time, but you need to run a DSP program to do this.
See DSPMemorySize.tar.Z on the archives.

--
Izumi Ohzawa             [ $@Bg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: (510) 642-6440     Fax:  (510) 642-3323
Internet: izumi@pinoko.berkeley.edu (NeXT Mail OK)
Newsgroups: comp.sys.next.misc
From: cgb@count0.cmhnet.org  (Charles G. Bennett)
Subject: Re: The Electronic AppWrapper
Reply-To: cgb@count0.cmhnet.org
Organization: BenaTong
Date: Sat, 14 Nov 1992 17:18:42 GMT

In article <1992Nov10.160431.24326@ifi.unizh.ch> roettig@ifi.unizh.ch (Thomas  
Roettig) writes:
> I somehow lost the email address of Richard Carey of Paget to ask him  
directly.
> Can somebody send it to me please?
> Did anybody get The Electronic AppWrapper yet?
> --
> 
> Gruss 
> Tom
> _____________________________________
> Thomas Roettig
> thomas@nice.usergroup.ethz.ch


try aw@paget.com......
-- 
Chuck Bennett, BenaTong Consulting
Harem Security (UNIX Consulting :-) )
cgb@count0.cmhnet.org
From: wave@media.mit.edu (Michael B. Johnson)
Newsgroups: comp.sys.next.misc
Subject: wherefore the apocryphal Icon doc?
Date: 22 Nov 92 20:00:55 GMT
Followup-To: wave@media.mit.edu
Organization: MIT Media Laboratory

Well, since it Appsoft Image isn't going to ship for a few more weeks still,
and I have a demo to give in two weeks, I've gotten a copy of the patched
Icon from a friend for 3.0.  Problem is, everything I ever figured out 
about how to to use the damn program has disappeared from my head.  I
just checked for Icon in the latest set of FAQs using DL, I downloaded
00ls-lr from both sonata and orst and grep'ed for icon, with no luck.  I'm
sure I remember one or two notes people had written (for some user group?)
about tips and tricks for using icon...

Anyway, any help would be appreciated.  
-- 

-->  Michael B. Johnson
-->  MIT Media Lab      --  Computer Graphics & Animation Group
-->  (617) 253-0663     --  wave@media-lab.media.mit.edu
Newsgroups: comp.sys.next.misc
From: Monty Solomon <monty%roscom@think.com>
Subject: Re: Pwerbook as a window on a NeXT
Reply-To: Monty Solomon <roscom!monty@think.com>
Organization: Proponent
Date: Fri, 20 Nov 1992 10:13:44 GMT

In article <1992Nov14.232913.17904@seas.smu.edu> dleon@seas.smu.edu (David  
Leon) writes:
> Does anyone out there have the number for Cayman?  If they ported directly to
> NeXTSTEP, then I could think of some really nifty things...such as builing a
> cheapo cat-mac and using the NeXT as the server/monitor/printer...

Cayman Systems Inc.
26 Landsdowne Street
Cambridge MA  02139
617 494 1999
Fax 617 494 5167
support@cayman.com



-- 
# Monty Solomon / PO Box 2486 / Framingham, MA  01701-0405
# monty%roscom@think.com
Newsgroups: comp.sys.next.misc
From: gvh@metrosoft.com (Gordon Van Huizen)
Subject: Re: 3.0 Mac Floppy Copy Less Than Useful
Reply-To: gvh@metrosoft.com (Gordon Van Huizen)
Organization: Metrosoft
Date: Sun, 22 Nov 1992 20:31:23 GMT

In article <1992Nov22.035136.15646@trilithon.mpk.ca.us>  
henry@trilithon.mpk.ca.us (Henry McGilton) writes:
> 
> In 3.0, I notice that the ``system'' seems to look only at the Data
> Fork of Macintosh files.  This is less than useful for Macintosh
> format Type 1 font files, which in almost all cases have their
> useful data in the resource fork of the file.
> 
> Changing directory to the Macintosh floppy and doing ls -1 shows
> the Type 1 font to be of length zero, when in fact there's plenty
> of font data hiding in there somewhere.
> 
> So, one of the major potential uses for 3.0 reading Macintosh floppy
> disks is nullified by this behavior.  I've looked in the 3.0 release
> notes and didn't see anything mentioned about 3.0 and Macintsoh
> floppy disks, except for the watning about writing lots of small
> files.
> 
> Anybody have any great ideas how to deal with these issues in 3.0?
> I hope FloppyWorks is OK on 3.0, because I can't seem to do without
> using FloppyWorks.
> 

There is a way to read it, which I've posted before. You can open() the  
resource fork of a data file 'foo' by opening  'foo.#rsrc#'. Note that this has  
to happen while the Mac filesystem is mounted. Copying via the file viewer to a  
NeXT filesystem loses the resource fork. You can however use cp from the  
command line to copy the resource fork onto a NeXT filesystem.

The Font Installer and Sound Importer of MetroTools take this into account and  
look for the ".#rsrc#" file (resource fork). They also look for resource forks  
in MacBinary files (useful for Mac fonts downloaded straight to a NeXT from an  
online service) and for "flat" resource forks brought over by FloppyWorks.

FloppyWorks runs OK under 3.0, but I understand it is no longer supported by  
DIT (or at least their desire is to phase it out). If you ever install  
FloppyWorks under 3.0 (or a system that is upgraded to 3.0), beware that you  
will have to remove the macintosh.fs from /usr/fileystems before you can  
directly mount a floppy via NeXTSTEP.

As an aside we have recently modified Font Installer to generate ascii-encoded  
Type 1 fonts from binary-encoded ones, and enhanced its conversion  
capabilities. It now successfully converts 98% of all 'unusable' fonts we have  
ever been sent.

We also have our NiteLite screen saver module of MetroTools running while the  
Login Window is up, in house. We will be releasing the upgrade soon.

-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------
Newsgroups: comp.sys.next.misc