Trouble installing VMS AXP Hobbyist on a PWS 600au
Wesley Dunnahoo
600au that used to contain Debian Linux. I can load Windows NT but
receive an error when I try to boot the Hobbyist version of the CD-ROM
(see below). Any help would be extremely appreciated.
Thanks,
Wesley
SRM details:
Digital Personal WorkStation 600au
Console V7.2-1 Mar 6 2000 14:47:02
Environment variable srm_boot created
pmem: 0 00023E7C00000000
>>>
>>>show device
dka0.0.0.1010.0 DKA0 RZ1CB-BA LYE0
dka400.4.0.1010.0 DKA400 PIONEER DVD-ROM DVD-303R 1.06
dva0.0.0.0.1 DVA0
ewa0.0.0.3.0 EWA0 00-00-F8-75-5C-3B
pka0.7.0.1010.0 PKA0 SCSI Bus ID 7 5.57
pqa0.0.0.4.0 PQA0 PCI EIDE
pqb0.0.1.4.0 PQB0 PCI EIDE
>>>
>>>show conf
Firmware
SRM Console: V7.2-1 Mar 6 2000 14:47:02
ARC Console: 5.70
PALcode: OpenVMS PALcode V1.20-16, Tru64 UNIX PALcode V1.22-18
SROM Version: v5.90
Processor
DECchip (tm) 21164A-2 Pass 600MHz 96 Kbytes SCache
0 MB BCache
PYXIS ASIC Pass 257
MEMORY
Memory Size = 640Mb
Bank Size/Sets Base Addr
------ ---------- ---------
0 256Mb 00000000
1 256Mb 10000000
2 128Mb 20000000
BCache Size = 0Mb
Tested Memory = 640Mbytes
PCI Bus
Bus 00 Slot 03: Digital Semiconductor 21143 Network Controller
ewa0.0.0.3.0 00-00-F8-75-5C-3B
Bus 00 Slot 04: PCI IDE
pqa0.0.0.4.0 PCI EIDE
Bus 00 Slot 07: Intel SIO 82378
Bus 00 Slot 11: Matrox Millenium
Bus 00 Slot 20: DECchip 21052 PCI to PCI Bridge
Bus 01 Slot 09: Vendor: 9005 Device: 80 sub_id: e2a09005
Bus 01 Slot 10: ISP1040 Scsi Controller
pka0.7.0.1010.0 SCSI Bus ID 7
dka0.0.0.1010.0 RZ1CB-BA
dka400.4.0.1010.0 PIONEER
DVD-ROM DVD-ISA
Slot Device Name Type Enabled BaseAddr IRQ DMA
0
0 Mouse Embedded Yes 60 12
1 KBD Embedded Yes 60 1
2 COM1 Embedded Yes 3f8 4
3 COM2 Embedded Yes 2f8 3
4 LPT1 Embedded Yes 3bc 7
5 FLOPPY Embedded Yes 3f0 6 2
6 EIDE Embedded Yes 1f0 14
3f6 15
170
376
7 ES1888 Singleport Yes 220 5 1
>>>
>>>show *
adv_diag off
auto_action HALT
boot_dev
boot_file
boot_osflags 0,0
boot_reset OFF
bootdef_dev
booted_dev
booted_file
booted_osflags
char_set 0
console graphics
controlp on
d_bell off
d_cleanup on
d_complete off
d_eop off
d_group field
d_harderr halt
d_loghard on
d_logsoft off
d_oper off
d_passes 1
d_quick off
d_report full
d_runtime 0
d_softerr continue
d_startup off
d_status off
d_trace off
dma_prefetch ON
dump_dev
enable_audit ON
ewa0_arp_tries 3
ewa0_bootp_file
ewa0_bootp_server
ewa0_bootp_tries 3
ewa0_def_ginetaddr 0.0.0.0
ewa0_def_inetaddr 0.0.0.0
ewa0_def_inetfile
ewa0_def_sinetaddr 0.0.0.0
ewa0_def_subnetmask 0.0.0.0
ewa0_ginetaddr 0.0.0.0
ewa0_inet_init bootp
ewa0_inetaddr 0.0.0.0
ewa0_inetfile
ewa0_loop_count 3e8
ewa0_loop_inc a
ewa0_loop_patt ffffffff
ewa0_loop_size 2e
ewa0_lp_msg_node 1
ewa0_mode Fast
ewa0_protocols MOP
ewa0_sinetaddr 0.0.0.0
ewa0_tftp_tries 3
exdep_data 23E7C00000000
exdep_location 8
exdep_size 8
exdep_space pmem
exdep_type 3
ffauto OFF
ffnext OFF
graphics_page 0
graphics_type VIDEO
kbd_hardware_type PCXAL
language 36
language_name English(American)
license MU
mop_debug OFF
mop_password 00-00000000-00000000
mop_version 1
mopv3_boot OFF
os_type OpenVMS
pal OpenVMS PALcode V1.20-16, Tru64 UNIX PALcode
V1.22-18
pci_device_override 0
pci_parity off
pka0_host_id 7
pka0_mode ultra
pka0_soft_term diff
quick_start OFF
scsi_poll ON
srm2ctrl
srm2dev
srm_boot on
sys_serial_num NI720035VB
tt_allow_login 1
tta0_page 0
tta0_type VIDEO
tty_dev 0
version V7.2-1 Mar 6 2000 14:47:02
>>>
>>>boot dka400 –flags 0,0
(boot dka400.4.0.1010.0 –flags 0,0)
block 0 of dka400.4.0.1010.0 is a valid boot block
reading 969 blocks from dka400.4.0.1010.0
bootstrap code read in
base = 1d8000, image_start = 0, image_bytes 79200
initializing HSRPB at 2000
initializing page table at 1ca000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
halted CPU 0
halt code = 5
HALT instruction executed
PC = 20067e80
>>>
Bradford J. Hamilton
!I've spent the past several weeks trying to install VMS on an old PWS
!600au that used to contain Debian Linux. I can load Windows NT but
!receive an error when I try to boot the Hobbyist version of the CD-ROM
!(see below). Any help would be extremely appreciated.
!
!Thanks,
!
!Wesley
!
!SRM details:
!snipped for relevance...!
!PCI Bus
! Bus 00 Slot 03: Digital Semiconductor 21143 Network Controller
! ewa0.0.0.3.0 00-00-F8-75-5C-3B
!
! Bus 00 Slot 04: PCI IDE
! pqa0.0.0.4.0 PCI EIDE
!
! Bus 00 Slot 07: Intel SIO 82378
!
This CDROM will not boot VMS...at least not easily, from my understanding
(folks, please jump in here if you have information to share...).
!snip!
! >>>boot dka400 –flags 0,0
!(boot dka400.4.0.1010.0 –flags 0,0)
!block 0 of dka400.4.0.1010.0 is a valid boot block
!reading 969 blocks from dka400.4.0.1010.0
!bootstrap code read in
!base = 1d8000, image_start = 0, image_bytes 79200
!initializing HSRPB at 2000
!initializing page table at 1ca000
!initializing machine state
!setting affinity to the primary CPU
!jumping to bootstrap code
!
!halted CPU 0
!
!halt code = 5
!HALT instruction executed
!PC = 20067e80
! >>>
!
__________________________________________________________________________
Bradford J. Hamilton "All opinions are my own"
bMradAhamiPltSon-at-coMmcAast.nPeSt "Lose the MAPS, and replace '-at-'
with @"
Tom Crabtree
<snip>
> >>>show device
> dka0.0.0.1010.0 DKA0 RZ1CB-BA LYE0
> dka400.4.0.1010.0 DKA400 PIONEER DVD-ROM DVD-303R 1.06
Here's your trouble. Even though it is SCSI _AND_ SRM sees it, VMS
doesn't know what it is, and does not know what to do with it.
It could be something as simple as the block size jumper or termination
jumper, or as fatal as 'it just won't work with VMS'.
If you want to boot to VMS, you'll have to add a VMS Compatible SCSI CDRom.
I see that you have the Miata MX5 version PWS600A(U) with the Intel SIO
IDE chipset, so an IDE CDRom isn't an option. If you had a Miata GL
with the Cypress chipset, you would have been able to boot from a $5.00
IDE CDRom.
Any of the DEC RRD series will do, as well as several models of Toshiba
SCSI CDRom's. I've also found the CDRom lurking in some models of Apple
computers work well too.
I'm willing to bet that your Pioneer DVDRom will work once VMS is
booted, i.e., you'll be able to load layered products with it, just not
the OS.
Good luck!
TomC
Craig A. Berry
Wesley Dunnahoo <wdun...@mindspring.com> wrote:
> I've spent the past several weeks trying to install VMS on an old PWS
> 600au that used to contain Debian Linux.
VMS version?
> Bus 00 Slot 07: Intel SIO 82378
This means you can't boot from an IDE device, so you are correct to try
using dka400 (see section 14.4.4.2 of the FAQ). However, I don't know
whether your Pioneer DVD-ROM will work. Does it support 512-byte block
transfers or have a switch, jumper, etc., that will enable such?
> Bus 00 Slot 11: Matrox Millenium
There is no VMS driver for this. You will need to acquire a supported
graphics controller. The supported options are here:
http://h18002.www1.hp.com/alphaserver/products/graphics/au/index.html
Be sure to read the FAQ:
Tom Crabtree
>> Bus 00 Slot 11: Matrox Millenium
>
>
> There is no VMS driver for this. You will need to acquire a supported
> graphics controller. The supported options are here:
Good catch. Didn't see that on the first pass through.
Yes, you will need an OpenVMS compatible graphics card, which is a
_very_ short list:
Powerstorm 3D30
Powerstorm 4D20
Powerstorm 4D10T (Elsa Gloria Synergy 8mb PCI)
Powerstorm 300
Powerstorm 350
S3 Trio64V
Permedia 2
3DLabs Oxygen VX1 (OpenVms 7.3 or higher)
Check eBay, saw a 3D30 the other day that went for ~$50.
TomC
Rich Jordan
not work on a PWS system; I think the Oxygen VX1 is also not supported
(that one is EV6 only last I heard).
Rich
Didier Morandi
> I've spent the past several weeks trying to install VMS on an old PWS
> 600au that used to contain Debian Linux. I can load Windows NT but
> receive an error when I try to boot the Hobbyist version of the CD-ROM
> (see below). Any help would be extremely appreciated.
As stated by others, the PWS600au has an IDE CD-ROM drive. It was intended to
run Unix or Windows NT. I have one.
I went to a shop, I purchased a SCSI CD-ROM and its flat cable. I opened the
box, changed the drive, closed the box, powered it on, put my favourite
operating system CD in the drive and today I have another uncle named Bob.
All this from the first screw to the last one has been pixed. I'll post the
HowTo for hardware newbies on the VAXUS site asap.
Cheers.
D.
--
VAXUS - Your new helpful friend in the DEC Family!
EHQ: 19 chemin de la Butte, 31400 Toulouse, France
Phone: +336 7983 6418 Fax: +335 6154 1928
http://www.vaxus.org
Island Computers USA
Powerstorm 3D30, 4D20 (PBXGB-AA, -CA)
Any Permedia 2 8MB SGRAM Card (PCI) (Includes Diamond FireGL Pro 1000, Elsa
GLoria Synergy, Io Magic etc Compaq 4D10)
S3Trio64 or 64V
The Oxygen will not work nor the Radeon 7500 PCI Card - Pwerstorm 300/350 I
think may work in VGA mode only
DT
"Rich Jordan" <duo...@speakeasy.net> wrote in message
news:QCudnU4e9vJ...@speakeasy.net...
Hoff Hoffman
:In article <gDSQb.24210$i4....@newsread1.news.atl.earthlink.net>,
: Wesley Dunnahoo <wdun...@mindspring.com> wrote:
:
:> I've spent the past several weeks trying to install VMS on an old PWS
:> 600au that used to contain Debian Linux.
:
:VMS version?
I would not install any release older than V7.1-2 on this box, and I
would strongly recommend use of V7.2-2, or V7.3-1 or later.
Also check that the console OS_TYPE variable is set to OpenVMS.
:> Bus 00 Slot 07: Intel SIO 82378
:
:This means you can't boot from an IDE device, so you are correct to try
:using dka400 (see section 14.4.4.2 of the FAQ). However, I don't know
:whether your Pioneer DVD-ROM will work. Does it support 512-byte block
:transfers or have a switch, jumper, etc., that will enable such?
The 512-byte sector requirements is applicable to SCSI devices.
Recent versions of DQDRIVER can de-block 2048 byte ATA or ATAPI
disk sectors just fine -- DQDRIVER reads the sector(s) underlying
the block reference, and returns the requested block(s).
The OpenVMS FAQ section "CD-R and DVD device requirements?" has
some related details. (I do see I missed an incomplete reference
to 512-byte disk block requirements over in another section of the
FAQ. Grumble. I've queued the fix for the next edition.)
:Be sure to read the FAQ:
:
:http://h71000.www7.hp.com/wizard/openvms_faq.html
FWIW, the h%%%%.www%.hp.com URLs are potentially transient and are
considered website-internal URL cross-links. Such internal URLs can
potentially be moved or can be changed.
The official external URL for the OpenVMS FAQ is:
And yes, the biggest problem here will be the graphics controller.
The Matrox is not supported by OpenVMS, you'll need to find a PCI
graphics controller that will work in the box and that has OpenVMS
support -- and I don't know that the Radeon 7500 PCI nor Oxygen VX1
device driver support extends as far back as the Personal Workstation
600au series platform.
---------------------------- #include <rtfaq.h> -----------------------------
For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com
Peter Weaver
news:eEbRb.13056$942....@news.cpqcorp.net...
>...
> FWIW, the h%%%%.www%.hp.com URLs are potentially transient
and are
> considered website-internal URL cross-links. Such
internal URLs can
> potentially be moved or can be changed.
Someone should tell the documentation writers that. Just so
happens that I am looking for information on AMDS, so I find
http://h71000.www7.hp.com/openvms/products/availman/6552pro.html.
Chapter 2 tells me to go to
http://h7100.www7.hp.com/openvms/products/availman/ for
installation instructions. Of course, seeing that the
documentation was written less than 1 year ago,
http://h7100.www7.hp.com/openvms/products/availman/ no longer
exists.
So please,
1. Someone tell the documentation writers not to use these
h71000.www7.hp.com/whatever addresses.
2. Someone tell HP in general that these
h71000.www7.hp.com/whatever addresses are a big problem for
their customers. (If they insist on using these at least they
can put a line at the top of every page saying "If you want to
access this page in the future then bookmark
http://www.hp.com/whatever and not
http:://h71000.www7.hp.com/whatever since we are going to move
http::/h71000.www7.hp.com/whatever at some random point in the
future just to annoy you!"
3. Someone tell me where I can find the documents on how to
install the AMDS data analyzer on VMS so I can work with some
machines on the other side of a firewall.
--
Peter Weaver
Weaver Consulting Services Inc.
Canadian VAR for CHARON-VAX
www.weaverconsulting.ca
Hoff Hoffman
You may well want to send your feedback directly along to the
site-wide webmaster directly, as I am not at all certain that any
of the messages posted here would be seen.
The OpenVMS Webmaster has added "/go" links for the OpenVMS FAQ
and other portions of the OpenVMS website I and others regularly
reference, which allows me static URL "/go" addresses I can then
publish.
Language and localization, geographic network routing considerations,
replication, and other such issues are not easy problems to resolve.
:3. Someone tell me where I can find the documents on how to
:install the AMDS data analyzer on VMS so I can work with some
:machines on the other side of a firewall.
You would have to open the firewall to the AMDS (and Availability
Manager) wire-level protocol. Off the top, I do not know which
802.3 protocol code might be used -- if the AMDS documentation does
not show it, some SDA commands will.
I'd tend not to open a firewall to this traffic, just because the
access and control tends to be incompatible with the usual purpose
of a firewall installation.
Peter Weaver
> You may well want to send your feedback directly along to
the
> site-wide webmaster directly, as I am not at all certain
that any
> of the messages posted here would be seen.
The problem is actually in the documentation, it says
h7100.www7 instead of h71000.ww7 so I sent a note to
openv...@hp.com to have that corrected. (But I still think
HP's web naming standard is terrible.)