>>Hello.
>>
>>I have a problem with a report. Every time I try to print the report it
>>just hangs on the "Printing..." dialog and the only way to get the
>>machine to work is to press the "O SHIT" button.
>>
>>The application contains about 30 reports and they all work fine
>>except the one discribed above. In the network that runs this
>>application there are 8 computers all running on WIN95 with a
>>Novell 3.12 server. First the report stopped working on one machine
>>but worked allright on the other 7. But it has stopped working
>>on one after another. And now there is no machine that can print
>>the report.
>>
>>I can print the report on my machine and I also have a Novell 3.12
>>server.
>>
>>Can anyone help my because the report is very important for the
>>client.
>>
>>/Magnus Nordin
>>magnus.nordin@solutor.se
>
>
>Can't be sure if this will help but I had a problem with Win95 and 2.6 printng
>on Novell 3.12 going to an HP laser 5si. The two things that would allow me to
>print the report were,
> 1. Set display colors to 16 colors.
> or
> 2. Remove all boxes from the report and replace with lines.
>
>I used several different vid boards and drivers, all acted the same.
>Hp never came out with any other drivers that I was able to find.
>Your guess is as good as mine as to the boxes.
>I truly believe that it was the print driver.
>
>Hopes this helps
>Jeff Butler

I had the same problem with the same hardware configuration. If the printer is set up as a local printer to the workstation printing the reports, it worked fine. I think that the problem lies in the fact that the Novell 3.12 server does not process long filenames (even after the Novell patch) as well as Novell 4.11. As a result the HP5 drivers which are installed for Win95 have some long filename characteristics that get screwed up when they go thru the 3.12 server. Try printing on a workstation where the printer is local and see if you have the same problem. I thought I was going crazy for a while too. I ended up upgrading the network to NT as they needed MS SQL anyway and that got around the problem.

HTH,

Bill