Troubles imaging V90 (any method) – please help

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

    Hi everybody.
    Some weeks ago, I bought a second-hand V90. I power on and “play” with it, to understand the difference of XPe with XP, the write filter, flush cache and so on…

    And so I decided to upgrade the OS… I tried with rapport, but the software doesn’t find the device.

    So I tried with PXE: after some issue with “no boot file found” and similar I setup correctly my dhcp and tftp. The thinclient starts to boot from network but during some operation with push.k gives me an error (sorry I have no more the log file :S).

    So I tried with WSI, but again a message of invalid firmware appear…

    After that I have some troubles turning on the client: often a fix orange led instead of green. Sometimes is green but black screen. A couple of times a infinite beep….

    I tried the method with USB bootable pen, but with version 1.3 the wyse doesn’t even recognize my pen (perfectly bootable from my laptop, a sony microvault 1GB).

    I made, with the same pen, again all the step reported in the guide but the version 1.4 (hp tool, copy dos command and rename the firmware placed in the right dir, …).

    Today, after more than one month of test, the unit power on and starts the boot from USB (AMAZING!)… I don’t know what happened in these days….

    I choose to run V90, starts the red screen scrolling data. After a while the unit reboots, for sure before making the re-imaging.

    I searched in the pen kinda log file but nothing…. please, someone can help me?

    The firmware is taken from here: http://www.wyse.com/serviceandsupport/support/dlOraFW.asp?which=62&model=V90(Windows%20XPe)

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

    Hi,

    Make sure you rename the .i2d file to “9V90.i2d” and place it in the V90 folder in the root of the USB imager – that should do it!

    If you still have the K.file error you may have a bigger problem,

    Cheers,
    -TT

    #12205
    Avatardragoshenron
    Member
    • Total Post: 2
    • Newbie

    Thanks for the quick reply.
    I double check… the firmware is in V909V90.i2d

    I didn’t find a method to redirect the output on a file, so, with the help of “pause” key, I found these rows on the screen



    Operating in DOS mode...

    WISard 4.0.4.4 Wyse PXE agent...........
    =undefined, cmdline=dl "=9v90,=push,>&RR=V90, .....
    ....
    ignoring 'logfile' to ' fsdos/v90/9v90.log
    .....
    Loading run-time process instructions.. please standby...
    ..... graphic stuff.... WISdetect.gif
    ....
    Searching for:(~) ->(.k)->(/push.k)->(/9v90/push.k)
    ->(fsdos/tools/sa/9v90/push.k)
    Evaluating:
    'fsdos/tools/sa/9v90/push.k' to ' stream/sec/test'
    [tools/sa/9v90/push.k]
    Searching for: (>E2sec>)->(2c)TARGET COMPRISON FAILED**********************failed
    Searching for.....
    Searching for.....
    Searching for.....
    Searching for.....
    Searching for.....
    Searching for: (secerr.msg)
    ********* THE CLIENT IS NOT AUTHORIZED TO OPERATE IN THIS ENVIRONMENT *************
    ......
    .....graphic stuff......
    ....
    processing: 'overload.msg' to 'stream/rep/st'
    searching for: ()->()->(BOOT)
    searching for: (~)->(~BOOT)

    and after few seconds the client restart.

    Could be this useful?

    What do you mean with “bigger problem”? And, more important, what is this .k file? Why so difficult upgrade the OS in this thin client? I supposed was just a filecopy or a bit more….

    Take care!

    Alex

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

    Hi,

    Try opening the push.i2c file in the toolssa9v90 folder and edit the line below in this file like this:

    =NO

    See if it helps,

    Cheers,
    -TT

    #13493
    AvatarArjunSol
    Member
    • Total Post: 4
    • Newbie

    @thinkthin wrote:

    Hi,

    Try opening the push.i2c file in the toolssa9v90 folder and edit the line below in this file like this:

    =NO

    See if it helps,

    Cheers,
    -TT

    This has just helped with pulling an image using simple imager. I wonder, what does this parameter set?

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

    Hi,

    The imaging process does a number of checks to stop you pushing the wrong image to the wrong device. Making this setting skips a few of these checks.

    One issue that comes up occasionally is the units security keys get messed up and it will not let you image is as it thinks you have the wrong image. (environment security failure),

    Cheers,
    -TT

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