FFS!

  • Thread starter Thread starter C# Learner
  • Start date Start date
Uri said:
please Find Somebody Who Cares
Click to expand...

Are you telling me that you know for sure that no-one in here cares?

If you can provide absolute proof of this, let me know and I'll cancel
my post.

In the meantime, I have two counter-requests for you:

1) Stop top-posting.
2) Next time you set out to write a worthless post, don't.
 
C# Learner said:
It must be .NET!
Click to expand...

Or something else about your system? It's hard to say what for sure, of
course, but the fact that no-one else seems to be able to reproduce it
suggests it's nothing inherent in the framework as a whole.
 
Jon said:
Or something else about your system? It's hard to say what for sure, of
course, but the fact that no-one else seems to be able to reproduce it
suggests it's nothing inherent in the framework as a whole.
Click to expand...

So far, I can say that it's /probably/ not the graphics card nor the
monitor, since the problem has been observed with two different graphics
cards and two different monitors (with all other components the same in
each case).

I guess the only other thing that could cause this in practise is the
processor. I'm no expert on hardware, though; does anyone know if there
are any other possible, practical causes of something like this?
 
C# Learner said:
So far, I can say that it's /probably/ not the graphics card nor the
monitor, since the problem has been observed with two different graphics
cards and two different monitors (with all other components the same in
each case).

I guess the only other thing that could cause this in practise is the
processor. I'm no expert on hardware, though; does anyone know if there
are any other possible, practical causes of something like this?
Click to expand...

Its unlikely its the hardware. A processor bug that only affects
instructions writing to the display seems fairly unlikely. Its possible its
due to your motherboards AGP system, but thats unlikely as well.

I would suspect its due to windows, possibly driver(though unlikely at this
point) or perhaps a strange installation of GDI+?
 
C# Learner said:
I guess the only other thing that could cause this in practise is the
processor. I'm no expert on hardware, though; does anyone know if there
are any other possible, practical causes of something like this?
Click to expand...

The only way you're going to find this problem is to start from scratch;
remove your existing hard drive(s) from the system for safekeeping,
install a temporary one, and put a fresh install of Windows and VS.NET
(and nothing else that's not mandatory) on it. If the problem is there,
it's hardware related. If not, you can start installing all your other
stuff to see what causes the problem.

Warning though: even this method may not find it, since the problem may
be installation-order related.
 
Daniel said:
Its unlikely its the hardware. A processor bug that only affects
instructions writing to the display seems fairly unlikely. Its possible its
due to your motherboards AGP system, but thats unlikely as well.
Click to expand...

Prior to installing the new graphics card, my computer was using onboard
graphics built into the motherboard -- it wasn't using the AGP slot
until now, so it looks even more unlikely.
I would suspect its due to windows, possibly driver(though unlikely at this
point) or perhaps a strange installation of GDI+?
Click to expand...

Hmm... good suggestion, though I did reinstall the .NET SDK and runtime
today. I'd presume that the .NET installers install or check for
up-to-date GDI components.

Actually, I'm thinking of purchasing a TFT monitor anyway -- I wonder if
such a monitor might help here at all...
 
Kevin said:
The only way you're going to find this problem is to start from scratch;
remove your existing hard drive(s) from the system for safekeeping,
install a temporary one, and put a fresh install of Windows and VS.NET
(and nothing else that's not mandatory) on it. If the problem is there,
it's hardware related. If not, you can start installing all your other
stuff to see what causes the problem.
Click to expand...

Putting in a new hard drive wasn't really practical here, but I did a
complete reinstall of XP today, and the problem persists :-(

I feel like taking the whole box back (it's only a matter of weeks old)
but I wonder whether the fact that .NET controls flicker badly would be
a sound reason for a refund.
 
Back
Top