Ive had 4.0 loaded onto my old laptop (slow and old, about 120mhz 16mb ram) and I was having some problems trying to use the ALDL on my newly aquired 1993 Typhoon. When I tried to change the dash, the selection would run off the screen with no down arrow to view the bottom half. It also wouldnt record or log. I downloaded Tunerpro RT 4.13 onto my newer laptop, opened it up and I can view all selections for the dash readings.

So I burn "setup tunerpro 4.13" to a floppy (my old laptop has no modem) and load into the old laptop. Setup is complete but the program wont open. I get two error messages consistently-

" The TUNERPRO.EXE file is linked to missing export KERNEL32.DLL:lsDebuggerPresent"

and in another window I get-

" C:\ProgramFiles\TunerProRT\Tunerpro.exe
A device attached to the system is not functioning. "

Is my old laptop missing something or is it just inadequate for the new version? Unfortunately deleted 4.0, thinking that the two couldnt coexist. I have also loaded and old 3.09 version and it works fine- no errors.

What can I do? I dont have 4.0 saved anywhere to try it again.

 

Can someone send me TunerPro RT 4.0 so I can see if that still works at least? I cant find it on the web anywhere.

Please send to SBNova@Yahoo.com , Thanks

 

I am running windows 95, Is tunerpro RT 4.13 compatable with Win95??

Ive searched the web and I find that Win95 doesnt have a debugger, so I dont know why I am getting this error. Like I said, 4.0 worked fine, and now 3.09 works fine- just no 4.13 !!

 

I'm really surprised (however pleasantly) to hear that any version of TunerPro worked on your Win95 machine.

Unfortunately I can't support Win95. I don't have a machine with Win95. Or, said clearer, I don't have a machine that I wish to pollute with Win95. Aside from that, though, there are many things about Win95 that just aren't good for forward progress of any software. It's lacking many of the common APIs used in Win98 and later. It's also just plain old man! 11 yeeaars old.

I know that's not what you want to hear, and I'm very sorry about that. I just don't have the kinds of time resources that supporting an OS that far back would require.

 

By the way, the IsDebuggerPresent means that somewhere in my code (or code it links to) a function, "IsDebuggerPreset()" is being called. Since I know I'm not calling it myself, it must be in a library I've added since v4.0. If I can find it and safely remove it, I will. That will get you working again.

I'll let you know if I can track down the cause. No promises, though.

 

" C:\ProgramFiles\TunerProRT\Tunerpro.exe
A device attached to the system is not functioning. "

Mark I had a similiar problem a week or two ago. I did a datalog over to a friends house no problem. When I tried to get a log back home I was receiving the same error message as the previous post although I was not getting any other message. I tried this a number of times and I even went to preferences and it found the cable no problem. As soon as I tried to connect I woudl get this message also. This has not happened to me until the latest version of TP '4.13'.

 

That particular message typically means you're missing a system component (i.e. driver, DLL).

I'm guessing both of these are related to the io.dll (parallel port DLL for the Prominator) that TunerPro uses. I didn't write that particular code, and it has been causing a headache for ages now.

 

OK but I am not using the prominator I am using a autoprom. I also noticed on my last datalog the frames seemed to be slow like another post. I normally problably have about 3 times the frames for this run which I have been doing for a while now. I also only pretty much use the laptop for only datalogging and I did do some MS service packs, etc but nothing out of the ordinary. It all appeared to happen after I tried to set the speed to 11MHz which I believe is a new setting in TP?

 

The io.dll is accessed regardless of whether or not you're using a Prominator. That will change in the future.

 

Thanks Mangus, I was gonna try to upgrade to 98, but I cant find a disc to do it. If you do happen to stumble on a fix I would appreciate it if you would reply here about it.

Have you (or anyone) got a 4.0 version of RT available anywhere so I can get back to where I was?

Thanks

 

Mark. The only thing that changed from before was that I upgraded to TP 4.13 and to the latest XP updates. Should I be looking to reloade the io.dll to see if that is the issue? Again it appears to be happening to a number of users so if you need me to test for you I will.

 

So far the count is at 2. You're right that 2 is a number. The problems you're both seeing are operating system (install) issues, not outright TunerPro issues, I'm afraid. As I said earlier, I have an idea what component within TunerPro is hitting the operating system issue, but it isn't a TunerPro issue. I just want that to be clear. ;-)

Do a google search on "A device attached to the system is not functioning" (with the quotes) and you'll see more of what I mean.

Do you both have parallel ports on your machines? If so, how are they configured?

 

Yeah Ive got a parralel port.

I searched for my error, and I found that windows 95 doesnt have a debugger, only 98 and newer. I really dont understand computer lingo, but from what I read I believe it says that the software is seeking a debugger and its not present. Maybe I am completely wrong- and probably so. Mark I am not blaming you in any way at all. I think what you do is great. Nor do I expect you to spend your quality time fixing an issue that only affects a very small quantity of us.

I would LOVE it if someone would send me a copy of any TunerPro RT older than 4.13, like 4.0 or even the ones between 4.0 and 4.13 for me to try.

 

This IsDebuggerPresent error is not for lack of a debugger in windows. IsDebuggerPresent is a function that an application (any application) can call to determine if someone has a debugger (which is a piece of software used for developing software) is connected to the particular application. Windows 95 doesn't have an implementation for IsDebuggerPresent, so it spits out this error. Again, this doesn't surprise me (I've never claimed to support Windows 95).

The "Device not functioning" error is due to some piece of equipment on the computer being missing, or a driver issue with a piece of hardware that TunerPro needs. As stated, this is most likely the parallel port (since the Prominator uses the parallel port).

Blame me, it's cool. No need to kid-glove. ;-)

I will roll some changes that have a chance of fixing this into another incremental release, as soon as I get more information on some other reported issues.

 

Guys -

Do 2 things for me:

1) Download the latest FREE version of TunerPro and install it and let me know if that works.

2) Try this (hopefully fixed) BETA build of TunerPro RT:
http://tunerpro.net/beta/Builds/Setu...ProRT_v413.exe

Let me know if each works.

-M

 

Did a search and found something about the error message with Visual Basic 3.0 programs and also about some network card drivers. I also went to the FTDI site and noticed there is a updated 2176 driver that resolves issues with freezing, etc. I will try the link to the download. Question is there any reason why I should not try this updated driver?

 

"I would LOVE it if someone would send me a copy of any TunerPro RT older than 4.13, like 4.0 or even the ones between 4.0 and 4.13 for me to try"
Version 4.0 sent. Hope it helps.

 

Thank you, Thank you, Thank you!!!

Mark, I will try your regular and beta tonight too. Like I said, I appreciate all your effort.

 

Neither one of those worked. I got the same errors with those as I did with TunerproRT 4.13.

Ive pretty much decided its time to upgrade. Ive got two newer laptops both running XP but neither have a serial port. I have tried adapters on my 3 year old laptop with very little success (had WinALDL working but no Tunerpro). It was a radio shack adapter, and it wont work at all with my newest laptop.

Ive been looking into port replicators. I really dont know if I want to try one or just spend $150 on another old laptop. I think I will search this board and maybe make a new post about the current use of adapters/replicators to see if anyone is having any luck.

 

Why not just buy a USB cable?

Moates sells a nice one that works very well for me.

 

I like serial ports myself.
Sagerlaptop.com (they also build the Alienware stuff behind the scenes)
I bought mine 5 yrs ago and it still works great (PIII, 800 Mhz)
I'm going to upgrade again this year and they still offer serial on allot of their units.
I do allot of component programming with RS232 so the ports are needed.
USB is nice but gives me headaches too many times due to "Plug-n-Play" not cooperating.

 

Moates also sells a $20 4-port USB PCMCIA adapter. Your laptop almost undoubtedly has a PCMCIA slot. That'd probably solve your problem too.

Which laptop is giving you trouble? Not one running XP, right?

 

My XP laptops run the software fine. I just cant connect with ANY of them. They dont have serial ports, and I tried 2 different USB to serial cables with little success.

I can get simple USB to serial adapters for $10-15, but might just be wasting more money. I can get a port replicator that I believe plugs into a PCMIA(?) slot and gives me a serial, which I think may be more solid. They run $20-$200. Then I could just get a $200 300mhz laptop with a serial and a USB and not worry anymore.

 

It's interesting that WinALDL connects but TunerPro doesn't. They both utilize the port in the same way (4800 baud).

The PCMCIA USB card from Moates is known to work. It's $20.

 

Yeah but I dont need a USB, what I need is a serial port. Unless I am misunderstanding you about something.

My new laptop has 4 USB's, yet I cant link with them. I tried both my cables with quite a few different driver software's that I found on the net, and I even tried a virtual port replicator too. None of it would let me link up.

Moates has that USB to ALDL cable for $80, but then I might as well get a *new* laptop for just a little bit more so my wife can have the newest one to herself.

 

I'm sorry, my fault. I kept seeing USB serial adapters and was thinking of converters for serial cables to USB connectors on the PC side. Backwards. If you don't have serial, I'd recommend ditching serial hardware. You could probably sell it for a decent amount.

 

Is the moates USB to ALDL cable the only one out there so far? I havent seen another. I understand that it may solve alot of problems but its $80.

 

This USB to serial convertor contains the FTDI chipset, which can support the 8192 baud rate. It works, I use it myself. (you still need to make yourself an serial-to-aldl convertor though)

Parallax, Inc-StoreFront Product Detail Page



Most usb to serial convertors contain a chipset made by Prolific. It does NOT do 8192 baud.

 

That's what I've been telling him.

Oh, and for the record, all of the Moates USB devices use the FTDI chipset. Many of the lesser expensive converters also use that chipset.

 

I think there is, although Moates is the one I have and use and only one I can recomend.

Sometimes for me spending an extra few bucks is worth NOT having the hassles down the road. Seems everytime I try to buy something a bit cheaper I struggle with it forever.

 

I have had 3 Dell laptops and logging problems ranged from none to periodically not being able to connect. I tried the Beta version of Tunerpro and was able to connect fine the first time then the second time I was not able to so I tried to duplicate the reason why I could not connect. The conclusion is that you must always open up the preferences and APPLY the settings even though they may be set properly before trying to connect. I verified this after failing to connect the second time. So try this:

1. Fire up your laptop and make sure you don't have any virus software or XP firewall turned on.
2. Open TP and go to preferences to set you connecting device. APPLY the settings even though they may not have changed.
3. Select your ALDL file and your datalog file.
4. Plug in your device.
5. Turn key on.
6. Connect.

Again step 2 appears to be the key for being able to connect for me. I don't know if Mark can do anything about this in TP but I cannot connect without performing step 2. I have tried this even by rebooting, etc. It appears that TP is not ready for the connection until you do this.

I have had both versions of the Autoprom and I can tell you this the serial connected much easier and was more consistent for me.

 

I can assure you that TunerPro doesn't do anything with the prefernces when you apply them other than save the data to memory. The ports aren't reset, reconfigured or otherwise.

The port isn't even opened until you try to connect to your ECM, and it's closed when you disconnect. So I'm 100% certain that the whole preferences "apply" thing is a red herring.

What happens when you shut down TunerPro and re-open it?

 

Failure. If it is a red herring it appears to do something for my laptop. Past posts even state that I open TP and check the cable connection and it works fine which implies AP is connected at that point. Then try to datalog and it fails saying it cannot connect to the port. Once the failure message appears I could never connect in that session although I did not try to get a failure then try to reapply the preferences in the session without reopening TP but I would expect it to fail also. Hardware device appears not to recognize the port after the failure either. As stated before a plain reboot does not fix the problem. Don't know if it is windows related or Dell but my other laptops had W2k on them or had them updated to XP. This latest is clean load of XP Home with service pack 2.

My latest laptop gave me fits if you remember to the point of private messages to Mark and Craig. There was a post I think from JP on the setup sequence that finally got me going. I have it written in a log book on page one and been using it to connect. Nothing is more frustrating than datalogging for a few months and then not being able to connect the next time an then trying to figure out the subtle differences. You can chalk it up to user error but hopefully I can get my laptop to connect as easily and consistently as I can get it to fail.

Mark if you want me to do a specific set of tests for you I will no problem. Just let me know. Also I tried the new FTDI drivers -do not load them until Craig or Mark configures them. All I got was a consistent blue screen of death. I believe the latest is 2176 -use 2154.

 

USB, right? Make sure you get the latest driver from the FTDI web site. Their driver has been sucky up until recently, where it sucks only slightly less. They had issues where the driver wouldn't release the port immediately after the application did.

Here's a link:
http://www.ftdichip.com/Drivers/VCP.htm

Outside of that, I'll look into it. Thanks.

M

 

Mark check my edited message above.

 

what does "-do not load them until Craig or Mark configures them" mean? You should be able to load it just fine. No driver config is necessary.

If you're getting blue screens of death, that tells me that something is very sketchy with your OS install.

See, that's what makes these kinds of things difficult. There are quite a few people out there using TunerPro (maybe ~1000 or more). Only a few (like, 10 or less) regularly report these types of instability issues, and every time they're reported it seems to involve wishy-washiness (that's a technical term) around the operating system (be it Win98, ME, 2K, or XP). Windows XP is respondible for by far the least of these types of issues, being by far the most stable OS.

So if it seems like I'm pushing this off on the OS... well, in many cases I am.

Blue screens of death tell a wonderful tale. I bet after it blue screens and you reboot, you get the "Windows recovered from a critical error", and when you hit "Submit" (provided you have an Internet connection) IE opens up with "the error was due to a driver". Is that about right? If so, there's little I can do as the TunerPro guy to help with driver issues, unfortunately.

I do nothing extravagent with the port. I open it, write and read from it, and close it.

I'll still look into it.

 

OK here is the deal I tried to load 2176 on my desktop Friday night. Again this is clean load of XP as of just a couple of weeks ago on a Athlon machine. I do all my burning on my desktop. Installing the driver immedialtely failed and gave me the BSOD with windows shutting down. I got it to load the driver in Safe mode. When I rebooted and in regular mode and plugged in the AP it would immediately go into the BSOD. I did check the Moates USB driver install with the 2176 and it appears Craig may have coded the install slightly differently but what do I know? I did not try to even load 2176 on my laptop after that. I did load your Beta version of TP on both. Have you installed it on your machine yet?

 

Not sure if you're talking about TunerPro or the driver, but in any case the answer is a "yes, of course" to both. On every machine I own with a USB port (see this).

 

I was talking about the driver itself. I have seen the BSOD in other high end software applications. In that situation it came down to NVIDIA video card drivers needing to be updated. I have not tried the 2176 driver on my laptop only my desktop. My desktop has a NVIDIA video card and my laptop does not. The desktop is running the latest videocard driver. I have always been able to plug in my AP and burn chips without any problems what-so-ever. All the problems I have ever experienced have always been related to the datalogging side only. So it always has involved a laptop and only while trying to connect to the ecm. With the 2176 driver installed on my machine I can plug in the AP fine with TP closed and when I open TP instant BSOD. If I go the opposite route -TP then plug in the AP again instant BSOD. When I use the 2154 driver from the MOATES site it works fine. One other variable the USB port is version 1.1 on my desktop.

 

That's an interesting tidbit. I'll investigate. Can you PM some specific repro steps?

 

OK I will send you email when I get home tonight. Let me install the 2176 driver on my laptop also and see if I have any issues.

 

Anyone looking for a Serial to USB cable FTDI makes one thats USB 2 capable for $35. Its distributed by http://www.saelig.com.

 

Any closure to this? I get the same error message on my old laptop I did the same thing, delete 4.0 to update, and it bit me in the butt.

I also have a newer laptop with Vista that is giving me problems in the car. I'm using a Radio Shack usb to serial and I'm going to talk with craig about buing one of his cables.

 

Missing IsDebuggerPresent is because you're probably running an unsupported OS. TunerPro v4.0 supports Win98 and newer. Win95 is not supported.