![]() ![]() The driver checks the major version number, but only checks if it’s 5 or 6. Windows used to have version 5.0 for Windows 2000, 5.1 for XP, 6.0 for Vista, 6.1 for Windows 7, 6.2 for Windows 8, 6.3 for Windows 8.1. The Intel OpenGL driver in ig4icd64.dll or ig4icd32.dll tries to check the Windows OS version and refuses to work if it finds a version number that it doesn’t expect. The main takeaway is that Microsoft and Intel are both somewhat responsible for this. I can understand your position as an Intel representative but I think you'll agree with me that Intel's behaviour was all but unclear in managing this situation.Is a bunch of info about the HD 3000 and other older Intel iGPUs and OpenGL support at this link. Now you tell us "Sorry guys, there's no way to get HD 2000/3000 working with Windows 10".If you publish a beta driver for my Intel card, what am I supposed to think about the future compatibility of my system hardware with the new OS? On its site Intel published a link to a mysterious beta driver available ALSO for HD 2000/3000 that webpage was available to public several days after the release of Windows 10 (I checked it before my system upgrading the same way I checked AMD site for the new driver for my graphic card).Microsoft told us "Everything's ok in upgrading your system" by the horrible GWX10 app (Microsoft's fault).The table you referenced in many post of yours should have been published a long before the date of Windows 10 release, so that users with "not so young" pc/notebook could have been advised of potential risks in upgrading their systems. I'm sorry but Intel's behaviour seems to me at least unfair on customers.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |