Tom-Guy

Nokia 6110, netsearch for 6110 pinout, you can deconstruct the cable and go by pin placement.

I'm all out of them, actually.

sporkcrx

Ok, just got done downloading the new version and tried to open it and I get this:


Is this a machine or program error? Crappy dell :P

Joseph, PMed you my address

TurboEF9

Holy ----... 1.29 is falling apart...

I don't know about that error. It doesn't seem like a program error. It's tied to a control used within TE, Try to reinstall over the top of itself.

Maybe install 1.28, then install 1.29 over it. Something is messed up with what VB thinks that computer has to use.

ShadowRex

i reverted back to a 1.29 before any fixes and its fine just no fixes lol

sporkcrx

Ok, well the 1.27 and 1.28 still get into the program. But the new 1.29 still has that code no matter what. The "old" 1.29 was fine so whatever you changed must of been the difference. I wonder if anyone else has tried the new 1.29 yet? I'm starting to think maybe it's my laptop that's the problem. I'll have to see if any of my friends have laptops to try. By the way man, don't stress yourself over this...as long as the maps work well that's all I need

TurboEF9

OK ok ok ok...



Hahaha.. Luckily I saved the source for the original 1.29.. I reimplemented the 2.0 cut of the datalogging code.


So, once again, uninstall, redownload, reinstall, and tell me if A) You can open the crap, and B) if the datalogger works.

ShadowRex

A opens I cant test the data logger yet I have to go get a cable yet.....

sporkcrx

Can get into the program again And just to let everyone know we narrowed it down, that the problem probably lies in the hardware. As the datalogging wheel turns