One would assume? I invite you to look further into the links you've posted in effort to help with this frustrating issue. None of them support Win 7 or beyond. Yes, I've seen the 64 bit Xp versions listed, which made me think the .ini could be modified for use on a 64 bit Win 7.
Have I mentioned that it works flawlessly on Win 7, 32 bit? The driver installs without any issues, and appears in the Device Manager.
How are we supposed to know what you tried and didn't try unless you tell us off the bat? Also how are we supposed to know your level of experience when we don't know you without asking questions?
We tried to help and you snap back as we're if we're being silly. Great way to ingratiate yourself here
Oh BTW...
I'm Out.
That's fair?How are we supposed to know what you tried and didn't try unless you tell us off the bat? Also how are we supposed to know your level of experience when we don't know you without asking questions?
We tried to help and you snap back as we're if we're being silly. Great way to ingratiate yourself here
Oh BTW...
I'm Out.
But, rather than the back and forth about all the troubleshooting steps I've used to arrive at said conclusion, after I said in the second sentence of post #1. "I have an advanced knowledge of computers", you could have said that in post #2.
You could have simply said. "I don't know anything about driver scripting." ... But why even post at all, then?Troll.
If that's the M.O. of this forum, I'd rather not integrate at all!
Well, after calling a member that tried to help you a troll, I doubt its your choice to stay here or not.That's fair?How are we supposed to know what you tried and didn't try unless you tell us off the bat? Also how are we supposed to know your level of experience when we don't know you without asking questions?
We tried to help and you snap back as we're if we're being silly. Great way to ingratiate yourself here
Oh BTW...
I'm Out.
But, rather than the back and forth about all the troubleshooting steps I've used to arrive at said conclusion, you could have said that in post #2, right after post #1 in where I ask if anyone in the forum knows about driver scripting.
You could have simply said. "I don't know anything about driver scripting." ... But why even post at all, then?
If that's the M.O. of this forum, I'd rather not integrate at all!
Just because you ask about scripting and whatnot doesn't actually mean you know what you're talking about. We get a ton of people who read stuff on google and come here to repeat it, when they simply don't understand what they are reading.
If you knew you needed a script, coming to a Windows 7 troubleshooting forum was your first problem. I'd assume if you had as much knowledge as you say you have, you would have figured this out by now and/or found the correct place to get that information.
You're probably better off not coming back to this thread because I highly doubt anyone will give you any real help after this long thread of resistance. Good luck.
For your information...
I have been a desktop repair engineer for 10 years.
I can tell you that there are instances where the PC just fails to detect the monitor correctly, through VGA cable, and the generic PNP or non-PNP driver fails to work correctly -- it may be buggy like the monitor not coming out of sleep, games may fail to run in full-screen or it may fail to work entirely. There is no 64 bit driver for the monitor in question and there is often no fix except changing. It has happened to at least two of my customers when upgrading their PC, it has happened to me too.
(Acer LA1716, Samsung Samtron 73V and others)
I tried a special program designed to home-brew monitor inf files, I tried traweling the internet for something.
Ultimately, the solution was to change monitor. Sorry!
Quote