|
|
| Home > Computers and Hardware > |
The NeXT-FAQ (Frequently asked questions) |
Section 8 of 8 - Prev - Next
All sections - 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8
17a18
> esac
21c22
< PRSERVER="/usr/lib/NextPrinter/Server/prserver -p \$PRINTER -n \$USER
-h HOST -f -"
---
> PRSERVER="/usr/lib/NextPrinter/Server/prserver -p \$PRINTER -n \$USER
-h \$HOST -f -"
27c28
< psdf) psbad \$FILTER \$PRINTER \$USER \$HOST | \$PRSERVER;;
---
> psdf) dvips -f -D 400 -r | \$PRSERVER ;;
8.11 How to get TeX with NEXTSTEP to make proper fonts for a 600 dpi
laserwriter?
600dpi TeX fonts TeX, 600dpi
If you upgrade to a 600 dpi laserwriter then the version of TeX that
ships with NEXTSTEP (either 2.X or 3.0) does not know about 600 dpi
fonts, i.e. does not know how to make them and will instead use scaled
400 dpi ones (which look significantly worse at 600 dpi than they do
at 400 dpi). Some simple modifications to a few Metafont files and
rebuilding the metafont bases are all that is needed. What to do to
get the 600 dpi stuff working is as follows:
* Edit /usr/lib/mf/inputs/next.mf and add a laserjetIV mode. Simply
copy the entire imagen mode, change the name to laserjetIV, and
change the pixels_per_inch to 600. Save the changed file.
* Build a new mf.base file by executing the following commands:
inimf "plain; input next; dump"
(as superuser): cp plain.base /usr/lib/mf/bases/mf.base
* Edit /usr/lib/tex/ps/config.ps and change the `D 400' line to `D
600' (you may have `D 300' or something else if you've set up a
different printer.)
* Edit /usr/bin/MakeTeXPK (as superuser), adding the lines
elif test $BDPI = 600
then
MODE=laserjetIV
right before the second `else' in the file.
That should do it! You might have to (depending on how you configure
NEXTSTEP for the LaserJet IV) select `custom resolution' and set the
gadget to 600 in the TeXview print panel, and save Preferences. These
instructions are written for an HP Laserjet IV, but they should also
work for a QMS printer just fine.
Finally, if you have one of these printers and work in a "mixed"
environment with perhaps 400 dpi and/or 300 dpi printers that you also
print to on a regular basis then you might want to consider getting
Type 1 PS version of the Computer Modern fonts instead. They obviate
the need for the instructions above, and the savings in disc space
will be considerable since having printer fonts for several printers
takes lots of room, and the file sizes for 600 dpi are quite large
(the files grow roughly as D logD, where D is the resolution). These
fonts are made by Blue Sky Research, and work beautifully. Y&Y
software is a reseller for BSR and sells a "NEXTSTEP specific" version
of them which comes with appropriate instructions and installation
scripts.
8.12 How to get printer description files (PPD)?
PPD, where? printer description files, PPD
Adobe has a mail server and ftp site where you can get .PPD files.
They are:
ps-file-server@adobe.com (put "send help" in the mail body)
ftp.mv.us.adobe.com
8.13 What are the Canon part numbers for ink cartridges equivalent to those
NeXT's Color Printer uses?
ink cartridge, Canon Canon, ink cartridge
Part Numbers are:
Red: BJI-643 M
Yellow: BJI-643 Y
Blue: BJI-643 C
Black: BJI-643 Bk
8.14 JetPilot does not work with my JetDirect box, why?
JetPilot, JetDirect JetDirect, JetPilot eXTRAPRINT
It seems, that there is a bug in the /etc/rc-script. The bootpd is
given with to arguments -a -f, which are not available for the bootpd
under 3.3.
Make an entry in /etc/bootptab like this:
\#
\# host htype haddr iaddr bootfile
\#
printer 1 XX:XX:XX:XX:XX:XX XXX.XXX.XXX.XXX
where
* host: your given hostname for the printer (eg. picasso)
* haddr: The Ethernet hardware address (Can be seen, if you press
the TEST-Key on your JetDirect box.
* iaddr: Is the hostaddress for the printer (eg. 192.42.172.1)
Entries have to be done also in the Netinfo-database. It's like adding
a new host.
Insert the following line to your etc/rc.local script:
\#
\# Starting JetDirect-Printer configuration
\#
fbshow -B -I "Starting Printer initialization" -z 92
/usr/etc/bootpd -d /etc/bootptab >/dev/console 2>\&1
There is an additional FAQ available at:
ftp://ftp.gscorp.com/pub/support/HP_JetDirect_Configuration.rtfd.tar.g
z
8.15 powering down NeXTprinter during bootup, printer still works
power down, printer printer, printer down
Type the following to your rc.local.
\#turn off NeXT laser printer.
fbshow -B -I "Powering off NeXTprinter" -z 95
if [ -f /usr/etc/nppower ]; then
sleep 3
/usr/etc/nppower off
(echo 'powering off NeXTprinter') >/dev/console
fi
This works fine... the printer powers down immediately, and is
available for any app which wants it.
8.16 How to set up the HP LaserJet 4M?
HP Laserjet 4M
I solved the problem by building a serial cable based upon the pinouts
supplied by HP in their manual. Please note that the LJIII cable does
not work. In particular, pin 1 from the DIN plug must be connected to
pin 6 of the DB25. I used 38500 bps on both sides, and the 600 dpi
ppd.
Emulex offers the NETJet network interface which speaks lpd protocol,
unlike the HP unit.
8.17 Laserwriter NTX & NEXTSTEP
Laserwriter NTX
This are the pin assignments.
Eight-pin mini DIN-8 RS-422 Port
Pin Signal Description
1,3 SG Signal Ground
4 TxD+ Transmit Data +
5 TxD- Transmit Data -
8 RxD+ Receive Data +
9 RxD- Receive Data -
IBM-compatible DB-25 Plug LaserWriter DB-25 Plug
Signal Pin Pin Signal
Shield 1 ............ 1 Shield
TxD 2 ............ 3 RxD
RxD 3 ............ 2 TxD
RTS 4 ............ 4 RTS
CTS 5 ............ 5 CTS
DSR 6 ............ 8 DCD
GND 7 ............ 7 GND
............ 20 DTR
The other aspect is to set the DIP switch on the printer. Here are the
DIP switch settings:
Switch 1 Switch 2 Meaning
UP UP LocalTalk---RS-232 port disabled
DOWN UP Serial ports at 1200 Baud
UP DOWN Serial ports at 9600 Baud
DOWN DOWN RS-232 at 9600 Baud; RS-422 at 0 Baud
Switches 3 and 4 can probably be ignored---they're for strange stuff
like Diablo 630 and HP LaserJet emulation modes.
Switch 5 Switch 6 Meaning
DOWN DOWN XON/XOFF
UP UP XON/XOFF
DOWN UP ETX/ACK
UP DOWN DSR
8.18 Problems with gray levels in printout
gray levels color space PS Level2
If you have problems with your shades of gray (e.g. light gray is
indistinguishable from white) this might be well a problem in the
Level2 Color Space calibration of your printer.
To ensure, it's a problem of your printer (and not a problem of the
printer driver or PPD file) try the following:
* Save a printout to a file
* Edit the following line in your printout file:
/\_NXLevel2 systemdict/languagelevel known {languagelevel 2 ge}{false}i
felse \_\_NXdef
to:
/\_NXLevel2 false \_\_NXdef
* Send the modified file directly to the printer using the
commandline command lpr.
If you still have problem with the shades of gray, the printer
driver/PPD file is probably broken, otherwise your printer is broken,
which means he has problems with the Level2 color space calibration
(The given correction turns PS Level2 off).
8.19 Can't print using additional fonts
printer, fonts
In rare circumstances some printers refuse to print, if they don't
recognize a font. In these cases add the _nxfinal form property to the
printer's property list with NetInfo.
9 OBSOLETE BUT STILL INTERESTING?
This chapter contains information covered in the early days of the
FAQs. It is not updated anymore. Note that with new releases of
NEXTSTEP and OpenStep some information might still be useful to those,
who e.g. didn't update.
9.1 Where can I get NeXT paraphernalia?
Paraphernalia NeXT paraphernalia are no longer available. Let's stop
reading 1 minute and remember the times ..... Thanks!
9.2 Is there any way to change the text in the title bar of a terminal window?
There is no way of changing the title bar of a Terminal.app window in
2.x; in 3.x there is. Check Preferences (Title Bar): set CustomTitle,
type in the title, and hit CR (or Set Window) and voila!
[From: andre@ramsey.cs.laurentian.ca (Andre Roberge)]
Actually, there is a way to change the title bar of a Terminal window
in 2.x (at least in 2.1 which is what I am using). It is somewhat
limited but it might be useful to some.
The trick is to make a symbolic link between /bin/csh (or whichever
shell one wishes to use) and a file in / named
"Whatever_you_want_to_appear_in_the_title_bar". Then select this new
"shell" in the terminal preference and, voila!, you'll have your
terminal window with /Whatever_you..... in the title bar.
You can edit Stuart's titlebar interactively from the "Window..."
Inspector (Command-3).
Stuart provides emulation of certain Operating System Command (OSC)
sequences which can be used to modify the titlebar under subprocess
control.
Stuart can change the title of the current window from the command
line. In Stuart is possible to get more descriptive titles by linking
/usr/ucb/rsh to /usr/hosts/. Then by adding /usr/hosts to your Stuart
ShellPath you can then get the hostname into the title bar:
$ dwrite StuartShellPaths :/usr/hosts
You should then type in the hostname as the shell to invoke (disable
the "Shell reads .login file" for this. You can also add hosts to your
.Stuartrc file:
Shell=golem.ps.uci.edu
SourceDotLogin=NO
WinLocX=545
WinLocY=563
Lines=24
|
WinLocX=76
WinLocY=833
For the localhost, link /bin/csh to /usr/hosts/, or even better
/usr/local/bin/tcsh instead of using rsh.
[From: Garance A Drosehn ]
For what it's worth, I do this with a script called "telnet_to" and a
(bash) function called "telnet_window". The function simply does a
local soil_pars="-Lines 32 -Keypad YES -Reverse \
YES -Strict YES -TestExit YES";
soil -Shell "telnet_to $1" $soil_pars
and the script is just:
#!bin/sh
/usr/ucb/telnet $*
echo ' '
echo ' --> telnet exited, press enter to close window.'
read -r Waste_Var
exit 0
This has a number of advantages, not the least of which being that I
can pop up a "telnet_window" to anywhere. I don't have to create links
for each host (though I do create aliases for the most common hosts),
and I can type "telnet_window" (or, e.g., "tel_aix") as a unix
command.
Also, if I lose the connection suddenly then the window stays around
until I get a chance to see what happened. I use telnet instead of rsh
because I generally connect to hosts which won't accept rsh's.
9.3 I can't get my pictures in OmniWeb
OmniWeb You have to install the OmniImage.service in your
/Library/Services or /LocalLibrary/Services (This is also a nice way
to get pictures converted in other applications as well.
You can ftp this from ftp.informatik.uni-muenchen.de
9.4 How do I remap the and | keys on my keyboard?
Keyboard
NeXT introduced a new keyboard configuration with the 040 products.
The
| keys which had been located on the main keyboard was moved to the
numeric keypad. Many users have since complained about it, and a work
around is to remap these keys using the demo application Keyboard
(/NextDeveloper/Demos/Keyboard), Mike Carlton's keyboardfix program:
ftp.cs.orst.edu:/pub/next/sources/next-interface/keyboardfix.tar.Z
...which lets you put these keys on shift-return or shift-delete. One
can hope that there will be a choice of keyboards in the future.
9.5 How do I stop NeXTMail/Sendmail adding &Mcirc;s onto the end of lines?
Sendmail
In /etc/sendmail.cf make this change:
[old code]
##### UUCP Mailer specification
#####
Muucp, P=/usr/bin/uux, F=msDFMhuU, S=13, R=23,
[new code]
##### UUCP Mailer specification
#####
Muucp, P=/usr/bin/uux, F=msDFMhuU, S=13, R=23, E=\n,
This has been fixed in 3.1, and the default mailhost sendmail is UUCP
oriented.
9.6 Why does NEXTSTEP 1.0 hang a few seconds after attempting to boot?
Boot hang, NS1.0
Release 1.0 contains a bug that can corrupt the kernel /odmach if a
user attempts to launch /odmach from the browser. The solution is to
copy a clean /odmach from another NeXT system. Be sure to change the
permissions of the newly installed /odmach to remove execute
permissions to prevent future occurrences of the same problem. Release
1.0a and beyond do not have this problem.
It is possible for the sdmach to get corrupted in the same way. Boot
from the OD, copy an uncorrupted version of the kernel to the hard
disk, and remove the execute bits from sdmach.
9.7 Modem hangs under NS2.0 by incoming calls
modem calls, incoming
There is a bug in the serial driver which causes getty to get stuck.
The situation arises after a successful uucico connection, subsequent
connections via modem will get a connection with the modem, but no
login prompt.
This is caused by getty hanging. A simple work around is to have a
process run in cron to reset the getty every 15 minutes:
#! /bin/sh -u
PIDS=`ps -ax | bm getty | grep -v bm | awk '{print $1}'`
kill -TERM $PIDS
Of course trying to connect when the script is running will not allow
you to connect, try again a minute later. This fix will not affect
on-going UUCP or interactive connections. This will probably be fixed
in the next kernel release.
This bug is corrected in NEXTSTEP 2.1 and later releases.
9.8 NS2.0 doesn't recognize /LocalApps path
/LocalApps, NS2.0
Workspace has its own internal application path. In 2.0 /LocalApps was
omitted. Improv needs to have /LocalApps in the Workspace path if you
have Improve installed in /LocalApps. The work around in 2.0 only is:
dwrite Workspace ApplicationPaths "~/Apps:/LocalApps:/NextApps: \
/NextDeveloper/Apps:/NextAdmin:/NextDeveloper/Demos"
This bug is corrected in NEXTSTEP 2.1 and later releases.
_________________________________________________________________
This document was converted from LaTeX using Karl Ewald's latex2html.
--
--
Bernhard Scholz (IRC: Boerny)
scholzb@pst.informatik.uni-muenchen.de http://peanuts.leo.org/
scholz@ve1.rm.op.dlr.de http://www.leo.org/~scholz/
Section 8 of 8 - Prev - Next
All sections - 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8
| Back to category Computers and Hardware - Use Smart Search |
| Home - Smart Search - About the project - Feedback |
© allanswers.org | Terms of use