Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

Printing on NT network causes crash :-( (AREV Specific)

At 22 JAN 1998 06:44:46PM Cortex (cortex@cortexmed.com) wrote:

We are having difficulties with a few of our newer customers. Typically we are running ARev in a Novell environment with few problems. As we have switched to NT, however, our printing has become an issue. A particular, repeatable problem occurs when we have a Win 95 workstation with a HP LaserJet 5 attached to it. The printer is being shared with the other workstations on the network, all of which are NT workstations. There is no difficulty printing from the remote workstations. The problem occurs when we attempt to print from the Win 95 station. A critical Windows error occurs every time we try to print to it locally. The error is severe enough that the workstation must be rebooted. We are utilizing the NET USE commands to change and delete network printers in our commands to print. After an attempt through Revelation to select the local printer, a simple R/Basic command of

PRINTER ON

PRINT (Escape Sequence)

PRINTER OFF

is sufficient to cause the error. We are wondering if anyone has seen similar problems with NT networks and ARev. If so, is there a good solution to this problem? In particular, can you detect whether the printer the machine is currently routing it?s data is local or remote?

Any help would be greatly appreciated, either here or email us directly at cortex@cortexmed.com

At 28 JAN 1998 12:50AM Kevin at KPW wrote:

We had serious difficulty sharing printers until …..

We decided to configure a single work station to act as a Print Server.

This station was DEDICATED to this task and is running Windows

NT Workstation V4.0

All users wishing to print to shared printers MUST print thru' this

printer.

All users are now able to SHARE the attached printers without any

difficulty. These are very high volume printers, 4 in all on direct

connect (2 parallel and 2 serial connections).

We now insist that NO LOCAL PRINTER IS SHARED!

In a mission critical system this was the only answer after trying very

many iterations of alternative choices.

Regards,

Kevin at KPW

email kpw@compuserve.com

At 29 JAN 1998 02:00PM Cortex wrote:

Thanks Kevin, 

That's what we're considering here as well.  Just looking for other options...  (Which we may have gotten in email.  I'll post what I find)

Doug Davison

Cortex M.M.S., Inc.

View this thread on the forum...