I took a look at the images you sent, and I did notice one problem with the stream files. They were made with the 1.2mb drive set to "high density" even though these are "low density" disks.
If you are using the command line, use the parameter -dd1 or "density line high" in the GUI. It is confusing because they refer to the drive's logic line signal level rather than actual density, which is the exact opposite. (Logic line high=low density, logic line high=low density). On top of that confusion, one never really knows for 100% sure if a 5.25 disk has high or low density data on it until the content is examined.
The kryoflux folks will tell you it does not matter, but in practice having the wrong density set can cause intermittent read errors, and it can confuse some decoding tools. The Kryoflux's decoder can aparently deal with this. But, when I tried to decode them with the PCE tools to check for copy protection, the tools barfed.
FYI, DEC Rainbow disks are normally Low Density ("Double Density"), MFM, single sided, 80 tracks 96TPI, 10 sectors of 512 bytes per track.
I would recommend redumping with the correct setting for preservation purposes. But in this case, I did not detect any copy protection, so the raw flux streams are not as important, and I was able to decode them and write usable disks directly from the stream files.
I also created ImageDisk images from the stream files, which are more useful to those wanting to write fresh disks than unstructured IMG files. (360k, 720k, 1.2mb, and 1.44mb IMG files are standard, but the DEC Rainbow's format is very non-standard).
I'll send you a PM with those.
