Error Dos message by TPAutoConnsvc.exe after installing East Asian language

[sjackwu]

I also submitted a request to VMware Support

This happens on Vista as well (JP version, http://itsukamitaasa.jugem.jp/?eid=11, but I can't read the post)

---

OS: Windows XP Pro SP2, with latest updates, VMware Tools (build 43733) drivers and Boot Camp (1.2beta) drivers

Error message in a Dos box after reboot:

Title:

"C:\Program Files\VMware\VMware Tools\TPAutoConns..."

Content:

"TPAutoConnect User Agent, Copyright (c) 1999-2007 ThinPrint GmbH, 7.8.364.1

Virtual channel initialized.

No suitable client protocol found."

And then the two last lines just keep repeating themselves...

Also, the "language bar" does not appear (it should be after installing "East Asian languages" support)

Procedure to create the error:

1. Install "East Asian languages" support in Control Panel's "Regional and Language Options" and change all applicable settings to either "Taiwan" or "Chinese (Taiwan)" in "Regional and Language Options".

2. Reboot.

3. The Dos box in question appears, and the "language bar" does not appear (it should be after installing "East Asian languages" support).

[Harliv]

Thank you for your feedback. We are looking into this issue and tracking it via your Support Request

[solgae]

This is happening to me as well during startup, but I can use the language bar normally. I minimize it to the taskbar. I just get that annoying DOS windows TPAutoConn thing. What is the purpose of the program?

[heypeter]

Just wanted to confirm that you are not alone .... same general issue (XP Pro SP2, Bootcamp, VMware Tools etc all up to date). Installed languages are Japanese, English, and German. In my case the language bar (ie. blue square for selecting languages) shows up and is functional.

I think the DOS box started happening with the latest release of Fusion with Bootcamp support. It only happens with Bootcamp "VM's" as far as I can see, my regular XP Pro VM based on a .vmdk file inside OSX does not have this problem.

[sjackwu]

I think it's not the Bootcamp "VM" that TPAutoConnsvc.exe conflicts with, but the the Bootcamp drivers.

Why do I know that? Because my VM image is .vmdk as well. . But I installed Bootcamp drivers on it...

[blackpuma]

This happens on Vista as well (JP version,

http://itsukamitaasa.jugem.jp/?eid=11, but I can't

read the post)

It basically says that he ran into he same problem when installing Vista.

Hmm... maybe Mr. Gertzfield can be prodded to translate the response at the bottom of the post. My Japanese is too elementary to get a handle on it. Looks like it's a (known?) problem in the VMware Tools version of the file. OK. I'll top embarassing my self trying to work with Japanese.

(Cool. I'm adding "virtual machine" to my vocabulary list. grin)

[admin]

Google[/url] and/or babelfish to the rescue (?).

[blackpuma]

LOL. Rikai-chan.

[sjackwu]

Problem persists with new Fusion & new Boot Camp...

VMware Fusion 1.0b4 (48339)

VMware Tools for Windows 7.3.0 build 48339

Boot Camp 1.3 beta

Windows XP Pro SP2 Eng (image built on VMware workstation 5.5.x)

BTW, do you guys test Fusion with other native language versions of Windows? I saw some complains about App menu doesn't launch programs on Traditional Chinese Windows...

[Dreamszz]

Still have the problem with Vista Business US, Bootcamp 1.2 and Fusion 1.0 51348, FYI.

VMware Tools 7.3.1 build 50460

[Pat_Lee]

To solve this problem, try the following:

1) Inside your VM, go to Add/Remove Programs and uninstall VMware Tools

2) Restart your VM

3) Once the VM restarts, select Install VMware Tools from the Virtual Machines menu

4) Go through the Tools installer and restart when done

The components causing this problem should not be removed.

Hope that helps.

Pat