I'm curious. Did the option of using one of the workarounds posted in the Microsoft Security Advisory (912840) article come up?
Running "regsvr32 -u %windir%\system32\shimgvw.dll" or even removing the DLL from the system seems like a reasonable workaround while the official patch is being tested by Microsoft.
I've had some Logitech keyboards, but I did not like the plastic quality. They were making cracking noises when I typed on them, which drives me mad.
The Logitech MX series mice are totally different quality and imho much better than the competition.
After trying several keyboards from Logitech, Keytronic, MS I found that the HP EasyAccess USB is excellent. Very quite on ALL buttons in the right place.
Note. Strangely a brand new keyboard like the Keytronic 2001Pro is still using PS/2. I don't have such ports in my PC and I really think we need to exterminate all those Ps/2 and parallel/seriel port devices! - Along with the floppy drives of course;)
I still use PowerQuest DeployCenter 5.0 at work. We have a small testlab of desktop computers and around 60 GB of compressed images of Windows operating systems served fra a central computer.
Having a permanent partition for DOS on the clients, it is very fast to restore an image from the network. A bit of tweaking the TCP/IP networking in DOS was needed to get good performance. Tuning some TCP settings, especially TCPWindowSize, improved performance bigtime.
So I'd still recommend PowerQuest as a good product, though I can understand people not wanting to invest in PowerQuest products when I read about Symantec buying PowerQuest.
\o/ - got it fixed! Brought it in in the morning and could pick it up later that day. And guess what the invoice stated: "High voltage part fixed, tested ok". So, you were absolutely correct in your diagnose:)
It cost med about $150 USD, but goddamn I had forgot how nice the colors are supposed to be on this monitor!
You are right. Holding the menu button when turning on the monitor and then pressing the menu button again will go to the "secret menu". The code however is not 5455:(
I'll try search around too - let me know if you should come across it somewhere.
Oh well, maybe I can find some shop that knows exactly what this problem is caused by.
As to a "secret menu" that would fix it - I'm sorry, I must seem that one to believe it:)
I'll give it a google though...
And thank you for the info.
While on the subject of quality monitors I'll take a chance and hope someone know the problem and how it can be fixed.
About 3½ years ago I purchased a Nokia 446PRO 19" CRT monitor with totally flat image and very nice colors. Cost me about $1000 USD and Had a 3 year warrenty.
Of course it had to happen...a few months ago I noticed the colors where getting too bright - the black was more like gray - even turning down brightness to 0% was way too bright and adjusting contrast did not help either.
So, all the hardcore ppl of/. - Anyone know if this kind of problem can be fixed or I need to get myself a new monitor?
(Dealer says it will cost me $100 USD for them to just find the problem.)
I've been coding applets for commercial use with JRE on the Windows platform and I'm never doing that again. Every new release of JRE screws something up and currently I have to force users to have several versions of JRE installed which is a terrible solution.
Since the release of JRE 1.4.0 a critical feature has been broken and thought the bug has been submitted and acknowledged it has not yet been fixed. It has had the same "in progress, bug" status for more than 6 months:(
I can only agree with Sun, that there are serious problems with JAVA. For me it is especially part 4 "It is not backward-compatible across minor releases" which is why I vil NEVER do a JAVA-project which has to run on numerous customers computers again.
I enjoy programming JAVA, but the cost of support and maintenance are imho simply to big.
Slashdot Mirror
I'm curious. Did the option of using one of the workarounds posted in the Microsoft Security Advisory (912840) article come up?
Running "regsvr32 -u %windir%\system32\shimgvw.dll" or even removing the DLL from the system seems like a reasonable workaround while the official patch is being tested by Microsoft.
Hey, there is plenty of great Danish beer!!!
:]
Carlsbergs's "Semper Arden" series is definitely worth the hangovers
Plenty of other goodies:
http://ohhh.myhead.org/list/1c-den.html
sure they do...since none of M$'s own ERP product are targeted at the CAS market.
;)
Not yet anyway...
I've had some Logitech keyboards, but I did not like the plastic quality. They were making cracking noises when I typed on them, which drives me mad. The Logitech MX series mice are totally different quality and imho much better than the competition. After trying several keyboards from Logitech, Keytronic, MS I found that the HP EasyAccess USB is excellent. Very quite on ALL buttons in the right place. Note. Strangely a brand new keyboard like the Keytronic 2001Pro is still using PS/2. I don't have such ports in my PC and I really think we need to exterminate all those Ps/2 and parallel/seriel port devices! - Along with the floppy drives of course ;)
I still use PowerQuest DeployCenter 5.0 at work. We have a small testlab of desktop computers and around 60 GB of compressed images of Windows operating systems served fra a central computer.
Having a permanent partition for DOS on the clients, it is very fast to restore an image from the network. A bit of tweaking the TCP/IP networking in DOS was needed to get good performance. Tuning some TCP settings, especially TCPWindowSize, improved performance bigtime.
So I'd still recommend PowerQuest as a good product, though I can understand people not wanting to invest in PowerQuest products when I read about Symantec buying PowerQuest.
I think we can live with a few friendly casualities... ;)
\o/ - got it fixed! Brought it in in the morning and could pick it up later that day. And guess what the invoice stated: "High voltage part fixed, tested ok". So, you were absolutely correct in your diagnose :)
It cost med about $150 USD, but goddamn I had forgot how nice the colors are supposed to be on this monitor!
Thank you for convincing me to get it repaired.
You are right. Holding the menu button when turning on the monitor and then pressing the menu button again will go to the "secret menu". The code however is not 5455 :(
I'll try search around too - let me know if you should come across it somewhere.
Damn, 4 out of 5...
:)
Oh well, maybe I can find some shop that knows exactly what this problem is caused by.
As to a "secret menu" that would fix it - I'm sorry, I must seem that one to believe it
I'll give it a google though...
And thank you for the info.
Ok, thank you for the info. I will try to ask around some of the other shops than the one where I bought it.
:)
Maybe they have more of a clue
While on the subject of quality monitors I'll take a chance and hope someone know the problem and how it can be fixed.
/. - Anyone know if this kind of problem can be fixed or I need to get myself a new monitor?
About 3½ years ago I purchased a Nokia 446PRO 19" CRT monitor with totally flat image and very nice colors. Cost me about $1000 USD and Had a 3 year warrenty.
Of course it had to happen...a few months ago I noticed the colors where getting too bright - the black was more like gray - even turning down brightness to 0% was way too bright and adjusting contrast did not help either.
So, all the hardcore ppl of
(Dealer says it will cost me $100 USD for them to just find the problem.)
I've been coding applets for commercial use with JRE on the Windows platform and I'm never doing that again. Every new release of JRE screws something up and currently I have to force users to have several versions of JRE installed which is a terrible solution.
:(
Since the release of JRE 1.4.0 a critical feature has been broken and thought the bug has been submitted and acknowledged it has not yet been fixed. It has had the same "in progress, bug" status for more than 6 months
I can only agree with Sun, that there are serious problems with JAVA. For me it is especially part 4 "It is not backward-compatible across minor releases" which is why I vil NEVER do a JAVA-project which has to run on numerous customers computers again.
I enjoy programming JAVA, but the cost of support and maintenance are imho simply to big.
Make a OS/2 port of ROTT then ;)