|
A Guide from MC Customer Support - December 1999
| HP 9000 Printer Setup
Set up Jet Direct on HP/UX 10.20
pg hosts
Next start sam
Select Printers and Plotters
Select LP Spooler
Select Printers and Plotters
TAB to activate the menu and use the arrow key and move the cursor to Actions then select Add Remote Printer/Plotter . . . Or if you have loaded JetAdmin on the HP 9000, select Add Network-Based Printer/PlotteR.
In this example, we have not loaded JetAdmin so we are selecting Add Remote Printer/Plotter. Then Fill the queue name in the Printer Name: field and the IP address of the Jet Direct print server in the Remote System Name and the same IP address in the Remote Printer Name. Select OK.
In this example, we have loaded JetAdmin so we are selecting Add Network-Based Printer/Plotter. Select Add Printer/Plotter Connected to HP JetDirect.
This is the JetAdmin menu. Select Add printer to local spooler. Enter the appropriate information as the menu requests (queue name and IP address as in the example above).
|
| NT Printer Setup Here
Special Note: On an NT system using Win 95/98 workstations, the following is found on winfiles.com: Win 95/98 machines logged into an NT network must have the master browser feature disabled, or they will argue with the NT server over who will maintain the list, causing delays and extra network traffic. The default setting is automatic. The Fix - Go to "Network properties". Highlight File and printer sharing for MS networks. Click the properties box. Highlight Master Browser. Select disabled from the menu on the right. Click OK. Click OK again. Re-boot for changes to take effect. Set up Jet Direct printer on NT 4.0 server with service pack 4. |
 |
Set up the Jet Direct Card/External Device via the Jet Admin software. | |
 |
Apply a valid IP address that matches your system's existing IP address structure and netmask. Remember to set the gateway setting in the Jet Admin software to be the same as the IP address for the Jet Direct device. | |
 |
After adding the printer in the Jet Admin software (refer to HP Jet Admin booklet and software help for instructions on using Jet Admin), print a test page from the Jet Admin software to verify the printer is communicating via TCP/IP with Jet Admin. | |
 |
After setting up the Jet Direct print server and assigning it an IP address, do the following:
Click My Computer Click Printers Click Add Printer Select My Computer and click Next Click Add a Port Click on HP JetDirect Port Select Easy Setup then click Next Click on Printer List (this should show the printer and IP address you set up earlier with the Jet Direct server set up with Jet Admin.) Click on the printer to you want to add Click OK This will fill in the Network Printer Name, TCP/IP address, and hardware address under the Manually specify printer area on the screen. Click Finish A box will pop up and should display Successfully created port. Click OK. Click Next in the Add Printer Wizard Either Select from the List of Manufacturers/Printers or click Have Disk and insert the diskette/CD that came with you printer and follow the instructions included with the diskette/CD. If this printer uses the same driver as a previously installed printer, you will get a message asking to Keep Existing Driver or Replace Driver, select Keep Existing Driver and click Next. Either leave the default printer name or if you desire change the printer name to something that is easy to understand but unique from previously installed printer names. Select Yes or No on Use This Printer as the Default Windows Printer. Click Next. Click Shared and type the name of the printer as you want it to appear to network clients. Do not worry about the box to Select Operating Systems at this time. Click Next. Click Yes on Print a Test Page and click Finish. Verify that your test page printed correctly. |
| Data General Aviion Printer Setup
Set up Jet Direct on DG/UX 4.11mu05
pg hosts
Next go into the sysadm menu and set up the printer queue using the device name set up above in the host's file. # sysadm
Printer name: lp1 The connection type indicates what the system must do to reach this printer. Choices are: 1 Local /dev/tty, /dev/lp, or /dev/parallel Enter a number, a name, the initial part of a name, <NL> to take the default, ? for help, ^ to return to the previous query, < to restart the operation, or q to quit. ... end pager? (? for help) [yes] 5 Choices are: 1 dg_annex Enter a number, a name, the initial part of a name, <NL> to take the default, ? for help, ^ to return to the previous query, < to restart the operation, or q to quit. ... end pager? (? for help) [yes] 3 Networked printer device name: oki395print Enter a number, a name, ? or <number>? for help, <NL> to redisplay menu, ^ to return to previous menu, or q to quit: q Are you sure you want to quit? [yes] Next check to see that you are in the /etc directory to test print the file inittab to the new print queue you just set up. # pwd # lp -dlp1 inittab This is what print queue should look like while it is printing the inittab file.
This is what the lp1 queue should look like when it is idle.
Repeat these steps for each of the print queues you wish to add. If you have any problems, remove the queue and start back with the Jet Admin setup and test first. |
| Novell/DOS Printer Setup Here
Set up Jet Direct printer on Novell 4.xx server. |
|
Set up the Jet Direct Card/External Device via the Jet Admin software. | |
|
Apply a valid IP address that matches your system's existing IP address structure and netmask. Remember to set the gateway setting in the Jet Admin software to be the same as the IP address for the Jet Direct device. | |
|
After adding the printer in the Jet Admin software (refer to HP Jet Admin booklet and software help for instructions on using Jet Admin), print a test page from the Jet Admin software to verify the printer is communicating via TCP/IP with Jet Admin. | |
|
After setting up the Jet Direct print server and assigning it an IP address, do the following:
Click My Computer Click Printers Click Add Printer Click Next Select Network Printer Click Next Click Yes on Print MS-DOS Based programs Click Browse Select your Novell server name from the list Click on the printer you want to add Click OK The Network Path or Queue name should show the full UNC Path to the printer. Click Next Click Capture Printer Port and select the appropriate LPT port. Click OK Click Next Select from the List of Manufacturers/Printers or click Have Disk and insert the diskette/CD that came with you printer and follow the instructions included with the diskette/CD. If this printer uses the same driver as a previously installed printer, you will get a message asking to Keep Existing Driver or Replace Driver. Select Keep Existing Driver and click Next. Leave the default printer name or, if you desire, change the printer name to something that is easy to understand but unique from previously installed printer names. Select Yes or No on Use This printer as the Default Windows Printer. Click Next. Click Shared and type the name of the printer as you want it to appear to network clients. Do not worry about the box to Select Operating Systems at this time. Click Next. Click Yes on Print a Test Page and click Finish. Verify that your test page printed correctly. |
Many customers have asked, "Is my system Y2K compliant?" This is a little more complex than a yes or no answer. Computer Hardware and Operating System Compliance MC writes software that runs on many hardware platforms. We do not have control over the hardware and operating system you are running. You need to verify Y2K compliance issues with the hardware manufacturer and the operating system manufacturer. You may need to install patches or releases to be compliant. Software Application Compliance The MC OFFICE Software has been tested and MC certifies that its software is compliant. Refer to www.mcoffice.com/company/y2k.html for Y2K information. MC software is written in Interactive Cobol. This requires a runtime program to allow the MC software to function. MC uses a product called ICOBOL. ICHOST and ICOBOL are made by the same company. ICOBOL has replaced ICHOST and you can refer to the ICOBOL Web site www.icobol.com for information on Y2K compliance. MC recommends you upgrade to ICOBOL if you are still running ICHOST. To verify which product you are currently using do the following: Log into your MC software and go into path (09.13). In the upper-right-hand corner of the screen you will see the following message: "USING: ICOBOL." This indicates that the system is running ICOBOL. If it says, "USING: ICHOST," this indicates the system is running ICHOST.
If you are running ICOBOL, you will need to verify that you are running version 2.40 or higher. You can do this by watching the display as the system starts into MC. It will display ICRUN Revision 2.xx. If you are running ICHOST, you need to contact the MC Marketing Department and get ICOBOL ordered as soon as possible. The Y2K testing at MC showed ICOBOL to be compliant, but ICHOST has Y2K date problems. ICOBOL is available for Data General UNIX, IBM UNIX, HP UNIX, Win NT, Novell, and DOS. There is a version available for the Data General AOS V/S "MV" systems. But this should only be used as a temporary "stop gap" until you can move to a UNIX, Network, or PC system. The AOS V/S version does not have all the features and capabilities of the UNIX, Network, and PC versions. It is intended to be a temporary use item only (The current version for AOS V/S is 2.15. The current version for UNIX, DOS, Novell, and NT is 2.52). |
