Well, things are working well when I run on TRAM 0 only, but I'm having bad luck going any further than that. I see this error message when the network server attempts to boot the next eligible TRAM connected to TRAM 0, which is a T414 with 1 MiB ofRAM:
In Helios, decoding the fault code by typing `fault d105000a` reports that ns is experiencing a timeout. Does anyone know what might cause this? I think the TRAM should be healthy enough since it works with CSA Mandelzoom and since it passes `rspy /zmx`and `rspy /f` tests. Some thoughts:
- Is a 15 MHz T414 too slow for Helios?
- Would host.con for an 8 MHz PC/AT need a BOGOMIPS setting? Surely not...
- Some TRAMs on this network don't have enough RAM for Helios, but those aren't the ones that are having this trouble. Could they still be a problem?
1. I'd like to use rspy to reconfigure the c004 switch. It can do this, but it needs a file in "iswitch" or "swc" format. Is there a good reference for this format anywhere?
2. Is there any way to have rspy tell TRAM 0 to issue a subsystem reset?
3. Why does rspy /ch produce the line "reset { driver; ; null_ra.d }" instead of "reset { driver; ; tram_ra.d }"?
4. Why does rspy number my TRAMs as 0,1,3,4,5,6,7,8? Where's #2?
(or <) are unidirectional link connections- is bidirectional
connect 1>2 1<2
connect 1-2
connect 1>2 2>1
... all 3 are identical
Is it correct then that you cannot specify which link is used in this format? The connect line only indicates that different Transputers are connected
Could it refer to the B008's D-sub connector somehow?
this numbering is confusing
My 2 Euro-cents to that: C004 sux... even more when your network grows.
1. I'd like to use rspy to reconfigure the c004 switch.
Of course, if I could get my hands on some more capable TRAMs, there
might be less of a need to identify optimal configurations. Please
feel free to let me know if you are aware of any spare ones lying
around. :-)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 399 |
Nodes: | 16 (2 / 14) |
Uptime: | 111:35:38 |
Calls: | 8,369 |
Calls today: | 8 |
Files: | 13,165 |
Messages: | 5,899,112 |