A Computer hardware and components forum. ComputerBanter.com

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » ComputerBanter.com forum » General Hardware & Peripherals » Homebuilt PC's
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

HP L2335 1920x1200 monitor died (?) after 12 years, 1 year afterstatic eletric discharge and 3 days after HDMI experiment via GT 520.



 
 
Thread Tools Display Modes
  #1  
Old December 2nd 18, 08:56 AM posted to alt.comp.hardware.pc-homebuilt
[email protected]
external usenet poster
 
Posts: 230
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year afterstatic eletric discharge and 3 days after HDMI experiment via GT 520.

Hello,

HP L2335 monitor 1920x1200 died after 12 years of usage, 1 year after it received a static electric discharge from my body/finger tip loaded by couche with static eletricity.

The power button of the monitor received the shock from my finger tips. I am surprised this monitor still managed to live for another year.

The power supply of the computer failed much sooner, also this PC power button received a shock at that time.

I suspect the HP L2335 power supply has developed some kind of failure because of over-voltage because of these high voltage static eletric discharges over time perhaps or perhaps that big one a year ago.

But there is more... I will get to the HDMI experiments in a moment...

The monitor HP L2335 cannot be opened, screwing off it's stand is easy, but I don't see a way to open up the display so I cannot investigate for any burn marks or whatever.

There was also some accumilated dust on the under-side/bottom-side of the device where there seem to be some gates/holes for very modest airflow or so.. It's quite a thick device and I can see some heatsinks inside.

(Currently I am typing this with help of a fujitsu siemens monitor which a (knwon defunct ) priest once bought for my mother which I kept through the years which kind belongs to an old athlon xp computer also from my parents but I never once used it inside my own appartment still have it though. It's resolution is 1280x1024, it has a little scratch cause I was careless transporting it, though not to bad, it's colors are kind nice, and it can be angled which is very nice)

Anyway I will tell you the moment of failu

1. First World of Warships updater was copieing a file inefficiently.

2. I finalled decided to de-install this piece of crap software cause it's taking way too long to update 35 GB... it's probably computing some kind of RSA key... I wonder if it was maybe done to check if my copy is "genuine" not modified or something probably not though... the download at 3.7 mb stuck at 47% which is also kinda weird. It was almost done though... but after many hours I decided it was enough. Time to say goodbye to at least this game for a while.

3. So after deinstalling WOWS... I deinstalled some other crap.

4. Then I decided it's time for a defrag of the C: drive, which is the only drive I configured for not automatic defragging, though I am not sure if windows respect this setting but probably, I could vaguely see that last run was 2017.

5. 1% was defragmented it said after analysis... however this is a 2 terrabyte drive so I am very skeptical. 1% of 2 TB is still 20 GB of fragmentation which could still be a lot.

6. So I decided to defrag the system drive. (After 5 passes I think I notice my system a bit faster now, not sure will have to test later).

Anyway I go to sleep or walk away the monitor goes into standbye or something... I try to power it on... and it fails to show a screen.

The symptom is now:

THE GREEN LED KEEPS BLINKING RAPIDLY...

So it's receiving power... but the screen won't come on.

another symptom is:

I CAN HEAR A SOFT/VAGUE CLICKING, IT'S SUNDAY MORNING SO VERY QUIET.

So either:

1. The power button circuitry is somehow failing.

or probably much worse:

2. The power supply has developed some kind of failure.

But there is mo

I was also experimenting with HDMI cables. I bought one "cheaper" one from rainbow computers in my local city, still 13 euros, so not too cheap.

Did look like good build quality, produced in netherlands it's high speed, think and has "ethernet" too which I asked the salesmen about... but he could not tell me much about it... it's probably some kind of HDMI control function capability.

I attached this HDMI cable to my receiver and to a toshiba laptop, and also later to my DreamPC from 2006 to it's GT 520 hdmi port.

I re-enabled HDMI driver in Windows 7 updated it and such and continued to experiment.

All while HP L2335 monitor was also connected to GT 520 asus graphics cards..

I noticed a couple of odd things in this setup:

1. Default windows 7 would try to extend the screen size or it did something weird, where on the right side of the screen the cursor would drop off.

It's like the resolution became 1920x1080 from receiver HDMI or something.... while actually/extended (?) size was 1920x1200.

I tried to reconfigure windows display options to only display on one device, but then HDMI and audio stopped working.

The idea was to use HDMI audio via GT 520 to a/v denon 1909 receiver which is used for audio only... to speakers from gigaworks s750.

This setup worked, though the resolution/mouse issue was weird and not ideal.

SO now I AM WORRIED:

That maybe somehow this FEEDBACK from the RECEIVER via HDMI to GT 520, may have OVERLOADED the HP L2335 which is using DVI.

What do you think ?

Is it possible that this setup somehow caused the HP L2335 to be overloaded with VOLTAGE from the ASUS graphics card GT 520 which is now using both DVI and HDMI ?????

Now that I think about it... maybe this GT 520 was not designed to use both PORTS at the same time ?!?!?!?!?!?!?!?!?

Maybe it did something weird causing the HP L2335 to receive OVER-VOLTAGE via it's DVI interface/cable ?!?!?!?!?!?!?!?!?!?!?

Another possibility is that the "heavy" defragging and copieing of WOWS caused many tiny voltage fluctations finally causing the monitor to fail after heaving received a big shock a year ago, though this scenerio seems much less likely since the HD is always busy anyway.

So I share this story with you in case using HDMI and DVI at the same time might cause some weird OVER-VOLTAGE issue ?!?!?!?!?

Also all experiments where done while all devices were on, except sometimes I did shutdown receiver just in case but PCs and laptops mostly kept running... too time-costly to shut those down for reconnect experiments.

Curious to hear from you guys if you have ever connected HDMI and DVI at the same time and if this caused any damage to monitors ?!

Let me be perfectly clear though:

The HP L2335 monitor does not have a HDMI port/interface, it was only connected via DVI. HDMI was only connected from PC to Receiver.

Fortunately 1920x1200 monitors are not that expensive anymore... I hear stories of 1920x1200 monitors for 100 or 200 bucks... I kinda look forward to buying some cheap/new... maybe it will be better... maybe better colors, maybe better refresh latency... sub 12 ms maybe ? though I also have my doubts... since gt 520 not that powerfull low latency would not be too usefull for now.

Though this monitor 1280x1024 is kinda nice... maybe I will change my mind and keep it as main monitor for this PC but probably not... bigger monitor would probably be a bit more nice and I do plan to keep using this dreampc from 2006 till hopefully 2019 and buying maybe a chiplet based CPU or maybe I will have to buy a new one sooner if more equipment dies.

I am glad my PC and drives are still functioning... the drives aren't too old... just a couple of years... so they should be able to handle a defrag it was a bit risky... but ok... windows 7 or it's windows explorer also has some kind of bug... it cannot delete two files which appear to have zero size... this is kinda funny... I will try deleting it from ms-dos might work.

Anyway I hope you enjoyed this story somewhat and see you later alligator ! =D

Bye,
Skybuck Flying ! =D
  #2  
Old December 2nd 18, 04:07 PM posted to alt.comp.hardware.pc-homebuilt
Paul[_26_]
external usenet poster
 
Posts: 885
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year afterstatic eletric discharge and 3 days after HDMI experiment via GT 520.

wrote:
Hello,

HP L2335 monitor 1920x1200 died after 12 years of usage, 1 year after it received a static electric discharge from my body/finger tip loaded by couche with static eletricity.

The power button of the monitor received the shock from my finger tips. I am surprised this monitor still managed to live for another year.

The power supply of the computer failed much sooner, also this PC power button received a shock at that time.

I suspect the HP L2335 power supply has developed some kind of failure because of over-voltage because of these high voltage static eletric discharges over time perhaps or perhaps that big one a year ago.

But there is more... I will get to the HDMI experiments in a moment...

The monitor HP L2335 cannot be opened, screwing off it's stand is easy, but I don't see a way to open up the display so I cannot investigate for any burn marks or whatever.

There was also some accumilated dust on the under-side/bottom-side of the device where there seem to be some gates/holes for very modest airflow or so. It's quite a thick device and I can see some heatsinks inside.

(Currently I am typing this with help of a fujitsu siemens monitor which a (knwon defunct ) priest once bought for my mother which I kept through the years which kind belongs to an old athlon xp computer also from my parents but I never once used it inside my own appartment still have it though. It's resolution is 1280x1024, it has a little scratch cause I was careless transporting it, though not to bad, it's colors are kind nice, and it can be angled which is very nice)

Anyway I will tell you the moment of failu

1. First World of Warships updater was copieing a file inefficiently.

2. I finalled decided to de-install this piece of crap software cause it's taking way too long to update 35 GB... it's probably computing some kind of RSA key... I wonder if it was maybe done to check if my copy is "genuine" not modified or something probably not though... the download at 3.7 mb stuck at 47% which is also kinda weird. It was almost done though... but after many hours I decided it was enough. Time to say goodbye to at least this game for a while.

3. So after deinstalling WOWS... I deinstalled some other crap.

4. Then I decided it's time for a defrag of the C: drive, which is the only drive I configured for not automatic defragging, though I am not sure if windows respect this setting but probably, I could vaguely see that last run was 2017.

5. 1% was defragmented it said after analysis... however this is a 2 terrabyte drive so I am very skeptical. 1% of 2 TB is still 20 GB of fragmentation which could still be a lot.

6. So I decided to defrag the system drive. (After 5 passes I think I notice my system a bit faster now, not sure will have to test later).

Anyway I go to sleep or walk away the monitor goes into standbye or something... I try to power it on... and it fails to show a screen.

The symptom is now:

THE GREEN LED KEEPS BLINKING RAPIDLY...

So it's receiving power... but the screen won't come on.

another symptom is:

I CAN HEAR A SOFT/VAGUE CLICKING, IT'S SUNDAY MORNING SO VERY QUIET.

So either:

1. The power button circuitry is somehow failing.

or probably much worse:

2. The power supply has developed some kind of failure.

But there is mo

I was also experimenting with HDMI cables. I bought one "cheaper" one from rainbow computers in my local city, still 13 euros, so not too cheap.

Did look like good build quality, produced in netherlands it's high speed, think and has "ethernet" too which I asked the salesmen about... but he could not tell me much about it... it's probably some kind of HDMI control function capability.

I attached this HDMI cable to my receiver and to a toshiba laptop, and also later to my DreamPC from 2006 to it's GT 520 hdmi port.

I re-enabled HDMI driver in Windows 7 updated it and such and continued to experiment.

All while HP L2335 monitor was also connected to GT 520 asus graphics cards.

I noticed a couple of odd things in this setup:

1. Default windows 7 would try to extend the screen size or it did something weird, where on the right side of the screen the cursor would drop off.

It's like the resolution became 1920x1080 from receiver HDMI or something... while actually/extended (?) size was 1920x1200.

I tried to reconfigure windows display options to only display on one device, but then HDMI and audio stopped working.

The idea was to use HDMI audio via GT 520 to a/v denon 1909 receiver which is used for audio only... to speakers from gigaworks s750.

This setup worked, though the resolution/mouse issue was weird and not ideal.

SO now I AM WORRIED:

That maybe somehow this FEEDBACK from the RECEIVER via HDMI to GT 520, may have OVERLOADED the HP L2335 which is using DVI.

What do you think ?

Is it possible that this setup somehow caused the HP L2335 to be overloaded with VOLTAGE from the ASUS graphics card GT 520 which is now using both DVI and HDMI ?????

Now that I think about it... maybe this GT 520 was not designed to use both PORTS at the same time ?!?!?!?!?!?!?!?!?

Maybe it did something weird causing the HP L2335 to receive OVER-VOLTAGE via it's DVI interface/cable ?!?!?!?!?!?!?!?!?!?!?

Another possibility is that the "heavy" defragging and copieing of WOWS caused many tiny voltage fluctations finally causing the monitor to fail after heaving received a big shock a year ago, though this scenerio seems much less likely since the HD is always busy anyway.

So I share this story with you in case using HDMI and DVI at the same time might cause some weird OVER-VOLTAGE issue ?!?!?!?!?

Also all experiments where done while all devices were on, except sometimes I did shutdown receiver just in case but PCs and laptops mostly kept running... too time-costly to shut those down for reconnect experiments.

Curious to hear from you guys if you have ever connected HDMI and DVI at the same time and if this caused any damage to monitors ?!

Let me be perfectly clear though:

The HP L2335 monitor does not have a HDMI port/interface, it was only connected via DVI. HDMI was only connected from PC to Receiver.

Fortunately 1920x1200 monitors are not that expensive anymore... I hear stories of 1920x1200 monitors for 100 or 200 bucks... I kinda look forward to buying some cheap/new... maybe it will be better... maybe better colors, maybe better refresh latency... sub 12 ms maybe ? though I also have my doubts... since gt 520 not that powerfull low latency would not be too usefull for now.

Though this monitor 1280x1024 is kinda nice... maybe I will change my mind and keep it as main monitor for this PC but probably not... bigger monitor would probably be a bit more nice and I do plan to keep using this dreampc from 2006 till hopefully 2019 and buying maybe a chiplet based CPU or maybe I will have to buy a new one sooner if more equipment dies.

I am glad my PC and drives are still functioning... the drives aren't too old... just a couple of years... so they should be able to handle a defrag it was a bit risky... but ok... windows 7 or it's windows explorer also has some kind of bug... it cannot delete two files which appear to have zero size... this is kinda funny... I will try deleting it from ms-dos might work.

Anyway I hope you enjoyed this story somewhat and see you later alligator ! =D

Bye,
Skybuck Flying ! =D


It does sound like your little experiment had something to
do with the monitor being upset. I don't think the static
did this, but your experiment did this. I don't believe
in "coincidences".

The only really dangerous thing in the HDMI cable, is the
+5V, which is power for EDID.

The flashing green LED, could be the power supply
going over-current, over and over again.

Have you tested the HP monitor with all HDMI cables
disconnected ?

If you have a Bluray player, could you generate an
HDMI signal from that, to test the HP monitor with
no other computers involved ?

I would only bother to do the HDMI test, if the
green LED will stop blinking. If the power supply
in the HP monitor is not stable, it really won't matter
what HDMI source you use for testing.

Also, *make sure* you have unplugged the HP monitor
from the wall, waited a minute or two, then plugged
it back in, and checked the flashing LED problem.
Some supplies inside devices are "latching", and they
record a fault, and they only "forget" when the
device is unplugged and all AC removed.

OK, so here is the test plan:

1) Disconnect *everything* from HP monitor.
Even the power cable should be unplugged.
2) Plug in the monitor.
If the green LED flashes, the PSU inside is dead.
3) If the green LED doesn't flash, now run an HDMI
cable from a "safe" source like a desktop BluRay
player.

If you get this far, and it's working, then you'll have
to consider whether your "experiment" is worth it.

HTH,
Paul
  #3  
Old December 2nd 18, 05:24 PM posted to alt.comp.hardware.pc-homebuilt
Flasherly[_2_]
external usenet poster
 
Posts: 2,144
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year after static eletric discharge and 3 days after HDMI experiment via GT 520.

On Sat, 1 Dec 2018 23:56:22 -0800 (PST),
wrote:

MIne's 20 years old, when a big-honkin 32" flatpanel first cost $1000,
though I run it native at 1360x768. It's a teevee - though at the
time also made for the same exact model -- just without a tuner.

The monitor firmware allows software over the computer signal
interface to shut it down.

That's no#1

An included infrared remote

That's no#2

All else fails, and only then, do I touch the PWR button on the
monitor

No#3

It's also been "acting up", I suspect, due to cooler weather. Normally
I use the remote and turn it off when not using this computer.
Software can be nasty on a blue moon, and I'll return to find the
software, possibly a corrupted computer condition, that the monitor
has been switched back on, magically, by the Ghosts in the Shell, or I
may as well rewrite the OS with a binary backup.

As it is I'm using softwa Nicely defined for the mouse cursor
placement, tightly into the upper-right corner, whereupon the monitor
switches into a STBY state of backlite tubes on, a minute or two or
something, before they're also turned off. Cute as hell, the reverse
then holds true: that when the move cursor is moved out of its corner
the monitor powers itself back.

How else could I have the oldest know working monitor thats run 24/7
for 20 years -- Brilliant/Olevia Syntax is the make and I've the
serial/model#'s to match. No way do I hammer on any of its controls
if at all avoidable through software.

Not, of course, that I did not notice a BestBuy sale on a potentially
decent $150/USD 43" monitor a few days ago. They're the only place
I'm aware of that'll send out a truck, for a few extra bucks warranty,
at your home to repair or replace a failed monitor that's 5- maybe
7-years-old. I know and bought it on the this last 40" sale from
them, but haven't get to use it -- it has lasted over three years, so
far, maybe even five without crapping.

No games, but a thrill a minute at least for me. A monitor that
eventually craps is sad;- one that craps early is hateful: You
couldn't give me a Spectre brand monitor from Wallymart.


Hello,

HP L2335 monitor 1920x1200 died after 12 years of usage, 1 year after it received a static electric discharge from my body/finger tip loaded by couche with static eletricity.

The power button of the monitor received the shock from my finger tips. I am surprised this monitor still managed to live for another year.

The power supply of the computer failed much sooner, also this PC power button received a shock at that time.

I suspect the HP L2335 power supply has developed some kind of failure because of over-voltage because of these high voltage static eletric discharges over time perhaps or perhaps that big one a year ago.

But there is more... I will get to the HDMI experiments in a moment...

The monitor HP L2335 cannot be opened, screwing off it's stand is easy, but I don't see a way to open up the display so I cannot investigate for any burn marks or whatever.

There was also some accumilated dust on the under-side/bottom-side of the device where there seem to be some gates/holes for very modest airflow or so. It's quite a thick device and I can see some heatsinks inside.

(Currently I am typing this with help of a fujitsu siemens monitor which a (knwon defunct ) priest once bought for my mother which I kept through the years which kind belongs to an old athlon xp computer also from my parents but I never once used it inside my own appartment still have it though. It's resolution is 1280x1024, it has a little scratch cause I was careless transporting it, though not to bad, it's colors are kind nice, and it can be angled which is very nice)

Anyway I will tell you the moment of failu

1. First World of Warships updater was copieing a file inefficiently.

2. I finalled decided to de-install this piece of crap software cause it's taking way too long to update 35 GB... it's probably computing some kind of RSA key... I wonder if it was maybe done to check if my copy is "genuine" not modified or something probably not though... the download at 3.7 mb stuck at 47% which is also kinda weird. It was almost done though... but after many hours I decided it was enough. Time to say goodbye to at least this game for a while.

3. So after deinstalling WOWS... I deinstalled some other crap.

4. Then I decided it's time for a defrag of the C: drive, which is the only drive I configured for not automatic defragging, though I am not sure if windows respect this setting but probably, I could vaguely see that last run was 2017.

5. 1% was defragmented it said after analysis... however this is a 2 terrabyte drive so I am very skeptical. 1% of 2 TB is still 20 GB of fragmentation which could still be a lot.

6. So I decided to defrag the system drive. (After 5 passes I think I notice my system a bit faster now, not sure will have to test later).

Anyway I go to sleep or walk away the monitor goes into standbye or something... I try to power it on... and it fails to show a screen.

The symptom is now:

THE GREEN LED KEEPS BLINKING RAPIDLY...

So it's receiving power... but the screen won't come on.

another symptom is:

I CAN HEAR A SOFT/VAGUE CLICKING, IT'S SUNDAY MORNING SO VERY QUIET.

So either:

1. The power button circuitry is somehow failing.

or probably much worse:

2. The power supply has developed some kind of failure.

But there is mo

I was also experimenting with HDMI cables. I bought one "cheaper" one from rainbow computers in my local city, still 13 euros, so not too cheap.

Did look like good build quality, produced in netherlands it's high speed, think and has "ethernet" too which I asked the salesmen about... but he could not tell me much about it... it's probably some kind of HDMI control function capability.

I attached this HDMI cable to my receiver and to a toshiba laptop, and also later to my DreamPC from 2006 to it's GT 520 hdmi port.

I re-enabled HDMI driver in Windows 7 updated it and such and continued to experiment.

All while HP L2335 monitor was also connected to GT 520 asus graphics cards.

I noticed a couple of odd things in this setup:

1. Default windows 7 would try to extend the screen size or it did something weird, where on the right side of the screen the cursor would drop off.

It's like the resolution became 1920x1080 from receiver HDMI or something... while actually/extended (?) size was 1920x1200.

I tried to reconfigure windows display options to only display on one device, but then HDMI and audio stopped working.

The idea was to use HDMI audio via GT 520 to a/v denon 1909 receiver which is used for audio only... to speakers from gigaworks s750.

This setup worked, though the resolution/mouse issue was weird and not ideal.

SO now I AM WORRIED:

That maybe somehow this FEEDBACK from the RECEIVER via HDMI to GT 520, may have OVERLOADED the HP L2335 which is using DVI.

What do you think ?

Is it possible that this setup somehow caused the HP L2335 to be overloaded with VOLTAGE from the ASUS graphics card GT 520 which is now using both DVI and HDMI ?????

Now that I think about it... maybe this GT 520 was not designed to use both PORTS at the same time ?!?!?!?!?!?!?!?!?

Maybe it did something weird causing the HP L2335 to receive OVER-VOLTAGE via it's DVI interface/cable ?!?!?!?!?!?!?!?!?!?!?

Another possibility is that the "heavy" defragging and copieing of WOWS caused many tiny voltage fluctations finally causing the monitor to fail after heaving received a big shock a year ago, though this scenerio seems much less likely since the HD is always busy anyway.

So I share this story with you in case using HDMI and DVI at the same time might cause some weird OVER-VOLTAGE issue ?!?!?!?!?

Also all experiments where done while all devices were on, except sometimes I did shutdown receiver just in case but PCs and laptops mostly kept running... too time-costly to shut those down for reconnect experiments.

Curious to hear from you guys if you have ever connected HDMI and DVI at the same time and if this caused any damage to monitors ?!

Let me be perfectly clear though:

The HP L2335 monitor does not have a HDMI port/interface, it was only connected via DVI. HDMI was only connected from PC to Receiver.

Fortunately 1920x1200 monitors are not that expensive anymore... I hear stories of 1920x1200 monitors for 100 or 200 bucks... I kinda look forward to buying some cheap/new... maybe it will be better... maybe better colors, maybe better refresh latency... sub 12 ms maybe ? though I also have my doubts... since gt 520 not that powerfull low latency would not be too usefull for now.

Though this monitor 1280x1024 is kinda nice... maybe I will change my mind and keep it as main monitor for this PC but probably not... bigger monitor would probably be a bit more nice and I do plan to keep using this dreampc from 2006 till hopefully 2019 and buying maybe a chiplet based CPU or maybe I will have to buy a new one sooner if more equipment dies.

I am glad my PC and drives are still functioning... the drives aren't too old... just a couple of years... so they should be able to handle a defrag it was a bit risky... but ok... windows 7 or it's windows explorer also has some kind of bug... it cannot delete two files which appear to have zero size... this is kinda funny... I will try deleting it from ms-dos might work.

Anyway I hope you enjoyed this story somewhat and see you later alligator ! =D

Bye,
Skybuck Flying ! =D

  #4  
Old December 3rd 18, 08:16 PM posted to alt.comp.hardware.pc-homebuilt
[email protected]
external usenet poster
 
Posts: 230
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year afterstatic eletric discharge and 3 days after HDMI experiment via GT 520.

It does sound like your little experiment had something to
do with the monitor being upset. I don't think the static
did this, but your experiment did this. I don't believe
in "coincidences".


It is indeed a bit suspicious. Though the monitor is very old 12 years and had some power button/come on failures in the past, and it also got stuck in the past... it just would not come in, which is strange in itself.

Any explanation why a monitor would fail to come on or turn off ? Strange isn't it ?

So it's not like this monitor didn't have issues, it did sometimes... which was insanely strange.


The only really dangerous thing in the HDMI cable, is the
+5V, which is power for EDID.

The flashing green LED, could be the power supply
going over-current, over and over again.

Have you tested the HP monitor with all HDMI cables
disconnected ?


Yes, just the power connected.

The green power led on the monitor starts blinking/shimmering and there is a soft clicking noise hearable.

When I disconnect power the power led keeps blinking/on for a few seconds.

Just to be clear: the monitor does not even have an HDMI port/connector... so that makes it even more strange.

If you have a Bluray player, could you generate an
HDMI signal from that, to test the HP monitor with
no other computers involved ?


I fail to see the point in this but here is some further information:

When I plug the monitor into the power, it automatically goes "ON".

The green power led is automatically blinking and such... this is very strange... normally it would be off and I would first need to turn it on ?!

It's either:

1. Stuck in "ON" mode.

or

2. It's using the blinking power led and clicking noise to transmit a signal to me the user ?! I could try checking the manual to see if this is some kind of error indicator.

For now I just consider it an oddity and possible sign of damage/malfunction.
  #5  
Old December 3rd 18, 08:26 PM posted to alt.comp.hardware.pc-homebuilt
[email protected]
external usenet poster
 
Posts: 230
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year afterstatic eletric discharge and 3 days after HDMI experiment via GT 520.

On Sunday, December 2, 2018 at 5:24:57 PM UTC+1, Flasherly wrote:
On Sat, 1 Dec 2018 23:56:22 -0800 (PST),
wrote:

MIne's 20 years old, when a big-honkin 32" flatpanel first cost $1000,
though I run it native at 1360x768. It's a teevee - though at the
time also made for the same exact model -- just without a tuner.

The monitor firmware allows software over the computer signal
interface to shut it down.

That's no#1

An included infrared remote

That's no#2

All else fails, and only then, do I touch the PWR button on the
monitor

No#3

It's also been "acting up", I suspect, due to cooler weather. Normally
I use the remote and turn it off when not using this computer.
Software can be nasty on a blue moon, and I'll return to find the
software, possibly a corrupted computer condition, that the monitor
has been switched back on, magically, by the Ghosts in the Shell, or I
may as well rewrite the OS with a binary backup.


Hey Flasherly...

I believe you when it says it's acting up...

The HP L2335 monitor sometimes also did weird things.

Like it would not come back on... or the power button failed to power it up, this has even been noticed from the very first start/review of this monitor.

Even disconnecting/reconnecting the power to it would sometimes not fix it... even after 1 minute of disconnect time it would not fix it... eventually after 3 minutes of disconnect it would work again.

So some hypotheses why this could be:

1. The hardware or firmware/software for these early devices was rushed.

2. Perhaps some weaknesses in the design of these power related buttons/issues.

3. New type of power buttons... might have had weak design at first... hopefully this is now better.

Your comments about using "software shutdown" was somewhat interesting, but do realise this adds more complexity to the device and thus more potentialy for problems.

But I do see a slight advantage of it, which might even be bigger than I realise...

Less wear and tear of buttons and such... though usually I though these buttons very softly and such... so not really that much wear and tear... they feel kinda soft.... like a soft push is enough... though sometimes it wasn't.

As far as I know this HP L2335 monitor did not have a total shutdown possibility via DVI signal ?!

You mention TeeVee... though you also mention computer... I don't know how your computer would communicate with your 20 year old TeeVee or monitor to tell it to shut down ? Hmmmm sounds a bit fishy ?

The only thing my monitor could do was go into "standby" mode... the power led would turn orange.

I would be worried that at night it might come on... becomes of neighbours causing vibrations are slight little earthquakes... causing unnecessary power consumption and perhaps were and tear of power supply going on/off like that.

Plus I like the idea of total shutdown for as far as possible... makes me sleep a bit better at night I guess...

No worries about "standbye" devices overheating and catching fire as I have heard stories about that

I rather have a dead monitor then my appartment and me burned to a crisp ! =D

Though this "auto-shutdown-feature" of monitor sounds interesting.

I will look for this functionality when purchasing a new monitor to see if this is a real functionality... or some whacky story from the internetzz ! =D

Bye,
Skybuck =D
  #6  
Old December 5th 18, 03:39 AM posted to alt.comp.hardware.pc-homebuilt
Flasherly[_2_]
external usenet poster
 
Posts: 2,144
Default HP L2335 1920x1200 monitor died (?) after 12 years, 1 year after static eletric discharge and 3 days after HDMI experiment via GT 520.

On Mon, 3 Dec 2018 11:26:47 -0800 (PST),
wrote:

Hey Flasherly...

I believe you when it says it's acting up...

The HP L2335 monitor sometimes also did weird things.

Like it would not come back on... or the power button failed to power
it up, this has even been noticed from the very first start/review of
this monitor.

-
I've only once had my monitor occur to be in a locked condition,
either on or off: I had to completely power off the computer (remove
AC from PS), as well the monitor, restore PWR and backup/restream the
OS. Fixed, but for indeed seemed close to indications of an hardware
component-level fault.

Similar, OTH, but probably not limited to a similar instance, to where
my modem may become un-synchronized (these new MB BIOS chips also have
a basic fault-test network status screen).

Even disconnecting/reconnecting the power to it would sometimes not fix it... even after 1 minute of disconnect time it would not fix it... eventually after 3 minutes of disconnect it would work again.


So some hypotheses why this could be:

1. The hardware or firmware/software for these early devices was rushed.

2. Perhaps some weaknesses in the design of these power related buttons/issues.

3. New type of power buttons... might have had weak design at first... hopefully this is now better.


Your comments about using "software shutdown" was somewhat
interesting, but do realise this adds more complexity to the device
and thus more potentialy for problems.

-
Yes, I do not particularly relish the very old video utility that's as
much coincident, however useful, to overriding IR remote or physical
monitor control buttons - due to their extreme age - I'd as soon not
engage, effectively due to superstition or a "hunch".

But I do see a slight advantage of it, which might even be bigger than I realise...

Less wear and tear of buttons and such... though usually I though these buttons very softly and such... so not really that much wear and tear... they feel kinda soft.... like a soft push is enough... though sometimes it wasn't.

As far as I know this HP L2335 monitor did not have a total shutdown possibility via DVI signal ?!


Offhand, I'd disagree there. Basic precepts, say from CGA, EGA, to
VGA are augmented, layered upon, ostensibly for backwards
compatibility as well future-feature implementations. At some
hypothetical conjecture, which "your mileage" may then have to account
no less for outright obsolescence.

You mention TeeVee... though you also mention computer... I don't know how your computer would communicate with your 20 year old TeeVee or monitor to tell it to shut down ? Hmmmm sounds a bit fishy ?


It's a Syntax model XYZ -- with tuner subsection. At the time the
same model was sold for Model ZYX - sans the tuner circuitry. In
order to the use the tuner, it's the same as most monitors I've
encountered: In that the computer input to monitor is overriden,
vis-a-vis the monitor IR or direct control menu - to be switched to
the tuner circuitry and associated coax aerial antenna-cable.

Joe Cheap's bigshot computer monitor, if you prefer. A total aspect
and rendition which would not agree with a fine detail for gaming
monitors, where HP stands well.

The only thing my monitor could do was go into "standby" mode... the power led would turn orange.

I would be worried that at night it might come on... becomes of neighbours causing vibrations are slight little earthquakes... causing unnecessary power consumption and perhaps were and tear of power supply going on/off like that.


Yes and same here. I "bumped" the 8'-4' conference table, my
makeshift "computer console" occupies, and the mouse was sensitive
enough to immediately turn on the gas-filled tubes of the monitor
back-lighting. Which annoys me: the monitor had not, over time
adequately left alone, submersed itself into a full pwr-down state,
which normally is a green-power indicator that goes dark upon
"awakening" the monitor into an active display state.


Plus I like the idea of total shutdown for as far as possible... makes me sleep a bit better at night I guess...

No worries about "standbye" devices overheating and catching fire as I have heard stories about that

I rather have a dead monitor then my appartment and me burned to a crisp ! =D

Though this "auto-shutdown-feature" of monitor sounds interesting.

I will look for this functionality when purchasing a new monitor to see if this is a real functionality... or some whacky story from the internetzz ! =D

Bye,
Skybuck =D



It's really old, this monitor utility I refer to, except ages ago once
hugely popular.

Let's see ... ah-ha!
https://powerstrip.en.softonic.com/

Also originally among freeware regard, but you know how that can go,
with "free lunch" on the menu to initially get people in on otherwise
business propositions. So my version probably dates to Palaeolithic
computers, somewhere in SVGA standards, if only then upon first
exceeding 800x600 resolution.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
1920x1200 on L2335 via Single Link DVI Ray Matrox Videocards 8 December 14th 04 03:18 AM
1920x1200 on L2335 via Single Link DVI Ray Ati Videocards 7 November 27th 04 09:58 PM
1920x1200 on L2335 via Single Link DVI Ray Nvidia Videocards 7 November 27th 04 09:58 PM
Happy New Year ..... 50 Years Research On Herbs ! Mustafa Arif Intel 0 January 5th 04 06:13 PM


All times are GMT +1. The time now is 11:30 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Copyright 2004-2018 ComputerBanter.com.
The comments are property of their posters.