Imaging VX0 Dual Monitor doesn’t work on 4.4.1

  • This topic is empty.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #478
    AvatarAxman
    Member
    • Total Post: 6
    • Newbie

    I need some help from one of the experts.
    I have some newly shipped Winterms that have the Model description of VX0 on the side and underneath it says (Wyse V90 Dual Video).
    Not sure what model these are but i’ll refer to them as VX0’s.

    I have reinstalled Rapport 4.4.1 and applied all the hotfixes I can find.
    The VX0’s get detected by Rapport fine but I cannot successfully capture an image off them.

    When I choose Get Device Image (Requires PXE) by right clicking the device in Rapport 4.4.1 Device Manager the VX0 successfully reboots and PXE picks up the Rapport server fine.
    It then goes to the Wyse Spash screen where it passes through the DETECT phase and on to the IMAGE phase.
    It’s at this point it all starts to go wrong.
    After around 20 seconds I get FAILURE (or no archive) come up on the splash screen. It ends up rebooting the VX0 Winterm back into a Local Boot / WIndows and fails the imaging job in Rapport.

    The details of the failed Scheduled Package in Rapport are as follows:
    Error Code 10001
    Script Processing Error Please see Help File for more info.
    WISard-FAILURE-ENCODING

    I will paste the contents of the script it is trying to run below:
    [Version]
    Number=fieldday
    Description=fieldday
    OS=XP
    Category=Images
    USE_PXE=YES
    command=%imagewrite%
    BootFloppy=Rapportitf
    USE_REMOTE=YES
    ImageSize=512

    =9V92,
    =push,
    =pull,

    =.i2c,

    =/,
    =ftp/,
    =,
    =/,
    =ftp/,
    =,

    =root.i2u,

    =Tools/sa,
    =<&RR>/,
    =/, =/,

    =.i2c,

    [Script]
    QU “3” “120”
    RB

    Its picking up the product as a 9V92 but in the Rapport console it lists it as a V90 DUAL CONSOLE.

    Can someone please offer some assistance.
    Are there any other hotfixes that aren’t on this site?
    Is the script correct?

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

    Hi Axman,

    You are on the money, you need a patch for Rapport 4.4.1 as is does not know this new platform. I will see if I can dig up the patch for V90L, the other option is to upgrade to WDM 4.5.1.

    Cheers,
    -TT

    #9755
    AvatarAxman
    Member
    • Total Post: 6
    • Newbie

    LEGEND!
    Fingers crossed you can get that hotfix.

    Not sure of the licensing implications of upgrading to the newer version.
    In cost saving mode at the moment, so doubt i’d be able to get any extra funding if an upgrade license needs to be purchased.

    Keenly awaiting your reply.

    Thanks for your help!

    #9756
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★
    #9757
    AvatarAxman
    Member
    • Total Post: 6
    • Newbie

    Yes, i’m getting the Currently installed Hotfix ID HF04041035506 is the same as the hotfix id you are attempting to install, when running the setup for that file.

    Anything else?

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

    These are the hotfixes you’ll want:
    HF04041032905, HF04041018406, HF04041035506, & HF04041002007

    I’ve seen issues with a few of my V90L (9v92) where it had a problem pushing BIOS. You can update the push / pull .i2c file under the ftpserver path (c:inetpubftprootrapporttoolssa9v92)

    Find the line like =YES and change to NO
    Same thing for pulling =NO if needed.

    Good idea to make a copy of the file for backup in case you delete the wrong settings.

    I’d try that, and then see if you can PULL an image successfully now. If it fails, no loss of data. If it works, eureaka we have something to work from.

    -k

    #9761
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★
    #9765
    AvatarAxman
    Member
    • Total Post: 6
    • Newbie

    YOU FIXED IT!!!!

    Imaging fine now.

    Thank you very much!

    #9767
    AvatarAxman
    Member
    • Total Post: 6
    • Newbie

    Just to clarify it was not the hotfix but editing the Pull and Push i2c files that did the trick

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