New MazdaManiac BASE Calibrations
#2227
I zoom therefore I am.
hmm..totally understand what you say about a f**ked up IRQ settings..wow..it seems that 3 different computers must have fucked up IRQ's then. So it worked when I purchased it..then cobb updated the firmware and it has never worked right but it's MY computers doing this.. ok..sure let's stick that irq story.
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.
![Grouphug](https://www.rx8club.com/images/smilies/grouphug.gif)
#2228
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.![Grouphug](https://www.rx8club.com/images/smilies/grouphug.gif)
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.
![Grouphug](https://www.rx8club.com/images/smilies/grouphug.gif)
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.
#2229
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.
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.
#2230
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.
Last edited by waterproofone; 11-02-2009 at 08:24 AM.
#2232
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.
#2235
#2237
peace
#2239
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.
#2240
Registered Zoom Zoomer
iTrader: (2)
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.
Hopefully your new unit will work fine for you.
#2243
Grasshopper
iTrader: (1)
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
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
![Dunno](https://www.rx8club.com/images/smilies/dunno.gif)
Last edited by Jon316G; 11-02-2009 at 06:46 PM.
#2244
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.]
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.]
Last edited by MazdaManiac; 11-02-2009 at 06:41 PM.
#2245
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
![Dunno](https://www.rx8club.com/images/smilies/dunno.gif)
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.
#2246
Grasshopper
iTrader: (1)
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?
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?
#2247
YOU MUST DOWNLOAD THE NEWEST VERSIONS OF THE SOFTWARE FROM THE LINKS BELOW
DO NOT USE THE VERSIONS COBB PROVIDES ON THE CD THAT SHIPS WITH THE AP
Download the newest “AccessPORT Manager” HERE:
DO NOT USE THE VERSIONS COBB PROVIDES ON THE CD THAT SHIPS WITH THE AP
Download the newest “AccessPORT Manager” HERE:
Current Version : 1.2.2.1
Download the new "AccessPORT Updater" HERE:
Current Version : 1.2.2.2-11434
Download the new "AccessPORT Updater" HERE:
Current Version : 1.2.2.2-11434
#2248
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?
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?
#2249
Grasshopper
iTrader: (1)
![Wink](https://www.rx8club.com/images/smilies/wink.gif)
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.
Last edited by Jon316G; 11-02-2009 at 06:57 PM.
#2250
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.