runs on win2000, but not on xp

  • Thread starter Thread starter Bull
  • Start date Start date
B

Bull

Hi,

Our application was built on win2000 machine. It couldn't perform certain
functions (read binary data and view them) on an XP machine. It doesn't have
this problem on our win2000 machines. Then we installed Visual C++ and MS
platform SDK on that problematic XP machine in order to debug the problem.
But after we installed these development tools, the problem is gone.

Is there any migration issue we should know when migrating from win2000 to
XP, such as packaging some libraries that are unique on win2000 but not on
XP? For our case I suspect the develoment tools installed some libraries
that are required by our application.

Bull
 
-----Original Message-----
Hi,

Our application was built on win2000 machine. It couldn't perform certain
functions (read binary data and view them) on an XP machine. It doesn't have
this problem on our win2000 machines. Then we installed Visual C++ and MS
platform SDK on that problematic XP machine in order to debug the problem.
But after we installed these development tools, the problem is gone.

Is there any migration issue we should know when migrating from win2000 to
XP, such as packaging some libraries that are unique on win2000 but not on
XP? For our case I suspect the develoment tools installed some libraries
that are required by our application.

Bull


.
Click to expand...
my best guess on this issue is in the "compatibility mode"
feature. winxp can emmulate down to win95. check the
properties of your program. As a double check I would
set up another xp machine the same way as before the
addition of the c++ and ms platform sdk. make sure the
same version of xp is used. Then change the properties of
the program to emmulate the win2k platform.

BTY, the development tools probably added the runtime
package. which could also be the culprit.
 
-----Original Message-----
Hi,

Our application was built on win2000 machine. It couldn't perform certain
functions (read binary data and view them) on an XP machine. It doesn't have
this problem on our win2000 machines. Then we installed Visual C++ and MS
platform SDK on that problematic XP machine in order to debug the problem.
But after we installed these development tools, the problem is gone.

Is there any migration issue we should know when migrating from win2000 to
XP, such as packaging some libraries that are unique on win2000 but not on
XP? For our case I suspect the develoment tools installed some libraries
that are required by our application.

Bull


.
Click to expand...
my best guess on this issue is in the "compatibility mode"
feature. winxp can emmulate down to win95. check the
properties of your program. As a double check I would
set up another xp machine the same way as before the
addition of the c++ and ms platform sdk. make sure the
same version of xp is used. Then change the properties of
the program to emmulate the win2k platform.

BTY, the development tools probably added the runtime
package. which could also be the culprit.
 
Back
Top