Re: Building I64 bootable OpenVMS media on Alpha

On Mar 8, 4:48 pm, Stephen Hoffman <H...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
johnhreinha...@xxxxxxxxx wrote:
My Alpha system that I'm trying to build this on is a V8.2. Should I
upgrade to V8.3? Would that help with the tools at all?

If you are restricted to what is supported by HP OpenVMS, then the El
Torito structures are likely what can be officially expected and
required, and what Mr. Kleinsorge indicates is undoubtedly correct.

El Torito is a disk partitioning scheme built on ISO-9660 structures,
and it's one of the ways to boot EFI off various media. Basically, the
ISO-9660 and El Torito partitioning structures are overlaid onto an
ODS-style disk, and the two are merged together. (There's a technique
around for initializing an ODS-2 or ODS-5 disk with the region of the
disk that is required for the ISO-9660 and El Torito structures
reserved, but that's fodder for another discussion.)

There are other and unsupported paths that are available toward
bootable media that are present in the EFI specifications, and that have
been empirically found to work correctly with optical media devices.
And that can boot OpenVMS I64.

Details on the alternative CD and DVD media bootstraps? Wander over
to the oldwww.HoffmanLabs.comweb site, find the link over to the new
HoffmanLabs website at the top of the main page of the old site, and go
looking for the document "LabsNotes: Recording CD and DVD Media on
OpenVMS" at the new site. It's at /node/28, too. Hopefully everything
you want to know about recording disks, including how to master and
generate recordable media, as well as generating bootable media for
OpenVMS I64 and for OpenVMS Alpha, is included in that document.

The mastering description does not use and does not require the El
Torito and the ISO-9660 structures. I would certainly expect that Mr.
Kleinsorge would indicate the approach is unsupported. But it can and
does boot on EFI, so it may well address your requirements pending the
availability of supported El Torito and ISO-9660 mastering tools for
OpenVMS.

Hoff

--www.HoffmanLabs.com
Services for OpenVMS

Okay. Actually, I'm way ahead of you there because I had already
created an account on your new site (looks great BTW) and scoured the
whole thing (all the blogs back to early January and the other
miscellaneous postings) for any information on DVD mastering. I have
the LabNote you mentioned and also the OpenVMS tip on EFI and ODS-2
and ODS-5 (which is how I got the sys$setboot info posted
previously). My problem in the procedure comes at this step:

$ @SYS$SYSTEM:I64VMS$PCSI_INSTALL_MIN.COM LDA4700:

My Alpha V8.2 system doesn't have that command procedure anywhere. It
does, however, have AXPVMS$PCSI_INSTALL_MIN.COM. But I've looked at
the code and I can't see how it would create an I64 bootable piece of
media.

Moving on, my second attempt was also a failure. This is what I did -
if you spot any problems, please point them out.

1) LD CREATE DSA2:[LDD]I64083.IMG/SIZE=5668992
2) LD CONNECT DSA2:[LDD]I64083.IMG LDA2:
3) INIT/ERASE/GPT/CLUSTER=16 LDA2: I64083
4) MOUNT /OVER=ID LDA2:
5) BACKUP LDA1:[VMS$COMMON...]*.*;* LDA2:[*...]/LOG <-- Copy
the common OpenVMS system files
6) BACKUP LDA1:[SYS0...]*.*;*/EXCLUDE=([SYS0.SYSCOMMON...]*.*;*) LDA2:
[*...]/LOG <--- Copy one set of system root specific files
7) SET FILE /ENTER=LDA2:[SYS0]SYSCOMMON.DIR LDA2:[000000]VMS
$COMMON.DIR <-- Create the alias for the common files in the root.
8) SET FILE /ENTER=[000000]SYS1.DIR [000000]SYS0.DIR <---
Repeated for system roots sys2 - sys10

9) $ BACKUP LDA1:[ALPHA_TOOLS...]*.*;* LDA2:[*...]/LOG \
$ BACKUP LDA1:[AVAILMAN_I64026...]*.*;* LDA2:[*...]/LOG \
$ BACKUP LDA1:[AVAIL_MAN_BASE...]*.*;* LDA2:[*...]/LOG /
Repeated for all install kits on the DVD
$ BACKUP LDA1:[CDSA_I64022...]*.*;* LDA2:[*...]/LOG /

10) SET BOOTBLOCK/BLOCK_SIZE=2048/IA64 LDA2:
11) LD CONNECT DSA2:[LDD]I64083.IMG LDA2:
12) DSA2:[LDD]i64083.IMG is FTPed in binary mode to my Mac OS X system
and written to a DVD.

Here is the dump of the boot structure from sys$setboot.exe

$ sb -s -f lda2:
OpenVMS SETBOOT version V5.0-4
Boot Architecture : IA-64
Boot Address : 0x00004824 : 000000018468
Boot Size : 0x00001f40 : 000000008000
Boot Identifier GUID : C12A7328F81F11D2BA4B00A0C93EC93B
Boot Signature GUID : 4065000400AA488311DBCDE817180ED0
Master Boot Record : Protective MBR


When I put the DVD in the ZX2000 is a difference in the device mapping
table in the EFI shell. I have two additional block devices, however
I have no additional file structured devices:
blkA: Acpi(HWP0002,500)/Pci(2|0)/Ata(Secondary,Master)
blkB: Acpi(HWP0002,500)/Pci(2|0)/Ata(Secondary,Master)/
HD(Part1,SigC9B73EB7)

If I dump the first 2048 bytes of the blkA device I get:

Logical block number 0 (00000000), 512 (0200) bytes

74737973 20343649 20534D56 6E65704F 206E6120 73692073 69685420
34303030 0004 This is an OpenVMS I64 syst 000000
68742072 65746C61 20746F6E 206F6420 65736165 6C502020 2E6B7369
64206D65 em disk. Please do not alter th 000020
69687420 6E6F6974 69747261 702D6572 20726F6E 202C5450 47202C52
424D2065 e MBR, GPT, nor re-partition thi 000040
6F442020 2E746920 74707572 726F6320 756F7920 7473656C 202C6B73
69642073 s disk, lest you corrupt it. Do 000060
296E4B4C 4220726F 206E5346 28205450 47206E6F 20646E65 70656420
746F6E20 not depend on GPT (FSn or BLKn) 000080
00000000 00000000 00000000 00000000 00000000 00002167 6E697265
64726F20 ordering!...................... 0000A0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0000C0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0000E0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000100
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000120
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000140
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000160
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000180
00000000 C9B73EB7 00000000 00000000 00000000 00000000 00000000
00000000 ........................?>??.... 0001A0
00000000 00000000 00000000 00000000 00000015 A01F0000 00010000
00EE0000 ..?............................. 0001C0
AA550000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ..............................U? 0001E0

Logical block number 1 (00000001), 512 (0200) bytes

00000000 00000001 00000000 C54F24BF 0000005C 00010000 54524150
20494645 EFI PART....\...?$O?............ 000000
11DBCDE8 17180ED0 00000000 00159FFE 00000000 00000022 00000000
0015A01F ........".......?.......?...???. 000020
00000000 C177FD3D 00000080 00000080 00000000 00000002 40650004
00AA4983 .I?...e@................=?w?.... 000040
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000060
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000080
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0000A0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0000C0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0000E0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000100
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000120
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000140
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000160
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000180
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001A0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001C0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001E0

Logical block number 2 (00000002), 512 (0200) bytes

40650004 00AA4883 11DBCDE8 17180ED0 C12A7328 F81F11D2 BA4B00A0
C93EC93B ;?>?..K??..?(s*??...???..H?...e@ 000000
006E0065 0070004F 00000000 00000000 00000000 00006763 00000000
00004824 $H......cg..............O.p.e.n. 000020
002E0049 00460045 00240053 00590053 00200034 00360049 00200053
004D0056 V.M.S. .I.6.4. .S.Y.S.$.E.F.I... 000040
00000000 00000000 00000000 00000000 00000000 00000000 00000053
00590053 S.Y.S........................... 000060
40650004 00AA4783 11DBCDE8 17180ECF 04010004 00AA448B 11D7DE65
0000000B ....e??..D?.....?...???..G?...e@ 000080
006E0065 0070004F 00000000 00000000 00000000 00004823 00000000
00000000 ........#H..............O.p.e.n. 0000A0
0020006B 00730069 00440073 00790053 00200034 00360049 00200053
004D0056 V.M.S. .I.6.4. .S.y.s.D.i.s.k. . 0000C0
00000000 00000000 00000000 006F004C 00200079 0061006C 00720065
0076004F O.v.e.r.l.a.y. .L.o............. 0000E0
40650004 00AA4783 11DBCDE8 17180ED0 04010004 00AA448B 11D7DE65
0000000C ....e??..D?.....?...???..G?...e@ 000100
006E0065 0070004F 00000000 00000000 00000000 00000000 00000000
00006764 dg......................O.p.e.n. 000120
0020006B 00730069 00440073 00790053 00200034 00360049 00200053
004D0056 V.M.S. .I.6.4. .S.y.s.D.i.s.k. . 000140
00000000 00000000 00000000 00690048 00200079 0061006C 00720065
0076004F O.v.e.r.l.a.y. .H.i............. 000160
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 000180
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001A0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001C0
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 ................................ 0001E0

and all nulls for the rest of the block.

At the end it prints out the following:

Valid MBR
---------
Partition 0 OS EE Start 0x00000001 Size 0x0015A01F
Partition 1 OS EE Start 0x00000000 Size 0x00000000
Partition 2 OS EE Start 0x00000000 Size 0x00000000
Partition 3 OS EE Start 0x00000000 Size 0x00000000

If I dump the first 2048 bytes of blkB I get all nulls (zeros).

The system still won't boot and I assume it is because EFI cannot find
the filesystem. All it sees is the block device.

Any thoughts?

John H. Reinhardt



.

Relevant Pages

  • Re: LD container for DVD image
    ... ensuring that the entire LD container is full of zero'ed disc blocks first, ... This note summarises the commands and operations needed to create OpenVMS ... are common with the creation of bootable optical media for Alpha and VAX. ... the container as an image to a DVD. ...
    (comp.os.vms)
  • Re: Cant burn recorded tv to DVD!
    ... Does anybody know why Media Centre won't let me burn recorded TV ... When I try to burn a recorded tv program onto dvd, ... UDF format a RW disk and to view that disk on another computer it ...
    (microsoft.public.windows.mediacenter)
  • Re: AKICIF: Television Formats
    ... I checked on Newegg and I see what appears to be good quality DVD ... about 10 times the price of DVD burners. ... Blu-ray media is also a lot more expensive, ... Premium dual-layer is about $1.45 per disk. ...
    (rec.arts.sf.fandom)
  • Re: Cant read movie maker DVD
    ... promptly closes to use DVD Maker instead. ... the disk and goes to the completed project message. ... play it on a DVD player connected to my TV, I get a "Cannot Read Disk" ... The disk will play with Media Player on the computer. ...
    (microsoft.public.windowsmedia)
  • Re: Movie Maker and Sonic DigitalMedia Conflict
    ... that is the software used to create and burn the DVD. ... program seems to stop recording anything or locks up. ... DISK Drive works ok. ... Media Movie Maker Ver ...
    (microsoft.public.windowsxp.moviemaker)