Tagged: DVI, Extended, Mirror, Splitter Cable, VGA
- This topic has 2 replies, 2 voices, and was last updated 7 years, 4 months ago by slimchicken.
-
AuthorPosts
-
May 2, 2017 at 8:06 am #44319
Hi Guys,
I have around 80 D10D 5010 with ThinOS in production. The majority are using DVI to DVI+VGA Splitter cables.
I have just recently updated the firmware, built a WDM server and generated a new WNOS.ini with the Generator from this site. Everything seemed to be going great but then, as devices started rebooting, I started getting reports of the dual screen setups changing to mirror mode rather than extended mode. Interestingly this is only occurring with the new batch of splitter cables. The supplier, DELL, is telling us that they are the correct cables. I have tried rolling back the firmware but the problem persists.
Looking at the affected devices display settings it seems the device is not detecting the second screen. There is no Screen 1, Screen 2, dropdown menu.
That leads me to believe the issue is with my WNOS.ini and how the monitors are detected.
What I have is copied below, and it makes sense to me, but I thought you guys might see something I don’t that will help me out.
Any ideas would be great!
Thanks
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration Generator 7.7.02 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************
;*************************************************************
;* General 1 *
;*************************************************************autoload=1 LoadPkg=1 VerifySignature=no
; If you are using a version of WTOS code < 7.1_133 please use:
; Rapportserver= instead of WDMServer=
WDMServer=”SERVERNAME”;*************************************************************
;* General 2 *
;*************************************************************Locale=English
EnableGKey=yes;*************************************************************
;* General 3 *
;*************************************************************NoticeFile=AUS.txt Resizable=yes
Autopower=yes;*************************************************************
;* Display *
;*************************************************************; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=DDC Refresh=
;Screen=1 Resolution=DDC
DeskColor=”0 78 152″
Desktop=logo.bmp
FormURL=logo1.bmp
Dualhead=yes Mainscreen=1 MonitorAutoDetect=yes
Screensaver=5 SoftSaver=yes Type=0;*************************************************************
;* Redirection *
;*************************************************************TCXLicense=LICENSEKEY
;*************************************************************
;* Time *
;*************************************************************Timeserver=pool.ntp.org Timeformat=”12-hour format” Dateformat=dd/mm/yyyy
TimeZone=’GMT + 09:30′ ManualOverride=yes Daylight=yes Start=100107 End=040107 TimeZoneName=”AUS Central Standard Time” DayLightName=”AUS Central Daylight Time”;*************************************************************
;* Network *
;*************************************************************; If you are using a version of WTOS code < 7.1_133 please use:
; RapportDisable= instead of WDMService=
WDMService=Yes DHCPinform=yes DNSLookup=yes
SecurityPolicy=low
SignOn=Yes ConnectionManager=Hide SaveLastDomainUser=No EnableLocal=0
MaxVNCD=1 VNCD_8bits=no
VncPassword=”PASSWORD”
VncPrompt=no ActiveVisible=no ViewOnly=noMay 2, 2017 at 2:16 pm #44323And you do not see this issue with older splitter cables?
Sounds like an issues with monitor DDC.
If ThinOS cannot recognized the attached monitor, it will fall back to single monitor.
Nothing wrong with your INI file.CG
May 3, 2017 at 1:23 am #44334Thanks for the reply CG. It’s good to know the INI is fine.
Yes I can confirm the old splitter cable works ok. We have many different models of monitor out there so I may have to do some testing with different monitors and even different VGA cables to try and determine if it is a DDC issue. Thanks for the tip.
I have also just noticed all of these devices have been deployed with an associated INC file in the following format.
————–
Dualhead=Yes
Resolution=1920×1080 Refresh=60
DeskColor=”255 255 255″
DesktopColorDepth=32
Exit=all
————–I noticed in the generated INI there is a note to use “Resolution=DCC Refresh=” if the firmware is below 7.0.1_13, which our production firmware no longer is. Could these settings be causing any issue? These INC files are used to customise the resolution for users who struggle to read at the default resolution.
Thanks
-
AuthorPosts
- You must be logged in to reply to this topic.