Uninstall it.

 

not to belabor a point, but if you've installed a program / peripheral on one machine, it's likely you installed it on multiple machines. This one program / device could change a setting that until now made no difference in your daily life. I'm not saying it's something you did, per se, but I've seen it enough time with various USB devices that I know it can and does happen.

I have one computer that swears my Ipod is actually a thumb drive meant to boost the load time of vista. I've tried everything to change it but no dice. Anyway, it sounds like things are getting taken care of so i'm happy it's going to work out.

 

I understand completely what you are saying.
We have the same problem at work with thesel intra-oral cameras we sell to the the US army and dental offices..and some OS's see the camera as a sound device because they failed to put the correct chip in it to be strictly recognized as a usb camera. The problem is easily fixed by updating the driver by pointing the correct driver in the application's folder in windows.

In this case, it makes no difference if i use the cobb access port driver 2.0 with a release date of 2006 or 2.0w/release date of 2009, if i use xp, vista or windows 7, this firmware 1.5.0.2 they updated it to has a problem interfacing with computers. Let's just hope MM/Jeff can figure it out.

Cobb has too many points of failure. They need to have ONE and only one program that interfaces with the AP and does its own updates because now, with all these different tools, firmwares and applications, they are bound to have conflicts like this.

it's simple, start reducing the number of possible failure points by emlimination of the uneccessary.

 

Just keep in mind:
You are the ONLY person out of nearly 500 that is experiencing this problem.
Be prepared for the outcome of that evaluation, which will be documented in depth, regardless of the outcome.

 

This simply is not true. I was just on the COBB forum yesterday and the day before reading about others having the same problem. The computer not interfacing with it. Regardless, I have done nothing wrong with it. it worked when I got it, then it was shipped to cobb BEFORE i learned of anything going on with EVERYONE's calibrations befing grayed out..ONCE I GOT IT BACK,,it stopped working with computer.

I am not trying to argue..clearly stating FACTS. I am not the only one having this issue. It may have been resolved for everyone else..but not yet for me. Let's not get in a pissing match, cobb even stated it kept locking up for them. Just expect the device this week and you can see for yourself.

 

There was ONE other person on that forum that was having a similar (but not identical) problem (NRoberts), he is not a MazdaManiac customer and Cobb resolved his problem already over two months ago (old firmware).

 

Ok.. and I read he was using the 1.3 firmware..the very same they sent it back with.that did not work for me....then when i plugged it up, it reverted to the experimental 1.5.0.2 again.

 

There is nothing "experimental" about it.
That is the most current firmware.

 

I sure hope my week ago receipted for data is not being held up due to having to continuously annotate the soap opera of one in 500!

 

you told me once they had a beta 1.5. that you knew nothing about unless I misunderstood you.

 

^ Give it a rest already!!!

 

I'm sure your stuff will be fine. It may be a soap opera to you..but remember that my unit is not functioning.. Even though it may be trivial to you, but it's a major problem for me. Even though it may **** people off, remember I paid for a unit same as everyone else. I am not trying to cause a problem, just trying to figure out why it keeps freezing. I used the links on the MM page to download the most recent versions of the updater and mgr.

peace

 

What's to figure out? Send the unit back as instructed.

I do sympathize, as we all want things to work for which we lay down significant hard earned dollars. Unfortunately sometimes they don't and again in this case you have a ready solution.

 

Dude..chill..I already shipped it. calm the F**k down..you have 2400 posts..i have 32.. it's shipped..I can have a conversation on here if i want. so go spin on yourself.

 

And about 75% of your 33 posts are in this thread [and of no value add to the community] I'm really not all that spun up, just noting an amazing amount of MM's time consumed that imho could be better spent by his working the numbers as it were.

Hopefully your new unit will work fine for you.

 

yes i want my tune before it snows here in north idaho... mind you we had a dusting last week

 

Oh, yeah no worries. I just want to know at what point I should contact you if it doesn't show up. Sounds good

 

Just an FYI... I had issues with my AP and my laptop yesterday.
I upgraded my laptop to Win7 and the AP wouldn't connect.
The laptop made the "chime" indicating that it knew something was plugged in, but the AP Manager wouldn't recognize it.
The AP also showed up in the Device Manager as something like "Lil-USB..." or something like that.

I uninstalled the AP Manager, AP Updater, and the AP driver.
Then I went onto Cobb's website and downloaded the most recent programs/drivers.
After installing those programs my AP still wouldn't connect like before.
So I went into the Device Manager and told it to update the driver for the AP (allowing Windows to search for it).
Then I noticed something interesting... the driver was now listed as something different instead of the "Lil-USB..." category.
I'm not at home now to tell you exactly what the Device Manager has it listed as now, but I was able to open the AP Manager and recognize the AP device.

Not sure if this was helpful and I really wish I could remember more detailed what occurred.
Maybe when I get home I'll try to simulate it again and post up screen shots for anyone else with similar issues.
But simply telling Windows to update my AP driver actually worked

 

Its important that you install the latest AP Manager and let it update the AP drivers.
There are sometimes conflicting versions of the drivers embedded in the various installs.

I know I had a connection problem with the AP Manager when I reinstalled WinXP on this box this week, but then I remembered to install the newest AP Manager and that wrote new drivers (the old drivers were listed as being in the wrong language - German - and it asked if I wanted to update).

User error. lol

[Its "LibUSB-Win32 Devices" and "AccessPORT 2.0" in the device manager. Driver version should be 0.1.12.0.]

 

I'll have to give this a shot Jon. I didn't want to add fuel to the fire but I have a single machine at home that has been refusing to connect to the AP via the update manager. It's a Windows 7 Machine. However, my living room media system running Windows 7 was able to connect and update my AP to the latest firmware without any problems.

The manager would connect no problem, but the updater wouldn't. After performing the update I couldn't get the manager or updater to talk to the AP on my trouble machine.

It's clearly localized to one computer so I'll try your fix and see what happens.

 

LOL.
That's why I hoped that uninstalling the AP driver (through Add/Remove programs) along with the Manager and Updater would eliminate any "user error" conflicts with updating to Win7.
But like I mentioned, even downloading/installing the latest program and driver didn't work.
Maybe when I "uninstalled" the driver, Windows didn't actually remove it and still tried to use the previous one?

 

...

 

Did you have the AP plugged in as you installed the driver (like it instructs you to)?

 

Yup... followed the directions like a good boy
First I kept the AP plugged in the entire time, then (out of desperation) I kept it unplugged until it told me to have it plugged in before continuing.
Then I plugged it in and continued the installation.

And I could be wrong, but I thought I tried to install the program once before without having the AP plugged in and it wouldn't let me.
I actually had to have the AP connected. Memory sucks (obviously) so I could be wrong.

 

Jon's symptoms sound exactly like what I have been dealing with and there really wasn't anything different I could see between the two machines that would prompt one to connect to the AP but not the other. The AP would power up on the USB cord but there would be no "reconnect" option to connec to the PC.

I'll mess with it when I get home. It could easily be a weird quirk. I'm known for breaking electronics so this could be my touch of death.