Windows 3.1 "Black Screen of Death"
Mike Silano
patch vnbfix02.386 for Windows 3.1
Is this patch accesable via Internet somewhere?
(FYI: This patch fixes a bug in the Win 3.1 virtual interrupt controller.
It causes a hang on network access - hence, the black screen of death.
Microsoft has acknowledged this bug to some corporate customers, but not
to everyone.)
-Thanks
Mike Silano
Dirk W. Howard
>From: sil...@newton.cs.jhu.edu (Mike Silano)
>Subject: Windows 3.1 "Black Screen of Death"
>Date: Thu, 15 Apr 1993 18:08:22 GMT
This patch is not generally available, because what it fixes is not a
general case problem, but rather specific. If you have a problem that you
feel is the "Black Screen of Death", I would suggest that you open up a call
with Novell Technical Support. If you don't want to shell out the $$$, then
you may need to see if your Novell authorized dealer will take the call and
then contact Novell.
---------------------------------------------------------------------------
Dirk W. Howard These are my personal opinions. No one else
Novell Technical Support in their right mind would claim them.
dho...@novell.com
---------------------------------------------------------------------------
Chris Claborne
>This patch is not generally available, because what it fixes is not a
>general case problem, but rather specific. If you have a problem that you
>feel is the "Black Screen of Death", I would suggest that you open up a call
>with Novell Technical Support. If you don't want to shell out the $$$, then
>you may need to see if your Novell authorized dealer will take the call and
>then contact Novell.
Gee, I can't understand why someone wouldn't want to spend $150 on a
problem that has already been solved. People are so tight these days.
... __o
.. _`\<,_
chris.c...@sandiegoca.ncr.com ...(*)/ (*). CI$: 76340.2422
Bob
please elaborate on this bug. i think we have it, but "black screen of death"
and "bug" could describe a lot of situations. the situation is not imperative
enuf to warrant a million dollar call to novell tech support.
as it is, rather that doing that all network window stuff will be moving to
local HD's and we will be running a network compare/delete/update utility to
update the local disks from a network master.
anyway, thanx for info...
bob
--
Bob Hollinger <------------------------------------->
Wheaton College / B...@david.wheaton.edu \ Disclaimer:
CPO #1343 > uunet!tellab5!wheaton!Bob <
Wheaton, Il 60187-5593 \_____________________________________/ [CENSORED...]
708-752-6322
Bob
via network (netware 3.11).
what happens is a user prints, and it queues it up, and then starts to print(so
far so good) but it starts it out with a couple pages of garbage and then back
to the document, but usually part of the doc is then missing.
also it sometimes happens in the middle of the doc too.
we have tried reinstalling the printer drivers several times, but to no avail.
the problem occurs while printing from wp5.1 (since it's the only thing people
really print from on our PC network, i can't say it's necessarily wp's fault or
novell's or ibm for their ps/2's)
has anyone seen any problem similar to this? is there a bug in the pserver
NLM that is known about? is there a bug in wp that is know about? is there
life on Mars?
thanx for any info...
big...@mala.bc.ca
> we have been experiencing a very random and unstable problem with our printers
> via network (netware 3.11).
>
> what happens is a user prints, and it queues it up, and then starts to print(so
> far so good) but it starts it out with a couple pages of garbage and then back
> to the document, but usually part of the doc is then missing.
>
> also it sometimes happens in the middle of the doc too.
>
> we have tried reinstalling the printer drivers several times, but to no avail.
IF you are using capture check out the TI parameter. It may be that the job is
timing out if the machine is slow. WP does send a proper End_of_Job so a TI
is not striclty needed for it.
Are you using the WP Queue direct option or using capture. I have not tried
the Queue direct except to test it. If you are not using it you might want
to try it and VVersa.
>
> the problem occurs while printing from wp5.1 (since it's the only thing people
> really print from on our PC network, i can't say it's necessarily wp's fault or
Flame ON:
I find it amazing the WordPerfect { theres a joke } is so respected. Every bug
fix release is just another bug release. Fix one make two.
The Network support for the DOS version is ok if you dont mind giving all sorts
of rights so your users can clober each others setup etc. { we force it all to
the user directory }.
WP4Win ver 5.1 and 5.2 are crap and junk respectively. Same mickey mouse
network support { compare it to WinWord and Excell }. Useless Network setup
program... It offers you the network readme file then tells you to do the
install first.... dosent know that windows DLLs in a network install go in
in the shared WIN dir and not the users win\system and on and on.
Oh yea lets not forget the way those native WP drivers are sooo much
better than the windows ones.... well worth loosing the single point config
of Windows.
Now this is the sort of junk I expect from a new product or a company with
limited resources. WordPerfect { haha } has a very established product
and mega resources.... just no ability I guess.
Gotta love WP4Win 5.2 though esp that newfangeled HORIZONTAL scroll bar that
they added from 5.1.
Flame OFF:
Tony Bigras
Big...@mala.bc.ca
ok
hho...@flint.mines.colorado.edu
In article <1993Apr19....@wheaton.wheaton.edu> b...@david.wheaton.edu (Bob) writes:
>we have been experiencing a very random and unstable problem with our >printers has anyone seen any problem similar to this? is there a bug in >the pserver NLM that is known about? is there a bug in wp that is know >about?
Bob--
We had the same problem in our office just last month. The problem is with your version of PSERVER.NLM. You need to upgrade to PSERVER V1.27. You can find this version via FTP novell.com (anonymous login). I know its in the novlib directory, but beyond that I'm not quite sure. Get forum.zip (binary) and it should tell you where pserv v1.27 is located.