DEC (digital) VAX / VAXserver 4000 Model 300 Hardware and Booting Process [EN]
HTML-код
- Опубликовано: 25 июн 2024
- German Version/Deutsche Fassung: • DEC (digital) VAX / VA...
Chapters:
0:00 Intro
0:34 General Talk
2:38 Outside and Connections
7:19 Disassembly
7:36 Some Parts
8:35 SCSI Controller and Memory
9:44 Processor Module
11:24 Reassembly and Tests
12:06 Some Comments on the Failure
13:31 Booting 
Наука
If I saw one of these lying around, I would think it was an A/C.
Thanks for that. I used to use 4300s at work a long time ago, and they were a fair bit faster than the previous generation. I only have 3400's now and I find they are easier for the hobbyist as they dont have special connectors for the CPU card, memory card or disks. The 3000's used the Q-Bus backplace and added cables for the memory and DSSI interconnects. You could (and I have) make your own cables for those things if they were missing.
The 4200 is similar, and is just a faster 3400. Interesting that they are both labelled as 4000 series, but are *very* different internally. I vaguely remember that you could get an upgrade kit (4000-50?) to upgrade the 3300/3400 to a 4200 equivalent.
I've never seen a real 3400, but I like the visual design with the bigger window like the 4200. I was quite supriesed about the 4200, it is using QBUS and an older processor based on CVAX (SOC) and not Rigel, but it was released after the 4300. A new feature of the 4200 is the DSSI placed on the CPU-Module (SHAC), but it doen't work on my 4200. I've read, that the KFQSA, that I use at the moment, doesn't support direct communication between machines, therefore the cluster has to use Ethernet for that purpose. I've own 4 DSSI cables, but there are two differt kinds of connectors. I can use my cables for the connection between my machines, but I want to add a StorageWorks controller (HSD30) and this contoller has a different connector.
@@DECcomputers (Sorry, I'll use the right account now!). The 3400 also has DSSI on the CPU board. The 4200 is just a faster 33/3400. It even uses the same memory.
I've never used a KFQSA, so don't know about the clustering issues. Yes, I have a HSD10 module that I would love to play with but cannot find a cable for it (at a reasonable price). Don't know why they couldn't use the standard DSSI cable. I've got a couple of videos feature the 3400, but I assume you've seen them. Cheers,
@@digitaldiggings You're right, it was the VAX 3800, which has a separate DSSI and Ethernet controller (ruclips.net/video/J4hyQDnMopo/видео.html), so I thought that every VAX 3X00 is QBUS only, but I've watched you video again it seems to be quite similar to a 4200. Is it even the same console module? If so, it might be possible to swap just the CPU module to turn a 3400 into a 4200. I may bring my onboard DSSI controller back to life, the errors on my VAX 4300 have shown that DSSI seems to be sensitive to voltage fluctuations, I will measure my 4200 PSU, maybe there is just a voltage problem. I found a store in the UK that makes DSSI cables, it's not very cheap (about 100 GBP) but cheaper for an European buyer than ordering in the US.
@@digitaldiggings I'm currently reading an interessting book (VAXcluster Principles by Roy G. Davis) which describes the differences between the various DSSI adapters. The MicroVAX 3400 adapter is called EDA640 and has no direct memory access (it uses interrupts) but is able of communication to other VMS devices. The KFQSA has direct memory access but can only communicate with ISEs, not with VMS devices. Interesstingly, it uses the same interface (SII Chip). The adapter of the VAX 4000 series (SHAC) was the first single chip solution and supports communication with VMS devices and can access the memory directly. In terms of performance, the KFQSA is the slowest adapter but SHAC appears to be more than twice as fast as the EDA640 (cf. Davis, pp. 3-48 et seqq.).
Bro has the original encabulator 💀
netbsd 🤔?
NetBSD does not support the DSSI controller, but I'll try NetBSD on another machine :)
I went off to figure out what CPU features defined 'time sharing' vs. not and... I guess it's just hardcoded licensing. :)
Yes, I think so too. You can change the CPU ID to change the license requirement. I did that with my time sharing VAX 4000/200, now it is a VAXserver 4000/200 for VMS, because I do not have any time sharing VMS licenses.
Please have some respect and clean the cabinets
I have tried, but I don't want to damage the plastic by using overly aggressive cleaning maerials.
@@DECcomputers 8-Bit Guy (on RUclips) has a lot of advice on restoring old plastic, particularly ABS
Retrobrighting would be a monumental task. I can see why the owner wouldn’t want to do it. It’s not as trivial the OP is saying.
Talk a little slower, thanks.