Automate a File Copy to XP Embedded V90

  • This topic is empty.
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #363
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    I would like to know how to copy files to an XPe V90 device without manually having to connect, disable EWF, copy the files and enable EWF. In particular, there are updated files for a Terminal Emulation session I need to modify. Is there a script that can be written to do this that I can register in Rapport 4.4.1 for distrubution the devices?

    Thank you,

    /paul

    #9367
    Avatarkaraziel
    Member
    • Total Post: 74
    • Back Stage Pass
    • ★★★★

    If you are pushing the package from WDM/Rapport then it should handle the write filter for you.

    Just use the SF (send file) command to move the files down and hte automatic WF mgmt process in WDM will disable WF, apply your script, and re-enable WF afterwards.

    -k

    #9368
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Thanks for the info. I am pretty familar with Rapport but unfortunately not so much with the scripting component. I will locate an existing script file and see what I can do to include the command you referenced.

    BTW – Do you know of a source where I can go to learn more on scripting syntax?

    Thank you,

    /paul

    #9369
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Paul,

    Here is an artical on scripting:

    http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=21

    The downloads-Rapport-XPe section of this site is full up examples and also check out these samples:

    http://www.freewysemonkeys.com/site/modules.php?name=Downloads&d_op=viewdownloaddetails&lid=64&ttitle=XPe_Setup_Package_Examples.rar

    The scripting is really a simple wrapper and if you use a few existing packages to get started its not that hard,

    Cheers,
    -TT

    #9371
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Cool. I took one of the existing scripts and modified it. I was able to register it in Rapport. I applied it to a V90 and the device initially rebooted (I take it since the WF automatically gets disabled and thus reboots). The device came back online and then the message about the Admin is configuring the device… appeared. The device rebooted a second time. All good so far, right? Well, the files I needed to update did not get updated and there was an error in the Scheduled Packages that read:

    Error Code: 10001
    Desc: Script Processing Error. Please see Help…
    Extended Error Desc: XC Failed: 550 Line#:32 SF “MF_FQDN_V90MF_FQDN_V90*” “c:program filespowerterm”

    Note: I also tried the XC versus SF command and got the same error message. Ohh So close…

    My Script looks like this:

    [Version]
    Number=MF_FQDN_V90
    Description=Copies MF_FQDN_V90 Files
    OS=XP
    Category=Other Packages

    [Script]
    ;
    ;DATE: 30 March, 2007
    ;Prepared and Written by Paul Lantolf
    ;
    ; This package is for use with preSP1, SP1 & SP2 builds of XPE.
    ;
    ;


    ; Check Operating System, Check SP level and Confirm free space
    ;


    CO “XP”
    CV “c:windowssystem32ntoskrnl.exe” “>=” “5.1.2600.0”
    CV “c:windowssystem32ntoskrnl.exe” “<=" "5.1.2600.2622"

    CF “C” “2000”

    ;
    ;


    ; Lockout
    ;


    LU
    ;


    ; Copy over newer files
    ;


    ;XC “MF_FQDN_V90*” “c:Program FilesPowerTerm”
    SF “MF_FQDN_V90*” “c:Program FilesPowerTerm”
    ;
    ;


    ; End Lockout and Reboot
    ;



    EL
    RB

    #9372
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    OK,

    If you dont need to test for the OS version you can skip the “CV” bit. But this is not the error.

    Use XC to copy more than one file like this:

    XC “MF_FQDN_V90*” “c:Program FilesPowerTerm”

    to send one file you can not use the wild card so create it liek this:

    SF “MF_FQDN_V90myfile.xxx” “c:Program FilesPowerTerm”

    Cheers,
    -TT

    #9373
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    I tried the single file copy using:

    SF “MF_FQDN_V90myfile.xxx” “c:Program FilesPowerTerm”

    but still no luck. Same error message. The syntax looks the same as you suggested but I must be missing something. Hmmm! I will try again to recreate the .rap and see if maybe there are hidden spaces it is trying to read. It’s just a guess…

    /paul

    #9374
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    I modified the script (removed the CV entry and added a subdirectory name “C” under MF_FQDN_V90) and moved the 4 files I want copied. I thought maybe there was a conflict in this folder with the CRC.txt file. Anyway, it did not error out (yeah) but it still did not copy the files.

    XC “MF_FQDN_V90C*” “c:Program FilesPowerTerm”

    #9375
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Opps, I forgot the backslash on the end 😳

    XC “MF_FQDN_V90C*” “c:Program FilesPowerTerm”

    #9376
    Avatarkaraziel
    Member
    • Total Post: 74
    • Back Stage Pass
    • ★★★★

    XC sends all files and folder ( * ) under the specified path to a folder path on the remote server.

    XC “update files*” “c:updated files”

    To send single file you specify the file name in both source and destination (so you can change names mid script)

    SF “update filesfirst_file.txt” “c:updated filesfirst_file.txt”

    -k

    #9380
    Avatarplantolf
    Member
    • Total Post: 11
    • Regular Joe
    • ★★

    Ok – The addition of tha backslash at the end did not correct the error. I looked at the source directory structure from a pre-exisitng script and just followed that same paths.

    Before (not working):
    XC “MF_FQDN_V90C*” “c:Program FilesPowerTerm”

    After (working):
    XC “C*” “c:Program FilesPowerTerm”

    Note: The “C” subfolder has the 4 files I want to copy.

    It appears that it wants to be only one level away from the source. I can’t see any other reason why, since it now works. Or maybe it didn’t like the underscores.

    Any thoughts.

    #9382
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, if the package you created was called MF_FQDN_V90 you do not need to include this in the XC statement. Rapport will add this for you in the variable.

    You can go more that one level deep, the file location is in relation to any folder under the base package.

    Glad its working now!

    -TT

Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.