|
Quote: This is no doubt an attempt to bolster new pc sales
And most probably also an attempt to lower costs incurred to support their own products. But in doing so, they are losing what could have been loyal long term customers.
Get me coffee and no one gets hurt!
|
|
|
|
|
If that's their approach, I suspect a lot of people will simply revert back to an older OS, if that's an option to them, and keep using it until the hardware dies. Then they'll purchase something that was sold with Windows 10 already on it (so it damned well better be compatible).
|
|
|
|
|
dandy72 wrote: Then they'll purchase something that was sold with Windows 10 already on it (so it damned well better be compatible)
It'll be compatible, but for how long? My Lenovo laptop was abandoned by the manufacture when windows 8.1 came out -- I bought it new the year before, when 8.0 and the laptop model were both brand spanking new. They decided it was too much trouble to write 8.1 drivers for it, so abandoned it. Make no assumptions about longevity of hardware and OS compatibility.
|
|
|
|
|
Wow.
Luckily (?) I hardly ever buy laptops. I still buy/build my own PCs (of desktop variety) from parts, which tend to have more mainstream drivers than OEMs, who generally have their own and who have no incentive to keep supporting them across multiple OS versions.
|
|
|
|
|
Years ago, I had an even worse case:
This was before S/PDIF inputs on the mainboard was common, so I had an external box for S/PDIF-to-USB conversion. After a couple years, the vendor announced that they would be closing down hardware development to become a specialist in writing drivers for other harware manunfacturers.
So they became driver specialists - abandoning their own hardware. They stopped maintaining the drivers for it. Thiw was when XP came onto the scene, and they wrote lots of XP drivers for others, but not for their own, like the box with their label on that I was using. When I switched to XP, I had to find another way to input S/PDIF signals.
|
|
|
|
|
The problem seems to be augmented by the fact it is a ATI/AMD Graphics card. Recently tried to recycle a old laptop with a X1200 and same resolution...
- Win 10 had the same issues as yours.
- No Linux distibution I tried picked it up correctly.
- End up with win 7 and a day updating.
Paulo Gomes
Measuring programming progress by lines of code is like measuring aircraft building progress by weight.
—Bill Gates
Everything should be made as simple as possible, but not simpler.
—Albert Einstein
|
|
|
|
|
Personally, I've abandoned ATI years ago. Which means nowadays I'll go out of my way to avoid anything from AMD. To me, their drivers and associated bloatware has been their downfall.
Nvidia isn't doing much better with their 300+MB driver downloads, but at least you can be a little more selective about what you install. Although AMD might have remedied the situation in the last few years--I don't know and frankly I don't care enough about them to find out.
|
|
|
|
|
I had the same problem with a desktop PC last Sunday.
The PC was already equipped with a working W10 installation, just after the install of the "fall creators update" the video resolution dropped from 1600*900 to 1024*768.
Solution was:
- uninstalling the video card from the device manager (marking the "delete software driver" option)
- download and reinstall the official sw from the video card manufacturer's site
Same problem occurred on my personal home PC, after the "falling" update, my Sound Blaster audio card stopped working 
I suppose the new W10 update is messing around with drivers in general..
|
|
|
|
|
My Windows 10 PC, happily running at 1920 x 1080, suddenly went blank, then came back at 1024 x 768 recently, also with a Radeon card. Device Manager claimed the driver was the latest available, but the date gave away what had happened. Probing about in the device manager page, I found it allowed me to revert to the previous driver and even allowed me to say why. It lasted until The addition of a second monitor a couple of weeks later prompted an upgrade, but the 7 year old Radeon was coping fine otherwise, after the driver "downgrade".
|
|
|
|
|
I went though those motions. Deleted from Device Manager, downloaded and installed the latest from the manufacturer's own site--the last update to it was in 2009 (!)...Even though the driver installer didn't report any failure, and it was identified again in Device Manager using the correct name, the resolution selection screen still identified it as Basic Display.
|
|
|
|
|
Did you had any previous manufacturer's software version? Like the ATI Catalyst CC for AMD Video Cards, or NVidia's CPanel.
If so, try uninstalling them before installing the latest sw from the official site.
That did the trick for me on a HD radeon 6500
|
|
|
|
|
Other than the driver itself, no, there was no additional software. As old as Catalyst now seems to be, this laptop (and the driver--from ATI) predates it.
|
|
|
|
|
Before nuking the OS next time, I'd suggest trying a driver download directly from AMD first.
The windows GPU driver installer has issues around fringe cases, and is especially eager to break stuff in service pack updates. I wouldn't be surprised if it attempted to install the current "universal" AMD driver; despite that driver no longer working for your buddy's ancient GPU.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I must've skipped that in my initial post - yes, I did nuke the existing driver as thoroughly as I could, and downloaded the latest from the manufacturer--which in this case turned out to date from 2009 (!)... In fact I always go to the OEM's site first for drivers, rather than using those from Windows Update, as those tend to be a few versions behind (although in this case...you'd think they'd have the latest already, since it's this old). The end result was the same--even though Device Manager correctly identified it by name, the Metrofied portion still referred to it as "Basic Display". First time I've seen different parts of the OS disagreeing with each other.
|
|
|
|
|
I'm surprised it dropped out of the main driver that long ago. I'd've expected at least 4 years of nominal support (in the main driver even if no longer an optimizing target) based on my experience with nvidia drivers. I was under the impression the ATI/AMD kept similar support lifespans, if only to avoid being beaten over the head with the shorter number by the competition's marketing dept.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I had this exact problem with an old Radeon HD4600. Long story short - AMD don't provide a Windows 10 driver that you can install they only supply one via Windows Update. This had been replaced a newer Windows Basic driver that doesn't work.
The solution was simply to go onto the device manager and rollback a couple of versions to the non-Windows version that was dated a couple of years ago. Good as new now.
|
|
|
|
|
Had the same problem. Reverted to the old driver via Device Manager and now all good.
|
|
|
|
|
Here's the thing in this case - the driver had not been replaced. There was nothing to revert to.
|
|
|
|
|
Microsoft doesn't write the drivers. In this case I'd say AMD dropped support for the Radeon 3200HD display adapter.
|
|
|
|
|
0) Bootstrap grid - I get it now.
1) I'm still trying to over-engineer MVC extension methods
2) I've come to accept that I can't stop myself, re: item #1 above.
3) You don't have to wash that every time.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: 0) Bootstrap grid - I get it now.
Well done. It'll change though, you know that, right?
John Simmons / outlaw programmer wrote:
1) I'm still trying to over-engineer MVC extension methods
It's like trying not to comment when someone says something patently wrong. Never ends. You'll never win.
John Simmons / outlaw programmer wrote:
2) I've come to accept that I can't stop myself, re: item #1 above.
First step in solving a problem...
John Simmons / outlaw programmer wrote: 3) You don't have to wash that every time.
Only on Sundays, and her birthday. 
One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.
|
|
|
|
|
Mel Padden wrote: John Simmons / outlaw programmer wrote:
1) I'm still trying to over-engineer MVC extension methods
It's like trying not to comment when someone says something patently wrong. Never ends. You'll never win.
Well, after taking several runs at it, I've managed to whittle them down to about 600 lines of code, with support for EditFor, ActionLink, and FileUpload. I still have to redo the DropDownList and the Checkbox support 
Ostensibly, this is to make the outward-facing code appear trivial. I've got EditFor down to this in it's most simple form (notice there's no HTML wrappers that are visible) - this is the overload I use 9 times out of 10:
@Html.EditForEx(model=>model.Field)
and I have only one overload that lets you go nuts changing stuff by specifying up to three objects that you customize the components of a MVC Edit field (label, validator, and the field itself).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 11-Dec-17 11:09am.
|
|
|
|
|
Sounds nice. Extension methods and lambdas can lead to some mingin' APIs in the hands of novices, but overall, I think they've been of massive benefit to the libraries we have available at this stage.
One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Bootstrap grid - I get it now.
Welcome to the cool club. 
Jeremy Falcon
|
|
|
|
|
I used to have some of my best ideas in the shower. That was back when I could get up when ever I wanted instead of at the butt crack of dawn (another TLA that is BCD) as I do now. Anyway, one day I was telling my boss about my latest idea and he said, "Maybe we should pay your water bill." 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
