[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

1357.0. "AWD install problem" by AIMTEC::MORABITO_P () Thu Sep 03 1992 23:22

I have a customer who wants to upgrade their ALL-IN-1 environment to 
IOS 3.0.  This environment consists of 15 MicroVAX 3100s spread across 
a wide area.  The problem is that most of these systems have less
than 30,000 blocks of free space on their system disks.  The customer
has tried using the AWD option in VMSinstal.  As we all know, this still
requires that a minimum amount of space be present on the system disk.  

My question is this, can any files be modified in the KI*.COM to bypass
this disk space requirement?  The customer is satisfied to do the installation
in non-safety mode, but is very hard pressed to get 30,000 blocks on the 
system disk.  If there is a hardcoded value for the disk space check, I 
certainly cannot find it in any of the KI files.

Can anyone out there tell me if there is anything that can be done?   I realize
we are not supposed to modify installation files, but this is turning out to 
be quite a political issue.  The customer is not thrilled that AWD installs
do not work properly.

Thanks,

Paul Morabito

T.R Title User Personal
Name Date Lines

1357.1 Don't blame me! IOSG::HALLC Denser than a Black Hole Singularity Fri Sep 04 1992 10:27 26

T.R	Title	User	Personal Name	Date	Lines
1357.1	Don't blame me!	IOSG::HALLC	Denser than a Black Hole Singularity	`Fri Sep 04 1992 10:27`	26
	Hi there, The AWD problem is described in note 1010.1 By the way the customer would need 35,000 free blocks for a successful non-safety so its even more likely that you'll have to hack the installation checks! The reason you couldn't find the correct hard-coded disk space values is because they are in KICHKLLVINIT.COM which is in A1LUS030.Band not A1030.A with all the rest of the KI* files. The symbols you need to change are:- A1$NON_SAFETY_SIZE == 35000 A1$SAFETY_SIZE == 140000 $! NB. the callback adds 10%, so the actual value checked is 154000 blocks. So as long as your AWD has 154000 free blocks you can happily do change the symbol A1$SAFETY_SIZE to be some very low value. If you don't have 154000 free blocks but have enough for a non-safety installation on your AWD then change the A1$NON_SAFETY_SIZE value to something small. Hope this helps your customer. Cheers, Chris.

Hi there,

The AWD problem is described in note 1010.1

By the way the customer would need 35,000 free blocks for a successful non-safety
so its even more likely that you'll have to hack the installation checks!

The reason you couldn't find the correct hard-coded disk space values is because
they are in KICHKLLVINIT.COM which is in A1LUS030.Band not A1030.A with all the
rest of the KI* files.

The symbols you need to change are:-
A1$NON_SAFETY_SIZE      ==      35000
A1$SAFETY_SIZE          ==      140000
$! NB. the callback adds 10%, so the actual value checked is 154000 blocks.

So as long as your AWD has 154000 free blocks you can happily do change the 
symbol A1$SAFETY_SIZE to be some very low value.

If you don't have 154000 free blocks but have enough for a non-safety installation
on your AWD then change the A1$NON_SAFETY_SIZE value to something small.

Hope this helps your customer.

Cheers,
	Chris.