MEGA UPDATE:
I decided to perform a complete tabulated test of all possible configurations. There are two lines in System Configurations which loads after POST that discuss cache status on the machine- Cache Value (#), and L2 Cache type (type). The following are my results
WITH MODULE INSTALLED
Jumper = 512, L2 BIOS = Enabled = # "512 kb", type "Pipeline Burst", HIMEM ERROR
Jumper = 512, L2 BIOS = Disabled = # "W/B Cache", type "Write Back", HIMEM GOOD
-----------------
Jumper = 256, L2 BIOS = Enabled = # "512 kb", type "Pipeline Burst", HIMEM ERROR
Jumper = 256, L2 BIOS = Disabled = # "W/B Cache", type "Write Back", HIMEM GOOD
WITH MODULE REMOVED
Jumper = 256, L2 BIOS = Enabled = # "256 kb", type "Pipeline Burst", HIMEM GOOD!!
Jumper = 256, L2 BIOS = Disabled = # "W/B Cache", type "Write Back", HIMEM GOOD
I didn't continue testing with the module removed and jumpers at 512 because it seems clear to me from the first round with module in that the system's "Cache Value" number is responding to the total amount installed, independent of the jumper setting.
OBSERVATIONS:
I do indeed have 256kb of onboard pipeline burst cache on this mobo, which is pleasing news.
I seem to have a bad COAST module, despite sys configs recognizing it in the Cache Value entry as adding to a total of 512 in system.
QUESTIONS:
I am curious as to what would happen in one added 512kb via a COAST module to this system- clearly the jumper implies a 512 *could* be added- but I thought the VX chipset only allowed for a maximum of 512kb of L2 cache anyway...so what's the purpose of allowing a 512 stick and 512 jumper setting? Or am I mistaken, and the VX chipset is capable of addressing more than 512kb of L2 cache?
Since I have no intention of going through the riff-raff of shipping this thing back to Kazakhstan, does anybody have any socket 7 mobos lying around who want this module to plug in for testing and evaluation?