I wrote: >Yes, I had the same problems. I performed a dir > decw$terminal:menu*.pcf > >on VMS and found several files:
This was a typo. Should have been "dir decw$xterminal_font:*.pcf" JS wrote: > Think I found out why the fonts I copied didn't work. They're > not pcf fonts. > Mine look like this: > > -rw-r--r-- 1 u752359 mkgroup 4117 Jan 23 13:58 > COURIER10_100DPI.DECW$FONT > -rw-r--r-- 1 u752359 mkgroup 4370 Jan 23 13:58 > COURIER12_100DPI.DECW$FONT > -rw-r--r-- 1 u752359 mkgroup 4786 Jan 23 13:58 > COURIER14_100DPI.DECW$FONT > -rw-r--r-- 1 u752359 mkgroup 6227 Jan 23 13:58 > COURIER18_100DPI.DECW$FONT > -rw-r--r-- 1 u752359 mkgroup 8906 Jan 23 13:58 > COURIER24_100DPI.DECW$FONT > -rw-r--r-- 1 u752359 mkgroup 3435 Jan 23 13:58 > COURIER8_100DPI.DECW$FONT > > I did a search on VMS from root (I think it was root) on the > pcf files but > it didn't come up with anything: > > ISIS-WORK>DIRECTORY [...]*.pcf > %DIRECT-W-NOFILES, no files found > ISIS-WORK>DIRECTORY [...]*.snf > %DIRECT-W-NOFILES, no files found > ISIS-WORK>DIRECTORY [...]*.bdf > %DIRECT-W-NOFILES, no files found > ISIS-WORK>sho def > $1$DIA2:[000000] > Conversely, I don't have any *.decw$font files, so we must be dealing with very different versions of VMS. Do the *.decw$font files look like bdf files? If not, then I'm out of ideas. Bruce ----------------------------------------- CONFIDENTIALITY NOTE: This e-mail message, including any attachment(s), contains information that may be confidential, protected by the attorney-client or other legal privileges, and/or proprietary non-public information. If you are not an intended recipient of this message or an authorized assistant to an intended recipient, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution, or reproduction of this message and/or any of its attachments (if any) by unintended recipients is not authorized and may be unlawful.
