evoscan 2.5 w/ vista woes
evoscan 2.5 w/ vista woes
So I am now running a vista laptop and I amvery new to vista and I have all the programs, tactrix drivers, etc working except for evoscan.....
I have installed, re-installed x10 and I get the same error everytime. This is version 2.5 which I thought was vista compatible? I changed the security settings within the program to "full control".....I did see on evoscan website is says to change something in the registry but I am not sure what to do exactly and im not comfortable doing that until I am sure of what/why I am doing.
Here is the screen shot of the error message......ifanyone can help I would appreciate it, Thanks
I have installed, re-installed x10 and I get the same error everytime. This is version 2.5 which I thought was vista compatible? I changed the security settings within the program to "full control".....I did see on evoscan website is says to change something in the registry but I am not sure what to do exactly and im not comfortable doing that until I am sure of what/why I am doing.
Here is the screen shot of the error message......ifanyone can help I would appreciate it, Thanks
I have vista: home premium
- Fixed: EvoScan Vista 64bit now works with datalogging. I changed some compiler settings and have now got it working correctly. EvoScan also now uses HKEY\CurrentUser for settings, as Vista no longer allows HKEY\LocalMachine for storing settings.
Still not sure what were to change in the registry?
Hopefully Hamish will chime in when he gets a chance and can help get it all sorted out. Luckily I have my old laptop w/ xp to use until I get this one up and running correctly for car stuff.
Last edited by travman; Dec 25, 2008 at 10:15 PM.
OP: Did you right click and run the program as an administrator? Sounds like you have but just wanted to make sure. The error seems to be the pretty generic "you are trying to open a file from a restricted location and i won't allow you".
The odd thing is the path. x86 implies that this is a 32 bit program running on 64 bit windows using WoW. While I do have 64 bit machines i've still been running evoscan on 32 bit so for those on 64 bit is it that evoscan isn't natively 64 bit as of yet?
As to this quote:
HKLM was never supposed to be used for storing anything that was user specific. This is supposed to be used for certain properties/settings that are shared across all users. This is a common programming mistake that many Windows developers have been making for years.
That kinda stuff is supposed to be stored in HKCU or its equivalent. Should really be done for any Windows system but thankfully now the OS is enforcing it
.
The odd thing is the path. x86 implies that this is a 32 bit program running on 64 bit windows using WoW. While I do have 64 bit machines i've still been running evoscan on 32 bit so for those on 64 bit is it that evoscan isn't natively 64 bit as of yet?
As to this quote:
EvoScan also now uses HKEY\CurrentUser for settings, as Vista no longer allows HKEY\LocalMachine for storing settings.
That kinda stuff is supposed to be stored in HKCU or its equivalent. Should really be done for any Windows system but thankfully now the OS is enforcing it
.
Last edited by codgi; Dec 26, 2008 at 03:20 PM.
OP: Did you right click and run the program as an administrator? Sounds like you have but just wanted to make sure. The error seems to be the pretty generic "you are trying to open a file from a restricted location and i won't allow you".
The odd thing is the path. x86 implies that this is a 32 bit program running on 64 bit windows using WoW. While I do have 64 bit machines i've still been running evoscan on 32 bit so for those on 64 bit is it that evoscan isn't natively 64 bit as of yet?
As to this quote:
HKLM was never supposed to be used for storing anything that was user specific. This is supposed to be used for certain properties/settings that are shared across all users. This is a common programming mistake that many Windows developers have been making for years.
That kinda stuff is supposed to be stored in HKCU or its equivalent. Should really be done for any Windows system but thankfully now the OS is enforcing it.
The odd thing is the path. x86 implies that this is a 32 bit program running on 64 bit windows using WoW. While I do have 64 bit machines i've still been running evoscan on 32 bit so for those on 64 bit is it that evoscan isn't natively 64 bit as of yet?
As to this quote:
HKLM was never supposed to be used for storing anything that was user specific. This is supposed to be used for certain properties/settings that are shared across all users. This is a common programming mistake that many Windows developers have been making for years.
That kinda stuff is supposed to be stored in HKCU or its equivalent. Should really be done for any Windows system but thankfully now the OS is enforcing it
.Every program I have loaded has gone in the x86 progrm files folder but there is also another programs file folder that is not labelled w/ x86. I tried installing into that folder and I got the same message....
It seems 2.6 might have the 64 bit issues resolved maybe but to upgrade it says I need to have 2.5 working? I am very new to vista here so I guess I will just keep plugging away and see what I ca figure out.....
any and all help is appreciated - btw I have Vista Home Premium
Trending Topics
ok got it.......it was the administrator thing.
I was going into the main programs screen on the desktop and right clicking then for properties which is just the shortcut. I was changing what I thought is what I needed but then I went into the actual program file folder in the C: drive......I right clicked on the actual evoscan.exe file and there was the run as administrator box to click. I checked the box, program installed and it all worked....well least the opening part (need to test logging)
So codgi thank you for questioning me and making me dig deeper.....so far im not totally hating vista but its def. a little more security unfriendly but I will get used to it....
I will post tomorrow if it logs properly.....I have 2.5 and 2.6 opening without any errors so I will test both for logging and report back.
I was going into the main programs screen on the desktop and right clicking then for properties which is just the shortcut. I was changing what I thought is what I needed but then I went into the actual program file folder in the C: drive......I right clicked on the actual evoscan.exe file and there was the run as administrator box to click. I checked the box, program installed and it all worked....well least the opening part (need to test logging)
So codgi thank you for questioning me and making me dig deeper.....so far im not totally hating vista but its def. a little more security unfriendly but I will get used to it....
I will post tomorrow if it logs properly.....I have 2.5 and 2.6 opening without any errors so I will test both for logging and report back.
I get the same message..
So I am now running a vista laptop and I amvery new to vista and I have all the programs, tactrix drivers, etc working except for evoscan.....
I have installed, re-installed x10 and I get the same error everytime. This is version 2.5 which I thought was vista compatible? I changed the security settings within the program to "full control".....I did see on evoscan website is says to change something in the registry but I am not sure what to do exactly and im not comfortable doing that until I am sure of what/why I am doing.
Here is the screen shot of the error message......ifanyone can help I would appreciate it, Thanks
I have installed, re-installed x10 and I get the same error everytime. This is version 2.5 which I thought was vista compatible? I changed the security settings within the program to "full control".....I did see on evoscan website is says to change something in the registry but I am not sure what to do exactly and im not comfortable doing that until I am sure of what/why I am doing.
Here is the screen shot of the error message......ifanyone can help I would appreciate it, Thanks
Go to your C: drive and access the evoscan folder in the program files.
Right click on the evoscan.exe file and go to properties.
The you will see a check box to run the program as administrator, check the box and the error should go away.
- This worked for me and I no longer get the message, now if i can figure out why it connects but doesn't spit out any data when connected to the car I would be 100% satisfied.
Right click on the evoscan.exe file and go to properties.
The you will see a check box to run the program as administrator, check the box and the error should go away.
- This worked for me and I no longer get the message, now if i can figure out why it connects but doesn't spit out any data when connected to the car I would be 100% satisfied.
Ya I did that no more error message!! But it's not logging anything,,,
HELP HERE PLEASE,,,
HELP HERE PLEASE,,,
Go to your C: drive and access the evoscan folder in the program files.
Right click on the evoscan.exe file and go to properties.
The you will see a check box to run the program as administrator, check the box and the error should go away.
- This worked for me and I no longer get the message, now if i can figure out why it connects but doesn't spit out any data when connected to the car I would be 100% satisfied.
Right click on the evoscan.exe file and go to properties.
The you will see a check box to run the program as administrator, check the box and the error should go away.
- This worked for me and I no longer get the message, now if i can figure out why it connects but doesn't spit out any data when connected to the car I would be 100% satisfied.
Sooner or later it will be resolved....