I started taking a little look at the files after posting, and I am going to tentatively say that Kansas.ROM is a bad extraction and that from7 and from9 (identical, according to diff) are probably good.

My reason for surmising that is that at location 0x0000 0C80 I find the text:

Sony..Sound...EDisk...Backlight.display.device_type.....class-code..driver-ref..

in the latter two, but only garbage in the Kansas.ROM file.

Going to 0x0000 0320 (C80 / 4) in U4, I find:

oSDEaB.t.yt_..ocvi..

Which does seem to indicate a reversal of the byte order, but it also doesn't quite match up to a four to one ratio. I wonder if Copyrom inserted some extraneous bytes. Hmmm, but the total bytes are correct.

Let's see, at 0x0000 0320 (C80 / 4) in U3, I find:

yn.d.kilpsiv.esa..r-

At 0x0000 0320 (C80 / 4) in U2, I find:

......hgalec..-srdfen

At 0x0000 0320 (C80 / 4) in U1, I find:

oSnusikcidedpylcedremHp

Then interleaving these 2 bytes at a time and reversing the byte order yields

Sony..SoEDd...un

Hmmmm.. That's not working so good. What if I switch U4 and U1, so now I do U1, U3, U2, U4

Sony..Sound...EDisk...Backlight.display.device_type.....class-code..driver-ref..

Huh. Well, I wonder if that's all there is to it. Anyone want to write a little script to test it for the whole file? I could but it would take me days. So if one of the folks who's good at scripting would like to do it I would really appreciate it.

Ideally, such a script should take from7.ROM or from9.ROM, deinterleave them two bytes at a time into four segments. But reverse the order of the two bytes when putting them into each segment.