KB 195950 - running app compatibility

[Guest]

Quote: " The first time an application compatibility script is run,
Rootdrv2.cmd is run".

I have located rootdrv.cmd in c:\windows\application compatibility scripts,
but I donot see rootdrv2.cmd. I have attempted to launch rootdrv.cmd from
command line but only get the text dump from the cmd itself.

I know this is a silly question, however, how do I run "application
comaptibility" to generate a rootdrv2.cmd?

We have a W2K3 server that was running in Admin mode, with Peachtree 2005
installed. A support tech came in and "upgraded" the server to App mode nad
installed the TS licenses. He did not inform us that PT is not TS compatible.
It appears with a modification of the rootdrv2.cmd, I will be able to get PT
to function, however I need toapparently generate the rootdrv2.cmd. How?

Thanks!

 

[Guest]

I have launched chkroot.cmd which successfully generated RootDrv2.cmd, and in
which I set the drive letter to "P". In research, I have also noticed the
download for "act30pkg.exe". I have downloaded but not yet run or installed.
Will this also be helpful to me for debugging applications not TS compatibile?

 

[Guest]

I have been able to resolve getting Peachtree 2005 to run successfully, and
stable in TS. The information I was able to obtain from reading earlier posts
to other threads in this forum, from other Microsoft newsgroups, and in
addition to the websites posted by Vera and by Patrick in their signature
lines have been tremendously helpful. By far, even without direct reply to my
post, you two are the most competent tech support I have found. Thank you.

Randall A. Mitchell
RAMTEK Network and Computer Solutions, Inc

 

[Vera Noest [MVP]]

act30pkg.exe is the Windows Application Compatibility Toolkit, right?

Have you read the page which describes the content of the package? It
contains documentation about known compatibility issues and
techniques to solve them, and some tools to analyze and fine-tune
compatibility issues. Can be very useful, but it is not something for
the faint-of-heart.
Do *not* install the package on your Terminal Server, but install if
on your own workstation.
You can use the tools from your workstation to gather information
remotely about the applications installed on your Terminal Server and
save it in an AppComp database on your workstation for further
analysis.

 

[Vera Noest [MVP]]

Glad to hear that, Randall. Thanks!

 

[Guest]

Thanks for the "heads up" Vera. I'll play with it in my test lab first!

I appreciate your help!