[Tilt, TyTN II, MDA Vario III General] joel2009:
Alot of people are having problems making the switch to vista, i created this thread to help out making the move easier and help solve some compatability issues, as currently they aren't very easy to find all in one place. This thread is a depository for vista how-to's and fixes. I will continue to updates it as i find problems and solutions.

-----MY KAISER ISN"T BEING READ BY WINDOWS VISTA!!!!!-----

If your kaiser isn't being read by windows vista there is a pretty simple solution, you just need to disable advanced networking on your kaiser. To do this go to:

START----SETTINGS---CONNECTIONS---USB TO PC---UNCHECK THE BOX

After you do this your computer should greet you like r2d2 and install drivers and then connect to WMDC. :)

If you have further problems try swapping usb cords or using a different usb port (you have to connect via usb for the first time.)

------Using your device as a modem--------

WARNING tethering your devise is usually in violation of your contract, you will be able to use your phone as a modem but if you start using "excessive" amounts of data you could get in some trouble.

This is also a simple fix and requires only that you use the program "internet share" on your kaiser. (if you don't have it you can get it here thanks to ericc191) download the file and unzip the two items in it and place them in the windows directory. You can then create a shortcut and place in Windows>Start Menu>Programs.

Run the program and then select the type of connection you would like to use, bluetooth or usb. if you use bluetooth you will need to set up a partnership before hand. Personally i recommend usb because it is more secure won't kill your battery because it is plugged in and charging. Choose the internet service you would like to connect to and then push "connect" (left soft button.) Vista should automatically install the modem driver connect to your phone AS A MODEM. You will not be able to transfer file at this point as vista is recognising your phone as a modem, not as a windows mobile devise. you will not be connected to windows mobile devise center(WMDC.)

----I can't read my files or set up my device!----

Is your device connecting to WMDC? if not read "my kaiser isn't being read by windows vista." If your device is connected make sure you have disabled programs such as "MY MOBILER" as they do not react the same way as they do with active sync.

----Flashing in vista is here!!!

I take no credit for this, A big thanks to MrVanx as he made this tutorial possible!

One problem with windows VISTA is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.

NOTE: PLease Download the latest version of WMDC before attempting this.

You will need winrar to extract the files

First of all you will need one of these drivers depending on your version of Vista:

Windows Vista x32 Usb Driver

Windows Vista x64 Usb Driver

NOTE TO x64 WINDOWS USERS, you will need to boot up with driver signing enforcement turned off. To accomplish this, you will need to press F8 during boot up. If you do not do this, the 64 bit drivers will not install properly and this tutorial will not be of any use to you.

And of course you will need the Vista RUU

Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.

1.Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA PC.

2.Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon.

3.In the connection settings menu untick "allow USB connections" then press OK.

4.Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.

5.Scroll down the list and make sure these services are present:

Windows Mobile-based connectivity

Windows Mobile 2003-based connectivity

If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.

6.Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".

This will bring up the properties of the currently connected device (the Kaiser in bootloader).

7.Go to the "Driver" tab and click "Update Driver".

8.Click "Browse My Computer for Driver Software".

9.Select "Let me pick from a list...."

10.Click the "Have Disk" button.

11.Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.

12.

Vista x32 users select the file "wceusbsh.inf"

Vista x64 users select the file "wceusbshx64.inf"

Click open.

13.click next and the driver will be installed (wait a moment).

14.Press close and escape back to the desktop now.

Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.

Click the WMDC line and click "End Process". In the confirmation window, again press End Process.

Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").

Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which Vista uses when the device is in bootloader mode.

NOTE:: This technique is still in testing! It has been proven to work though!