🚀 go-pugleaf

Henry Manaster (manaster@yu1.yu.edu) on the lack of a PostScript
viewer on the Windows NT SDK:
 ----
| Why on Earth did microsoft put this out in this fashion without a
| viewer. It almost seems like this is part of some mad plan to
| force people to BUY the docs.
 ----

I suppose we can all see Machiavelian plots in almost every aspect
of society if we look hard enough.

In this situation however, the answer is really quite simple. We don't
have a PostScript viewer that we could put on the SDK.

I suppose we 'could' take a hit in our development scheduled for NT in
order to right one... but that would most likely delay the release of
NT (and add a testing burden), which would not be a popular solution.

I suppose we 'could' buy an existing one from somebody and ship it on
the disk... but that would force us to increase the cost of the SDK,
as well as add an extra testing burder to make sure the viewer kept in
sync with the changes in the system. Again, not popular decisions.

Or we could attempt to satisfy as many people as humanly possible without
affecting any schedules by simply tossing the PS files onto the disk
with the warning 'caveat emptor' so that those individuals who can make
use of these files are allowed that opportunity, and give those people
who can't use PS files something to complain about. :->


If anybody does happen to know of a public domain PostScript viewer, that
has been ported to Windows NT, and can read the PostScript files that
have been included on the SDK, I'd be more then happy to pass it on to
the SDK team for inclusion in a future rev of the disk.

-Robert