Develop Bugs

Windows Vista, WM6, and Tethering

Ok I searched on the forums hard for this one so forgive me if this has already been answered. I see to find people with Windows Mobile 6 and Windows XP or people with Windows Vista but Windows Mobile 5.
Since I'm running Vista, I use Windows Mobile Device Center instead of ActiveSync. The functionality of the program is fine, so I have no complaints. However, to upgrade ROMs or anything...I use an XP Machine as it seems Vista seems to think the device disconnects upon the loading of the bootloader. I've read somewhere in the forums that there is a driver update to fix that, but after applying...WMDC doesn't work properly...so I'd save the trouble and use a machine that has XP running instead until a better fix comes along.
My 8525 came stock with a program called Wireless Modem as of ROM 1.34.502.1 shipped, which seems to have been replaced by Internet Sharing.
The Wireless Modem application worked fine after setting up the modem with the Vista driver also found in the forums. I also tested the bluetooth connection and set that up to tether as well and it worked fine.
I finally decided to upgrade after days of reading and I tried to use the Wireless Modem feature. I noticed it wasn't there and tried to use Internet Sharing. The layouts are similar...but when I hook up the phone under USB, my computer doesn't even recognize it as a new device (modem) as I did uninstall the last driver.
When connected via Bluetooth, it recognized the device and installed the driver as Windows Mobile-based device support by default. Under services, only Active Sync is only available...as opposed to before when I had Dial-Up networking available. When I set up a PAN, the computer and device are connected together, however I do get the same problem as some others with a connection that is limited or local only. So the tethering is unsuccessful.
I recently upgraded my Cingular 8525 to WM6BE v1.2 (Cingular Edition)...which I can't seem to find in the threads anymore. I'm also running Radio 1.38.00.11...but I don't think that would affect anthing. I reverted back to my shipped ROM to check for alternate settings that might have helped...then I was going to revert back to WM6BE v1.2 Cingular...then I realized I accidently deleted that custom ROM and I couldn't find it anymore. I was stuck putting on the WM6BE v1.2 on the sticky thread after which forced me to reinstall the data settings/keyboard fix from the cab files. Haven't had problems with them but I did like that customized ROM for Cingular a little better considering I really like "clean" ROMs.
Anyway, I'm attempted to connect via MEdia Net AND Cingular GPRS settings provided by the Cingular Data Settings cab floating around the forums. It works fine it seems...it just seems like the problem is getting Vista to recognize the device as a modem, or at least having modem capabilities.
I guess thats as detailed as I can get right now. Hopefully someone can help now ^_^

You are right. I tried updating rom on Vista's Windows mobile Device and end up damaging my xda2i. The device displays "USB" when connected to cradle and "Serial v1. 01" when not. Do you have a solution apart from upgrading?

Solution on Vista
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck

Have I understand right? With this tweak We will be able to applied ROM upgrades to our HERMES from windows VISTA?

Confirmed.
I did already update my ROM in this way.
Cheers,
soniX
EDIT:
Please use HardSPL or something equal to be sure the risk is at a minimum.
And I can not be held responsible for any damage to your Hermes or your Brain
But as I said, for me it worked perfectly, remember to Restore the new Drivers or the Mobile Device Center will not work.

Hmm I don't think you people understand what I was asking...
I already know about that method to update with Vista...I actually tried it yesterday and for some reason it didn't work so I just use an XP Machine for now...but I was just asking merely about TETHERING.
I already have the ROMs of my choice loaded on my device.
In simpler words: How do I go about tethering (Running Internet Sharing) when my computer does not recognize the device as a modem...through USB or Bluetooth.
I'm running WM6BE v1.2 and Windows Vista Ultimate.

Maybe its Wm6BE, but I have used all the other roms (xda live, des, lsvw) and all I do is plug in the usb, start internet sharing and it connects no problem. Have to start internet sharing before wmdc starts. Internet Sharing works great, better than wireless modem. I was not able to use the WM6be due to problems with sbp pocket plus. I am currently using XDA live .30 and Vista Ultimate.

Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )

I enjoy the community so I think I'll do my best to contribute to it. When I get the chance, I'll try to make a guide with screenshots on using Windows Vista and loading WM6.
I'm going to try to switch to LVSW build with his new update today and I'll see how that works out.
I REALLY like the one custom build someone made (I forgot who) with the Cingular connection settings defaulted from the Cingular Shipped ROMs...I wish I can find those files again.
It seems like the people developing the new Cingular data connection cab files are really working hard at getting the default settings as if they just bought their phoes straight from Cingular.
I'll let you know how LVSW goes with Internet Sharing and Windows Vista

sonixwarrior said:
Hello Guys, I'm running vista too and I bothered 2 hours before getting it done.
So this is one of the "Step-By-Step Instruction Guides".
0. Extract the attached file into a directory of your choice
1. Disconnect your Device
2. Goto Settings > Connections and choose "USB To PC"
3. Uncheck the option there
4. Reconnect your Device
5. Goto your DeviceManager and search for "HTC USB Sync", double click it and choose Drivers
6. Click on the "Update Driver"-Button and choose search on the computer
7. Click "Choose a driver from list..."
8. Click the button to the right (Open from Media)
9. Choose any INF File from the extracted ones.
10. You're done, upgrade your ROM.
11. To Rollback drivers, use the "Automatic Update" instead of Manually selecting (it will choose the newest ones)
12. Recheck the option of step 2 unless you're planning to use the slow variant.
Have Phun and Good Luck
Click to expand...
Click to collapse
Also, I've seen this guide posted twice...yours missing one step where I was supposed to "End WMDC.exe Process in Task Manager"
I still can't get Vista to run RUU...do you run the RUU with your device in Bootloader? I think I even tried that once and and still couldn't get it to work with the older Driver.
Not exactly sure what I'm missing or doing wrong...but its definitely after I install the driver. It acts as if I didn't install it at all, even if I check in drive details and its all correct in there.

i tried the method above for upgrading in vista and it didnt work for me...
what am i missing?

Where is it stopping?
Because I did it once, it has to work.
Where is it stopping? - At the bootloader (LSD-Screen with psychedelic colors ?) - or before ?
I will do an upgrade in the afternoon again and this time i will record ALL of my steps.
Hopefully I'll find the recept for the cake.
Cheers,
soniX

Yea it gets to the bootloader screen and I'm stuck as if I never loaded the AS4.5 drivers.

Sorry, too less time today for a screenshot-decorated guide.
I just upgraded my device again (only to proove it does work).
So here is again a guide, which differs to the first one.
I guess there are two ways to do this...
Prequesites:
- Search my previous post and download the USBAS.zip-File
- Extract it into a directory...
- You'll need your device and it has to be connected, too
The first approach:
Change the Serial-Driver
- On the device click Start > Settings, choose "Connections" there and click on "USB to PC"
- uncheck the item for "Enhanced..." there
- Click on OK.
- Now goto your Device Manager.
- Search an Item named "HTC USB Sync".
- Right-click it and choose "Update Driver".
- Choose the second option, then select to choose manually
- Select the directory where the zip has been extracted to and choose any inf file.
Start the Update-Tool
- After the driver-update you need to set the device back to RNDIS-Mode (follow Step 1 and recheck the option)
- Verify that you're running the correct drivers for the RNDIS-Device, the date in the device-manager has to be around January, 17th 2007.
- Start the ROM-Upgrade.
- It should work now.
For me it did not really work to switch from RNDIS to USB-Serial drivers in my localized (thanks bepe for the great work!) german WM6.
So if you have a problem with the first method use this one.
- Start your Device-Manager, we have to be very fast.
- Start the ROM-Upgrade as you've probably done before
- If the bootloader starts up, you'll notice a device/dettached,device/attached sound, this is your sign, goto to you Device-Manager.
- Search for the Entry "HTC USB Sync".
- Update drivers like it's written above.
- If it won't work and the upgrade tool dies with "cannot connect", don't worry. Reset your device (soft) and try again, this time you should not need to update the drivers.
Cheers,
soniX

I'm using XP and a USB cable. USed to work OK before upgrading to WM6 Black but now I get Error 797 on the PC saying modem not found or busy!

mrvanx said:
Does the technique in the post above work??
Also once that procedure is carried out can rom updates and RUU programs be used exactly the same as on XP??
If anyone is available to do some screenshots for me for an updated GUIDE, please PM me (i dont use or have a copy of vista )
Click to expand...
Click to collapse
Take a look here
Code:
http://www.modaco.com/index.php?showtopic=252977
For Vista guide with screen shots, so far i've only flashed HardSPLv4 from inside Vista, but it worked i'm still plucking up enough courage to do a full flash of WM6
Nic

I do this (for Hard-SPL, don't know for other):
I have made what it was written on modaco (http://www.modaco.com/index.php?showtopic=252977), but
1) I was not in bootloader.
2) While active sync try to connect (but it does not succeed because they are not its driver) I've stopped WMDC.EXE and now hermes is connected.
3) NOW I do a flash.
If there is something that is not clear you say it to me.

My method also works (for me)
Can somebody confirm that my method works for vista?
soniX

I'm based also to your method, but it would be more complete to integrate it with the method on modaco.

It seems that most people didn't get the point of this thread...weird considering I put TETHERING in the subject line. However, it is nice to see people trying to help others with Vista to flash. I have the same problem myself but access to machines with XP nullify my real need for flashing on Vista for now.
I'm about to reinstall LVSW's latest ROM set for the billionth time and I'll try out tethering on that. It seems that people who were on WM6BE were having a hard time with Internet Sharing. I'll load a new rom and let you know how it goes.

COM4 dissapeared

Hi,
I use an MDA Compact III with the official T-Mobile WM6 ROM (dutch). After installing Trackr (www.trackr.nl) software I'm facing a serious problem: my internal GPS seems to be missing. In some GPS software I can still see COM4, but in Google Maps (for example) COM4 is missing. I've set the Windows Mobile GPS setting off, to avoid conflicts. I never use more than one GPS program at the time. Whether COM4 is visible or not, none of the GPS applications can connect to the internal GPS.
Is there a way to reset the COM4 port, so I can access the GPS again? I uninstalled Trackr and did several soft-resets, but nothing is working?
Thanks for your advice,
Wouter

Hi Wouter,
What version of trackr! did you use? The most current versions try to detect the MDA Compact III and avoid issues you describe by automatically disabling the GPS auto-detect option.
When using the GPS auto-detect option on your device in older trackr! versions, issues you describe might happen. This is caused by an external component used to access GPS devices. More information about this can be found here: http://www.geoframeworks.com/forum/Topic1253-45-1.aspx#bm1270 :
"GPS.NET will modify the "ActiveDevice" key with the Prefix and Index which it finds during detection. The keys starting with "GPSOne" will not need to be modified. Here are the typical steps a user would need to perform to restore their registry:
1) First, delete the "Control Panel Configured Device" key created by GPS.NET:
HKLM\System\CurrentControlSet\GPS Intermediate Driver\Control Panel Configured Device
2) Second, the Index and Prefix values underneath the "ActiveDevice" key should be set to "4" and "COM"
HKLM\System\CurrentControlSet\GPS Intermediate Driver\ActiveDevice "
To be sure, first backup your registry before making changes to the registry.
I hope this will fix the issues you have. I also hope you will still give trackr! a try by downloading the latest version. I'm sorry for the problems experienced by you.
Finally: please try to contact the people at trackr! first before posting your question here. They are more than willing to try to help you with any problems you might have.
Regards,
Marco

Is this an advert or what???

ActiveSynC via Bluetooth?

Anybody plz help me setup activesync via bluetooth...I am using k rom 1.30a full and bluesoleil 5.05...I could use activesync in default microsoft stack but that is just too crappy to be used ...the problem lies in activesync com port selection dialogue box ....it doesnt show the serial comport that blusoleil is using(com 24)in my case...Any body know how to make (com24) available in the activesync?
I will be very much thankful

Try using Widcomm bluetooth software and get the ISSCBTA driver.
Im using it and it works quite well. here is a link to a great guide:
http://www.telusplanet.net/public/wladykad/

This works for me:
Determine the local (PC) virtual serial port. For Toshiba Bluetooth stack (my case) went to: from Start -> Control Panel -> Bluetooth Local COM which Com port the “LocalCOM-Server[SerialPort]” is assigned to (in my case COM7),
Open the Registry Editor in Vista and go to: HKEYLM\Software\Microsoft\Windows CE Services\ and change the SerialPort from “Bluetooth” to the assigned COM port you found before (like COM7)
That’s it. Now reboot (dont' skip rebooting, otherwise it will not work) your PC and create a new Bluetooth partnership (I’m always initiating it from Windows Mobile). Should appear now ActiveSync.

latadeatum said:
This works for me:
Determine the local (PC) virtual serial port. For Toshiba Bluetooth stack (my case) went to: from Start -> Control Panel -> Bluetooth Local COM which Com port the “LocalCOM-Server[SerialPort]” is assigned to (in my case COM7),
Open the Registry Editor in Vista and go to: HKEYLM\Software\Microsoft\Windows CE Services\ and change the SerialPort from “Bluetooth” to the assigned COM port you found before (like COM7)
That’s it. Now reboot (dont' skip rebooting, otherwise it will not work) your PC and create a new Bluetooth partnership (I’m always initiating it from Windows Mobile). Should appear now ActiveSync.
Click to expand...
Click to collapse
Tried it but my acticesync still shows com 3 instead of what i want (com24)

Keyboard help QTEK S200 + Stowaway IR Keyboard

Installing from CD or from onine driver I get identical results. Working with Windows Mobile 5.
The PC shows this message:
Could not delete registry: SOFTWARE\\Microsoft\CurrentVersion\\Uninstall\\{FD32EBD5-A526-44C0-8464-5BC3F4136F60}\\WceIniFiles\\Install
while at the same time the PDA shows: Keyboard installed and ready to use.
Then after a PDA restart (automatic) I get this:
Keyboard Driver Error! The Keyboard driver StowawayXT.dll is not responding. Please reinstall.
I have uninstalled and reinstalled several times!!!
Then when I go into "Program Files" and press the Keyboard icon, I get this:
The Keyboard language file StowawayXTRes.dll has not been loaded on the system. Please use the correct installation process.
I can select the Stowaway as text input but nothing happens when I press keys.
I don't know anything about programming. I just hope to run the installation and everything works... so I'm in big trouble now!!! Anyone have a clue?

Hi I have the same problem with the Serial keyboard did you manage to resolve your problem?

IR keyboard
can you please put the online site for the download of the software for th eIR keyboard

help for dll

hallo friend, i ve a big problem on my p3300, i have downloaded program much important for my job as FIELD TEST, but on artemis does not works.
so i have read on web more more pages and i understand that the problem is a dll that in p3300 /windows there isnt: rilgsm.dll.
without this dll some port are closed on my htc i suppose com 9 and 6 (network ) so field test doesnt work propely!
can someone explane me how i can solve this problem or i can extract or add this dll.
i have actually italian wm6 official on my p3300 , but i can install also a unofficial rom with rilgsm.dll.
i wait for help as soon as possible
thanks

rilgsm.dll is in the Artemis Touch 4.01 WM6.1 WWE ROM - Lite without cube ROM as well as the other versions (full, vanilla, etc) I suppose.
But, I'm not sure that is the complete answer to your problem. I was trying to run a program which ran fine on my previous PPC using com6 but would not run on my Artemis using com4 (needed to run TomTom). Today, I found a solution here that works. It's called portsplitter. I installed it today and sucessfully used TomTom (requires com4) and the other program (requires com6) as well on the newly created com8! (see the link above to makes sense of that). Maybe what you need?
Here's another link in the Artemis forum discussing this issue.

runningtiger said:
rilgsm.dll is in the Artemis Touch 4.01 WM6.1 WWE ROM - Lite without cube ROM as well as the other versions (full, vanilla, etc) I suppose.
But, I'm not sure that is the complete answer to your problem. I was trying to run a program which ran fine on my previous PPC using com6 but would not run on my Artemis using com4 (needed to run TomTom). Today, I found a solution here that works. It's called portsplitter. I installed it today and sucessfully used TomTom (requires com4) and the other program (requires com6) as well on the newly created com8! (see the link above to makes sense of that). Maybe what you need?
Here's another link in the Artemis forum discussing this issue.
Click to expand...
Click to collapse
thanks for answer, maybe can you explane how i can set ports?
i need only field test works , it is only excutable file, no need installation, there isnt configuration to do , is very simple, maybe i can send to ou the file to test.
i wait for help thanks again

pls help me

I don't know how to copy just the rilgsm.dll file you want. It's part of the rom and so access is denied on both the phone and via activesync.
Also, I don't know how to set ports. Did you try the portsplitter application I linked to above? I am using an application on my phone right now that uses port 6 thanks to the portsplitter application. Try it!
Upload your application here or post a link, and I'll see if I can give it a try.

i ve uploaded file here: http://www.megaupload.com/it/?d=ZL2OLMS0
please try it, anyway i dont know how to use port spkitter right mode, maybe i wrong to setup it
for it i need help

no one answeres.........

what's up with the (mad) face man? I have been trying to help you. I had a busy weekend and we are in totally different time zones - so relax.
Here, I will spell out very clearly how to use portsplitter...
Artemis settings:
start menu\settings\system tab\external GPS
programs tab...com8
hardware tab...com9/baud 4800
access tab...tick (select) manage GPS automatically
PortSplitter settings:
input: using your keyboard type COM8
baud: select 4800
output: select com6 and press 'add' then press 'start splitter'
the program will then be running in the background
Now go to your fieldtest app and set it to use com6 at 4800 baud. Or, if you know it uses com6 by default, just open it and see if it works.
If it works, you have two options. You can either start portsplitter each time you want to use it. Or, go back to the portsplitter app and tick 'autostart' so a link will be placed in the \windows\startup folder and you won't have to start it manually each time you reboot. It will always just run in the background. (edited to ad...) Actually, selecting 'autostart' only saves your settings so each time you open portsplitter it will run on com8 etc. You need to manually put a shortcut in the windows\startup folder for it to actually start up each time you turn your phone off and back on.
Now, if you use the portsplitter AND any other GPS programs (i.e. TomTom), you'll need to set that program (i.e. TomTom) to use com6.
In TomTom you do this by pressing the lower right hand corner of the screen where the clock and signal strength bars are. On the next screen press the right hand side of the screen where the battery status and signal strength bars are. Now press the lower left corner button called 'configure' and choose 'other NMEA GPS receiver' and press 'select'. Set the baud rate on the next screen for 4800 and press 'done'. Finally, press 'com:6 Port Splitter' and press done!
It works fantastic on my Artemis. I have another GPS program and I set up the GPS communications to use com6 at 4800 and it works like a charm as well. I've set PortSplitter to autostart after each boot, and I haven't given it a thought since. It just works.
I tried to download your app but there is a message that says "The file you are trying to access is temporarily unavailable."

I have fieldtest running on my Artemis right now. It looks like it auto sets itself to refresh every 3 seconds. The right hand side of the screen is called 'GSM' the left is called 'data'. Almost all data fields say N/A except for RSSI and Rx Quality. So, it looks like it runs, but does not work.
Probably due to this:
"fieldtest is not compatible with 9100/Prophet/Artemis. For those devices you need to use GSMTestMode.exe"
However, just in case you might still find this info useful...before trying fieldtest on my phone, I searched what it was about and found the info here. You may have already read it, but if not, there you go. BTW, (if you DID read it) you could have just directed me there to download the program rather than how you did it.
Lastly, I tried the registry edit:
HKEY_LOCAL_MACHINE -> SOFTWARE -> HTC -> EngineerMode -> BuildInEngineeringModeApp = 1
It changed nothing, the program is still mostly full of N/A responses. Also, ran the program from \windows and got the same responses as when I ran it from the memory card.

GSMTestMode.exe exists on my Artemis in the \windows folder.
To use it check this registry setting:
HKEY_LOCAL_MACHINE -> SOFTWARE -> HTC -> EngineerMode -> BuildInEngineeringModeApp = 1
Mine was 0 originally. I changed it to 1 and soft reset the phone. Then, opened the \windows folder and clicked on GSMTestMode.exe and all the info shows up instantly.
That was with portsplitter running in the background. So, I disabled portsplitter, soft reset and clicked on GSMTestMode.exe again - and it worked. Using/not using portsplitter made no difference. I did not check the values reported since I don't care enough. The rest is up to you.

thank you very much runningtiger, your info were very very precious for me, now works all fine.
only 1 problem: after i edit value from 0 to 1 in registry, gsm test mode works fine , but if i reboot artemis or shutdown and restart registry value back 0.
is there any way to solve?
bye and thanks again

This isn't an issue on my phone. I made the registry change using TotalCommander and used the exit command on the menu to close TotalCommander (rather than the X in the upper right hand corner). Then, I soft reset by pressing the reset button with the stylus. When my phone was ready to go again, I opened GSMTestMode.exe used it, closed it, then reset my phone again, used GSMTestMode.exe again and it worked again. So, the registry change sticks on my phone.
Usually the reason registry changes don't stick is not enough time passed before soft-resetting the device. Some registry changes are ready to use immediately, but others take a moment to actually write to the registry and if that process is interrupted then the change isn't actually made.
Three thoughts on your phone...
1) did you wait about a minute after making the registry change before soft-resetting your phone? This allows plenty of time for the change to be actually written to the registry.
2) wait a minute after doing the registry change, then try instead of soft-resetting doing a full power down by holding the power button until you are asked if you for sure want to turn off the phone and then let it sit a minute (off) before starting it up again?
3) can you try using TotalCommander to make the registry change like I described above?

runningtiger said:
This isn't an issue on my phone. I made the registry change using TotalCommander and used the exit command on the menu to close TotalCommander (rather than the X in the upper right hand corner). Then, I soft reset by pressing the reset button with the stylus. When my phone was ready to go again, I opened GSMTestMode.exe used it, closed it, then reset my phone again, used GSMTestMode.exe again and it worked again. So, the registry change sticks on my phone.
Usually the reason registry changes don't stick is not enough time passed before soft-resetting the device. Some registry changes are ready to use immediately, but others take a moment to actually write to the registry and if that process is interrupted then the change isn't actually made.
Three thoughts on your phone...
1) did you wait about a minute after making the registry change before soft-resetting your phone? This allows plenty of time for the change to be actually written to the registry.
2) wait a minute after doing the registry change, then try instead of soft-resetting doing a full power down by holding the power button until you are asked if you for sure want to turn off the phone and then let it sit a minute (off) before starting it up again?
3) can you try using TotalCommander to make the registry change like I described above?
Click to expand...
Click to collapse
i resolved upgrading to wm6 official and now works all fine, so my friend thanks again for support and precious infos