Jump to content

AGR

Member
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Posts posted by AGR

  3. Watchpax 2 not discovered

    in WATCHOUT FORUM

    Posted

    I have the same issue with 3 Watchpax 2 which I have inherited from a job. They all have the green network light and flashing amber. I see the Display name and IP address. However the Production computer does not connect.

    Watchout version 5.5.2

    I have tried direct network connection and via a switch.

    I am testing them independently.

    A fourth one I had already works perfectly, so I know the production computer and network setup is correct. So I am assuming it is the way the previous user had set them up.

    One of the three has the display specification Mismatch error. Something I cannot remedy because I cannot connect to to to upload a new show and delete the old.

    I have also plugged in the license key into each Watchpax and powered up, waited for the retart now dialogue.

    So my question is there a way to reset them to factory default?

    Thanks

    0

  5. ip issues - 5.5

    in WATCHOUT FORUM

    Posted

    This is the first time I have bought and used a display with 6 display outputs (Win7). It is so fast that it boots and loads Watchpoint in a few seconds. Which is great!

     

    However I too get an incorrect IP address of 169.254.231.114 displaying in Watchpoint. Which can mean that there are other adapters connected/configured as Jim states, but this is not the case here.

     

    My production laptop (Win8) is connected directly with ethernet cable. I can ping to the correct IP of 192.168.0.102 successfully. Therefore I came to same conclusion as noted by Jonas that it is starting before Windows has completed. Also because once the display software is up and running showing the wrong IP, I then relaunch it and it finds the correct IP address of 192.168.0.102

     

    If I use a switch between the two computers it finds the correct IP address. However I would prefer not to use a switch for this stand-alone installation if possible.

     

    I therefore tried Jonas' suggestion

     

    It looks like WATCHOUT starts a bit before Windows networking is all up and running.

    Try this:

    • A command line option is added to the display software, allowing a delay to be introduced when the software is started. This may occasionally help in avoiding start-up problems, by delaying the start of the display software until things have settled down. To use this feature, append -Delay 3 to the shortcut used to start the display software ("WATCHPOINT.EXE"), where 3 is the desired delay in seconds.

    from the "5.5 Release Notes" found here:

    http://www.dataton.com/downloads/watchout/support/Release-Notes-55.html

     

    , but appending -Delay 3 (or any number) to the shortcut Target makes no difference to the startup time.

    "D:/WATCHOUT/WATCHPOINT.EXE" "-delay 10"

    NB: without the " " , Windows gives an error indicating that the entry is incorrect, so perhaps the Users Guide screenshot could be updated?

     

    I have added it to the shortcut in the main Start menu as well as the one found in ProgramData/Microsoft/Windows/Start Menu/Programs/Watchout5

     

    This is possibly also related to the issue I have in adding commands to the autostart.txt file (either direct or using the Edit Startup Script from the display file menu.

     

    I want to run this display as a cluster (which I have done many times with previous versions of Watchout and XP) so that it starts the show automatically after booting up and executing the display software. The show is in a folder called Shows inside the folder that contains the Watchpoint.exe

     

    The script I use is below but when I boot the pc the only change is that the display has the line "The show will begin shortly" but it doesn't.

     

    authenticate 1
    setLogoString "The show will begin shortly"
    delay 8000
    load "Shows/Performance Today"
    wait
    run

     

    Perhaps I am missing something, I also tried ommitting the "Shows/" from the load command.

    0

  6. Error in watchpoint

    in WATCHOUT FORUM

    Posted

    There have been changes related single computer cluster operation when no network is connected,

     

    Hi Jim

     

    Could you expand on what those changes are please?

     

    Watchout 5.5

    Windows 7 display computer (only one).

    This is an installation that needs to run from startup without a production computer.

     

    At present I cannot even add the name of my Cmd.txt file to to Target box of the Watchpoint shortcut properties. Windows error "The name specified in the Target box is not valid. Please make sure that the path and file name are correct". I'm following page 258 of the latest Watchout_5_Users_Guide.

    0

  7. WIBUCM32.dll is missing?

    in WATCHOUT FORUM

    Posted

    I have a new production laptop with Windows 8 - Acer Aspire V3-771-32324G50MAii W8.

    I followed the tweaking list (as much as I could) for Windows 7 as I could not find a link to one for Windows 8. Installed Watchout 5.5 from downloaded file not from key, installed QuickTime from key.

     

    Issue: an error on launching Watchout "WIBUMC32.dll is missing from your computer".

     

    Solution: discovered that Codemeter installer did not auto install when plugged in, infact I could not see anything on any of my V5 keys related to CodeMeter. I know it's there because I earlier installed on an older Windows XP laptop without problems.

    Therefore I downloaded the CodeMeter installer from http://www.wibu.com/en/downloads-user-software.html#wk and after installing the software launches OK.

    0
×
×
  • Create New...