Re: FFS!
From: Daniel O'Connell [C# MVP] (onyxkirx_at_--NOSPAM--comcast.net)
Date: 03/21/04
- Next message: Tony: "DB Sample Code Request"
- Previous message: Sky: "Re: Enumerate Static Fields of an non-instantiated class?!?"
- In reply to: C# Learner: "Re: FFS!"
- Next in thread: C# Learner: "Re: FFS!"
- Reply: C# Learner: "Re: FFS!"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 21 Mar 2004 13:03:54 -0600
"C# Learner" <csharp@learner.here> wrote in message
news:eX$aUE3DEHA.548@TK2MSFTNGP10.phx.gbl...
> Jon Skeet [C# MVP] wrote:
>
>> C# Learner <csharp@learner.here> wrote:
>>
>>>It must be .NET!
>>
>> 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.
>
> 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?
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+?
- Next message: Tony: "DB Sample Code Request"
- Previous message: Sky: "Re: Enumerate Static Fields of an non-instantiated class?!?"
- In reply to: C# Learner: "Re: FFS!"
- Next in thread: C# Learner: "Re: FFS!"
- Reply: C# Learner: "Re: FFS!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
