[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

1373.0. "Spell check A1CONFIG disk name not correctly stored" by GIDDAY::SETHI (Man from Downunder) Tue Sep 08 1992 07:08

    G'day All,
    
    The installation procedure has a slight problem namely the lenght of
    the disk name and A1CONFIG.DAT.
    
    I have a disk that's called DISK$OFFICE_DISK the disk containing the
    ALL-IN-1 installation.  This name is stored correctly, however for the
    spell check lexicon it is not it's stored as DISK$OFFICE_DIS.
    
    The code in the startup procedure is as follow
    
    $ lexicons      = "''f$extract(lex, lex_len, base_record)'"
    
    The values of lex is 265 and lex_len is 15, so it looks like your disk
    names should not be greater than 15 characters.  Spell check is not 
    installed and you get an error during startup as follows
    
    $ define /exec /nolog /table=lnm$system_table lci$lexicons -
      DISK$OFFICE_DIS[LCI.LEXICONS]
    
    %DCL-W-PARMDEL, invalid parameter delimiter - check use of special
    characters \[LCI\
    
    The disk name is stored for all other cases, it's a problem with the
    lexicon.  Does this need to be SPR'd ?
    
    Thanks
    
    Sunil
T.RTitleUserPersonal
Name		DateLines
1373.1Er, yes, sorry about that....IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Sep 08 1992 10:3312
    This is a known problem.
    
    Whilst investigating a fix for a PFR, we discovered that we shouldn't
    really be doing the lexicon startup at all, rather we should be
    generating the lexicon startup procedure (if it didn't already exist)
    and getting that executed as part of the main VMS system startup.
    
    So for V3.0, if this is causing a problem the workround is to create a
    oneline LCI$STARTUP.COM that defines the logical and execute that
    instead. You'll need to comment the duff definition out of A1V30START.
    
    Graham
1373.2My work aroundGIDDAY::SETHIMan from DownunderFri Sep 11 1992 02:1513
    Hi Graham,                    
    
    I don't like the idea of telling customers to edit A1V30START.COM.  So
    what I did was the following in SYS$MANAGER:SYSTARTUP_V5.COM :-)
    
    $ on error then continue
    $ @sys$startup:a1v30start
    $ define/sys/exec lci$lexicons <disk name>:[lic.lexicons]
    
    Thanks
    
    Sunil 'I like to see the customer keeping their dirty hands of our
    command procedures' Sethi  :-)
1373.3Agreed!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeFri Sep 11 1992 08:3311
    Sunil,
    
    Yes, you're right, that's a much better thing to do. How could *I* have
    suggested they change A1V30START!!
    
    Graham
    
    PS You could set up and call a specific (but only one line!) startup
    file for LCI as I previously suggested, since that's the *right* way to
    do it according to the linguistics people. And, it may possibly be the
    way we might perhaps do it in a possible future release :-)