Waylander
|
| Posted: 05/03/2003, 1:34 PM |
|
Finally, I now have my pop up windows working. All I did was remove Microfats critical update Q813489 for XP... I am now about to try the Win2000 box and see if we can fix that...
Thanks microsoft and Yes softweare for your complete lack of support on this issue as now I must choose having a critically insecure PC on a cable modem or NOT have CC work.
NOT happy!!!
|
|
|
 |
James Puddicombe
|
| Posted: 05/04/2003, 3:33 PM |
|
Quite agree - this makes CodeCharge on its own totally unacceptable as a commercial piece of software.
|
|
|
|
Joachim Uersfeld
|
| Posted: 05/05/2003, 4:28 AM |
|
It is not fair to attack YesSoftware. Microsoft made changes without advance notice. Before the 813489 patch CodeCharge works without any problems on my system. I am safe me, YesSoftware will find soon a solution for the problem. But debt does not meet this developers.
|
|
|
|
rclayh
|
| Posted: 05/05/2003, 9:31 PM |
|
It just points up the whole problem of a monopoly operating system. Yes has to deal with whatever comes down the pipe. Microsoft can "patch" them out of existence while Microsoft can make sure their stuff works since they know in advance what they are going to break.
It's silly to blame Yes for this.
|
|
|
|
Larry Boeldt
|
| Posted: 05/05/2003, 11:02 PM |
|
I can't figure out why everything is a Microsoft Monopoly thing. I run Various Windows, Linux systems and an OSX system. Patches always mess things up, just the way it goes. Fact is Microsoft OS is by far the easiest to use and is used by a majority of developers (sorry linux folks it's the truth).
SO let's end the meaningless banter and get down to the core issue. A patch in Windows XP (and windows 2000 from what I can tell) seems to break code charge, an application from Yes Software that Waylander has every expectation would operate just like his other applications. Fact is it doesn't and none of Waylanders other software is affected, hense the problem must not be with Microsoft in the first place. Afterall the problem is not with Windows XP it is with Code Charge. Thus Yes software is responsible to fix the problem for all of us.
|
|
|
|
Angelo
|
| Posted: 05/06/2003, 7:24 AM |
|
I don't even have this patch listed in my install, so I'm stumped at what the problem could be.
Damn and blast you microsoft and you're infernal 5 patches a week! Anyone noticed at least once a week on XP you get a "security patch to fix a vunerability that could give a remote user COMPLETE UNADULTERATED ACCESS to your computer/files/life/bank account/Secret files" ;)
|
|
|
|
Billy
|
| Posted: 05/06/2003, 11:10 PM |
|
Larry has it right, Dreamweaver, Adobe, Visual Studio, PhotoShop, Illustrator, Office 2000, Office XP, ER Win, Oracle, ER Studio and none of the other software I have on my computers were effected.
What can you expect from a VB6 application?
|
|
|
|
|
