October 2017 - vcf-midatlantic

Re: [vcf-midatlantic] vax scsi questions
by VAXman＠tmesis.org 09 Oct '17

09 Oct '17

william degnan via vcf-midatlantic writes: >>> > >>> >Guessing there us a way from the >>> prompt to change a drive's volune, >>> >but I did not find a way to do it. >>> >>> From the dead sergeant, you can select a boot device. Volume information >>> -- >>> label, structure, ownership, etc., etc. -- are manifestated in the >>> operating >>> system (VMS). If you had an issue with the device on SCSI id 2, you could >>> have physically removed that drive. The device would then not appear in >>> the >>> device configuration and the MOUNT command would fail: >>> >>> %MOUNT-F-NOSUCHDEV, no such device available >>> >>> Assuming there is no ON ERROR in the startup procedures, your system >>> should >>> then boot through the system startup to the point where you can login. At >>> that point, you can reconnect the device and issue: >>> >>> $ MCR SYSGEN AUTOCONFIGURE ALL >>> >>> Then, a: >>> >>> $ SHOW DEVICE D >>> >>> should show you your disk devices including the device at DKx200:. >>> >> >> >> >> >one last thing...I only had one bootable drive, and I could only get to the >$ prompt from the drive that was configured to mount and load some stuff >from the ID=2 drive. What you suggest above would work, but would still >have to have done what I did to get into minimal boot, etc. At least in >VMS 5 minimal boot does not mount nor include any other drive than the boot >drive in a $ show dev d. Minimum boot will not execute your system's SYSTARTUP_VMS (or *_V5 because you're living in the past). That is, typically, where one would add MOUNT commands to mount other device volumes available to the system. When you DO startup the system minimally, there are many other aspects of *normal* VMS startup that are also bypassed. You can also modify the system startup in SYSGEN when you boot conversationally (>>> BOOT/[R5:]1) and define the startup to the OPA0: (SYSBOOT> SET/STARTUP OPA0:). WHen your system boots, it will leave you at the DCL prompt ($). No need to even know the SYSTEM password or login to the SYSTEM account. However, when you do this, there is no error handling! A error, even a typo precipitating an unknown command syntax error, will kick you out with no resolve other than to reboot. The trick here is to issue a "$ SPAWN" command first. This way, you'll have a subprocess that, if it terminates, will dump you back into the STARTUP pro- cess. NOTE: If you change the startup, you will want to change it back. Conversationally boot. SYSBOOT> SET/STARTUP SYS$SYSTEM:STARTUP.COM and SYSBOOT> CONTINUE. On my systems, I MOUNT volumes in a procedure (I call SYSTARTUP_MOUNT.COM) that I run as a detached process. If it hangs up on a MOUNT I can still, eventually after STARTUP.COM and its scion complete, login.

2 1

AOL keyword "RIP"
by Jeffrey Jonas 09 Oct '17

09 Oct '17

AIM, AOL's instant messaging service, is to shut down December 15 after 20 years of operation. I'm just re-tweeting this from hash-tag (something catchy but useless)

6 5

FS: Very Early Bob Mullen S-100 Card Extender
by systems_glitch 09 Oct '17

09 Oct '17

link: http://www.ebay.com/itm/272880651747 This one just has initials, no actual Mullen name, but the PO Box address is the same. Unlike later Mullen cards, this one is just an extender -- no fuses, no logic probe, no prototype area. It uses a high quality 3VH50 mil-spec S-100 connector, which really grabs the inserted S-100 board. Previous owner applied labels with the S-100 pinout to the front and back. This extender is short enough to leave in with the chassis cover installed, so you don't have to pull it out every time you want to put the cover back on. My preferred style -- saves wear on motherboard S-100 connectors. Thanks, Jonathan

1 0

Re: [vcf-midatlantic] vax scsi questions
by VAXman＠tmesis.org 09 Oct '17

09 Oct '17

william degnan via vcf-midatlantic writes: >This all came up because I wanted to replace a drive, but the only >replacement I had avail was also ID 2 but a diff volume name. >Systartup_v5.com was hanging on the mount of the drive. So, knowing no >other way, I had to access the OS via minimal boot to bypass systartup >and then comment out the mount of drive 2. In MIN state I could not >mount the new drive to initialize it so re!enabled a full boot. I >could not get to drive ID=2 in an ONLINE state. I mounted drive ID=2 to >initialize and change its volume name to.match the old volume name. >Next I returned systartup to mount drive id=2 (dkb200), and finally >rebooted into a normal system. > >The trial and error associated with all that was a useful learning >experience. > >Guessing there us a way from the >>> prompt to change a drive's volune, >but I did not find a way to do it. >From the dead sergeant, you can select a boot device. Volume information -- label, structure, ownership, etc., etc. -- are manifestated in the operating system (VMS). If you had an issue with the device on SCSI id 2, you could have physically removed that drive. The device would then not appear in the device configuration and the MOUNT command would fail: %MOUNT-F-NOSUCHDEV, no such device available Assuming there is no ON ERROR in the startup procedures, your system should then boot through the system startup to the point where you can login. At that point, you can reconnect the device and issue: $ MCR SYSGEN AUTOCONFIGURE ALL Then, a: $ SHOW DEVICE D should show you your disk devices including the device at DKx200:.

2 2

OT: Test
by Jeffrey Brace 09 Oct '17

09 Oct '17

Where is my message?

2 1

Festivus 2017 Dec. 9 & 10 - Signup
by Jeffrey Brace 08 Oct '17

08 Oct '17

Signup here: https://docs.google.com/spreadsheets/d/1odmPxfBK9BrR-NDZIx4_c-V2lZpt_-vU-3f…

2 1

Re: [vcf-midatlantic] vax scsi questions
by VAXman＠tmesis.org 08 Oct '17

08 Oct '17

william degnan via vcf-midatlantic writes: >> >> Some MicroVAXes in the 3100 series came with two SCSI busses. There >> are designated A and B. The SCSI id for the MicroVAX controller was >> typically 7; so devices could be attached with ids from 0 to 6. The >> naming of the devices, when VMS is booted are: >> >> ddcn: when dd is the name of the driver controlling the device. If >> the device is disk, this is DK (DKDRIVER). If the device is a tape, >> it's MK (MKDRIVER). The 'c' in the device designation if the adapter >> upon which the device is located. If there are two adapters, this is >> either A or B. The 'n' is the device number. Unless you're looking >> as a dvices served from a storage controller, the sub-LUN vallues are >> 0. So on your MicroVAX, you see somehting like a DKA300: for a disk >> addressed as SCSI id 3 on the A adapter. >> >> If you need more info, ask. > >This applies exactly, thanks. >Bill I should take this time to mention that there's also a GKDRIVER (generic SCSI); albeit, you'll need to connect that driver manually to the appro- priate SCSI id. I used to use a large HP bed scanner; it was SCSI based. Via the GKDRIVER, there was software that would allow me to scan pictures, documents, and whatever else I might place upon the scanner bed.

2 1

FS: Two Processor Tech 4KRA 4K Static RAM S-100 Boards Tested/Working
by systems_glitch 08 Oct '17

08 Oct '17

Board #1: http://www.ebay.com/itm/272879702807 Board #2: http://www.ebay.com/itm/272879706168 I'm guessing both of these boards were used in the previous owner's Altair 8800 until they had RAM failures, and were likely replaced with something newer and less power-hungry. These are one of Processor Tech's earlier S-100 boards, and they use 32x low-power (for the time!) 2102 static RAMs. Both boards have been repaired and fully tested in my IMSAI 8080 with a 2 MHz 8080 CPU board. The first one is fully socketed and had five dead SRAMs. The second is not socketed and had one dead SRAM, which was replaced with a machine pin socket. The second one used soldered jumpers for address selection, so I switched it over to machine pin sockets for easy re-addressing. I'd suggest that these boards not be purchased by someone wanting a static RAM board for general debugging -- they're low-density, I don't believe they support the *PHANTOM line, 2102s aren't the world's most reliable SRAM, etc. They'd go nicely with an original Altair 8800 (especially if you have a CUTS system!) or SOL-20. Thanks, Jonathan

1 0

FS: Processor Tech VDM-1 Video Board Tested/Working
by systems_glitch 08 Oct '17

08 Oct '17

link: http://www.ebay.com/itm/272879570374 This board had some trace damage in the address jumper area, which was repaired by installing machine pin sockets in all of the address jumper positions. One position had the through-hole completely pulled out, with no pads on either side -- the trace to this pin was repaired, and the pin secured in place with two-part epoxy. After repair to the address jumper area, it was found that the DM8131 address decoder was bad, this was replaced with a NOS part. As shown in the listing, this board is now 100% functional and tests out according to the Processor Tech manual. It was tested in my IMSAI 8080 with an Intel 8080 CPU board. Do note that this is an older design and requires I/O addresses to be mirrored (high byte should be the same as low byte). This is standard for 8080/8085 CPU boards, but other CPU boards (e.g. Z80) may not support it, or may require a jumper change. Thanks, Jonathan

1 0

Re: [vcf-midatlantic] vax scsi questions
by VAXman＠tmesis.org 08 Oct '17

08 Oct '17

Jim Scheef via vcf-midatlantic writes: >Bill, Are the two SCSI port two separate bus or two ports on the same >bus (controller)? If there is only one bus, terminate the empty >connector. If there are two bus, turn off the empty bus. This is >standard SCSI. Duplicate SCSI ID's are a no-no and must be fixed. All >devices on the bus must has a unique ID. Hope this is what you asked. >Jim Which MicroVAX 3100 model? In general, each device on a SCSI bus must have a unique SCSI address. If, for example, two drives are address as SCSI id 3, you'll find you will have issues with both or corrupt one or both drives. Typically, the MicroVAX startup firmware will probe the SCSI bus and complain if there are SCSI id conflicts. Some MicroVAXes in the 3100 series came with two SCSI busses. There are designated A and B. The SCSI id for the MicroVAX controller was typically 7; so devices could be attached with ids from 0 to 6. The naming of the devices, when VMS is booted are: ddcn: when dd is the name of the driver controlling the device. If the device is disk, this is DK (DKDRIVER). If the device is a tape, it's MK (MKDRIVER). The 'c' in the device designation if the adapter upon which the device is located. If there are two adapters, this is either A or B. The 'n' is the device number. Unless you're looking as a dvices served from a storage controller, the sub-LUN vallues are 0. So on your MicroVAX, you see somehting like a DKA300: for a disk addressed as SCSI id 3 on the A adapter. If you need more info, ask.

2 1