Conference 49.910::kav30

    Very interesting as yesterday I got a customer call which told me that
    while trying to boot from the EPROM (b prb1) on his KAV30 system he
    gets a ?06 HALTINST at PC 1A03 ....
    Could it be possible to get quickly the patch you talk about and give it to
    this customer ? 
    Thanks for help.
    
    Jean-Pierre

	unfortunately the 'patch' isn't as easy as we thought in the first
	attempt (the ELN image has to be moved while copying from ROM to
	RAM...). We'll do our best to get it out this week...

	Thomas

    re: .1
    
    Hi Jean-Pierre,
    
    I just want to make sure that your customer is experiencing the problem
    described in 54.0.  Has your customer burnt their own VAXELN system
    image into EPROM?  Or are they using the B PRB1 option to boot off of a
    SCSI disk?
    
    Graham

    Hi Graham,
    
    The customer has burnt their own VAXeln image into EPROM and wants to
    boot it from them not from a disk.
    
    Jean-Pierre
    

    Hi Jean-Pierre,
    
    Thanks for the information.
    
    Graham

	We tried hard (the whole last week..), but there is no easy patch
	to the .sys file possible...

	Now there are two possible solutions for customers experiencing
	this problem:

	1) burn the image at start address 0000, thereby overwriting the
	   diagnostic code (rtVAX300 internal diags will run test E.. to 8..,
	   but no KAV30 specific diags will be available..)

	2) if the customer wants to have the diag features *and* his image
	   in the EPROM, than his KAV30's rev A0x have to be changed to
	   rev B01 modules (could be done by FS).

	If you have a customer who wants to go with solution 2), please
	contact me immediately (EICMFG::LEMMER, 865-3875).


	Thomas

	thanks to Julian, the patch is possible...

	it was tested by us and two customer sites and it is easy to handle..

	the next reply contains EPROM_PATCH.COM, the user hase to answer
	the 'size' of his EPROM:

>>> this is a 'copy' of the test run:

$ @eprom_patch rom.exe
%PATCH_SYS, Filename being patched is: ROM.EXE
* EPROM Size 2 MBits / 4MBits (2/4): 2


  PATCH  Version 5-05    20-June-1991

%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-NOLCL, image does not contain local symbols
old:    00000004:  03020100
new:    00000004:  00000000
old:    00000008:  64646464
new:    00000008:  00000400
old:    00000010:  55555555
new:    00000010:  00018200
old:    00000014:  0AAAAAAAA
new:    00000014:  00018600
%PATCH-I-WRTFIL, updating image file DKA300:[000000.LEMMER.KAV30_V11.ROMS]ROM.EX
E;24
%DELETE-I-FILDEL, DKA300:[000000.LEMMER.KAV30_V11.ROMS]PATCH.TMP;1 deleted (3 bl
ocks)

>>>


	Thomas

$!
$! Patch a Ebuild SYS file for rtVAX300 Rev B1
$!     
$ Restart:
$ If "''p1'" .Eqs. ""
$ Then
$    Inquire P1 "* Filename to patch"
$    Goto Restart
$ EndIf
$ Write Sys$Output "%PATCH_SYS, Filename being patched is: ''p1'"
$ Rep1:
$ Inquire Size "* EPROM Size 2 MBits / 4MBits (2/4)"
$ If ("''Size'" .NeS. "2") .AND. ("''Size'" .NeS. "4")
$ Then
$    Write Sys$Output "%PATCH_SYS, Size must be either 2 MBits or 4 MBits"
$    Goto Rep1
$ EndIf
$ If "''Size'" .EqS. "2"
$ Then
$    Size = "400"
$    ChkSum = "18600"
$ EndIf
$ If "''Size'" .EqS. "4"
$ Then
$    Size = "800"
$    ChkSum = "18A00"
$ EndIf
$ Open/Write X Patch.TMP
$ Write X "$ Patch/Absolute ''P1'"
$ Write X "SET MODE HEX"
$ Write X "DEPOSIT 4"
$ Write X 0"
$ Write X "EXIT"
$ Write X "DEPOSIT 8"
$ Write X ''Size'"
$ Write X "EXIT"
$ Write X "DEPOSIT 10"
$ Write X 18200"
$ Write X "EXIT"
$ Write X "DEPOSIT 14"
$ Write X ''ChkSum'"
$ Write X "EXIT"
$ Write X "UPDATE"
$ Write X "EXIT"
$ Close X
$ @Patch.TMP
$ Delete/Log PAtch.TMP;*

Hi,

A customer of ours at General Dynamics has asked what impact the system
image patch would have if it were eprommed for rtVAX300 rev C's.
They will be receiving new KAV30's rev B's with the rtVAX300 rev C's and would
like to burn the same system image (plus the 96k diags) for each system.

Can you confirm what the consequences would be?

Thanks,

Alan

	as the previous entries to this note clearly state, the patch only
	works on rtVAX300 rev B1, which is on all KAV30 rev Axx. If you use
	a patched EPROM on a rtVAX300 rev C1 (KAV30 rev Bxx, Cxx), your
	application would not run, because the patch changes the start
	address of your image...

	Thomas