Dear Allison,
   
   You wrote:
> Edit out the noise and get to the point I may read it.
   
   Let's postpone this discussion a little bit, OK? It is very important to
discuss the KA410/SCSI/TK50Z issue, but I need to take a closer look at
Ultrix before I can continue the discussion. That requires installing
Ultrix, and I don't have my hardware ready yet.
   
> Your knowledge of engieering and business is overloaded with emotion.
> If a programmer did the allocation he would have commited several teams
> of people downstream as well.  Code was/is written tested, and documented
> at that time inside DEC.  There is cost associated and project teams were
> also tasked to meet time to deliver and cost to deliver.
   
   But this only shows the inferiority of commercial software compared to
the various non-profit forms (research by-product, hobbyist-written, etc.).
   
> <artificially block the loading of a driver cannot be classified as
> <anything but high treason and a crime against humanity.
>
> This is mow a matter of business history.  Your rant has been duely noted
> and is unnecessary.
   
   No, it is not rant and it is not unnecessary. A lot of people who use
KA410 systems with DEC software sorely miss the ability to use SCSI disks.
Many of them think that there is some technical reason for this, and it's
important to point it out to them that there is none and that they should
thank DEC management/marketing/whatever for putting in two lines of code
that artificially block the SCSI disk support.
   
> <   BUT WHY NECESSARILY NETBSD?!?! If there are much better codesets
> <around, why not use them instead? As for the encumbered code, I have
> <addressed that issue in the posting immediately preceding this one.
>
> It sources are unencumbered by copyrights.  Since I'm not a corperation
   
   Apparently you have missed the following sentence from my posting, even
though you have quoted it:
   
> As for the encumbered code, I have addressed that issue in the posting
> immediately preceding this one.
   
   I am negotiating with SCO on this issue RIGHT NOW.
   
> It's useful as is.
> [...]
> since the vs2k can boot from rx33/rdxx/tk50 and can still use the scsi
> to access larger disks there is little reason to bother with the rom.
   
   I have reasons to believe that not being able to boot from SCSI disks is
not the only problem. Let's postpone this discussion for now, OK? I'll get
back to it when I get the MV2000/VS2000 technical manual and play a little
with Ultrix.
   
> If you don't like the roms, rewrite the code from
> zero.  There is nothing to stop you.
   
   This is extremely counter-productive.
   
> Me I have other things to do.
   
   I will do the ROM tweaking myself. I have never asked anyone else to do
this. All I am asking you to do is to participate in this discussion when I
get back to it.
   
   Sincerely,
   Michael Sokolov
   Phone: 440-449-0299
   ARPA Internet SMTP mail: sokolov@alpha.ces.cwru.edu