HP OmniBook 3100 HP OmniBook 2100 and 3100 PC User’s Handbook - Not O - Page 47

Printing Problems, Serial and Parallel Problems - omnibook 300

Page 47 highlights

• If the OmniBook is performing an operation, it normally waits for the operation to finish. • Check the Power Button Mode in the BIOS Setup utility (Power menu). You can configure the power button to either suspend or shut down the OmniBook. Printing Problems Hint For most printing problems, use the Print Troubleshooter in Windows Help. If a serial or parallel printer doesn't print • Check that you are using a proper cable or cable adapter, and that the printer is on. • Check for paper in the printer or other printer errors. • Make sure the printer cable is secure at both ends. If an infrared printer doesn't print • Windows NT 4.0 does not support infrared devices. • Make sure the infrared light path is not blocked. • Check for paper in the printer or other printer errors. • Make sure Windows is running-infrared printing is supported only while Windows is running. • An infrared driver must be installed and the BIOS Setup setting must be enabled. For details, refer to the driver's Readme file (located in \Omnibook\DriversWin95\Irda\Fastir). • In Windows Help, use the Print Troubleshooter. If the left edge of printed output is missing • If the printer you are using is a 600-dpi (dots per inch) printer, try selecting a compatible printer driver for a 300-dpi printer. For example, for a 600-dpi HP LaserJet printer, try using the HP LaserJet IIIsi driver (300-dpi). Certain applications may not work properly with 600-dpi printers. Serial and Parallel Problems If the serial mouse doesn't work • First, confirm that you have followed the manufacturer's installation instructions completely and have installed the mouse properly. • Check the port connection (may be loose). If a serial modem doesn't work properly • In Windows Help use the modem troubleshooter. • Check the port connection (may be loose). 47

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53

47
If the OmniBook is performing an operation, it normally waits for the operation to
finish.
Check the Power Button Mode in the BIOS Setup utility (Power menu). You can
configure the power button to either suspend or shut down the OmniBook.
Printing Problems
Hint
For most printing problems, use the Print Troubleshooter in Windows Help.
If a serial or parallel printer doesn’t print
Check that you are using a proper cable or cable adapter, and that the printer is
on.
Check for paper in the printer or other printer errors.
Make sure the printer cable is secure at both ends.
If an infrared printer doesn’t print
Windows NT 4.0 does not support infrared devices.
Make sure the infrared light path is not blocked.
Check for paper in the printer or other printer errors.
Make sure Windows is running—infrared printing is supported only while
Windows is running.
An infrared driver must be installed and the BIOS Setup setting must be
enabled. For details, refer to the driver’s Readme file (located in
\Omnibook\DriversWin95\Irda\Fastir).
In Windows Help, use the Print Troubleshooter.
If the left edge of printed output is missing
If the printer you are using is a 600-dpi (dots per inch) printer, try selecting a
compatible printer driver for a 300-dpi printer. For example, for a 600-dpi
HP LaserJet printer, try using the HP LaserJet IIIsi driver (300-dpi). Certain
applications may not work properly with 600-dpi printers.
Serial and Parallel Problems
If the serial mouse doesn’t work
First, confirm that you have followed the manufacturer’s installation instructions
completely and have installed the mouse properly.
Check the port connection (may be loose).
If a serial modem doesn’t work properly
In Windows Help use the modem troubleshooter.
Check the port connection (may be loose).