Related
I have recently "upgraded" from xdaII to xdaIIs and I'm having a few problems. I have upgraded the BT stack to 3500 but I still can seem to connect to my tomtom gps. Device sees it but tomtom 3 cant. I'm completely confused by the connection wizard- none of the profiles seems to fit gps. I also dont seem to be able to send or receive files from my old xdaII. What am I doing wrong?
I'm also a little confused about roms. Do I need to upgrade my rom? Is there a simple way avoiding anything too technical (I've read about "country codes" and other wierd stuff). My current config is:
ROM: 1.12.62
Radio: 1.02.00
Protocol: 1337.32
ExtROM: 1.12.178
Could someone please help! I only have a few days to decide if I want to keep it or stick with my xdaII...
Gps's use the serial profile to transmit the data over - its like a virtual serial connection - so you need to tell tomtom to look on a com port AFAIK,.
For eample in my Tomtom list of connections there is one called 'BT on Com6, ' which is the bluetooth comport on my unit.
But there are also listed more com ports...
Com5
Com4
Bluetooth Serial port Com7
The XDA only actually has 1 com port (com1) so any other are virtual ports created by various software, you just need to find out which one is the one for the GPS...
So in "tomtom gps v3.07" I go to the gps tab and by default its set to infrared port. I change to "BT on com6" and click OK. When I restart the program it always resets to "infrared port" even if I try a different port. Really am stuck- never had any problems with my xdaII- just put in BT port and it picked it up automatically...
The problem is it's not always the same com port for different devices - firstly does your unit have the widcoom stack version of are you on the microsoft stack..
Whichever you have you need to find where the BT com port is configured..
On my widcomm i go to 'bluetooth setting' ; 'services' ; "serial port'; 'advanced'
in there it says...
inbound com port : 6
outbound com port : 7
so the incoming com port on my bluetooth is 6 hence the 'BT com port on 6' listed in my tomtom gps.
so you need to find your BLuetooth com port and find out which com port number it is set to. Not sure as to why tomtom gps does not save your settings, the only thing I can think of is becuase it never gets a valid signal from the comport select, and does not save the change unless it does.
Also: I assume the gps unti has a pairing with your XDA unit?
So does the widcom stack work on the xdaIIs? If so where can get it?
Sorry: I cannot be certiain the widcomm works with the IIs, but is can be downloaded from this site if you are willling to try, just do a search oin widcoom, and you will find a lot of entries...
For the MS BT stack; look under start, settings,System tab. There is a icon labeleld Bluetooth settings in there you can see/set the com ports for the bluetooth link. they also need to be enabled witch a check box before they will work...
So on "bluetooth seetings" serial port/advanced I have inbound COM port 5 and Outbound COM port 6. Below it says "Default device for outgoing serial connections: TomTom Wireless GPS. Display the device selection screen the next time an outgoing serial connection is attempted" next to a ticked box. I have tried bt com 5 and 6 in the gps settings and it wont save or recognise either. I can, however, pair and connect to the device in my BT manager but Tomtom doesnt recognise it...
Hmmm - all sound ok to me but I currently use a wired GPS, so I have not actually done it. I'm afraid I'm as stuk as you are now...
Sorry bro- I have sorted this now. Thanks...
For me, I just selected Comm 5 from the GPS status drop down and it works like magic!
I can't seem to connect my Bluetooth GPS reciever to my BA with WM5 on, I can pair the device, but thats about it. Tomtom 5 can't see it and I can't see any way of manually connecting it to the GPS device?
Any ideas ?
Have you looked at my piece in the WM5 Wiki?
Mastiff said:
Have you looked at my piece in the WM5 Wiki?
Click to expand...
Click to collapse
Took a bit of finding but I followed instructions, installed Tomtom, paired the GPS, set the COM ports.
When I went into Tomtom setup the port (Com 7) was not in the list of available ports.
I have BT UART, COM2: Serial Cable on COM1: COM9: Ir on COM 3
but no COM 7, any ideas ??
This has been reported on a few PPCs here. I know somebody made a very small app that makes available the port you want to. You may try to search for that.
Does anyone know what this small app is called??
is there anyone using WM5 ROM's on a BA that succesfully uses the integrated GPS virtualizer as can be found as "GPS" button in the settings->connections
In more detail this is what i find:
Ozi seems to be the only gps using application that can setup an active bluetooth connection to an GPS device using the build-in GPS virtualizer of WM5 wich is called Intermediate GPS driver and wich can be found via the "GPS" button at the connections settings page of your device.
The use of this virtualizer is that you can simultanious have multiple applications active that use GPS data.
Next info is what i tested so far, maybe others recognize and/or understand much better then i do how this should work. Any help is appreciated.
I think it has something to do with discovering, or being allowed to discover by WM5, COM ports.
Just to make sure we're talking the same issue a little chain:
- there's a BT-GPS device
- discovered via BT-applet on WM5
- on my bt-gps: if the blue light goes on&off it's not connected, if its steady on it's connected to a PDA
NEW in WM5 is that one has to seperatly define:
- the service the bt-gps needs to use: just one choice "serial services"
- next on a seperate tab one needs to define an new outgoing and/or incoming port
- one can choose only the discovered bt-gps
- one can only choose a COM port numbered 6, 7 or 8 and one defines the baudrate here.
- i choose COM6 and 57600baud
From this point there is a COM6 available for applications, any application i start is able to set-up the bt-gps connection and read gps-data.
- ozi explorer, tomtom, igo, reperion
- all setup with listening to COM6
- all make the blue-light on the gps-device go steady on
- all disconnect from the gps-device when exiting the application, blue-light on gps-device starts flashing
Next step is using the intermediate gps driver incorporated in WM5 to virtualize&share the gps-device.
- on the GPS-applet define COM6 as the h/w port with 57600 baudrate
- on the GPS-applet define COM7 as the s/w port, choices are COM0/9 and GPD1/9
- i defined COM7 as the s/w port.
So now with COM7 we are on the virtual side of the GPS-applet
When i start ozi-explorer i can choose several ports for the GPS
- COM1/4 for specific goals
- COM6 (recognized by ozi as Bluetooth Serial Port)
- COM7 (recognized by ozi as ActiveDevice)
Activating the GPS function in Ozi with GPS-port set to COM7 will make ozi to talk to the virtualside of the intermediate gps driver and then via this driver will initiate the bt-gps connection (blue light on the gps-device will go steady on) and start reading gps-data. Stopping&starting the gps function in ozi will nicely turn the bt-gps connection off&on.
So far so good.
Important note: In the registry one can find \HKLM\System\CurrentControlSet\GPS Intermediate Driver\ActiveDevice
According to the writer of gpsid.dll http://msdn.microsoft.com/library/d...rmediatedriverinputsourceregistrysettings.asp this is the place to look for the gps-device definitions.
As you might have read above the name "ActiveDevice" is exactly what ozi found as tag for COM7
All the other gps using product like Igo see COM7 as "unnamed" port.
So it looks as if the other app's, including Fransons serial tools, don't look at the right place in the registry for the info on COM7. And since Ozi does work well i think it's a problem to be resolved by the navigation application developers and not on WM5 level.
And once ozi setup the connection all the other apps suddenly do find COM7 and read GPS data. From that point on i can stop ozi, the connection to the bt-gps will stay. When i then stop igo or reperion or whatever, then the bt-gps will be disconnected.
Then a bit about gpsgate, maybe to get some more idea on how the behaviour is in wm5.
- i totaly inactivate the Intermediate GPS driver from WM5 (b.t.w. i softreset after every change to make sure it's a clean test)
- all the nav. Apps can directly connect to COM6 (see above)
- gpsgate will only give me COM1/4 and COM9 as an option
- COM6/7/8, the only options i have as h/w port on the bt-gps are NOT seen by gpsgate
- then i re-active the Intermediate GPS driver and now gpsgate gives me the option of COM7 as input and i setup a virtual port in gpsgate COM8.
- quite useless, a gps-virtualizer which can only listen to some other driver's virtual port.
- but then it act as all the other app's. Only when a bt-gps connection is setup via ozi, gpsgate will read data on the virtual com7 port.
- this gives the weard situation:
- bt-gps comes in on h/w COM6
- Intermediate GPS driver from WM5 listens to port6 and virtualizes that to COM7
- Ozi explorer initiate the connection and listens to COM7
- gpsgate will also listen to virtual COM7, where gpsgate thinks this is the h/w input side
- gpsgate will passthrue to its own virtual port COM8
- reperion i configured to listen to COM8, and reperion will succesfully read data from COM8, via COM7, via COM6.
Still with me? Maybe you need to draw this out on a little piece of paper ;-)
Anyway, it looks as if most gps-using s/w don't setup the gps-communication up in a proper way to be handled by the Intermediate GPS driver. Ozi Explorer is the positive exception here.
Found an app on SourceForge called GPSproxy... first off it enables me to use Garmin Que, and all the MapSource maps with my non Garmin BT-GPS... but it also enables the use of Virtual COM Ports in WM5... so far I have had Garmin Que, with at least two of the following: TomTom, Vito Navigator II and Virtual Earth Mobile running at the same time on my BA... still playing, I'll update after my trip to Scotland...
thx for the info. took me a while to get it all my pda via gprs on holiday and no desktop around.
just can't get the virtual ports passing data. it works when mapping one port to another via ' settings' in gpsproxy. but when I add a port in 'virtual port' settings it is recognized in navprogs, but gps data comes through.
I turned off the internal gps-applet
any tips on how you set it up.
thx.
Have you guys tried these?
http://www.pocketgear.com/software_detail.asp?id=22697
http://franson.com/gpsgate/
We're judging them in the PocketPC Magazine Awards.
V
yep, tried it. doesn't pickup the right definitions from wm5 registry, doesn't setup the comms to the gps. and when asking for support just blaming microsoft, so i'm not thrilled.
so far the only good one is ozi-explorer. picks up all the right registry values, realtime, no softresets or whatever needed. just plug&play on bt-gps & wired gps.
I was using Mapking 7 and Agis 1.66 beta when a friend introduced me to Garmin que. I managed to use GPSProxy 2.2 to run Garmin Que 2.9 with Agis concurrently but was not able to run Garmin que and Mapking concurrently. If I don't use Garmin Que and use WM 5 GPS control, I can run Agis and Mapking together but not Garmin Que.
Garmin Que needs at least 1 available port as virtual port to support Garmin Que protocol and another available port as virtual port to run another GPS programme. I'm using a O2 XDA IIs and I can only manage to squeeze out com port 7 for Garmin Que protocol and com port 0 which is not supported in Mapking. Agis is able to use com port 0.
After searching for about a week, I realised that if I don't need to use Infra Red, I can make use of that com port. I used Task Manager v2.1 by FdcSoft to unload the infra red dll (IRCOMM.DLL) and got hold of com port 3, which I was able to create as a virtual port.
Now I can run Garmin Que and Agis or Garmin and Mapking using GPSProxy.
GPS port is com port 6.
Garmin Que Protocol is com port 7
Garmin Que output port is com port 3
The only issue I have now is to find out a way to disable com port 3 by default so that I don't need to do it after each soft reset. Any help here would be most appreciated.
xdaradar said:
is there anyone using WM5 ROM's on a BA that succesfully uses the integrated GPS virtualizer as can be found as "GPS" button in the settings->connections
In more detail this is what i find:
Ozi seems to be the only gps using application that can setup an active bluetooth connection to an GPS device using the build-in GPS virtualizer of WM5 wich is called Intermediate GPS driver and wich can be found via the "GPS" button at the connections settings page of your device.
The use of this virtualizer is that you can simultanious have multiple applications active that use GPS data.
Next info is what i tested so far, maybe others recognize and/or understand much better then i do how this should work. Any help is appreciated.
I think it has something to do with discovering, or being allowed to discover by WM5, COM ports.
Just to make sure we're talking the same issue a little chain:
- there's a BT-GPS device
- discovered via BT-applet on WM5
- on my bt-gps: if the blue light goes on&off it's not connected, if its steady on it's connected to a PDA
NEW in WM5 is that one has to seperatly define:
- the service the bt-gps needs to use: just one choice "serial services"
- next on a seperate tab one needs to define an new outgoing and/or incoming port
- one can choose only the discovered bt-gps
- one can only choose a COM port numbered 6, 7 or 8 and one defines the baudrate here.
- i choose COM6 and 57600baud
From this point there is a COM6 available for applications, any application i start is able to set-up the bt-gps connection and read gps-data.
- ozi explorer, tomtom, igo, reperion
- all setup with listening to COM6
- all make the blue-light on the gps-device go steady on
- all disconnect from the gps-device when exiting the application, blue-light on gps-device starts flashing
Next step is using the intermediate gps driver incorporated in WM5 to virtualize&share the gps-device.
- on the GPS-applet define COM6 as the h/w port with 57600 baudrate
- on the GPS-applet define COM7 as the s/w port, choices are COM0/9 and GPD1/9
- i defined COM7 as the s/w port.
So now with COM7 we are on the virtual side of the GPS-applet
When i start ozi-explorer i can choose several ports for the GPS
- COM1/4 for specific goals
- COM6 (recognized by ozi as Bluetooth Serial Port)
- COM7 (recognized by ozi as ActiveDevice)
Activating the GPS function in Ozi with GPS-port set to COM7 will make ozi to talk to the virtualside of the intermediate gps driver and then via this driver will initiate the bt-gps connection (blue light on the gps-device will go steady on) and start reading gps-data. Stopping&starting the gps function in ozi will nicely turn the bt-gps connection off&on.
So far so good.
Important note: In the registry one can find \HKLM\System\CurrentControlSet\GPS Intermediate Driver\ActiveDevice
According to the writer of gpsid.dll http://msdn.microsoft.com/library/d...rmediatedriverinputsourceregistrysettings.asp this is the place to look for the gps-device definitions.
As you might have read above the name "ActiveDevice" is exactly what ozi found as tag for COM7
All the other gps using product like Igo see COM7 as "unnamed" port.
So it looks as if the other app's, including Fransons serial tools, don't look at the right place in the registry for the info on COM7. And since Ozi does work well i think it's a problem to be resolved by the navigation application developers and not on WM5 level.
And once ozi setup the connection all the other apps suddenly do find COM7 and read GPS data. From that point on i can stop ozi, the connection to the bt-gps will stay. When i then stop igo or reperion or whatever, then the bt-gps will be disconnected.
Then a bit about gpsgate, maybe to get some more idea on how the behaviour is in wm5.
- i totaly inactivate the Intermediate GPS driver from WM5 (b.t.w. i softreset after every change to make sure it's a clean test)
- all the nav. Apps can directly connect to COM6 (see above)
- gpsgate will only give me COM1/4 and COM9 as an option
- COM6/7/8, the only options i have as h/w port on the bt-gps are NOT seen by gpsgate
- then i re-active the Intermediate GPS driver and now gpsgate gives me the option of COM7 as input and i setup a virtual port in gpsgate COM8.
- quite useless, a gps-virtualizer which can only listen to some other driver's virtual port.
- but then it act as all the other app's. Only when a bt-gps connection is setup via ozi, gpsgate will read data on the virtual com7 port.
- this gives the weard situation:
- bt-gps comes in on h/w COM6
- Intermediate GPS driver from WM5 listens to port6 and virtualizes that to COM7
- Ozi explorer initiate the connection and listens to COM7
- gpsgate will also listen to virtual COM7, where gpsgate thinks this is the h/w input side
- gpsgate will passthrue to its own virtual port COM8
- reperion i configured to listen to COM8, and reperion will succesfully read data from COM8, via COM7, via COM6.
Still with me? Maybe you need to draw this out on a little piece of paper ;-)
Anyway, it looks as if most gps-using s/w don't setup the gps-communication up in a proper way to be handled by the Intermediate GPS driver. Ozi Explorer is the positive exception here.
Click to expand...
Click to collapse
wow wow wow....
I read it twice... I will read it again... because it's a little hard to understand ! (I took my piece of paper )
But I think I've got solution to my GPS prb here !
For me this is the solution - Tmob MDA Vario II - Cingular rom
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...
jppech said:
wow wow wow....
I read it twice... I will read it again... because it's a little hard to understand ! (I took my piece of paper )
But I think I've got solution to my GPS prb here !
Click to expand...
Click to collapse
Yes, I also have some problems in going through this text
I have a problem with Ozi and external GPS receiver as well, I do not know how to use the information i this post, perhaps if I tell you what the problem is you could help me
I have the FS Loox n560 with a built in GPS receiver but due to its rather poor reception I decided to buy an external device.
So far so good
Ozi has no problem in using the internal GPS, I simply choose the right COM port and the receiver switches on automatically.
But the problem is to use the external GSP receiver.
OZI can use only a limited number of COM ports (1,2,3,5,6,8)
COM 6 is the predefined software GPS port and COM 8 is the hardware port.
I cannot associate my BT GPS receiver with any of these ports.
Port splitter also does not help since it also can split only ports that I cannot associate with my BT GPS receiver.
I have been wondering how I could make use of my external GPS receiver with OZI???
Do you have any idea how to handle this probem?
my i-mate kjam have only 6 and 7, how can i have more???
my i-mate kjam have only 6 and 7, how can i have more???
many GPS softwares are looking for different ones.
please help me
Hi all
Just upgraded to Helmi_WM2k5_AKU3.2_32mb_v1.3.2_16mb_bitpool_32mbRamdisk
My new config is now
P H 2 0 B W W E 5.0 4.0 6. 1.3 1.15.00 4
I have got the Phone, Wi-Fi, Bluetooth all working and can see my GlobalSat BT-388 and its Serial interface. But when I try and make a new outgoing or incoming port on com6, I get and error: "The COM port could not be created. Please check settings and try again" - COM7 an 8 work but cant get tomtom to see those ones.
I have soft reset the device and still no luck - Anyone know what I may try to fix as I am trying to pair for tomtom 5.21.
BTW - Hemi fantastic - keep up the good work.
Hi,
have the same problem here, TomTom 5.21 on Helmi AKU26. Bluetooth COM-Port doesnt show up, also some other applications that enumerate the COM Ports dont show it either.
My workaround is to use the GPS Multiplexer from OS (Settings->Connections->GPS). In AKU26 i set up Bluetooth to COM7, set Microsoft GPS to look at that Port with 33600 and set COM5 as new Multiplexer Output Port. Device 10 Seconds of, Softreset and than detected at least TomTom that COM5 and worked.
Thanks MCSchermer....
found the GPS config under the connections section. WM2003SE never had this. Changed the GPS program port to another COM port and then was able to changed the hardware port to com6.
TOMTOM now up and running.
Excellent... now able to drive across town again.
Thanks mate
Hi,
I'm trying to get GPS2Blue to work and managed to get a connection between my Kaiser and my desktop (with a dongle using the Toshiba Bluetooth stack) by creating an outgoing port on the Kaiser (start-settings-connections-bluetooth-com ports-new outgoing port-DESKTOP-next).
I am successfully paired with a Lenovo T61 using the internal bluetooth with a broadcom stack (Vista Bunsiness x64), but while the Desktop advertises 'Serial Port' and 'ActiveSync' as bluetooth services, the T61 stack only advertises 'ActiveSync' 'Wireless Stereo' and 'Headset'. As a result, I can't add an outgoing port to the laptop and GPS2Blue doesn't work.
Does anyone know how to tell the broadcom stack to tell the kaiser that it has SPP (Serial Port Profile) available for it? Using GPS2Blue over TCP/IP is not an option because the virtual com port driver currently doesn't support Vista x64.
This has been bugging me for a loooong time, I'd really appreciate any help with this. Thanks!
Lncdoc
OK, 2 things.
Firstly, GPS2Blue doesn't need an Outgoing port on the Kaiser, but an Incoming one. Then, you discover services on the phone, from the PC, and you'll have a serial port you should connect to. Not the other way around like you were saying. Now, WM6/6.1 don't let the user set an incoming port from the BT configuration page anymore, so a manual registry edit is necessary. Attached is a .reg file that will set an incoming port on COM6.
Apply this, soft reset. Then run GPS2Blue, set it to use COM6, discover services from the PC, connect to the serial port, and connect to whatever serial port the stack maps it on the PC with your GPS program.
Secondly (but now unrelated!), if from the phone you'd like to see a serial port on the PC, there are 2 solutions. Firstly look for an "add new seral port" option in your BT stack on the PC, some support multiple ones.
If there's none, you should open activesync connection page, disable serial connection. On the Phone the Arcivesync entry will now revert to serial port. To have AS again, reenable the COM port connection in AS.
Thanks a lot! That worked like a charm. After Vista with the Broadcom stack forced the use of COM9, I changed it manually to COM5 in the device manager (For reference of other people wanting to do this: Device Manager / Ports (COM & LPT) / Standard Serial over Bluetooth link (COMn) / Right Click / Properties / Port Settings / Advanced / COM Port Number), since some software (like MeHere) only supports up to COM8.
Now everything works like a charm on my laptop.
Note that this weirdly enough also works with an Outgoing port on the Kaiser if you have a stack (on your PC) which broadcasts the availability of an incoming serial port (in which case the Kaiser initiates the connection, not the PC, and the COM Port sends regardless of whether something is connected or not...). Not that I'm recommending this route to anyone, but I got this working on the Toshiba stack.
Anyway, thanks a lot again, it's finally working perfectly with OziExplorer, MeHere, Google Earth.... you name it.
Lncdoc
Arrrrgggg! I am so close. The incoming BT port bit helped me to get connected but, although GPS2Blue is gettting a lock, and I appear to be connected to EarthBridge/PC, the GPS data doesn't appear to be transmitted to Earthbridge/PC. Google Earth keeps putting me off the coast of Africa instead of south Florida.
I'm about ready to go pickup a copy of Streets & Trips with GPS.
GPS2Blue 1.9
I allready got .reg file on my computer.
The only thing i don't understand is how to get the incomming port on my laptop....
Greetz
Peter
Loaded the appropriate reg values...nothing. Still doesn't work. I can't see the port on the PC or Handheld under "Bluetooth Services".
Thanks kilrah
Your solutions works great for me and i have tested this with my i900 and two different notebooks running Windows 7 and Windows XP
Works in both notebooks
I was using Garmin Mobile PC Version 5
Thanks again for your great help
thx kilrah
'elpetah1984' you must import registry value to PDA windows not PC
http://forum.xda-developers.com/showthread.php?p=8429209#post8429209
F I N A L L Y !!!!!!!
I've finally managed to do it!!! Oh man.. what a fight! almost 4 am and trying since days.. eheheh it is really rewarding! Will be doing a tutorial to avoid hours and hours of frustation to anyone trying this!
iRiKi said:
F I N A L L Y !!!!!!!
I've finally managed to do it!!! Oh man.. what a fight! almost 4 am and trying since days.. eheheh it is really rewarding! Will be doing a tutorial to avoid hours and hours of frustation to anyone trying this!
Click to expand...
Click to collapse
That'd be great!
Did you get it to work with many apps? I remember one time I managed to get it set (don't know how, can't reproduce my semi-success) so I could share the ActiveSync port and in Windows I could open the COM port on PuTTY to see the NEMA output but only a couple apps recognized that there was a GPS there -- the main thing I wanted to work (inSSIDer) couldn't see any GPS.
I'd definately be interested if you came up with a reliable way to make it work.
mmiller7 said:
-- the main thing I wanted to work (inSSIDer) couldn't see any GPS.
Click to expand...
Click to collapse
I saw your post @ metageek forums, because I too am unable to make it work with either version of inSSIDer, although Netstumbler saw it nice and easy. Thing is: I have Vista, and Netstumbler doesn't like Vista like me
I'm gonna get a XP lappy tomorrow which battery only works for half an hour but hey, it's a start
iRiKi said:
I saw your post @ metageek forums, because I too am unable to make it work with either version of inSSIDer, although Netstumbler saw it nice and easy. Thing is: I have Vista, and Netstumbler doesn't like Vista like me
I'm gonna get a XP lappy tomorrow which battery only works for half an hour but hey, it's a start
Click to expand...
Click to collapse
Good luck, XP is out of the question for me because HP doesn't provide Bluetooth drivers back to before Vista. Maybe I can find a way to forward the COM port and a USB WiFi adapter through VirtualBox and use XP that way...though I've been unsuccessful with either of those so far.
Actually you can forward the USB device to Oracle's Virtualbox, I have my TP-Lnk USB WiFi forwarding into a linux virtual machine working perfectly in monitor mode with kismet and aircrack I don't think you can forward COM ports tho, but if you have an external USB bluetooth adapter you can also forward it into XP!! Will try that asap!
Thing is, I wanted to use the onboard wireless because it's way more sensitive than the external USB adapter, but it's not possible to forward it inside a virtualbox.
Ahhh computer issues.. always bugging me since 1993 XD
iRiKi said:
Actually you can forward the USB device to Oracle's Virtualbox, I have my TP-Lnk USB WiFi forwarding into a linux virtual machine working perfectly in monitor mode with kismet and aircrack
Click to expand...
Click to collapse
I got bad news and good news.
Bad news:
The USB forwarding of my wireless card works under Linux but FAILS under a XP VM!!! %$#*@#!"#
Good news:
Downloaded Franson GpsGate trial and now inSSIDer is working !!!!