Just a reminder that the DEC Legacy Event is nearly upon us!
October 8/9 in Windermere, more information here: http://declegacy.org.uk
The exhibits page gives a summary of the hardware that will be making an appearance: http://wickensonline.co.uk/declegacy/hardware
I'm in the process of securing an internet connection. Hopefully I'll be connecting a couple of my boxes to HECnet over the course of the weekend, to show participants what they're missing out on.
Regards, Mark.
On 6 Sep 2011, at 07:30, Ian McLaughlin wrote:
When I dd'd off a copy of the VAX VMS CD-ROM it didn't work for me initially either. Now I can't remember which way round it was now, but I think I dd'd the whole CD-ROM and it didn't work and then I dd'd off only the *partition* with the data in and that worked fine. Either that or the other way around. From the looks of the quote above you only need the partition.
Memory is terrible, sorry :)
On my system (CentOS 5.6) I see the /dev/cdrom device which is symbolically linked to /dev/hda (which makes sense - it's the only IDE device I have in the machine). There is no hda1 or other devices for the partitions. fdisk /dev/hda comes back with an invalid partition table.
I remember how it went now - I was doing it on a Mac which uses a BSD disk structure. I dd'd the disk device (/dev/disk6) and it wouldn't work. I then dd'd the slice that reported as the actual volume (/dev/disk6s0) and it worked a charm.
I don't know how that's represented in Linux, however. Also fdisk won't show a partition table for a CD-ROM, I don't believe, because they are not structured as hard drive partitions. I put my VMS VAX CD-ROM in my Ubuntu box and the Disk Utility reports it at /dev/sr0 which is a SCSI ID but my Microserver has a weird disk controller.
I honestly don't know how to approach it unless you have something like gnuparted to hand to look at the disk?
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
On 2011-09-05, at 11:21 PM, Mark Benson wrote:
On 6 Sep 2011, at 06:52, hvlems at zonnet.nl wrote:
The dd command ought to produce a bootable copy of the cdrom. On Tru64 the correct partition is
If=/dev/disks/ cdrom0c
When I dd'd off a copy of the VAX VMS CD-ROM it didn't work for me initially either. Now I can't remember which way round it was now, but I think I dd'd the whole CD-ROM and it didn't work and then I dd'd off only the *partition* with the data in and that worked fine. Either that or the other way around. From the looks of the quote above you only need the partition.
Memory is terrible, sorry :)
On my system (CentOS 5.6) I see the /dev/cdrom device which is symbolically linked to /dev/hda (which makes sense - it's the only IDE device I have in the machine). There is no hda1 or other devices for the partitions. fdisk /dev/hda comes back with an invalid partition table.
Ian
On 6 Sep 2011, at 06:52, hvlems at zonnet.nl wrote:
The dd command ought to produce a bootable copy of the cdrom. On Tru64 the correct partition is
If=/dev/disks/ cdrom0c
When I dd'd off a copy of the VAX VMS CD-ROM it didn't work for me initially either. Now I can't remember which way round it was now, but I think I dd'd the whole CD-ROM and it didn't work and then I dd'd off only the *partition* with the data in and that worked fine. Either that or the other way around. From the looks of the quote above you only need the partition.
Memory is terrible, sorry :)
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
The dd command ought to produce a bootable copy of the cdrom. On Tru64 the correct partition is
If=/dev/disks/ cdrom0c
Your unix flavor may be different.
Or use a cdwriter program that writes to disk, like Nero on Windows does.
Verzonden vanaf mijn draadloze BlackBerry -toestel
From: Ian McLaughlin <ian at platinum.net>
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 5 Sep 2011 22:41:35 -0700
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Subject: Re: [HECnet] SIMH on CentOS 5.6
Thanks for the response. I think my issue has something to do with making the ISO image. I used 'dd if=/dev/cdrom of=cd.iso' which made a 676Mb file. But using this file gives me the error. I then tried attaching directly to the cdrom drive in vax.ini using 'attach -r rq3 /dev/cdrom' and it worked! I was able to do a full installation from the actual physical media.
Does anyone have any pointers for making an ISO image of the CD? Am I doing it wrong? I would like to make a backup of the disk because I'm already on my second physical copy and would like to back it up before I lose it again :)
Ian
On 2011-09-05, at 10:20 PM, hvlems at zonnet.nl wrote:
While in simh commandmode, show the devices that are seen in simh.
Do the same in srm mode: sho dev
The boot device type may be DK, RQ or DQ, I forgot
You must have typed it in: to assign the hosts cd drive to a iunit name.
Verzonden vanaf mijn draadloze BlackBerry -toestel
From: Ian McLaughlin <ian at platinum.net>
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 5 Sep 2011 15:57:38 -0700
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Subject: [HECnet] SIMH on CentOS 5.6
Hello All,
I'm trying to compile and run SIMH on CentOS 5.6. I've followed the instructions at http://www.wherry.com/gadgets/retrocomputing/vax-simh.html but when I try to boot from the CD image, I get:
[root at zork data]# /usr/local/vax/bin/vax
VAX simulator V3.8-1
NVR: buffering file in memory
RQ: unit is read only
Eth: opened eth0
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua3
(BOOT/R5:0 DUA3
2..
-DUA3
?42 NOSUCHFILE, DUA
HALT instruction, PC: 00000C1A (MOVL (R11),SP)
sim>
Any ideas about what I might be doing wrong? The CD image file I made directly from the Montagar 7.3 CD. The vax.ini file is exactly as shown on the instructions page.
Thanks in advance for any suggestions!
Ian
---
Filter service subscribers can train this email as spam or not-spam here
Thanks for the response. I think my issue has something to do with making the ISO image. I used 'dd if=/dev/cdrom of=cd.iso' which made a 676Mb file. But using this file gives me the error. I then tried attaching directly to the cdrom drive in vax.ini using 'attach -r rq3 /dev/cdrom' and it worked! I was able to do a full installation from the actual physical media.
Does anyone have any pointers for making an ISO image of the CD? Am I doing it wrong? I would like to make a backup of the disk because I'm already on my second physical copy and would like to back it up before I lose it again :)
Ian
On 2011-09-05, at 10:20 PM, hvlems at zonnet.nl wrote:
While in simh commandmode, show the devices that are seen in simh.
Do the same in srm mode: sho dev
The boot device type may be DK, RQ or DQ, I forgot
You must have typed it in: to assign the hosts cd drive to a iunit name.
Verzonden vanaf mijn draadloze BlackBerry -toestel
From: Ian McLaughlin <ian at platinum.net>
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 5 Sep 2011 15:57:38 -0700
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Subject: [HECnet] SIMH on CentOS 5.6
Hello All,
I'm trying to compile and run SIMH on CentOS 5.6. I've followed the instructions at http://www.wherry.com/gadgets/retrocomputing/vax-simh.html but when I try to boot from the CD image, I get:
[root at zork data]# /usr/local/vax/bin/vax
VAX simulator V3.8-1
NVR: buffering file in memory
RQ: unit is read only
Eth: opened eth0
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua3
(BOOT/R5:0 DUA3
2..
-DUA3
?42 NOSUCHFILE, DUA
HALT instruction, PC: 00000C1A (MOVL (R11),SP)
sim>
Any ideas about what I might be doing wrong? The CD image file I made directly from the Montagar 7.3 CD. The vax.ini file is exactly as shown on the instructions page.
Thanks in advance for any suggestions!
Ian
---
Filter service subscribers can train this email as spam or not-spam here
While in simh commandmode, show the devices that are seen in simh.
Do the same in srm mode: sho dev
The boot device type may be DK, RQ or DQ, I forgot
You must have typed it in: to assign the hosts cd drive to a iunit name.
Verzonden vanaf mijn draadloze BlackBerry -toestel
From: Ian McLaughlin <ian at platinum.net>
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 5 Sep 2011 15:57:38 -0700
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Subject: [HECnet] SIMH on CentOS 5.6
Hello All,
I'm trying to compile and run SIMH on CentOS 5.6. I've followed the instructions at http://www.wherry.com/gadgets/retrocomputing/vax-simh.html but when I try to boot from the CD image, I get:
[root at zork data]# /usr/local/vax/bin/vax
VAX simulator V3.8-1
NVR: buffering file in memory
RQ: unit is read only
Eth: opened eth0
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua3
(BOOT/R5:0 DUA3
2..
-DUA3
?42 NOSUCHFILE, DUA
HALT instruction, PC: 00000C1A (MOVL (R11),SP)
sim>
Any ideas about what I might be doing wrong? The CD image file I made directly from the Montagar 7.3 CD. The vax.ini file is exactly as shown on the instructions page.
Thanks in advance for any suggestions!
Ian
The KZPSA is a differential scsi controller. It supports dual hosts and may be used as a cluster interconnect (data only, no cluster control messages).
------Origineel bericht------
Van: Peter Coghlan
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] And yet more begging: KZPAC style controller?
Verzonden: 6 september 2011 00:49
Here's a photo of mine, can you draw the bit I need to change onto it, or the general area:
http://sampsa.com/wp-content/kzstyleboard.jpg
That picture reminded me of something. I have what I thought was an extra long
and overly complex PCI SCSI card in my stash. It has the same Intel i960 as
the card in the picture but doesn't have the extra daughter board. It is
marked KZPSAPS and has a single 68 pin external SCSI connector and five
resistor packs commonly found as terminators on old-style (ie non-low-voltage)
differential SCSI cards.
I tried firing it up in my AS1000A and found that SRM sees it as follows:
SHOW CONF
12 DEC KZPSA pke0.7.0.12.0 SCSI Bus ID 7
SHOW DEV
pke0.7.0.12.0 PKE0 SCSI Bus ID 7 R01 A11
VMS (7.1-2) sees it as:
Device PKA0:, device type KZTSA/SCSI (SIMport), is online, error logging is
enabled.
Error count 0 Operations completed 24
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size 0
Anyone know what (if anything) is special about this card?
Regards,
Peter Coghlan.
Verzonden vanaf mijn draadloze BlackBerry -toestel
On 11-09-05 05:28 PM, Sampsa Laine wrote:
Oh the complexities of the world we live in:
Nah, there's nothing to it. There's just a lot of nothing. :)
Phil
So I'm willing to live with the single storage array I have for now, and am thinking of acquiring say off ebay, a second controller.
Which model should I go for? I only need one port but would like it to support as large a logical drive as possible (well, I've got 7x18 GB drives in a stack to use)..
Suggestions?
