wa2flq
Experienced Member
I have a RD54 (aka XT2190) that is currently only a boat anchor. So I'm reaching out to get some advice on how to attack the problem of creating a bootable diagnostic tape, so I can take a shot at reformatting it. The drive has bit rot typical for its heritage. I'm hoping a reformat will leave it in a more usable state.
I've tried to find or build a tape with the MDM diagnostic. This link seems to have all the necessary files - AQ-QL5AH-DN (http://www.vaxination.ca/vms/microvax/mv_ii.html). However after building a TK52-K (CompacTape II) it refuses to boot.
>>> b mua0
2..
?43 FILESTRUCT, MUA0
?06 HLT INST
PC = 00000EE6
Others have seen the same challenge. I have built a VMS 5.5 STABACKIT on the same tape cartridge (from a MV3100). The MVII loads Standalone Backup just fine and sees the RD54, so the basic hardware and tape media is ok.
I also looked a MDM kit that appears to be used for SIMH AQ-GL5AE-DN.tk50 (http://www.9track.net/vax/mv2diag.zip). The file is in a virtual tape format and along with some metadata, has captured the headers. I don't currently have a way to create a tape from this source. But looking at dump of the content, it appears the MDM files are built on the tape differently that what I see when I create my own tape under VMS via copy.
I suspect that the original diagnostic tapes used 512 byte records for the files (sysboot.exe, etc..) while the tape I create under with VMS copy uses a different record size (2048 bytes). The STABACKIT uses 512 byte records. There is a setsize program created on the fly for this purpose. Does anyone know if this record size is a limitation in the MVII onboard VMB? Or does this diagnostic just not work on a TK52-K? I don't have a way to write a TK50-K at the moment.
Thanks is advance for any advice or feedback.
I've tried to find or build a tape with the MDM diagnostic. This link seems to have all the necessary files - AQ-QL5AH-DN (http://www.vaxination.ca/vms/microvax/mv_ii.html). However after building a TK52-K (CompacTape II) it refuses to boot.
>>> b mua0
2..
?43 FILESTRUCT, MUA0
?06 HLT INST
PC = 00000EE6
Others have seen the same challenge. I have built a VMS 5.5 STABACKIT on the same tape cartridge (from a MV3100). The MVII loads Standalone Backup just fine and sees the RD54, so the basic hardware and tape media is ok.
I also looked a MDM kit that appears to be used for SIMH AQ-GL5AE-DN.tk50 (http://www.9track.net/vax/mv2diag.zip). The file is in a virtual tape format and along with some metadata, has captured the headers. I don't currently have a way to create a tape from this source. But looking at dump of the content, it appears the MDM files are built on the tape differently that what I see when I create my own tape under VMS via copy.
I suspect that the original diagnostic tapes used 512 byte records for the files (sysboot.exe, etc..) while the tape I create under with VMS copy uses a different record size (2048 bytes). The STABACKIT uses 512 byte records. There is a setsize program created on the fly for this purpose. Does anyone know if this record size is a limitation in the MVII onboard VMB? Or does this diagnostic just not work on a TK52-K? I don't have a way to write a TK50-K at the moment.
Thanks is advance for any advice or feedback.