CoastGuard71
Sailor
Guys, I'm on W7Pro not 10... whatever is going on is due to restrictions embedded in 7 not 10. Will anyone using 7 comment about this? This did not happen with previous builds so it's reasonable to suspect something was introduced that conflicts with the Lenovo chip set or the W7Pro... right? I'm looking at what is in play, what the error message hints at... not really helpful in diagnosing problems is it? I'm left with guessing.
Lenovo Intel965 chip set is what I am working with... has been good in previous builds... what about this is creating a conflict... error messages say DX8Render.dll is being corrupted... hence the in-game failure experienced. When the files are inspected I find two Radeon85 files that did not exist prior to this failure and the cryptic error message implicates duplicate Radeon85 which is unique to NVIDIA graphics code... right? Deleting the two Radeon85 inserts does not restore play... could MS security be involved, flagging the error as malware that persists even when the two insertions are removed? Is this the smoke that indicates a fire? Focus on W7 issues and limits. W7 actually uses DX9, could retrograde DX8 use be creating a conflict that was not previously conflicting? What about previous builds is so different from v22(24)? Any big change in graphics handling code could be problematic and generate errors like this. MS security has been a problem with Lenovo using W7, causing denial of allowing application drivers because they are not "digitally signed"... of all things!? MS demands contacting the application creator for a digital signature before MS allows the driver use!
Any incompatibility with the NVIDIA additions or changes in B14v22(24)? Why did this not happen in v19, 18, 17, 16...etc. If you alter something and errors appear you have altered something that is inconsistent with the code that previously worked. So, what alterations took place? I have no way of knowing... all I can do is provide the symptoms of the disease to you doctors of the code who should be able to at least guess as what is in play that creates such a conflict that the error messages describe... that's what they're for... troubleshooting problems caused by altering the code with incompatible routines conflicting with the logic.
Would be nice if anyone using W7Pro on a Lenovo T61 notebook would comment. Is not rational that these events are unique to only my notebook and the dozen different HD/SSD C and USB drives I'm using... I believe we can rule out an individual drive corruption being replicated in so many different and unique drives. I've run malware scans using three different commonly used and up to date malware applications with zero hits. Everything points to code incompatibility with the strangely irreproducible...
Right now I'm dealing with a VPN mystery. Privado VPN offers security and is Swiss in origin, or claims to be. So I installed it for trial. Suddenly EDGE and Firefox(DuckDuckGo) cannot link to the Net... Only when I delete PRIVADO is my Internet access restored... Explain that? Is my Lenovo haunted with evil malware spirits? No, there is an obvious conflict with something P runs in the background blocking my Internet link to my Comcast service.
So. my question to those who were involved in B14v22(24) is... what did you do to the working code that causes this dysfunction? Either it's you or MacroStupid... did you use W10 subs that are not W7 compatible? W7 users not having this issue would deselect the code alterations, leaving only Lenovo or MS security as the source of this. Since previous Builds did not exhibit this error the Lenovo is not the cause. Forced security updates by the 5-Ton OS "Gorilla" (MS) is a possible cause for W7... not W10... these changes are most likely directed to W10, since that is what MS is trying to force on users. Any chance the NVIDIA Radeon85 calls are inserting into the code that in W7 is only compatible with Intel965 chip set? Just throwing out possibilities that seem consistent with observations... would enjoy hearing other ideas how these facts can be reconciled with this demonstrated reality.
Thanks for taking the time to think about this even if it's not bothering you
Lenovo Intel965 chip set is what I am working with... has been good in previous builds... what about this is creating a conflict... error messages say DX8Render.dll is being corrupted... hence the in-game failure experienced. When the files are inspected I find two Radeon85 files that did not exist prior to this failure and the cryptic error message implicates duplicate Radeon85 which is unique to NVIDIA graphics code... right? Deleting the two Radeon85 inserts does not restore play... could MS security be involved, flagging the error as malware that persists even when the two insertions are removed? Is this the smoke that indicates a fire? Focus on W7 issues and limits. W7 actually uses DX9, could retrograde DX8 use be creating a conflict that was not previously conflicting? What about previous builds is so different from v22(24)? Any big change in graphics handling code could be problematic and generate errors like this. MS security has been a problem with Lenovo using W7, causing denial of allowing application drivers because they are not "digitally signed"... of all things!? MS demands contacting the application creator for a digital signature before MS allows the driver use!
Any incompatibility with the NVIDIA additions or changes in B14v22(24)? Why did this not happen in v19, 18, 17, 16...etc. If you alter something and errors appear you have altered something that is inconsistent with the code that previously worked. So, what alterations took place? I have no way of knowing... all I can do is provide the symptoms of the disease to you doctors of the code who should be able to at least guess as what is in play that creates such a conflict that the error messages describe... that's what they're for... troubleshooting problems caused by altering the code with incompatible routines conflicting with the logic.
Would be nice if anyone using W7Pro on a Lenovo T61 notebook would comment. Is not rational that these events are unique to only my notebook and the dozen different HD/SSD C and USB drives I'm using... I believe we can rule out an individual drive corruption being replicated in so many different and unique drives. I've run malware scans using three different commonly used and up to date malware applications with zero hits. Everything points to code incompatibility with the strangely irreproducible...
adjective
- That cannot be reproduced or duplicated.
- Impossible to reproduce or duplicate.
Right now I'm dealing with a VPN mystery. Privado VPN offers security and is Swiss in origin, or claims to be. So I installed it for trial. Suddenly EDGE and Firefox(DuckDuckGo) cannot link to the Net... Only when I delete PRIVADO is my Internet access restored... Explain that? Is my Lenovo haunted with evil malware spirits? No, there is an obvious conflict with something P runs in the background blocking my Internet link to my Comcast service.
So. my question to those who were involved in B14v22(24) is... what did you do to the working code that causes this dysfunction? Either it's you or MacroStupid... did you use W10 subs that are not W7 compatible? W7 users not having this issue would deselect the code alterations, leaving only Lenovo or MS security as the source of this. Since previous Builds did not exhibit this error the Lenovo is not the cause. Forced security updates by the 5-Ton OS "Gorilla" (MS) is a possible cause for W7... not W10... these changes are most likely directed to W10, since that is what MS is trying to force on users. Any chance the NVIDIA Radeon85 calls are inserting into the code that in W7 is only compatible with Intel965 chip set? Just throwing out possibilities that seem consistent with observations... would enjoy hearing other ideas how these facts can be reconciled with this demonstrated reality.
Thanks for taking the time to think about this even if it's not bothering you
Win7Pro? Lenovo T61... MS forced security updates? Not totally replicated circumstancesSo here is at least one account of everything working properly - including with Windows 10 and Intel graphics. Thank you for your reply, @AkrimalS!
Last edited: