BuGS

My bro has figured out the fix to all of the connection problems with E6K's with XP Professional. It is just a matter of shutting off the FIFO Buffers for the COM1 port.

To do this go to:

Control Panel->System->Harware->Device Manager->Ports (COM & LPT)->Dbl Click on COM1->Port Settings->Advanced-> Then unchecking the use FIFO Buffer setting. After that your Haltek software should be able to communicate to the Haltech E6K useing XP with no problems. My bro just did that and as I type it is uploading the map. I do not know if this Fix is already known (did not find it when I searched). Thats for reading and hope this helps.

Clayton

PS for any other assistance PM me.

82streetracer

iTrader: (1)

not able to try it right now, but thanks alot man.

much appreciated.

13BT510

It would be ohh so nice if this were true - unfortunatelly its not, plain and simple !

Well not on my XP machine anyway - nor any i have tried it on

anyone else been able to get this to work? or is someone's little brother exagerating his families abilities with a computer??

BuGS

Well my whats weird is that the fixed worked last night for my bro. He loaded the Haltech map up onto his haltech and it was all sweet. Then this afternoon when he went to try it it didn't work. So He just told me to post it up. He is a weird guy. But his car is awesome. Hopefully it will work for someone. He said that after he turned off the buffer it worked instantly. But today it won't work. He is gonna mess with it tomorrow so hopefully he can figure out a complete fix. He thinks it has to be a couple things and the FIFO buffer is definately one part of it.

Clayton

p51020b

This doesnt work on my machine either

zinx

iTrader: (3)

This is what i recommend doing. Creat two partitions on your laptop, one for windows XP (NTFS) and one for DOS. Setup in your boot.ini so you can choost which partition to boot too.

Setup the haltech software to automatically run in the autoexec.bat for the dos side so its like haltech is its own OS on your computer.

I haven't actually set this up because i just use two different hard drives but i'm getting tired of switching them so i'm going to set this up soon.

Wang

Hey guys I'm BUG's Bro I figured out you do need to turn off the FIFO Buffers at least with my setup and I'm using a usb to 9 pin adapter, this works if you boot up in bios. So the partition idea is probably the way to go, although I did get it to work in command prompt from XP but its not constant it'll work sometimes but I cant figure out whats different when it does work but I also did install the patch off the hitman site, not sure what it does because its all in GERMAN! haha anyways good luck guys I"m gonna partition tonight goodluck.

pengarufoo

Hey what USB to serial adapter are you using?

I'm interested in seeing if your random adapter works with the latest e6tuner beta, if you're willing to give it a try and can boot from floppy on your machine - check it out - I'd love to hear what kind of results you get:
http://pengaru.com/downloads/e6tuner/beta/
look at the readme.txt file

All the videos at the latest gallery page are of e6tuner running with a "prolific" based USB to serial adapter, and it worked really well! You may have better luck in windows with one of these, I suspect it depends heavily on the driver for the adapter. Heres the gallery page: http://pengaru.com/gallery/tuning/e6tuner_beta_pre10/

The way the E6K communicates requires the operating system/driver to not queue any of the data into bulk transfers, I'm not sure how much control you have over this in windows. All of the communications are 1 byte at a time, the software sends one byte, waits for one byte to come back from the E6K.. The E6K sends a byte and waits for a byte to come back from the software before sending another. So if the OS and/or driver is trying to make things more efficient by queueing many bytes before flushing them to the wire the communications will just get blocked up and the program will appear to be frozen - when it's really just waiting for IO that will never occur because it's command is sitting in the OS/driver layer queued - perhaps indefinitely.

Good luck

Wang

Hey actually I bought it off ebay for like $5, and its manufactured by "Prolific"
Oh and guys this is a weird way but I figured out why sometimes it would work and sometimes not. My driver disk also came with a "tester" program, if I use this program and "Open" up my com port and send some test txt, then close the program but without hitting the "close port" button on my test program it will then run the haltech from XP's command prompt. if you'd like the program I'll email you a copy its 125kb zipped so its too big to attach. I am not going to use this every time I want to connect it thought I"m still going to partition my hard drive.