ecuflash PROBLEM!!
#1
ecuflash PROBLEM!!
during the installation i've got this...
i also got the "error loading FTD2XX.DLL" message in the task info panel..
the program doesnt work and or can't open any hex or bin file...
ANY IDEAS?
note
my windows are not english
i also got the "error loading FTD2XX.DLL" message in the task info panel..
the program doesnt work and or can't open any hex or bin file...
ANY IDEAS?
note
my windows are not english
#4
Newbie
iTrader: (3)
Join Date: Jul 2005
Location: DFW
Posts: 16
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by greek_evoVI
note
my windows are not english
Are you referring to your operating system Windows? What version and what language are you running? And as to the comments of the other two members... ????
#5
EvoM Guru
iTrader: (5)
yeah ECUFlash won't work correctly without that driver, I think the driver has to be repackaged localized for it to work. Probably a few languages left out, or it has to be localized for english only as default.. Contact CBoles on www.openecu.org and send him the snapshot of the driver/install problem.
#7
yes i'm refearing to the windows XP language.
you see i've install the software in 2 laptops and to the one with the greek windows it's not working... it doesn't even find the driver to install the openport cables usb port...
to the other with the english version of windows everything is OK...!!
the same things happens with evoscan as well....witch is might reasonable because there are no dvivers of the cable installed..(they are supposed to be installed with ecuflash..)
so since the same app is installed in both of them and it works only in one... there is got to be something with the language pack since this is their only difference..
and now i must i repeat...HHEEEELLLLLPPPPPP!!!!!!
you see i've install the software in 2 laptops and to the one with the greek windows it's not working... it doesn't even find the driver to install the openport cables usb port...
to the other with the english version of windows everything is OK...!!
the same things happens with evoscan as well....witch is might reasonable because there are no dvivers of the cable installed..(they are supposed to be installed with ecuflash..)
so since the same app is installed in both of them and it works only in one... there is got to be something with the language pack since this is their only difference..
and now i must i repeat...HHEEEELLLLLPPPPPP!!!!!!
Trending Topics
#9
Evolving Member
iTrader: (2)
Join Date: Nov 2005
Location: Troy, MI
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
Have you try to setup your regional settings to "USA"?
It's probably the way Windows understands comas and other signs.
I know for instance 12.6 in US format is 12,6 with French format.
It's probably the way Windows understands comas and other signs.
I know for instance 12.6 in US format is 12,6 with French format.
#10
get a new computer or reinstall the win xp driver to repair or install the language pack.
You need to have the whole thing installed in english version, I believe or have 2 of them installed so you could swap them.
Seek microsoft website, they have language packs, just install all of their upgrades, in english.
You need to have the whole thing installed in english version, I believe or have 2 of them installed so you could swap them.
Seek microsoft website, they have language packs, just install all of their upgrades, in english.
#11
Newbie
iTrader: (3)
Join Date: Dec 2005
Location: Seattle, WA
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
I will try to put better multi-language support in the next release. For now, try executing the following command line:
(your ecuflash install dir)\drivers\DPInst.exe /L 0x409
and see if that runs OK.
Colby
(your ecuflash install dir)\drivers\DPInst.exe /L 0x409
and see if that runs OK.
Colby
#15
Evolved Member
Originally Posted by evo150
i am having the close to the same problem. no language problem but the "error loading ftd2xx.dll " in the info task bar". any help would be great.
I may be blind but I didn't see anyone give an answer to where dll can be found or why this happened.