[Birdofprey97]

Had this installed and running with 2010 on my xp machine. Updated laptop and BE to 2012 and nothing works.

Win7 dual core with 4GB ram and 100GB of free space on the laptop.


Not happy with 2012 or spending over $375 for something that doesnt work.

[crakrz]

Before you say something you might regret, have you sent an email to Clint. He is extremely helpful and is always quick in responding.
I'm sure it will be something simple in the end. You say nothing works, but in no way do you describe what is actually happening or what errors are appearing. How can anyone help you with this lack of info. As you see from my sig, I also run BE2012, so I'm sure it will be something minor causing you frustration.

[Birdofprey97]

Before you say something you might regret, have you sent an email to Clint. He is extremely helpful and is always quick in responding.
I'm sure it will be something simple in the end. You say nothing works, but in no way do you describe what is actually happening or what errors are appearing. How can anyone help you with this lack of info. As you see from my sig, I also run BE2012, so I'm sure it will be something minor causing you frustration.

Click on the BE.exe and get the binary editor 18.13 and an inch long green progression bar. That is it.

Read it was a latency issue with windows xp machines. This is a window 7 machine.

Latency issues usually occur from drivers not being certified with o/s or missing digital sigs.

Control L doesnt pull up anything.

Get the drivers fixed or at least let me down load them. I see updates out there, but it doesnt let me down load as it says files cant be found/exist.

My PCs cannot be viewed from outside the company. That is a 3rd party and with the information available through the network no 3rd party is allowed in to view the information.

Have 3 shops throughout the US and all 3 Laptops having this issue. Shops are not running a piece of the equipment they are not making that $. That allows me to be a bit ticked off. Not angry, but not happy.

Are the drivers registared with windows7 O/S?

[cgrey8]

Without the ability to see better what's happening, I can't begin to guess what's wrong. But I'm sure the problem can be resolved if information about what's wrong continues in a 2-directional pattern particularly with Clint involved. He supports his product better than any other product owner or company that I know. Coming in at a close 2nd would be Craig Moates.

Anyway, the drivers likely aren't signed because they are derivatives of the FTDI drivers. FTDI is big enough to sign theirs. But the default parameters in FTDI's drivers are not optimal for use with the Quarterhorse, so derivatives based on the FTDI drivers were made. But there simply isn't enough business to justify the cost to "register" a driver. I think it's something like $1500 each time you want to re-register a driver. And each time FTDI comes out with an update, the same tweaks need to be done to the driver, then re-released for Quarterhorse users...another $1500. For a big company, that's drops in the bucket and is a no-brainer. But to a 1-man show, like Clint, that supports the tuning community on the side (not as a full time job), it just doesn't make economic sense. There's simply not enough demand to justify it. And given most BE/QH users should be somewhat computer savvy or they have no business tinkering with an EEC, signed drivers just makes even less sense.

The catch is users that experience problems with the software/hardware have to be willing to work with Clint and/or Craig to work out issues that come up. These guys don't have massive test depts to run their software and hardware through massive computer configurations. They do release beta product to volunteer beta users and make changes based on feedback. In fact, I just last week helped Clint discover a really bizarre bug in some new changes he's doing to BE that related to me running Win7 in "classic" mode, but wasn't reproducible on his Win7 machines. Also keep in mind, most of the volunteer testers are not professional HW/SW testers. They are just users of the product. So as hard as the developers and volunteer testers work to find issues before a product is released, it's inevitable that problems are going to be found after release particularly in edge-cases where the computer is configured in a way not typical amongst the majority of users. But given there simply isn't a better product out there for the price for the vast majority of DIY users, it's worth it. And once the product is working, it works great. Perhaps it's not worth it to you and your business? That's a decision you'll have to make. But before you make that decision, I highly recommend you work with Clint 1st.

Maybe I should add this tidbit to the things to know BEFORE buying a TwEECer or QH writeup in the FAQ. Thoughts?

[decipha]

with Clint involved. He supports his product better than any other product owner or company that I know. Coming in at a close 2nd would be Craig Moates.

i think he's see's the five oh foe, and goes "oh-no" lol just messin'

[crakrz]

A search would have got you fixed with the loading issue.
viewtopic.php?f=10&t=19869

The latency issue has also been discussed many times.

See if it loads up and let us know what else comes up.

[Birdofprey97]

A search would have got you fixed with the loading issue.
viewtopic.php?f=10&t=19869

The latency issue has also been discussed many times.

See if it loads up and let us know what else comes up.

This did not correct the problem.


Which file from http://www.ftdichips.com needs to be downloaded for the QH1? Seems the BE 2012 doesnt have drivers the for QH1 if you have a 64bit OS.?.?.? Clint told me to download drivers from that site, but there are several listed. Which is the correct one?

[reef93lx]

You using a dongle? I had the same issue and the drivers for the dongle needed to be updated. Clint was very helpful in getting the issue resolved.

[markedforlife]

There is a known bug in windows7 64 bit concerning the ftdi drivers,
when you load the ftdi drivers the DOS like window needs to appear or
the drivers were not installed even though you permitted it, its something concerning
windows virtual com port bug, supposedly the drivers need to be downloaded twice
for the drivers to be installed. On a side note i had an issue when downloading the DataQ
drivers wherein i had to load them twice??? Yesterday i downloaded 52 window updates because
i never permitted any updates since i bought my windows 7 64bit computer on febuary 11 2011
and when i updated but created a restore point to fall back too BE 2010 would not open.
Window updates caused a problem.

[crakrz]

Have you emailed Clint yet?

[86GT]

Without reading all of this, the issue with the progress bar going only about 1/3 the way is caused by windows 7 UAC. The UAC is the user access control. If it is set to high then BE will not have high enough permissions to run. For some reason BE just gives up when it can not access something it does not have permissions to.

The fix is simple. Right click the desktop icon for BE and select properties. Now select the Compatibility tab and check the option next to "Run as administrator". Press apply or ok and now it will work. This will now prompt you each time BE is ran to elevate the security.

As for the other errors i need more detail on what and when they occur. I do not check the forums as often anymore due to the number of emails i get per day. If you need assistance on tech question on BE, emails are the best way to get faster response.