yes my VD shows a shield,how should i turn off adminstration? i have a windows 7 laptop can you plz help me i have too see some important logs.

 

i agree why does it need to elevate, something is not right... i think evoscan uses some updater and it does not ask me to elevate every time. that prompt is just a hassle, uac is there for a reason (not perfect) but is better than having nothing. if programs are made correctly they do not need to elevate if not required.

another thing that gets me is... why do i have to go through 4 steps everytime to choose my car, it would be soo simple if it just remembered my prev car selection and use that... apart from pro tuners... 99% of ppl would have the same car and would almost never need to change their cars. and even the pro tuners it would benefit as if they working on the same car they dont have to change... till they get to a different car.
or have i missed something obvious.

 

Ziad: you can set a profile for a car and then work with that profile the entire time and it remembers your settings.

The proper way to handle the UAC is to ask for elevation of rights using application manifests but I may be doing it incorrectly. Im going to consult with a guy at work today that worked at Microsoft on the CLR team (common language runtime for the .NET framework). He just happens to work on the same team as me. He may have some insight into this permission elevation issue.

 

We will get it corrected. In the mean time you can turn off UAC to get it working. Like I said Im going to fix this problem as I thought it was already fixed but obviously not.

 

Dragging and dropping from different permission levels in windows is not allowed. Even if you are running an admin account with UAC turned on you arent running as an admin. It only elevates you to the level you need to run or do the task you are doing. Hence the problem. You cant drag from a lower level app say Explorer, to VD at a different level. There is a fix for this but maybe I implemented it incorrectly so Im going to ask a guy today about this.

 

its working now thanks. but now the thing is my previous log showed at 1.7 bar my car had 435 whp and today i did 3 runs and everything was the same and its saying close to 500whp or above,is something wrong? cause i know my car is not a 500whp car.

i do 3rd gear pulls from 2000 rpm to 8000 rpm.

and how accurate is VD?

 

Negative. Unless the XML files are stored in a location where they shouldn't be you should never need to elevate to do this.

 

I know how Drag and Drop across processes of a different level work. I am asking why your program needs to elevate in the first place. Solving that will solve the drag and drop problem since then they won't be a difference in the levels of the processes. Its definitely how you implemented it.

Anytime you need to turn off UAC for a basic application like this, the application has been implemented incorrectly.

 

So I took a quick look at program since I've never used it before. Its setup so that it automatically must request admin rights on a properly locked down system. It then launches using admin and saves all its files under the app data folder of the admin. The last part is ok since it means at least it saves/reads its files from the correct place. The issue is understanding why it defaults to running as admin. It may be the options that are used on it at compile time aren't what they should be. Once you tinker with that this will work fine with UAC on from what I saw in my 15 mins of looking at it.

Edit Just re-read one of your earlier posts where you talk about requesting permissions. This is where the bug is.

 

It uses the application manifest to elevate to the level of an admin to run because it must use the registry. If you have some experience with different compiler options that address the UAC or different application manifest options please do let me know. I dont know of ANY compiler options that deal with the UAC.

Also the UAC would LOVE for you to have a signed certificate from someone like Verisign to sign your assemblies with. I dont have the extra cash to put toward a certificate as they are sort of expensive Im not the biggest fan of the UAC as it tends to cause more trouble than it prevents (from my experiences).

 

When I looked at the registry it wrote to HKLM on install. I didn't see it write there again but I may have missed it since it was late. HKLM needs admin rights, if you write to HKCU you don't...the registry is outdated in 2012 anyway (unless you are guaranteeing backward compatibility to pre XP systems as well). No need to store anything there anymore. At best you need to elevate to run your updates, and you could solve that by forcing folks to have to click an update link/button where you elevate at that point.

I threw the compiler option out there as possibility since I wasn't sure what you were using to compile. Some 3rd party compilers do fun stuff. I run with UAC all the time and see similar stuff from even big companies that should know better (Google and Oracle come to mind) and it usually is an issue with how the app is written. I'll get around to taking a closer look at the app again some time in the next couple of months and hopefully I can figure it out then.

I see UAC as a great enforcer. Forcing standards on loose Win32 app developers that really should have been enforced 15+ years ago.

 

i did some testing tonight this things damn close to the real dyno.. i had the wrong equation for my evoscan boost logging so i completely f'ed myself.. but its within 10whp or so.. its stupid accurate. ill do the testing again when i get more free time.

when doing runs on smooth flat road man this things on the money.. i can prove it once i drop my boost log into vd so it overlays over the actual vd run to compare boost curves with real dyno logs.

with afr and boost.. will update later.. but doing the runs on the freeway made night and day difference Brad.

33 spike drop to no clue.. but it was registering 499hp and 493hp right at or under 500 each time unless the car got a misfire then it would spike the log and inflate the number if you tried to smooth it over. on the real dyno it showed 490/444 @ 34psi on vd it showed 499/464 @ 33-34psi roughly.. i was eyeballing the gauge.

i have to change plugs & regap and will do a full blown comparison with my current data logs and dyno graphs i have here currently.

i look forward to testing this.. just need to make sure its the same 55F temp outside again when i do it for accurate comparison..

but ya the road surface makes a world of difference with this program.

 

Are you comparing virtual dyno runs on the street to dyno runs?

 

@tscompusa: thanks for the compares ... keep us posted for sure. I agree that the road surface makes a huge difference. I think some people are trying to log on a mountain side and wondering why they dont line up. *sigh* ( I cant fix stupid ) I just sent 1.1.8 beta 9 to a new beta tester and within a day or so I should have it tested and ready to release unless something major is found. Its got a lot of bug fixes and I ripped out a lot of the code that requires elevation in the UAC so that should be a non-issue anymore. I hope.

That small of a variance is expected ESPECIALLY if its not the same day and runs right next to each other. Thats why you usually get a base pull and then tune on the same day. Every time you tune you need to get a baseline just for comparisons because the run from the day before could be completely off due to weather changes. I used to work for a place that tunes (big tune in a box company which will remain unmentioned) and they would get a baseline even in the afternoon after lunch because of the temp and humidity changes just to be a little more accurate. It can vary and most people dont know that. If I was out to get high numbers Id wait for a high pressure system to move in and it be the middle of the winter in canada. Some people just dont know how much that affects numbers. Ohh and dont get me started on the usefulness of peak numbers.

 

ya.. i have the logs from the dyno so i can play with my car on the street until the boost & afr match really close then i can get an idea how accurate VD really is..

i know its not a controlled environment like a dyno is where it literally maintains the same surface run after run after run which is what makes the real dyno the most accurate power tuning tool in the world, but im just trying to find out how close vd can simulate it on a smooth flat road.

the interstates here are like airport strips.. they are super super smooth and around 2am there is nothing on them on weekends.

have you compared yourself before?