How best to determine which driver is being used?

[GlynH]

How best to determine which driver is being used by RadarBox to ensure I am using the latest version?

Looking in Device Manager under Universal Serial Bus Controllers/AirNav RadarBox I see it listed as v2.2.4.0 but it is dated 27/6/07 which seems quite old to me.

Drilling down further by clicking Driver Details I see 3 drivers listed;

ftdibus.sys 2.04.00.3 Beta built by WINDDK 2000-2007
ftbusui.dll 1.1.0.1 2006-2007
ftd2xx.dll 3.01.14 2001-2007

All provided by FTDI, all very old and none of them digitally signed.

One is even listed as Beta...can this be correct?

Thanks & regards,
-=Glyn=-

[tarbat]

Probably the best approach is to use the Update Driver button in device manager, point it at the Radarbox drivers folder, and let it pick-up the latest driver from there.

Mine are from Primetec, v2.2.4.0, dated 27/06/2007

[GlynH]

Hi Chris,

Thanks for the reply...I did look for drivers but all I could see were the following;

C:\Program Files\AirNav Systems\AirNav RadarBox\Drivers\ANRB64bitDrivers
C:\Program Files\AirNav Systems\AirNav RadarBox\Drivers\ANRB64bitDrivers.zip

Neither seem suitable for a 32Bit XP System?

The other ones listed above reside in C:\WINDOWS\System32

Thanks & kind regards,
-=Glyn=-

[tarbat]

There should be a .........\AirNav Systems\AirNav RadarBox\Drivers\i386 folder.

[Allocator]

Glyn, I'm pretty sure that you are using the latest Driver 2.2.4.0 - the last driver update was so long ago I can't remember when it was.

I'm not in front of my RB PC at the moment, so I can't check.

I would be very wary of letting Windows choose the 'best' driver, as this is often a recipe for disaster.

[tarbat]

Just checked, and the dates on all the driver files in my Drivers\i386 are all 22/10/2009, so quite recent.

[GlynH]

Chris: There is an i386 folder but I took it to be for 64Bit systems being that it is inside \ANRB64bitDrivers alongside an AMD64 folder?

Gary: It is listed as AirNav Systems 2.2.4.0 in Device Manager but when you look at the Driver Details there I see reference ot those three drivers I listed in my first post - one of which is marked as Beta?

It's no big deal...as I have some time on my hands I just wanted to make sure I was using the latest & greatest of everything!

Not been able to spend much time on the PC so far this year but I have the opportunity to do so now!

Thanks & kind regards,
-=Glyn=-

PS: Just seen your latest post Chris. Those drivers are much newer than mine unless that was when they were installed and not the actual driver build date?

[tarbat]

Mine's definately NOT in a 64bit drivers folder.  It's in the \AirNav Systems\AirNav RadarBox\Drivers\i386 folder and is version 2.6.0.0.  I'm pretty sure these are the latest drivers.  Maybe they're part of the v4.03 download.  Glyn, what version of Radarbox are you using?

[GlynH]

Chris, I wonder if it's because you are on Vista and I am still using XP?

I am using ANRB 2010 3.13 2009/12/09 02:24 here...just looked at my HTPC, Laptop & Netbook all running XP and they have the same directory structure with the 64bit folder under Drivers.

Still can't get ANRB running on the Netbook as I am unable to get past the Enter your Location page...I have posted on this before along with some others who had the same problem but never saw a resolution to my issue.

Seems like I was just born lucky! ;^)

Thanks & regards,
-=Glyn=-

[Allocator]

Looks exactly the same as mine.

[Allocator]

The RB V3.13 does 'Hide' the i386 drivers in a ANRB64bitDrivers folder.

I've checked my various installations and this is the only version that dies this.

[GlynH]

Seems totally illogical if those i386 are indeed 32bit drivers hiding in a folder named ANRB64bitDrivers??

Interestingly those drivers are much newer than the ones already installed in our systems Gary so I suspect they might be 64bit after all.

ftdibus.sys 2.6.0.0 (or 2.06.00?) 2006-2009
ftbusui.dll 1.2.0.1 (or 2.0.6.1?) 2006-2009
ftd2xx.dll 3.1.19.0 (or 2.06.00.1?) 2001-2009

There are some others lurking in there also;

ftcserco.dll
ftd2xx.lib
ftlang.dll
ftser2k.sys
ftserui2.dll

Talk about DLL Hell ;^)

Thanks & regards,
-=Glyn=-

[Allocator]

It's not an issue Glyn, driver installation is easy and they work as advertised.  People only have problems when they let Windows run riot.

There are a whole bunch of ftdi drivers out there - I've got a number of different versions for cameras, scanners, radios etc.