El 08/02/2013, a les 23:14, Johnny Billquist <bqt at softjar.se> va escriure:
And the problem is just that the boot rom uses a more restricted disk block addressing,
limiting the booting to disks of less than 1G. (Actually, you can boot from larger disks
as well, as long as the boot rom don't need to read from anything above 1G.)
Nice to know. IIRC I read about the firmware dropping the high bits of the block address
so at some point in time the writes against the disk would "wrap around" and
trash the first 4GBs... but it seems its quite an urban legend :)
BTW, This is a nice sight:
$ sh net
VAX/VMS Network status for local node 7.61 BITXOO on 8-FEB-2013 23:26:08.76
The next hop to the nearest area router is node 7.60 BITXOV.
Node Links Cost Hops Next Hop to Node
7.61 BITXOO 0 0 0 (Local) -> 7.61
BITXOO
7.6 MBSERV 0 3 1 UNA-0 ->
7.6 MBSERV
7.60 BITXOV 0 3 1 UNA-0 ->
7.60 BITXOV
7.64 BITXO1 0 3 1 UNA-0 ->
7.64 BITXO1
7.65 BITXO2 0 3 1 UNA-0 ->
7.65 BITXO2
7.67 BITXO4 0 3 1 UNA-0 ->
7.67 BITXO4
7.68 BITXO5 0 3 1 UNA-0 ->
7.68 BITXO5
7.70 BITXOT 0 3 1 UNA-0 ->
7.70 BITXOT
7.71 BITXOR 0 3 1 UNA-0 ->
7.71 BITXOR
7.72 BITXOM 0 3 1 UNA-0 ->
7.72 BITXOM
7.74 BITXOW 0 3 1 UNA-0 ->
7.74 BITXOW
7.79 BITXT0 0 3 1 UNA-0 ->
7.79 BITXT0
Now, if I could just fix poor BITXO3 (which is a VS 3100 with a toasted cache in the
mobo...).
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES