topic Re: Booting install CD emulation problem in Operating System - HP-UX

Booting install CD emulation problem

Tim Nelson — Mon, 11 Dec 2006 12:41:00 GMT

I see this mentioned a couple times but just cannot find the resolution.

When booting the June 2003 HPUX 11iv1 using my laptop I am having problems getting my emulation to work. Tried all emulation types.

Screen is garbage when the installer screen boots. There is also a note just before that saying that the terminal type is set to HP but this does not match my console device.

This RP7420 does not option to change emulation at CM level unless I am missing something. VFP says term type is ansi.

I was thinking to update the FW to 3.3 but wanted to check with the forum before I went that far.

Any ideas ?

Re: Booting install CD emulation problem

Torsten. — Mon, 11 Dec 2006 13:00:59 GMT

Hi,

if you use hyperterminal you should set the emulation to Vt100 instead of ansi - this should work.

Re: Booting install CD emulation problem

Steven E. Protter — Mon, 11 Dec 2006 13:07:58 GMT

Shalom,

From a serial console you should use EM100 emulation.

Otherwise I'd think that vt100 or vt220 is the TERM variable to use for the install.

I think the June 2003 CD is three years out of date for HP-UX. I think the June 2006 CD/DVD will save you a lot of post installation patching.

SEP

Re: Booting install CD emulation problem

Tim Nelson — Mon, 11 Dec 2006 13:31:39 GMT

Thanks Guys.

The message on the Install screen says that it thinks the install screen emulation is HPTERM. My hyperterm connection is set to vt100.

I found a June 2006 HPUX 11iv2. I will try this instead and see if that effects the issue.

Will let you know.

Re: Booting install CD emulation problem

Patrick Wallek — Mon, 11 Dec 2006 14:15:39 GMT

You can change this within GSP.

Do a CTRL-B to get into GSP mode.

Then at the prompt type 'CA'.

This will give you a list of things it can change and the terminal should be one of them.

Here is a log of changing the term type from my N4000:

GSP> ca

CA

This command allows you to modify the local and remote modem serial port
configurations. Current configuration settings:

Local Console Serial Port bit rate: 9600 bits/s
Local Console Serial Port Flow Control: Software
Local Console Serial Port Terminal Type: vt100
Remote Console Serial Port Modem Protocol: CCITT
Remote Console Serial Port Modem bit rate: 19200 bits/s
Remote Console Serial Port Modem Flow Control: Software
Remote Console Serial Port Modem Transmit Configuration Strings: Enabled
Remote Console Serial Port Modem Presence: always connected

Do you want to modify the Local Console Serial Port settings? (Y/[N]) Y

Y

Current Local Console Serial Port bit rate: 9600 bits/s
Do you want to modify it? (Y/[N])

Current Flow Control: Software
Do you want to modify it? (Y/[N])

Current Terminal Type: vt100
Do you want to modify it? (Y/[N])
y
Enter Terminal Type ([Vt100] / Hpterm): vt100
vt100
New Terminal Type: vt100
Confirm? (Y/[N]): y
y
-> Terminal Type will be updated.

Do you want to modify the Remote Console Serial Port Modem settings? (Y/[N])

Command execution may take 25 seconds.

-> Settings have been updated.

Re: Booting install CD emulation problem

Bill Hassell — Mon, 11 Dec 2006 17:49:12 GMT

This is one of those crazy gotchas with the GSP. The GSP destroys any meaning to the terminal emulation you are using when you run HP-UX code such as ttytype or tset. Instead of asking your terminal emulation to identify itself, it completely ignores the terminal and sets the TERM value to whatever is stored in the GSP. The default for the GSP from the factory is vt100 which generally matches most PC emulators. About the only time you want to change the GSP to HPTERM (which is *not* the Xwindows hpterm program, just a GSP term for HP terminal) is when all your console access is through an HP terminal such as the 700/xx series or an HP terminal emulator such as QCterm or Reflection-for-HP.

So to fix this, follow the GSP instructions above and check that none of your other GSP's are set to HPTERM if you plan on using dumb vt100 emulators. Note that the OS installer runs fine on vt100 but once you are booted, the vt100 emulation is particularly annoying for SAM, swinstall and Glance. Since this override ONLY occurs on the GSP console port, it is not usually a big issue (run these tools on a network connection).

Re: Booting install CD emulation problem

Maria W. Bennett — Tue, 12 Dec 2006 11:27:04 GMT

I just had the exact same problem with an older rev of firmware on an N-Class. The GSP does not have the option for emulator. I had to hook the LAN console to a hub and then plug my laptop with Exceed on it into the same hub. I assigned them 10.X.X.X IP addresses and continued on with the install of 11.11.

Re: Booting install CD emulation problem

Tim Nelson — Tue, 06 Mar 2007 16:08:54 GMT

Just an update on this as I forgot to follow up and I just ran into this again.

If you use the http:// interface you can select the HPTerm java emulator.

The installation screen for the June of 2003 media uses the HPTERM emulation.