DVS

Hello Ali, We normally use a batch file in startup using a taskkill command for explorer. That would be our preference. In that batch file, we would then have the Watchout startup on a delay, giving time for Windows to kill explorer and for all drivers etc. to initialise. Hope this helps.

Has anybody performed testing using Windows 10 Pro for Workstations?

Hello Miro, Based on the information above, we have loaded a system as detailed and there does appear to be a dramatic improvement in the startup time, something more akin to how it run under Windows 7. So all good under Enterprise LTSB As an after thought, we are attempting to change certain aspects of Windows 10 Pro installation to see if the startup time can be improved. It would appear that the latest AMD driver is allowing the system to start quicker than the old Q4.1 driver under the Pro installation. We shall post our findings if we hit on a particular service on Pro that might improve startup time for 5+ outputs. Although it would potentially mean stripping back most of the code, do Dataton plan to re-write Watchout to support latest DirectX versions and video card drivers rather than relying on Microsoft/AMD/NVidia to bring things into line so that Watchout works reliably under current mainstream Windows versions? Basically, we will see an overhaul of Watchout or will it just be the usual additions and updates we normally see?

Hello Miro, Thank you for the information. Do AMD's driver issues relate to DirectX bugs again? We will attempt to move to the stated version and updates based on the information you have provided. Can you guarantee this will rectify the issues we are seeing? DVS

Glad we are not the only ones. For people who have not used Watchout before they may look at this and think it is normal and this is how it works, but for experienced users, we know this is an issue.

We would agree 100% if new Windows 7 licenses were not so difficult to purchase and the drivers for newer hardware was available for 7. Trouble is with Windows 7 was at the time of Win 8.1, Win 7 was having performance issues in playing back 1200 Projection media and while building systems for Expo 2015 in Milan, we worked with some of the guys from Dataton to achieve a stable playback across 10 outputs through 3 systems on what is now version 6. Unfortunately, time moves on and so does technology.

Nothing in the auto-start script.

Our apologies, no, it's just the one. Not sure how the WX7100 got in there. To confirm, it is just the WX9100 in the system. Original post edited to reflect.

Can anybody advise on the below please: Motherboard: Asus WS X299 Pro CPU: Intel Core i7 7800X, S 2066, Skylake-X, 6 Core, 12 Thread Memory: Corsair Vengeance LPX Black 16GB (4x4GB) DDR4 PC4-19200 (2400) O/S Drive: Samsung SM961 Polaris M.2, 256GB NVMe, MLC V-NAND, SSD PCIe Watchout Drive: Samsung 850 Pro 512GB 2.5" SSD, SATA III GPU: AMD 16GB WX9100 Radeon Pro, PCIe 3.0, GDDR5 DATAPATH VISION SC-SDI4 VIDEO CAPTURE CARD MS WINDOWS 10 PRO 64 Bit Windows has been stripped back to recommended setup following Dataton instructions. MS Windows Updated to 1709 (Build 16299.309) as of 27th March 2018. Latest AMD Driver as of 27th March 2018 (V.18.Q1.1). Still current. Running Watchout 6.2.2. Previously running 6.2.1 6x mDP to HDMI adaptors (Startech) to 1080P monitors running at 60Hz. Forced EDID has been used. Issue: When attempting to start using Watchpoint.exe on display systems, it will attempt to load and then fail, which will then restart via the watchdog and continue to go through the cycle but fail to start. When running WP.exe, this will take around 18 seconds to start but will actually start. Adding GPU scaling to each screen via Radeon Pro settings cuts load time to around 12 seconds and after 4 cycles through the watchdog, will then start the show when run via Watchpoint. When running 4 outputs, the screens seem to initialise quick enough under Watchpoint without causing the watchdog to kick in and restart the programme, but as soon as we go to 5 or 6 outputs, the time taken to initialise is too long and therefore, can cause the watchdog to restart the programme. This is happening on multiple systems of identical specification. The start-up is consistent and repeatable, as well as being identical between the two systems making a hardware fault very unlikely. Additionally, using different screen edids appear to impact the initialisation time, one edid with very flexible settings ( lots of colour depths, resolutions and refresh rates available ) took almost 45 seconds to initialise running WP.exe, subsequently putting watchpoint.exe into a restart loop. We also tried the gaming driver variant which is available to the WX9100 and this made little to no difference to the initialisation times for WP.exe. We found a forum post indicating that the TdrDelay and TdrDdiDelay registry entries be increased to prevent Windows from killing the graphics drivers too soon. However these registry entries were not present to edit, and adding them had no effect. This has also been seen on multiple other systems running more than 4 outputs at any one time and also on systems running W600 GPU, both at 1080 and 4K. Is there any way to resolve this and if not, is there something that can be done to extend the timeout of the watchdog so that everything has time to initialise?