Conference iosg::all-in-1_v30

        Hi Hilde

    I think you have a problem with logical LCI$LEXICONS. Is this logical
    pointing to a nonexistend directory or not defined in executive mode.
    
    Groetjes,
    
    Piet 

Thanks Piet for your reply,

but the directory did not exist before the installation, so the installation
created it, the logical did not exist before neither.

What I found out in the meantime is that the date of the system was 17-MAY-1992.
Do you think this can have something to do with it ?

I asked the customer to change it's date and try again. He will try it this
afternoon and call me back later.


Thanks and Regards

Hilde Willems

The customer tried to do the installation again this morning but it stopped on
the same place with the same error message.


Could it be that the combination of US as language, US_GB as dialect and BE as
market component is unsupported or doesn't work ?

Does somebody know where I can found it out and/or what my next step can be ?


Thanks in advance


Hilde Willems

    RE .2 It's vaguely possible that the system date prevented the licences
    from working.
    
    Re .1/.2 Did they specify a valid (and not very long!) location for
    LCI$LEXICONS.
    
    Re .3 "Does the BE kit support British English?"
    
    There are two answers to this:
    
    	a) Does the Belgian Country Support group support British as a
    	   valid combination
    
    	b) Has the kit been built to support this.
    
    To answer b, you'll need to unpack savesets A1CBE030.B and look in
    files A1.CLD and OAMARKET.BLI to see whether British is included in the
    list of languages supported. Although I would have expected it to fail
    earlier if they weren't. Then check that you have OAFORM_BE_BRITISH.FLB
    in the same saveset.
    
    Graham

    I have to guess, since I cannot access the old disks where we used to
    build the language kits.
    
    The Belgian C-Component supports languages French, German, Dutch and
    US-English. I simply don't know whether an additional GB-dialect is
    supported. All I can remember is, that we definitely never checked this
    combination of installation. 
    
    I recommend you do what Graham suggests and check for the *BE_GB* or
    *BE_BRITISH* files. 
    On the other hand, Graham, if a combination of B and C components is
    not supported and these files are missing, typically the installation
    tells you so....
    
    	Stefan                                                      

    <<< On the other hand, Graham, if a combination of B and C components is
    <<< not supported and these files are missing, typically the installation
    <<< tells you so....
    
    Er, yes, I was slightly worried about that too!
    
    Graham

Thanks you all for the reply's.

I checked the A1.CLD and OAMARKET.BLI and it stated only DUTCH, FRENCH and
ENGLISH as possible languages. Also OAFORM_BE_BRITISH was not in the savesets of
the BE market component.

So I suppose that US_GB as dialect of the US language is not supported in
combination with the BE market component.

The customer tried the installation without dialect and this worked fine.
I'm suprised however about the error that is given when the installation stops.
(see note 1).

I included a set verify in the KIIMAGES.COM and here is the area where he fails :

$       message /object /nolist /symbols /NOTEXT /object = vmi$kwd:wplmess.obj -
         a1$llv:wplmess, a1$llv:wplexcep, , , -
%DCL-W-NULFIL, missing or invalid file specification - respecify
         a1$llv:wplsort, a1$llv:wplforms
$WARNING_EXIT:
$       Gosub Procedure_Cleardown
$PROCEDURE_CLEARDOWN:
$       If A1$debug Then Set Noverify
$       If F$Trnlnm( "imagelist") .nes. "" Then Close imagelist
$       if f$trnlnm("sys$share","lnm$process") .nes. "" then -
          deassign/process sys$share
$       Verify = F$Verify( 0)

%A1-E-RETRY1, Please correct any reported problems before attempting
%A1-E-RETRY2, to install ALL-IN-1.

%VMSINSTAL-E-INSFAIL, The installation of A1 V3.0 has failed.

        VMSINSTAL procedure done at 09:34


Many thanks for the help and reply's.


Hilde Willems

    Your tests show that BRITISH must not be supported by the Belgian
    Market kit. However the failure is a bit bad. We've looked at the code,
    and it does checks that the language is supported by the market kit for
    second languages and for upgrades, so this problem will only occur
    during fresh installs.
    
    Could you report it please.
    
    Graham