Home
Products
Overview
Compare Products
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Download
Actual Window Manager
Actual Multiple Monitors
Actual Title Buttons
Actual Virtual Desktops
Actual File Folders
Actual Transparent Window
Actual Window Minimizer
Actual Window Guard
Actual Window Menu
Actual Window Rollup
Order
Single User License
Corporate Sales
Upgrade Center
News
Latest news
Newsletter
Support
FAQ
How to Upgrade
Restore License Key
Online Demos
Online User Manual
Forums
Announcements
General
Feature Requests
Technical Support
Tips and Tricks
Beta Testing
Feedback Form
Beta Testing Section
Resources
Articles
Reviews
Success Stories
Multi-Monitor Wallpapers
Company
About Us
Contact Us
Privacy
Our Clients
Press Center
Press Releases
In The News
Reviewer's Guide
Logos and Screenshots
Publishing-friendly Graphics
Forums list
New topics
Topics list
Search
Help
Login
Register
Topic: «
AWM sequence in startup process
, Flashing screen sometimes on startup » on forum:
Technical Support
Views: 9693
Scott Bonacker
Registered user
Posts:
12
Joined:
12/08/2014
Posted:
12/30/2016 23:37:16
Laptop running Win10x64 with Plugable U-3900, two external monitors using HDMI and DVI connections.
Sometimes on startup (both cold start and wake from hibernation), the primary screen flashes as if external monitors are not responding to AWM handshake signals as expected.
One solution is to disconnect the Plugable dock until after start up is complete.
Another solution is to remove AWM from the start list, and manually execute it after startup is complete. This is the one that seems most practical when moving from one location to another.
It can't be replicated at will, so likely has something to do with the vagaries of the startup process.
Looks like there are several techniques for controlling the order in which apps start at bootup but wondering if there isn't a way to specify 'start last'?
Thanks,
Scott
Top
Bogdan Polishchuk
Administrator
Posts:
4081
Joined:
04/04/2012
Posted:
01/06/2017 05:00:59
Hello, Scott
Could you please specify the version of Actual Window Manager you're running.
Do you mean the problem (when the screen flashes) happens on the laptop screen?
How long does the flashing last?
What is shown on the external monitors at that time?
Do you need to do something to make flashing stop or it stops by itself?
Best regards.
Top
Scott Bonacker
Registered user
Posts:
12
Joined:
12/08/2014
Posted:
01/06/2017 21:57:01
Running AWM v8.10
I have to say now that I don't think it is the AWM software.
Shutdown last night, cold start this morning with Plugable U-3900 connected and both external monitors on. Screen starts flashing, so I let it go on for a while to see if it would stop. Got tired of waiting, so powered down both monitors. Still flashing. Tried keyboard to see of login appeared and maybe could stop flashing that way. No response to keyboard, although maybe didn't wait long enough. Unplugged U-3900 and flashing stopped.
After login and startup appeared complete, reconnected the U-3900. Single flash (normal) then stability.
Proceeded with manual startup - loading AWM, OL2016, etc.. - and all seems fine.
Wanting to answer your question about how long the flashing lasted coincided with this occurrence so was able to see more of the actual sequence.
This article -
http://plugable.com/2015/07/27/windows-10-and-plugable-docking-stations-usb-graphics-adapters/
- mentions that drivers need to be reinstalled after OS upgrade to Anniversary edition (Summary: Windows 10 requires the latest drivers we recommend to be re-installed *after* OS upgrade is complete.)
Another article doesn't repeat that statement -
http://plugable.com/2016/08/01/windows-10-anniversary-update-and-plugable-docking-stations-and-usb-video-adapters/
.
I haven't installed any Plugable drivers since getting this new laptop, so maybe that's the answer? Time to talk to Plugable it seems.
Apologies for the false accusations.
Scott
Top
Bogdan Polishchuk
Administrator
Posts:
4081
Joined:
04/04/2012
Posted:
01/08/2017 05:44:47
Hello, Scott
Have you updated the driver? Have it solved the problem?
It looked like this problem is somehow associated with Actual Window Manager from what you wrote previously:
Quote
Another solution is to remove AWM from the start list, and manually execute it after startup is complete.
Is this previous statemet correct and the problem depends on whether Actual Window manager is on auto-start list?
Top
User(s) reading this topic
Number of guests:
1
, registered members:
0
, in total hidden:
0
Forums list
New topics
Topics list
Search
Help
Login
Register