Active Sync being a bore - General Topics

i had some usb issues and removed everything usb and put it back on with drivers and the likes
but since then activesync dont show other com ports then com1
it simply refuse to show my bluetooth com ports
i've tried to stop using ms drivers
changed to AS4.1
nothing seem to work do anybody have some info
about AS having some limit as to what # nr of com ports i want to play with
because my com port # are up in their 2X now
this guy seem to have the same issue
http://www.pdastreet.com/forums/showthread.php?t=64721
maybe if i login in vga mode where i can see all old unused devices i can remove com ports with lower #'s and add a new one inside AS's range if it have such a range ?

fixed it safe mode is not enough though you have to do a
set devmgr_show_nonpresent_devices=1
too
to see the devices you once had

Ah, indeed, that old chestnut! Not only is Activesync ****e, so is the operating system that bore it....
Enlighten yourselfs to this crap:
Phantom / Ghosted COM Ports:
Rid your XP system of 'phantom' COM ports. These ports have been created at some time by an app or hardware that is NO longer present, but XP is holding the COM ports as valid but hidden. MS ActiveSync (even v 4.1) will ONLY see single digit COM ports per design, so you HAVE to get those COM port assignments into the single digits. Here is the link the MS site that describes how to rid your XP system of the phantom ports:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315539
Further reading:
http://help.lockergnome.com/lofiversion/index.php/t26563.html
God preserve us! ARGGGGH :evil:
Andy

Related

Activesync 4.1 USB (Cradle) Issue

I've been using Activesync 4.1 (on WinXP Pro) with WM5 (1.60c) with no problems for the past month on my imate (Himalaya). I was able to sync via USB, BT, and IR. Suddenly, syncing through USB (Cradle) no longer works! I can sync fine via BT and IR, but when I try to sync via USB, here is what happens:
* Placed imate on cradle
* PC network detects this and provides IP address for USB. At this time, I can ping the imate. Activesync (AS) detects the imate and and the AS icon in the PC's toolbar turns green and starts to rotate
* AS says "connecting"
* imate neither says or shows anything (i.e. NO moving or rotating arrows on top bar near signal strength icon, as would be expected during sync).
* Activesync on imate also shows that it is NOT connected and shows info about last sync date and time
* when I press the "Sync" button on AS in imate, it shows "connecting" for a split second, then goes away, but that does not help.
* Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB when it was working with no problems.
*It stays in this state indefinitely, or until I remove imate from cradle
Here is what I did to troubleshoot (Believe me, AS 4.1 has been a headache that caused me many long hours, days and weeks to solve. I had that dreaded 85010014 error that took weeks to resolve, so I was prepared to do all kinds of things to troublshoot this, but to no avail. I searched many forums, including this one, and googled to no end before writing this post):
* Although it was working with my e-trust firewall before (had it set up to OK all activesync programs), I turned it off just in case.
* Although it was working with my e-trust Antivirus before, I turned off realtime montoring just in case.
* On the imate, I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1)
* I pinged imate, and it responds fine
* I checked on my PC under "Network Connections" and it shows a Local Area Network for the Windows Mobile-based device
* I checked my PC hardware and found Windows Mobile-based device and is working properly
* I made sure that both AS on the PC and imate have the USB syncing option checked
* I exited XCPUscaler and unchecked PPC Profiles Pro from Today screen
* Doubting that this had to do with application of Darren Humphries' Activesync tweek, I reverted it back to default (see below).
* I unistalled the "Windows Mobile-based device" under Network Adapters, restarted PC, then re-attached imate.
* I unistalled the "Windows Mobile-based device" under Network Adapters, restarted PC, uninstalled Activesync 4.1 on PC, restarted PC, removed AS folder in program files, looked for rapi.dll (did not find it), deleted activesync related entries in registry, restarted PC, removed partnership from imate, soft-reset imate, reinstalled AS4.1, then attached imate to cradle.
* Basically, I did everything that was suggested so far, short of reinstalling WinXP on my PC or hard resetting the imate
Believing that AS should not suddenly stop working on its own (not sure if this is a valid belief!), I retraced my steps to see what changed since the last USB sync. Here are the changes (note: there were no WinXP updates made during that period):
On imate:
* Installed XCPUscaler
* installed PPC Profiles Pro (Brett Darnell's)
* Installed Toe's ScreenRotate Fix
* Installed MS Voice Command
* Applied Darren Humphries' performance tweek as follows: "In order to stop Activesync from periodically starting on it's own. To do so open Activesync on your WM5 device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right. You can now go to Menu>Options and delete the Exchange Server setting you just added. Now Activesync will not start when you cradle your device."
Could it be a hardware issue, i.e. USB connection on the imate connector not working (if so, then why would I be able to ping the imate with no problems through USB?). Please let me know if I am missing something.
Thanks!
KJ
Just to help isolate the problem, I installed AS 4.1 to another WinXP machine and attached the USB cradle connector to it. Same problem. Hence, it does not seem to be a PC issue.
So far, it seems to be isolated to either the imate or the cradle (and cable). Note that the PC recognizes the USB connection and does the networking thing just fine, hence the cradle should be OK (is there a way to check the USB connection on the cradle to make sure it is OK?). Pinging also works both ways and I see the 169.254.2.1 address on teh imate. So, the problem does not seem to be the connection. Rather, it seems to be with Activesync on the imate realizing that the imate is cradeled.
Recall that one of the changes to the imate I made right before this problem was the AS hack of a fake Exchange server so that the schedule is changed to "Manually", as described in my first post. I reverted back to original "every 5 minutes" but the problem persists. Are there registry keys that I can compare to make sure registry is correct? Note that I can sync fine with BT and IR and both of these have entries in AS Menu that say "connect via IR..", etc. in order to connect manually, but no "connect via USB" manual option.
KJ
I had a problem very similar to this.. it only appeared with 'guest' and no partnership..
Turned out my calendar/contacts file was corrupt.
activesync issue
my exec sync the first time allright did instale some software after that next day ,i've got this message alltime :twisted: To synchronize this device,you must install ActiveSync 4.0 or higher.....
i did unstale the active sync instal it again same pb .plz help anybody
i keep reading the forum nearley every day but seems only me got pb now with activesync???
i hope it's the roght place to put down this issue otherwise plz direct me
many thnx
activesync issue
sry i was bit quick in the posting
well i've got win xp sp2
i've done the same things as kj
ihad aswell that error 85010014,;and the server assigned IP adress issue
and after unistallig many reboot anr reinstallig active sync .........
it's basiclly frustrating .
I 'm give up slowly on it
any help will be very welcome or direct me in the right posting
Activesync 4.1 USB Issue (more info but still _not_ solved.)
Thanks for the suggestions and comments. I refrained from responding before I performed a thorough (re)investigation. I have the following updates: I just received a boxwave minisync retractable USB cable for my imate/XDAII/Himalaya to test out the theory whether the cause of the problem was a cradle problem (i.e. applied process of elimination on hardware). Unfortunately, the problem still persists. I can now safely eliminate the possibility that it was the cradle from my previous investigations. Therefore, I decided (having done all the investigation above) that it must be either of the following culprits:
A. Himalaya hardware
B. Himalaya software
I tackled the hardware issue (A) first: I checked the functioning of the USB hardware: My logic dictates that if I can connect the Himalaya to a PC using USB and conduct functions through that connection, then the USB hardware should be OK (except for perhaps any hardware switches or pin grounding the flat connector on the other end of the USB cable makes that activate the Himalaya onboard activesync program, as discussed below). So, I performed the following tests (some are repeats of what I already tried and wrote, just for good measure):
1. Connected Himalaya to my laptop (call that “PC1”, since recall that I tested on two separate PCs) via USB cable. It detects it fine and goes through the hardware detection and driver install process, creates a network adapter and connection and provides an IP address for the USB connection (169.254.0.1 for Himalaya and 169.254.0.2 for PC1). At this time, I can ping the Himalaya. ActiveSync (AS) on PC1 detects the Himalaya and the AS icon on the PC's toolbar turns green and starts to rotate, as before, but no reaction from Himalaya.
2. Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB back when it was working with no problems, so not sure if this is an issue (it wasn’t before).
3. On the Himalaya, I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1). I pinged the Himalaya from PC1 and PC1 from Himalaya, and the responses are fine both ways. This tells me that USB connection hardware must be working, otherwise, I would not have been able to pass ping packets back and forth.
4. I went one step further (just to be sure) and downloaded and installed Softik’s Card Export II v2.10 (yes, this version supports WM5, a nice piece of software). In “Card Export mode”, I connected Himalaya to PC1,which detected it as a USB Mass Storage Device, as it should. It installed the drivers and it worked just fine! I wanted to make sure that I am getting USB speeds, so I benchmarked the connection and got over 3Mb/s transfers from PC to SD card, steady. This tells me that at least USB, as a connection, is OK.
5. So, only thing left is to eliminate any possibility of a hardware issue, I looked into the Himalays flat connector pinout diagram. To simplify, the following are the pins relating to USB (excluding any grounds):
13 USB_VDD
14 (or 15) UDC+
15 (0r 14) UDC-
For those who are not familiar with the Himalaya flat connector, “UDC+” and “UDC-“ are USB data pins. “USB_VDD” is the USB power pin. USB_VDD when powered wakes up Himalaya and activates onboard activesync. I thought perhaps if this pin were defective, Activesync on the Himalaya would not activate. I assume that this pin is where the Himilaya gets its battery charge current when connected via USB, as pins 20-22 are “V_ADP”, which are used for charging only when connecting to a wall or car charger (please let me know if this is an invalid assumption). Hence, I wanted to check to see if the battery indeed charges through USB. I saw that when Himalaya was connected via USB, the battery charged just fine (light goes solid amber, battery monitor says “Charging”) and it charges the battery fully as expected.
With the foregoing, I can conclude that the problem is very unlikely hardware related (as in A, above). Since I already eliminated a PC problem (I checked on another PC with different hardware/software, as described in my first post), the only thing left to investigate is a software problem on the Himalaya itself. This is where I look for the developers in the forum to provide expertise: My analysis tells that when the Himalaya is connected via USB and the PC Activesync shows “Connecting”, while the Himalaya shows nothing, that the Himalaya is behaving as if it were not connected to USB, or is ignoring the USB connection, i.e. in Himalaya Activesync, under “Menu””Connections …”, as if the box next to “Sychronize all PCs using this connection:” is not ticked or the drop down list is not set to “USB”. I checked and unchecked this box and chose other connections (such as various serial speeds), just to see if this would change some persistent setting and set it back, with soft resets in between, but to no avail. Is there a registry setting that I can check to see if this setting is doing the correct thing? If so, where is it? It is here where my investigation trail runs thin and is where I am looking for insight in the matter. Appreciate your input….
Active Sync 4.1 on WM5
I had the same problem after upgrading to WM5 on BA (Xda iis)
But I finally found the resolution for this problem
If you can not sync with your USB try this:
go to the properties of the My Network Places
Plug in you device and you will see a new network connection
On the properties page on the new connection you will see that the internet protocol (TCP/IP) is not checked
Select the TCP/IP checkbox an then apply changes
The USB will start connecting to the device.
@kj
i have the same problem as yours sinds yesterday.
i think i happend just right after i've cleart the duplicate enteries from the events database. (check notification/scarybear)
do you use some sort of databse cleaner software?
for the record i've tryed with htc wizard (wm5) and htc himalaya with wm2003. when i sync with the himalaya then is everyhing fine. the wizard have the same problem as yours.
Re: Activesync 4.1 USB Issue
Thx all for the replies.
@ISR: Verified that TCP/IP was already checked. Note that if that was not checked, I would not have been able to ping the device. I really doubt this is a PC issue, although I realize that most people had problems with their PCs and Activesync (I checked this with 2 separate PCs with completely different configs, one with no virus checker or firewall). The problem is most likely the software on the Himalaya. When you say yours had the same problem as mine, do you mean that you were able to ping pckets through USB both ways, sync through BT, but when syncing through USB, only Activesync on the PC shows "Connecting" with nothing going on on teh Himalaya (most people have the opposite problem due to firewall and other TCP/IP issues)?
@Badboy18: No, I don't use a database cleaning software, unless one of the softwares installed on the imate already does so in the background. Same question to you as with ISR: When you say yours had the same problem as mine, do you mean that you were able to ping packets through USB both ways, sync through BT, but when syncing through USB, only Activesync on the PC shows "Connecting" with nothing going on on the Himalaya (most people have the opposite problem due to firewall and other TCP/IP issues)?
hi all,
just to add to the defferentes experience well, I've got as well a xdalli and i did use it with activesync 3.8;so when i bought the exec I installed the as 4.0,after that I did remove all the activesync with ther regestry key and defferent folders on the pc;fraiche install again ,well all the step donne by kj
and now I got thise message came as <to synchronise this device,you must install activesync 4.0 or higher on your desktop computer> ?????
and on the pc i've got AS 4.1.0(build 4841)!!
some times when I restart the pc and do a soft reset on the exec ;it does connect as guest????..sometimes :x :x
and the xdalli still can do a parternership with the pc even it's AS4.1,were in the forum it's normaly has to be with AS 3.8???
I believe very much the probleme is in the activesync software put on the xda exec (sry i'm not very technical to try defferentes things;it's just suggestion) thx for u everybody to try to get this exec to sync just dont give up
How to ActiveSync after deleting repllog.exe
try this link of any help
http://www.ppcsg.com/lofiversion/index.php/t53614.html
kj said:
I've been using Activesync 4.1 (on WinXP Pro) with WM5 (1.60c) with no problems for the past month on my imate (Himalaya). I was able to sync via USB, BT, and IR. Suddenly, syncing through USB (Cradle) no longer works! I can sync fine via BT and IR, but when I try to sync via USB, here is what happens:
* Every now and then, a popup window says "Unable to Obtain a servier assigned IP address....", even though I made sure that the Remot-NDIS Host network adapter uses "Server assigned IP" addresses (and it shows 169.254.2.1) and pings fine. Actually, this message popped up all the time when syncing through USB when it was working with no problems.
I had this problem. Try config manually this:
In Settings/Connections/Network Cards :
Select Remote- NDIS Host ----> Use specific IP addrees
IP address = 169.254.2.1
Subnet mask = 255.255.0.0
Default Gateway: 169.254.2.2 or 169.254.2.1
I have this config and it is working now.
In your PPC Select In : My Network card connects to : "The Internet" and the same should be selected in your PC ActiveSync ---Connections Settings ---This computer is connected to: "The Internet".
Click to expand...
Click to collapse
Thx for suggestion. I tried that before, and again just now, but it did not work. As mentioned before, I can ping fine both ways, which tells me that DHCP worked and provided correct IP address for communication. Basic hunch is that the problem is with the device, i.e. Activesync on the _device_ ignoring the USB connection. All other software I tried that use the USB connection (whether pure USB, or through the TCP/IP stack) work. So, I am zeroing on activesync on the device, but have reached a dead end, as I don't know which registry settings and processes spawn on the _device_ when activesync starts a USB sync (perhapsone of them is not running).
KJ
kj,
Similar problem. Hard reset, problem now gone. Have you tried HR option yet?
I was planning to do a hard reset, as a last resort (I mentioned once that I wanted to debug the hard way first!). I will do a HR only if you think the problem will go away with a data-persistent HR (WM5 feature), rather than a clean wipe. The reason is that if I am to do a clean HR, I would rather do that when a new ROM is around for an upgrade (as you know the Himlaya ROM development is quite active). If you think a data-persistent HR would rectify this, please elaborate as to what options to choose with bootloader to make that possible.
Thanks!
I'm able to sync but I get the stupid "Unable to obtain IP..." via USB.
Everything is setup correctly and sync works, but the message is anoying and without a cause.
I used eramosipn solution - fixed IP - problem gone. Thanks dude!
I guess something is broken in the registry.
I sync with 2 different PC's and this problem occured on on both. Since the beggining I know this is a PPC problem. Just don't know what to correct.
Anyhow, with the fixed IP the stupid annoying message is gone.
Where can we found the correct registry settings related to USB activesync?
Activesync and Firewalls
I have a personal firewall in my pc (sygate).
I upgrade to windows 2005, everthing was fine.
Someday stop working.
After research I find that if I disable the Sygate Firewall service ( In Control Panel) it starts working.
Can this be the case for you?
Do you have any firewall in you system (including xp firewall)?
Try to disable or uninstall.
Hi
I am not sure if will help anyone but her goes.
Upgraded SPV M1000 to WM 2005 most recent 1.71a 64.
Upgraded desktop Windows XP and Company Lap with activesync 4.1.
I now have 3 different reactions from activesync.
1. No problems with Home desktop (outlook 2003 running in none exchange server mode).
2. Will not sync with comany laptop (Outlook in exchange server mode) while working at home offline (not connected to company server).
3. No problems to sync with Company Latop (Outlook in exchange server mode) when working online to company server.
Anybody found away to solve instance 2?
Thanks Mike
MTU problem?
I cannot recall where I read this, and cannot find any references via Google except for Sygate firewall MTU issue, but I did read somewhere that Activesync 4.x defaults to an MTU size of 8000 while the USB TCP driver starts having problems above 5000.
I used DrTCP to set the MTU much lower for every Windows Mobile Device interface (you will get one created for each independent USB port to which the Pocket PC is or has been connected). Currently I am at 2048 and connectivity for my Universal is much better than it was, although still far from reliable.
Hope this helps!
check this link
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm
it solves the 85010014 error in point 4 and below.... to be honest, it solves all ASync probs.

uSE Multiple GPS applications with 1 receiver

(TOPIC IN UNIVERSAL CAN BE DELETED - WRONG SECTION)
Searched all forums for ( GSP , Comports, Multple, split comport, duplex )
I have no troubles using any GPS app on my Universal (MDA Pro)
However, using...... GPS gate (buyware)
....or the free GPS splitter that comes with
Microsoft Virtual Earth Mobile (freeware, GPS icon suddenly appears under settings-connections after install of Microsoft Virtual Earth Mobile,
....or app found at http://www.gpsmeter.com/ (browse to portsplitter)
i am still unable to successfully run two GPS apps at the same time.
Don't get me wrong, I DO succeed in getting two GPS apps READ the data.
Both apps will show connection , for instance TomTom together with my own app PocketReperion, but tried with Visualgpsce http://www.visualgps.net/VisualGPSce/ and a lot of other apps too.
Symptoms : Even though successfull in setting up various comsplitters to send data to 1 virtual port, and have multiple GPS application accessing them, I am unable to get that situation stable.
So the concept on a lot if ISO layers has been proven, why the hell doesn't it work for longer that say a minute, 4 minutes, not at all, 10 seconds...
It seems that most comsplit apps are rather "reset" intensive (tested on clean device) and even when it does work for a while something will lockup and a reset is again necessary.
Does anybody use the blue GPS icon (free after install virtual earth mobile) to split ports and if so what is your setup ?
Does anybody use GPSGATE to split ports and if so what is your setup ?
Does anybody use the PortSplitter linked to above..to split ports and if so what is your setup ?
Please share your thought and expierences with me as I really really want to solve this issue. Be it for my "own" app, but also for all the other ones out there.
IT WORKS - TOMTOM WITH REPERION - portsplitter
IT WORKS !!!! BUT YOU HAVE TO CREATE TWO VIRTUAL PORTS - USE PORTSPLITTER !!!
All I had to do is download http://www.gpsmeter.com/ portsplitter as discussed in the other threads, HOWEVER......
Instead of what manuals seem to say, even from other softwarez like GPSGate, create TWO or more VIRTUAL ports in PORTSPLITTER!! Connect each GPS app to a DIFFERENT VIRTUAL PORT.
Also, when pairing and configuring your GPS, try taking a high Comport like 9. Go down one if no success.
Then when configuring PORTSPLITTER, don't be alarmed that your COMPORT isn't in the drop down list, MANUALLY enter "COMx" without the usual ":" where x stands for a number..the high real COM portnumber you configured when pairing/setting up.
You must use your keyboard or the stylus to manually enter the Comport if it is not in your dropdown list in PORTSPLITTER..
for speedreaders :
install PORTSPLITTER http://www.gpsmeter.com
use highest physical COMport available to pair your GPS
Define TWO virtual ports (instead of what seems to be written everywhere or am I really lame?)
Connect each Application to different virtual ports
My setup on a T-Mobile MDA Vario II (with Cingular ROM)
Physical Port 9
Virtual Ports in PORTSPLITTER 4,8
Hardware COMport in PORTSPLITTER (COM9 had to manually enter it, it was unavailable from drop down.... .... ...)
TomTom Navigator mapped to virtual COM8 (Didn't show up in TOMTOM until PORTSPLITTER running and connected to GPS.. ..)
Reperion *sweet favorite GPS app" mapped to Virtual COMPort 4 (Reperion eats all ports, no problems there....)
Please o please report...

XP, Serial Ports, ActiveSync

i didnt know where to post this so.. here is it...
so im at work and the boss (el cheap-o) drops an old Windows CE 3.0 barcode scanner on my desk and needs me to make it work so we can setup for and use it for inventory soon... it will connect great to a win98 computer. i cannot make a connection though with this computer. im using the only serial port (com 1). i know the port works as I use our label maker with it daily. what do i need to do in xp to get activesync to see the device?

[2 GUIDES] Auto syncing ActiveSync through bluetooth and BTServices Guide

I've noticed that many people are looking for a solution to automatically sync their devices using ActiveSync bluetooth sync.
for this... you will need 2 tools and one script
1. MortScript - http://www.sto-helit.de/downloads/mortscript/MortScript-4.1.zip
2. BlueStarter - http://smartmobiletools.freehostia.com/drupal2/system/files/BlueStarterCab.CAB
3. BTSync script (written by le_cactus) - included in this post (downstairs)
these are the steps you need to follow:
1. install mortscript
2. install bluestarter
3. put the script file in a dir of your choice
4. launch bluestarter
5. set the bluetooth device you want to sync with (all should appear in a dropbox)
6. write the path of the script file (e.g. \\storage card\\BTSync.mscr)
7. go to menu/interval config and choose the way you want to sync..
8. (DONT FORGET THIS STEP) open the script file and change all NIR36-PC to the name of your bluetooth connection, that is to your comp's name.
A few clarifications.
- if you set the interval to "On Power Button Pressed" a BTSync connection will occur EVERY time you wake your device up
- if you set the interval to "Time Interval" it will sync every set amount of time.. and even if you're sleeping and your comp is on it will sync and stay synced.. so it may drain your battery.
- in any case, if your comp is off, it will try to sync but nothing will happen.
if you're looking for a normal BTSync without an interval you can just set one of the hardware buttons to run the .mscr
cheers
If you found this guide helpful please Donate.. (all donations go to TZABACH Wounded Animal Service)
This is an old guide i wrote about 10 months ago. might help you out.
After a lot of strugle with using Wireless Headsets, Serial Ports, Activesync over BT and Sideshow... i managed to have them all work.. on VISTA and XP.
So i decided to write a fully detailed tutorial for whoever needs it.
1. Know your Stack.
if your stack is the toshiba one, when you right click on the bt trayicon you should see OPTIONS..
if your stack is the microsoft one, ... well.. you will not see OPTIONS
2. before starting to deal with services i suggest you download one of the stacks below, according to your demand, and install them. also install Windows Mobile Device Center (from now on WMDC).
This is WMDC6.1 x86...
http://rapidshare.com/files/120340376/MobileDeviceCenter6.1-x86.exe.html
These are both the LATEST versions of both stacks: (up until the day of posting this message of course )
TOSHIBA STACK:
http://rapidshare.com/files/120186967/TOSHIBA_BTSTACK.zip
MS STACK:
http://rapidshare.com/files/120187911/MS_BTSTACK.exe
i strongly suggest you keep both files on your comp as a cover for any services one might provide while the other doesn't.
to save you the trouble. (after a correction from Jadel):
MS Stack works with both Activesync AND sideshow.
TOSHIBA Stack is problematic although more userfriendly AND provides some different options which might come handy. i had to go thru a ****load of trouble to sync it with Vista... and syncing it with XP isn't a teaparty either.
3. after finding out which one you have we can begin.
AS - ActiveSync.
this will probably be the most problematic service to have working since a lot of times it DOESNT APPEAR AS A SERVICE. when you try to sync with the comp it tells you you have to pair it.. even tho the device is already paired with the comp.
XP might be more flexible with this but the solution is for both XP and VISTA.
To Async using TOSHIBA Stack do the following:
a. open Control Panel and open the BT Ports editor..
b. add a port and choose it as a Server.. (usually it rounds up to ports 6 or 7 but you may have to try others..)
c. go to WMDC/Connection Settings and mark "Allow connections to one of the following.." and choose the port you created.
d. on your device go to Bluetooth Settings and add a new device... put the desired passkey... and you should see a list of the services the computer provides the PDA.
e. now this is a bit tricky to deal with. sometimes ActiveSync might not appear there. if it doesn't, go to COM Ports (in bluetooth settings on your device) and add the COM port you added on your comp..
go back to Devices and choose your comp and click Refresh. if ActiveSync appears there, mark it. if it doesn't, you should delete your comp from your device and this time add the port BEFORE finding your comp. it that doesn't work, you should follow the links i will provide soon.
f. on your device, open ActiveSync and under Menu choose Connect Via Bluetooth.
To Async using MICROSOFT Stack do the following:
a. open Control Panel and open Bluetooth Devices
b. click Add and add your device. go to Options and mark "Allow Bluetooth devices to find this computer" and "Allow Bluetooth Devices to connec to this computer". you can also mark other options as desired.
c. go to COM ports and add an INCOMING port. it will choose a port for you automatically.
d. go to WMDC/Connection Settings and mark "Allow connections to one of the following.." and choose the port you created.
e. go back to Devices and choose your PDA. choose Properties and go to Services. there you should see all services your PDA provides. one of them should be Active Sync Bluetooth Service. mark it and click OK. your comp and PDA should connect and disconnect a few secs later.
f. on your device, open ActiveSync and under Menu choose Connect Via Bluetooth.
(if these methods don't work you should follow the reference links in the below post).
SP - Serial Port.
some services demand a serial port. for instance, if you're using the Desktop iGO8 and would like to connect a BT GPS receiver to your comp the serial port service must be enabled. i found TOSHIBA's stack to be much more flexible concerning port usage. in Control panel you have a BT Ports icon somewhere.. if you double click on it.. it will let you play with the ports and change them to help you adjust various devices as well as use the ports as Clients or as Servers. this is important for ActiveSync as well (depending on the device).
An example:
Ipaq's Desktop iGO8 supports a Bluetooth GPS receiver. to use it, you have to define a COM port (just as we did for activesync, depending on your stack)...
you will have to define a port for the receiver and make sure the Serial Port service is marked or the program will not identify the PDA. some programs might NOT need this service at all.
(of course, this is only for people who want to use their PDA's GPS receiver. people who have a seperate GPS receiver might get the port number automatically when pairing it with the computer or have to find the correct port themselves (in older receivers).
also, to use the Networking feature you have to use the Serial port service. (i will post links for this as well).
WH - I would prefer leaving this for later as i play with it a little further.
SS - Sideshow. (Vista Users)
i tried using sideshow on 3 different devices. Wizard, Polaris and Titan.
all 3 came out with nothing when i used the TOSHIBA stack. the devices didn't discover the SideShow service even tho it was installed on my comp and my device was paired with the comp.
now if you're using the MICROSOFT stack.. it's a whole different area.
Alright. so a little batch of detailed insturctions about using this:
(during the process make sure your device is DISCOVERABLE)
IMPORTANT! you should make sure the Sideshow software is active on your device while doing this. i tried syncing the service once with it on and once off and it sorta confused me. so we'll just agree on having it ON.
To use sideshow using TOSHIBA Stack do the following:
a. on your device, go to Bluetooth Settings
b. add your device.
c. look for the Sideshow service in the list. if it's there, Mark it, (on your comp) go to control panel, go to sideshow, and you should be able to mark V on the gadgets you'd like to use.
d. if it's not there, you should add a port on both your device and your computer. the ports should match.
e. go back to devices and refresh the Services list.
f. to my knowledge, if it doesn't work up to this point, give it up
To use sideshow using MICROSOFT Stack do the following:
a. open Control Panel and open Bluetooth Devices
b. click Add and add your device. go to Options and mark "Allow Bluetooth devices to find this computer" and "Allow Bluetooth Devices to connect to this computer". you can also mark other options as desired.
c. go to COM ports and add an INCOMING port. it will choose a port for you automatically.
d. go to Devices and choose your PDA. choose Properties and go to Services. there you should see all services your PDA provides. one of them should be Windows Sideshow. mark it and click OK. your comp and PDA should connect and disconnect a few secs later.
e. go to control panel, go to sideshow, and you should be able to mark V on the gadgets you'd like to use.
after syncing the service and choosing the gadgets you'd like to use from Control Panel/Windows Sideshow you can go back to your device and go back to the sideshow software and click Connect....... ................. ........
TP - Technical Port (this concerns only people who use ASUS's GXP Factory PDA so if you're not, just ignore this).
for the GXP to control Wireless devices such as ELTO's waterpipe controller and Applied Materials' connectors you HAVE to have a Technical port enabled as a service. other than Serial port this is the only service the GXP provides, so you won't have much trouble enabling it as it's part of the software.. it will always appear. MAKE SURE you DO NOT create another bluetooth port as it will use it instead of the default one and you will not be able to control ANY of the wireless devices around you.
i will update this post further on with detailed instructions for the use of every service and some howtos.
Hope it helps.
If you found this guide helpful please Donate.. (all donations go to TZABACH Wounded Animal Service)
Reserved for future guides
reserving another one
and another one

Qualcomm eXtensible Diagnostic Monitor with the Raphael

Has anyone succeeded to use QXDM with the Raphael?
Doing this in the CDMA HTC phones is very easy, you just need to run dmrouter.exe
But the CDMA dmrouter app won't work with the Raphael.
If you use the Wireless Modem app found in some ROMs, the Qualcomm Diagnostics port will be added to your computer but it won't respond to anything, of course, because the diag mode is not turned on. But this is telling us the Raphael can be connected to QXDM.
Hi, I have been working on this on and off for some time;
The raphael appears to be missing some components in it's driver set to enable this functionality. If you use smd_com.dll from another msm7201a device with debug code, you can activate the diag ports.. but i've not been able to get any data out of it.
Da_G said:
Hi, I have been working on this on and off for some time;
The raphael appears to be missing some components in it's driver set to enable this functionality. If you use smd_com.dll from another msm7201a device with debug code, you can activate the diag ports.. but i've not been able to get any data out of it.
Click to expand...
Click to collapse
Yeah, I do have smd_com.dll in my ROM, I guess that's why the diag port was created when I used the Wireless Modem app. Did you try any other apps? Have you found something similar to the dmrouter from the CDMA phones?
I also don't get any data from the diag port, maybe it's something related to the rilphone, like there is some procedure that needs to be called to activate the diag mode? Or maybe the rilphone we got just don't put any diag data through.
Whoops, was wrong about smd_com.dll, it's serialusbfnmodem.dll that's needed, along with some others
From the top of my head you need to insert the proper reg entries to load windiag.dll on port WDG1:
Then you need to load the CompositeFn drivers which support multiple com ports over a single usb connection, and set up the registry for those sub com ports, which uses serialusbmodemfn.dll if i recall
Using wmodem.exe by itself only connects to the device's SMD9: port which allows a data connection, but it won't allow diag communications over that port.. serialusbfnmodem.dll, and compositeusbfn.dll with support allows opening of a DAG1: port (diag)
These entries will load windiag.dll:
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WINDIAG]
"Dll"="windiag.dll"
"Prefix"="WDG"
"Order"=dword:500
"Index"=dword:1
"FriendlyName"="Windiag Driver"
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WINDIAG\Settings]
"ServerIP"="169.254.2.2"
"ServerPort"=dword:9C4
"MaxRetryCount"=dword:32
"RetrySleepMs"=dword:2710
"Enable"=dword:1
Note server ip, that's the default client IP on a RNDIS connection that the phone would be using, i've tried to connect to it on that port though (2500) and not gotten a reponse..
I've been studying KS20's drivers/registry as they have a working diag connection, which uses the compositefn drivers etc. (ks20 is msm72xx as is raphael)
They have there a program EngineerMenu.exe, which has a menu option "USB Switch Diag" - that menu option runs SwitchUSB.exe, it seems to just switch the default USBFn driver from "RNDIS" (activesync hi speed) to "CompositeFn" - however when I trigger this change on raphael I never get a connection on PC side.. registry entry can be changed back to RNDIS and works fine again.
Recommend studying the KS20 ROM,

Categories

Resources