morer like 60 entries

I have plenty of time to work on this system, why did you think otherwise?ALL code used to access the AMB is proprietry

You mentioned personal problems back on page 2.

Not if you worked out the protocol and wrote the code yourself.

"Must"? What makes you think having twice as many entries would cause the program to do twice as much work? Does it involve that much more processing to run 10 cars in a race compared to 5? There are a lot of overheads that need to be done to say run a race, even if there no drivers in it. But this is irrelevant, what does it matter how big the log file is, provided there is sufficient disk space? And how does this affect stability of a program?

And something I just thought of - earlier copies of a new version often have substantial debug logging in, which can SUBSTANTIALLY increase the size of a log file.

Time or lack of it won't help, in fact Alycat is a diversion.

Quote:

Not if you worked out the protocol and wrote the code yourself.

ROTFL, are you serious? Apart from the legal considerations of attempting to reverse engineer stuff, even if you put a port sniffer on and ran the AMBrc decoder, there is an awful lot of data going both ways. And USB was a further nightmare, mainly because AMB would not provide any specific info and AMB does not use a standard USB setup.

Fair enough.

How does one get hold of an API to interface with the AMB system?

There is nothing like a API - email me or better use MSN

What language do you program in?

Ask them if the copy of Alycat they are running says "Verified Setup Version" in the caption, and on the day make sure the printout says "Verified Setup Version: NSW State On Roads" or similar for the meeting. If not, ask them what they have changed from the verified setup and why.