Seriously, WHY would you do that? - Part 4

-

Episode 4 - "We have liftoff"



Last time, I got the RX2600 started up and failed to install OpenVMS because of a suspect hard drive.  From the screen shot above, you might observe that I have gotten OpenVMS installed and running on the machine.

 There were a bunch of issues.  The hard drive supplied with the system was bad, and it was not the original device if the butchered screws on the caddy were anything to go by.  The seller did offer to replace it for me, but since I have a box of replacements, I didn't take him up on the offer.  Needless to say, if I want another RX, I know where I will look first.

 The other curious issue is that the DVD drive is staggeringly slow.  It's not just OpenVMS, but also on RedHat.  Since it's not something you use much once the system is installed, HP didn't put much emphasis on it's performance.

 I'm not going to take you through the whole installation process, that's what the OpenVMS manuals are for, but I will give you a few hints I found useful.

 Boot the system with boot_ia64.efi which you will find in the "\EFI\VMS" directory of the DVD.  This should be "fs0:" in your EFI shell.

 Wait a few minutes (no, really) and you get the installation menu.  Choose "Install" (the first option) and go make a pot of coffee.  You might have time to harvest and roast the beans too.

 After an agonising wait you will get prompted whether to wipe or preserve the install disk.  Since mine was effectively a new disk, we want to choose "INITIALIZE"

You have to type INITIALIZE, so watch the spelling...

 Now comes the first real test of your hardware.  You will be prompted for the disk to install onto.  I would suggest entering '?' first of all, and confirming your device list.  In my case it was "DKA0".  If you don't have a disk in an "online" state, there's a problem you need to solve first.
There is a choice of filesystems for the system disk.  Actually on Alpha or IA64 there's always a choice of filesystems when preparing a new volume.  ODS5 is the current standard, and unless you intend to run an old application, there's probably no reason to select the older ODS2 filesystem.

 Next import question is whether to create or validate boot options.  This only appears on EFI (IA64) machines, and it's a really good idea to choose "Yes" for this one, because it creates an EFI boot manager entry:
Being lazy, not to mention inexperienced, I accepted the option to install default settings.

 When it comes to entering the PAK details, at this stage you really only need to enter the values for OpenVMS.  You can paste the other commands in once the system is up and running.  It's a tedious process, but it has to be done.

 After about an hour or so you will be greeted with the "installation is now complete" message.  Feel free to perform the victory celebration of your choice.

 But your work isn't over.  The system needs to restart, and configuration needs to be done.  More on that next time!


Comments

Post a Comment

Popular posts from this blog

The QYT KT-7900D

-
Image
But is it any good? As you might have noticed, I am now a freshly licensed radio amateur .  As such I do need a transceiver or two in order to get on the air.  This is the story of one of my new radios. I have a limited discretionary budget to use for my new hobby, and I have to say from the outset that my lovely wife has been very supportive.  As such, I want to try and get the best value for our money.  One evening I stumbled upon this little item on Banggood for a little over $A150 including shipping.  Covering both 2m and 70cm bands with a claimed 20W output it seemed almost too good to be true.  I bought one. About ten days later a tiny package arrived for me.  At just 98mm x 43mm x 126mm the photos don't convey quite how small it actually is.  The entire case serves as a heatsink so it is heavier than it looks, but certainly not bulky. The standard power cable comes with a cigarette lighter plug.  As I intended to run it from home using a regulated PSU, I just cut the plug o
Read more

Life with Deep Racer - Part 2

-
Image
 An Update on AWS Deep Racer OK, so AWS Summit Sydney has been run and won.  Not by us however, but there are few interesting tidbits to report: The console is now widely available This is actually pretty big news, because: The console ties together Robomaker, SageMaker and everything else you need in a convenient package There are actual examples of functions included It seems to stay running now There is new firmware for the car Also important; this includes a rolling update for the Ubuntu base as well as the Deep Racer specific bits.  WiFi connection seems more reliable now as well. Our car has a new look Since my employer (Versent) was generous enough to send me to Re:Invent last year (where I got the Deep Racer), I thought it appropriate to deck it out in the company colours, and it was well-received at Summit last week.
Read more

DIY Self-Driving - Part 9 - New Imaging

-
Image
Please Note:    Unlike most of my projects which are fully complete before they are published, this project is as much a build diary as anything else.  Whilst I am attempting to clearly document the processes, this is not a step-by-step guide, and later articles may well contradict earlier instructions. If you decide you want to duplicate my build, please read through all the relevant articles before you start. We have a lot of work to do in pretty short space of time now, with new competitive opportunities in the very near future. To be honest, the line detection has simply not been good enough, and this is leading to some of the poor performance I have been experiencing with the car.  Whilst it really does work, it is not accurate enough.  There are a couple of issues here which need to be dealt with: The core processor is just not powerful enough; and The optics aren't good enough Processing As I noted in my "Next Iteration" article I am looking at othe
Read more