win application and ctfmon conflict
- From: SMCDev <SMCDev@xxxxxxxxxxxxx>
- Date: Thu, 31 Mar 2005 17:57:02 -0800
I am posting this in a different group so sorry if it is a repeat...
We develop a suite of products that were originally written for windows 3.1
and have continued to work for Windows NT and now XP. With the release of MS
Office XP we have found our applications have a conflict with ctfmon running.
We have been telling our users to disable ctfmon according to the KB
articles provided by MS in order to get around the problem. We are really
wanting to get this fixed within our code base so we do not have to provide a
workaround.
Does anyone have an idea on how to achieve this with application calls?
One thing we realize is that the products are not "true" windows
applications. Some of the very low-level application startup code was
written in house.
Thanks,
SMCDev
.
- Follow-Ups:
- RE: win application and ctfmon conflict
- From: Rhett Gong [MSFT]
- Re: win application and ctfmon conflict
- From: adebaene
- RE: win application and ctfmon conflict
- Prev by Date: Re: Passing multiple arguments to a thread
- Next by Date: Re: Best way to access to the parallel port
- Previous by thread: deprecated API's in windows 2000
- Next by thread: Re: win application and ctfmon conflict
- Index(es):
Relevant Pages
|