Xerox 750DX Fiery SI Color Server Administration Guide - Page 87

Using AppleTalk with Windows NT

Get Xerox 750DX - Phaser Color Laser Printer PDF manuals and user guides
UPC - 042215455060
View all Xerox 750DX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 87 highlights

33-27 Using AppleTalk with Windows NT The Server name entry in the NET_WSCK.INI file should be the same as the server name you gave the Fiery SI in the Control Panel Server Setup. The device name entry in the NET_WSCK.INI file must match the device name that is internal to the Fiery SI. 2. Make sure that the TCP/IP protocol has been loaded on each workstation that will run the utilities. 3. Install the utilities. See Getting Started for details. 4. When you see the prompt to find the NET_WSCK.INI file, insert the floppy disk you prepared. The edited file is copied to the active Windows folder on the user's workstation. This method ensures that all users on the network have the correctly edited file. Using AppleTalk with Windows NT Windows NT servers can also use AppleTalk for printing with the Fiery SI. This approach is not as important with the current version of Fiery SI utilities, which now support TCP/IP and IPX/SPX protocols. The important thing to note, in creating a printer that you are sharing with AppleTalk users, is NOT to "capture" the printer. Capturing the printer forces all users to print to the server rather than directly to the printer. If you capture the printer, Fiery SI queues will not appear in the Macintosh Chooser. Loading the AppleTalk protocol on a Windows NT server is very similar to loading TCP/IP. If you are only using AppleTalk, you do not need an IP address or a Windows NT hosts file entry for the Fiery SI queue or queues. Install the Windows NT PostScript Printer driver and the Fiery SI PPD for your Windows NT server and for your Windows NT and Windows clients. Macintosh users can print directly to the Fiery SI and should install the Adobe PS Printer driver for the Macintosh and the Fiery SI PPD. All of these installations are described in Getting Started.

  • 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
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
3
3-27
Using AppleTalk with Windows NT
The Server name entry in the NET_WSCK.INI file should be the same as the server
name you gave the Fiery SI in the Control Panel Server Setup.
The device name entry in the NET_WSCK.INI file must match the device name that
is internal to the Fiery SI.
2.
Make sure that the TCP/IP protocol has been loaded on each workstation that will run
the utilities.
3.
Install the utilities.
See
Getting Started
for details.
4.
When you see the prompt to find the NET_WSCK.INI file, insert the floppy disk you pre-
pared.
The edited file is copied to the active Windows folder on the user’s workstation. This
method ensures that all users on the network have the correctly edited file.
Using AppleTalk with Windows NT
Windows NT servers can also use AppleTalk for printing with the Fiery SI. This
approach is not as important with the current version of Fiery SI utilities, which now
support TCP/IP and IPX/SPX protocols.
The important thing to note, in creating a printer that you are sharing with AppleTalk
users, is NOT to “capture” the printer. Capturing the printer forces all users to print to
the server rather than directly to the printer. If you capture the printer, Fiery SI queues
will not appear in the Macintosh Chooser.
Loading the AppleTalk protocol on a Windows NT server is very similar to loading
TCP/IP. If you are only using AppleTalk, you do not need an IP address or a
Windows NT hosts file entry for the Fiery SI queue or queues.
Install the Windows NT PostScript Printer driver and the Fiery SI PPD for your
Windows NT server and for your Windows NT and Windows clients. Macintosh
users can print directly to the Fiery SI and should install the Adobe PS Printer driver
for the Macintosh and the Fiery SI PPD. All of these installations are described in
Getting Started
.