Search the Community
Showing results for tags 'windows 10'.
Found 4 results
The official Windows 10 Tweaking Guide is now published and is available for free download. The guide describes how to tweak Windows 10 Enterprise for reliable performance with WATCHOUT: https://response.dataton.com/watchout-windows-10-tweaking-guide Topics covered: Support, warranty and service Microsoft EULA Install Windows 10 Enterprise Add and remove Windows components Group policies Windows & registry settings Task scheduler Whether you build WATCHOUT media servers for fixed installs in museums, show rooms, broadcast or for live events in theaters, concert venues or corporate events, this free Windows 10 tweak guide is essential reading.
Anyone want to share there 2 cents on best practices with SSD drives and windows 10 (watchout 6.2) Running a matrox c-680 video card with 6 outputs, so far it's been performing fine for video playback tests with watchout 6.2 I am going to make over my display machines. Options are how to configure multiple sata iii - SSD drives... Would you use a 60 or 120 as C_drive and a 500 as D-drive for watchout. or does that watchout need faster throughput and I can raid a set of 500gb can call that D-drive. or put a pair of 500gb drives as extended drive option and just have a single 1tb C-drive. Please give an option and why.... PS. I'm new to watchout but understand computers and servers fairly well
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?
Dear Dataton User community, we are very happy to announce that WATCHOUT 6.2 now is officially available for download from the web: https://www.dataton.com/ News & Views / Blog In addition, our blog - News & Views – has hit the streets! The first blog posts are available, with information about the technology used in the new features of WATCHOUT. http://newsandviews.dataton.com/ Best regards, The Dataton team!