Need Help!! PLEASE!!

[President Killer]

Well, I posted this a few days ago, but there's no answer...

I have a terrible problem with Windows XP Service Pack 2 and the .NET
Framework 1.0 (included with Visual Studio .NET 2002). Since I installed the
SP2, I can't see any text on labels, buttons, frames and lists on all my
..NET applications whose controls have the "FlatStyle" property set to
"System". I need to do that in order to make the Windows XP Visual Styles to
work with my applications. If I set back the property to "Standard", most of
the controls' captions are visible again, but some others aren't.

All the people I know that has Windows XP SP2 along with Visual Studio .NET
and the StyleXP application, don't have this problem. I've tried
re-installing the .NET Framework and even repairing the Visual Studio .NET
installation... but nothing seems to work. I'm desperate, and I don't want
to format my hard-drive again... I just did it like a month ago!!

PLEASE!! HELP ME!!

System Specs:

- 512 MB of RAM
- 160 GB HDD
- Pentium 4 2.4 GHz with HyperThreading enabled
- Windows XP Professional SP2
- StyleXP v. 2.16
- Visual Studio .NET 2002
- Microsoft Office 2003
- Macromedia Studio MX 2004
- Jasc Paint Shop Pro 9.0
- CyberLink PowerDVD 5.0
- Windows Media Player 10
- Maple 9.5
- Microsoft Encarta 2003 Reference Library
- WinZip 8.0
- WinRAR 3.10
- Nero 6 Ultra Edition
- McAfee VirusScan Enterprise 8.0i
- Sygate Personal Firewall 5.5

 

[Roy Chastain]

Well, you say that you are using VS, but I will pass this along to you anyway. There is an issue with Borland Delphi that is NOW
documented that sounds just like what you are describing. Only thing the Borland problem happens with both 1.0 and 1.1 after SP2
is installed. Borland is still working on the problem. They have overly integrated with the .net framework and it appears (from
what I understand of it) that they were looking at parts of the manifest that MS did not intend people to validate. When the
..DLLs got updated via SP2 and/or the Framework SP that came about the same time, things went haywire.

Good luck

 

[Nick Malik]

I'm going to suggest that you do something that you may not have thought
of... call Microsoft Product Support Services.

If you install a service pack, and the application dies (I've seen messages
like this before), it is sometimes a bug in the service pack. You are
unlikely to be charged for that.

--- Nick

 

[President Killer]

Well, I've tried calling the tech support about this, but they always
say that "they're still trying to find a solution", though there isn't
any yet...

This problem is terrible. I hope that the guys over Borland can manage
to solve this issue.

Thanks for your replies

 

[President Killer]

Well, I've found the little bastard...

My antivirus (VirusScan Enterprise 8.0i) was the one that didn't let my .NET
applications to work correctly... even though I don't know why. A friend has
the same antivirus (as well as VS. NET 2002 and Windows XP SP2) and he
doesn't have this problem... it's indeed strange. Maybe the guys at
Microsoft and Network Associates should check this problem and try to post
something about it, since nowhere in the freaking Internet says something
about it...

Well, now I'm using the "regular" VirusScan (with Internet Security Suite
7.0), and it works fine. I hope I don't get this crappy error with anything
else in the future.

Thanks anyway to all of you that actually replied to my first messages.