All info I can get is helpful. Thanks again raene.
How goes it? Need more help?
I have all but given up. I cannot get it right. If I add in the TPS part, the idle goes up,down,up,down. Something isn't right, but I have no idea what.
The problem is you are adding the TPS code where it was commented out. ASM writes everything in order. So lets say for instance rpm was at position 1, mbar at 2, and mph at 3. Inbetween mbar and mph there was a commented out tps. Now you add that tps back, the order changes. So now you have rpm at 1, mbar at 2, tps at 3, and mph at 4. This shifts all the memory locations down a couple bytes. Thus fucking up all the code. Get it? I hate ASM.
ASM writes everything in order. So that means that the spot in the als file, where it says values, needs to read in the same order as in the asm file.
I think I tried that, not sure though.??. I will try again. Thanks you as always bigwig.
One other question: What is the place in the als file where it says
//script values + flags??
//script values + flags is a comment... it tells you that the following are pointers to the dynamic controls created by the script. Those store the values that are entered by the user. I initialize them all to -1 except for the speed one which for some reason had to be initialized as hex or it wouldn't go in and out as the same value entered... You can see later in the als I set them equal to the controls created on the page, and I read into / out of them with setitem and getitem.
If you want, U2U me and I'll put you on my MSN...
Everything is in order. Idle still screwy. I do not get it.
Do I need one of those script value lines for tps?
Raene: U2U?