[pups] adding MSCP driver to 2.9BSD -- distribution is corrupt!

I got the driver to come up on a second controller in E11. Evidently the PRO350 RA driver would only work as a root drive, which is attached via some other mechanism that I am not familiar with. What I did to get it to autoconfig was create an "raprobe" routine that simply returned the status code that says "it's OK and you don't need to look for an interrupt". Crude, but the target machine won't work without the controller present. Now I need to work on the boot sector. The problem is that rauboot.s in the distribution is corrupt, in both the tree and the tar version. See file http://www.tuhs.org/Archive/PDP-11/Distributions/ucb/2.9-pro350/ mdec/rauboot.s, the line that begins "NDIRIN = 4." ends in garbage, and there is a chunk of code missing. One of the doc files, I think boot.doc, has the same problem. It seems that the disk from which the 2.9BSD-PRO patch distribution was prepared was slightly scrambled. There is a chunk of C code right in the middle of the doc in place of some important info. I've been able to reconstruct most of rauboot.s by comparing with other boot programs, except I need the snippet of code for initializing the MSCP controller. I can probably figure this out from the 2.11 driver, but I'd much rather not have to. The 2.11 driver is very different. Does anyone know where I can get the original file? -- Jonathan Engdahl Rockwell Automation Principal Research Engineer 24800 Tungsten Road Advanced Technology Euclid, OH 44117 USA Euclid Labs http://users.safeaccess.com/engdahl