een of andere bullshit printer instaleren (die er helemaal niet is)
die als default instellen.
Dan moeten ze elke keer expleciet nadenken welke ze nodig hebben. en als ze het vergeten .. nah ja dan zit er een mooi printertje in je systray met een printjob die nergens heen gaat .....
overweging: .. zou je ipv lpt1 naar NUL kunnen printen ?
ff testen
edit . woei
How to Test a Printer with the NUL Port in Windows 2000
If you're troubleshooting a printer, one test is whether or not network print jobs are reaching the printer. An efficient way to perform this test is to use a NUL port. Because the NUL port is virtual, not a real device, jobs sent to NUL don't waste paper, and don't interfere with print jobs that are printing to real ports. By default, Windows 2000 doesn't include the NUL port in a printer's list of available ports, but you can install a NUL port on all the printers attached to a Windows 2000 print server with the following steps:
1. Open the Printers folder. 2. Choose File, Server Properties. 3. Select the Ports tab. 4. Click Add Port. 5. Select Local Port, then select New Port. 6. Enter NUL as the port name and click OK. 7. Click Close twice to return to the Printers folder window.
The NUL port is now listed in the Ports tab of the Properties dialog box of all the printers installed on this computer.
To see whether the print jobs sent through the NUL port actually reach the printer, you must watch the printer's queue. Because print jobs move through the queue quickly, the best way to make sure you can see arriving print jobs is to pause the printer. To test the printer with the NUL port in a paused state, follow these steps:
1. Open the Printers folder. 2. Open the Properties dialog of the printer you want to test. 3. Select the Ports tab, select the NUL port, and click OK. 4. Double-click the printer's icon to open its window. 5. Select Printer, Pause Printing. 6. Send a print job from a network client. 7. Look in the queue to confirm that the job arrived. 8. Resume the printer. 9. Change the printer port back to its real port (usually LPT1:)
If the job arrives in the print queue, the printing problem is not a result of a network communication error. If the job doesn't arrive in the print queue, your network communication setup, or the configuration of the UNC for the printer at the sending workstation is faulty. By the way, if the test job arrives, it won't print, it disappears into la-la land.
source
zo daar ben ik tch wel 10 hele minuten mee bezig geweest
[
Voor 81% gewijzigd door
Fish op 11-12-2003 23:46
]