Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!dimacs.rutgers.edu!aramis.rutgers.edu!remus.rutgers.edu!declan From: declan@remus.rutgers.edu (Declan McCullagh/LZ) Newsgroups: comp.sys.next Subject: Re: NeXTstep 2.0 interesting features... Message-ID: Date: 17 Dec 90 05:51:03 GMT References: <368@heaven.woodside.ca.us> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 54 In article <368@heaven.woodside.ca.us>, glenn@heaven.woodside.ca.us (Glenn Reid) writes: > In article declan@remus.rutgers.edu (Declan McCullagh/LZ) writes: > > > >I finally got a chance to sit down with NeXTstep 2.0, and discovered > >some interesting things. > > >One minor squabble: one can no longer reorder the various "panels" > >in Preferences. > > Yes you can. Hold down the Control key when you drag the panels. Thanks. I thought it was possible since Preferences does have a LayoutOrder default, but I didn't see an easy way to do it. > How do you turn on banner pages? Taken from ReleaseNotes/Printing.rtf: --- npd now supports banner pages for the local NeXT 400 dpi laser printer. This works in the following way. The optional properties *BannerBefore: and/or *BannerAfter: in the printer database specify the path to a file containing a PostScript prologue for the banner. This prologue must define an operator *Banner:: printer user job date Banner 1 npd provides each of the arguments to Banner as strings. Printer will be the name of the printer, user the name of the user printing the job, job the job name, and date the current time and day. If the *BannerBefore: exists, npd will use the file it points to to print a banner before the job is started. If *BannerAfter: exists, npd will use the file it points to to print a banner after the job has completed. A default banner file can be found in /usr/lib/NextPrinter/banner.pro. The typical entry used on the NeXT 400 dpi laser printer would be to use the default banner file as *BannerAfter:. --- > Why would you want to boot with only 8MB of memory on a 16MB system, > out of curiosity? For testing purposes. Most developers have >8 MB in their NeXTs. Most users, especially new users with NeXTstations, are going to have just 8 MB in their systems. It's nice for developers to see the performance of their applications (or set of applications) on the "standard" NeXT system configuration. Declan McCullagh Independent NeXT Developer