Conference utrop1::linkworks_v3

    
    
    
    >>- i tried to start a batch programm from within a batch/cmd-file that was
    >>launched from within a method (external method call launches CMD, which
    >>itself starts BAT)... doesnt seem to work ! is that the way it's
    >>supposed to work ?
    
    What exactly do you mean, to start a bat file on NT you'll neet to call
    an external commandline call with following option "cmd -c xxx.bat"
    
    
    
    >>- anyone tried to use the NT 308 (oct96) lnx client kit with an NT
    >>installation on extended partition on drive E.. problems are when
    >>opening an compound object (envelop, folder, cabinet), the client
    >>crashes with dr.watson log. occurs only on this one PC, if same user
    >>does the same thing on a different PC its possible.
    >>(seems to be dependent on full screen with tree window mode, same
    >>happens in 320)
    
    No if feel this is a bug, please submit a NICE call.
    
    >>- also if (on 320) lnx-client in started on w95 or wnt via .lnk (shortcut)
    >>from the start-menu its not possible to start admin+config tools.
    >>(msg: it's not possible to start AM x site-id german).
    >>same happens after running a tool in between. cant start it after a
    >>first successful start of one of the admin/cfg tools.
    
    LinkWorks needs the working directory to be set to the correct location,
    otherwise it is impossible t o find AM/CM, instad of using .lnk you
    might consider using copy.
    
    >>- what are the pdmcom.exe processes on ant alpha-nt-srv ?
    
    The Pdmcom.exe is the server process that will bestarted to serve
    programs that are written against the libapodl.dll (server library).
    processes like slinter.exe will use this, it is the process that will
    behave as a linkworks client.
    
    >>>- what are the nt-file-security-rights to be applied to the oproot-tree
    >>>on NT to gain max.security (omuser with full-control i guess)
    >>>what about the db-files and transaction logs/dump devices (sa-account) ?
    ??????
    
    
    Han
    

    hi han !
    thx for the answers so far !
    re -1
    yep i know.. starting a bat/cmd prg from within a lnx-ext-method is 
    no problem - but try to start another bat/cmd-prg from within the first
    one.. doesnt work...
    re -2
    i'll try the working dir.. but strange enough its possible wo start lnx
    from the start-run app and enter c:/lnx/lnx.exe and be able to run adm/cfg.
    with this there is no working dir set at all (guesss lnx.exe looks then
    in the current directory, which is the one from where the last app was
    started (lnx.exe itself in this case - this would also explain why its
    not possible to start adm/cfg after launching another app in betweeen.
    so the current dir gets set to the startup dir of the other app and so
    it doesnt point to c:/lnx anymore and so adm/cfg wont be found... aaah
     

    re -2,
    
    
    Is this occuring on the december 3.0.8 client, because the should have
    been a fix on the working dir problem??
    
    Han

    hi han !
    no its the oct.release
    what about the starting 2-level-cmd's from
    cmds-that-were-started-from-lnx-ext-methods ?
    is this the way its supposed to work ? and if so -why ?
    REALLY would be nice to start another command-interpreter..
    thx paule

    
    Paule,
    
    Well tested it on my system an it seems to work, but not if I do it
    from the NT server??
    
    Please file a Problem report on this.
    
    Han

    do you mean (as on the phone): works if method executed on client,
    doesnt if on NT-server, does if on Unix-srv ? (doesn nt-intel/alpha
    matter) ?  thx paule

    
    Paule,
    
    It works if you use the nt-client, but it does not work when you start
    the same batch as an server commandline  ( started by the DCS ), did
    not have time to test this on other platforms.
    
    Han

    thx han, will file problem report..