Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!purdue!mentor.cc.purdue.edu!mtr
From: mtr@mentor.cc.purdue.edu (Miek Rowan)
Newsgroups: comp.windows.x
Subject: Re: purdue patches
Summary: update -
Message-ID: <870@mentor.cc.purdue.edu>
Date: 15 Jan 89 16:06:50 GMT
References: <8901131422.AA15557@meepmeep.UUCP>
Organization: Unix Groupie
Lines: 21

In article <8901131422.AA15557@meepmeep.UUCP>, jkh@pcsbst.UUCP (Jordan K. Hubbard) writes:
> Could someone send me the complete up-to-date actually usable Purdue
> and Purdue+ patches? I apologize for sending this to the whole list, but
> I'm pretty confused about exactly which patches are which at this
> point. The first set I got didn't apply and I've since seen a number
> of "updates", the order and purpose of which I can't fathom.

Well, as Gene found out in a hair pulling few days of debugging - the
Purdue+ patches don't work in all cases.  Until a fix to these come along
I would stick with the Purdue patches alone.   

If all you are working on are bwtwo frame buffers - then the Purdue+ patches
should work fine.  Its when you use the cgfour frame buffer on a 3/60
(works fine on a 3/110 with cgfour) - that it suffers massive bitrot. 
It is in the same code and so everyone involved seems stumped as to why it 
would act differently.  

Anyway...The point is, unless you only use black and white, (or 110's) I
would wait on the Purdue+ and just install Spaf's speedups. (Purdue)

mtr