W10, Drivers
|
|
 May 24 2016, 05:07 PM
|
 
Senior Member
9,048 posts Joined: Jan 2003 
|
QUOTE(TruboXL @ May 24 2016, 04:57 PM) right... but m$ft is getting rid of win7 and win8.x so maybe will focus more w10 soon... I moved to the Mac officially last March after 25 years with Windows. Fed up with W10. Will keep W7 running for as long as possible. |
|
|
|
|
|
May 25 2016, 08:44 AM
|
Senior Member
515 posts Joined: Jun 2010 From: SoME pLAcE 
|
QUOTE(TruboXL @ May 24 2016, 04:57 PM) right... but m$ft is getting rid of win7 and win8.x so maybe will focus more w10 soon... I use NVidia Display Driver only...but whateva I already abandon ship since release of 10TP, moved to Linux... hmm... ok but have you seen this 3D Video Controller when you start to install any display drivers or already uninstalled any display drivers?  ok so from what I know (maybe not true), that 3D video controller is your nvidia gpu (if that is correct) but why WIndows recognise that way instead of VGA compatible controller has its meanings... that HDMI port of yours (if you have) is connected directly to one of your gpus, be it intel or nvidia... if nvidia gpu is shown to be 3d video controller, chances are your hdmi port is used solely by intel gpu (i think newer laptop is like this) for output through hdmi cable (if you use)... is this a good thing or bad thing? i dunno but its definitely good thing on Linux  ok anyway that hd audio driver is only used for gpus that controls the hdmi port to output sound, thats why intel also got its intel hd audio if you installed from intel display driver also applies to nvidia probably to cover all sorts configuration on desktop/laptop so even if you installed the nvdia hd audio driver if your nvidia gpu is not the one controlling the hdmi port, i guess nothing will happen since the extra driver just sit there doing nothing... so yeah background info for your hd audio display driver...   |
|
|
May 26 2016, 02:52 PM
|
|
All Stars
14,674 posts Joined: Sep 2010
|
acbc Go blame the driver maker - Microsoft is no way responsible for this issue.
 The problem is hardware and software developers are glacial to changes (i.e. seriously can't they dedicate some resources to make a decent Windows driver)?  Only large hardware makers (such as AMD and nVidia) are able to do that - so why can't those smaller developers can do that?  I'm looking at TP-Link, especially. |
|
|
May 26 2016, 03:10 PM
|
|
Senior Member
9,048 posts Joined: Jan 2003
|
QUOTE(chocobo7779 @ May 26 2016, 02:52 PM) acbc Go blame the driver maker - Microsoft is no way responsible for this issue. Hardware maker is Intel. Blame who again?The problem is hardware and software developers are glacial to changes (i.e. seriously can't they dedicate some resources to make a decent Windows driver)? Only large hardware makers (such as AMD and nVidia) are able to do that - so why can't those smaller developers can do that? I'm looking at TP-Link, especially. Anyway, I've moved out of Windows for life. Fed up. Too much troubleshoot and less work done. Thanks for Nadella for forcing me to change. |
|
|
May 26 2016, 03:15 PM
|
|
All Stars
14,674 posts Joined: Sep 2010
|
QUOTE(acbc @ May 26 2016, 03:10 PM) Hardware maker is Intel. Blame who again? You also forgot something - bad power management Anyway, I've moved out of Windows for life. Fed up. Too much troubleshoot and less work done. Thanks for Nadella for forcing me to change. I know a lot of people don't bother doing a BIOS upgrade before upgrading  A bad BIOS = bad power management. I just don't know why people don't even do this OS X is extremely trouble free because backwards compatibility do not exist in the Mac world. Of course they have a very closed ecosystem (i.e. they have control on everything including the firmware and the driver) and that's why they can work so well. |
| Change to: |  0.0125sec
 0.30
 5 queries
 GZIP Disabled
Time is now: 10th December 2025 - 08:38 PM |
Quote