Desensitize the knock sensor 94/95 LT1

[spfautsch]

I've been sitting behind a telephone supporting hundreds of windows machines for the better part of 24 years. My mileage never varies. When in doubt I wipe it out (windows installation).

Note that I do not use it on any of my personal machines. Windows runs just fine in VirtualBox on any linux distro.

When my "registry" gets fouled up and eehack won't launch (never had it happen, completely speculative) I just delete /home/spfautsch/.config/EEHackB/fbodytech.com.conf and let the program create a new config file.

[vilefly]

What I had done is allow windows to associate log files with EEhack. Then, I double clicked on a log file, and EEhack does this.
EEHACK ERROR1.jpg
then this.
EEHACK ERROR2.jpg
Perhaps I should post this in a matching section for the subject.

[roachjuice]

Mine was working perfectly.
I tried to open a log without actually having EEHack open. When I clicked on the log, it asked to open EEHack. So I proceeded.
Then threw the error up at me and has done so ever since.
I’ve even tried to download the new beta you have and still the same thing is happening. No clue honestly.

[roachjuice]

I've been sitting behind a telephone supporting hundreds of windows machines for the better part of 24 years. My mileage never varies. When in doubt I wipe it out (windows installation).

Note that I do not use it on any of my personal machines. Windows runs just fine in VirtualBox on any linux distro.

When my "registry" gets fouled up and eehack won't launch (never had it happen, completely speculative) I just delete /home/spfautsch/.config/EEHackB/fbodytech.com.conf and let the program create a new config file.

I’ll try this. Thanks.

[NomakeWan]

I’ll try this. Thanks.

Note that this is for a Linux machine, not a Windows machine. He uses Linux for his EEHack machine.

Registry cleaners like CCleaner will identify that there are registry entries associated with a program/directory that no longer exist (such as the .eehack file association, and any other entries the program created upon installation) and clear them out. This way you can specifically target changes EEhack made, rather than resorting to trying to restore the system to an earlier point in time (something of a carpetbombing approach to a specific issue with a specific program, not to mention unreliable in my experience) or nuking your entire Windows installation and starting over (far more reliable than system restore but a total waste of time and effort for such an unbelievably minor issue).

Just sayin'.

[roachjuice]

Note that this is for a Linux machine, not a Windows machine. He uses Linux for his EEHack machine.

Registry cleaners like CCleaner will identify that there are registry entries associated with a program/directory that no longer exist (such as the .eehack file association, and any other entries the program created upon installation) and clear them out. This way you can specifically target changes EEhack made, rather than resorting to trying to restore the system to an earlier point in time (something of a carpetbombing approach to a specific issue with a specific program, not to mention unreliable in my experience) or nuking your entire Windows installation and starting over (far more reliable than system restore but a total waste of time and effort for such an unbelievably minor issue).

Just sayin'.

i ended up running ccleaner. didnt work.
i reverted back too a previous windows save. eehack works again. i dont keep anything on this pc as its from 2008 lol. all i do with it is tune and datalog and it barely does that. thanks again for the help.

[NomakeWan]

I know it's irrelevant since you already used system restore with success, but did you uninstall EEhack, remove its installation directory, then use the registry cleaning function in CCleaner to remove the orphaned entries? Just for my own personal curiosity.

As I said I haven't run into these issues with it before, but hey, if I do, it'll be good to know.

[roachjuice]

I know it's irrelevant since you already used system restore with success, but did you uninstall EEhack, remove its installation directory, then use the registry cleaning function in CCleaner to remove the orphaned entries? Just for my own personal curiosity.

As I said I haven't run into these issues with it before, but hey, if I do, it'll be good to know.

yes I did. It still did the same thing. Even though ccleaner found files EEHack left. I saw them on the list. Oh well. It works now. I’m not concerned. Just word to future people. Don’t open a log without having EEHack open first. It will fuck EEHack all up.

[spfautsch]

When I get a moment to play with a winblows machine I'll dig through the registry and possibly have a suggestion to fix this involving deleting the file association subkeys for .eedata. I'm relatively sure it's related to the DDE transaction that happens when explorer feeds a flie list to the associated executable.

Of course, the obvious solution to this one is not to associate .eedata files to anything. DDE is the brainchild of insane coders from the 80s.

[roachjuice]

When I get a moment to play with a winblows machine I'll dig through the registry and possibly have a suggestion to fix this involving deleting the file association subkeys for .eedata. I'm relatively sure it's related to the DDE transaction that happens when explorer feeds a flie list to the associated executable.

Of course, the obvious solution to this one is not to associate .eedata files to anything. DDE is the brainchild of insane coders from the 80s.

Yea I’m sure it’s related to the DDE. I know what that is. I just don’t wanna mess with it lol. Minor glitch for an awesome program.

[steveo]

its crazy this is happening. eehack is a really basic program with really generic (but bloated because i use qt) library set.

i made the file association with this generic installer-maker-thingie program i was using.

i lost the install script and forget which program i used....... so ill be using something else for the next version

hopefully that means problem solved....?

we shall see.

i refuse to give a crap about or research or look into how windows file associations actually work in modern versions of windows.