Evo X Logging
#633
Former Sponsor
iTrader: (4)
Kooldino, yeah its crazy Vista behavour... All I do in EvoScan code is use StartupAppPath + \SavedDataLogs\ so I'm guessing Vista is hacking my StartupAppPath to put it where it likes. no wonder people are waiting for Windows7 other than me creating a folder in "My Documents" called "\EvoScanLogs\", thats the only thing I can think of doing that might get around this.
#634
Former Sponsor
iTrader: (4)
I just tried some logs for practice with EvoScan and found something odd. If I go to "C:\Program Files\EvoScan\EvoScan v2.6 Beta17\SavedDataLogs" I will only see two sample logs.
However, if I go to "Graphs & Maptracer>Analyze .csv", I will get a list of the same exact directory (I verified it was the same) with the two sample logs PLUS all of the logs that I've taken.
What the hell?
Edit - I ended up finding them in "C:\Users\Dino\AppData\Local\VirtualStore\Prog ram Files\EvoScan\EvoScan v2.6 Beta17\SavedDataLogs"
I guess this is some kind of Vista thing? The original default "C:\Program Files\EvoScan\EvoScan v2.6 Beta17\SavedDataLogs" does exist, but it's not being used. Don't ask me why.
However, if I go to "Graphs & Maptracer>Analyze .csv", I will get a list of the same exact directory (I verified it was the same) with the two sample logs PLUS all of the logs that I've taken.
What the hell?
Edit - I ended up finding them in "C:\Users\Dino\AppData\Local\VirtualStore\Prog ram Files\EvoScan\EvoScan v2.6 Beta17\SavedDataLogs"
I guess this is some kind of Vista thing? The original default "C:\Program Files\EvoScan\EvoScan v2.6 Beta17\SavedDataLogs" does exist, but it's not being used. Don't ask me why.
I found this response on google:
It's really pretty simple. Just Right Click on the Icon for the program or it's shortcut and go to Properties. On the Compatibility tab at the bottom is a check box to select to Run as Administrator. There is also an option at the top to run it in a mode from a prior operating system. I would recommend also setting this to XP service pack 2 mode.
Data Redirection
With so much emphasis on running as a standard user, there’s some concern about whether common LOB applications will function correctly. To address this concern, the data redirection feature facilitates application compatibility. Data redirection, also known as data virtualization, provides a driver for the file system and registry that will redirect writes targeted at certain protected locations, such as HKEY_LOCAL_MACHINE\Software or %ProgramFiles%, to the user’s profile.
For example, if a member of the Users group is logged onto a machine and runs an application that writes a log file back to the Program Files directory, this write will fail. Why? Because the access control list (ACL) on the Program Files directory does not allow standard users to write to that location. When the data redirection file system driver receives the failed return code from this write, it redirects the write to a copy of the file made in the virtual store, a location in the user’s profile. An application that is marked with a run level in its manifest or that is a natively compiled 64-bit app is assumed to not require virtualization, so data redirection is disabled for that app. Windows binaries are marked with a run level, thereby disabling virtualization, and it is a requirement of the Windows Vista logo program that certified apps can run without data virtualization.
With so much emphasis on running as a standard user, there’s some concern about whether common LOB applications will function correctly. To address this concern, the data redirection feature facilitates application compatibility. Data redirection, also known as data virtualization, provides a driver for the file system and registry that will redirect writes targeted at certain protected locations, such as HKEY_LOCAL_MACHINE\Software or %ProgramFiles%, to the user’s profile.
For example, if a member of the Users group is logged onto a machine and runs an application that writes a log file back to the Program Files directory, this write will fail. Why? Because the access control list (ACL) on the Program Files directory does not allow standard users to write to that location. When the data redirection file system driver receives the failed return code from this write, it redirects the write to a copy of the file made in the virtual store, a location in the user’s profile. An application that is marked with a run level in its manifest or that is a natively compiled 64-bit app is assumed to not require virtualization, so data redirection is disabled for that app. Windows binaries are marked with a run level, thereby disabling virtualization, and it is a requirement of the Windows Vista logo program that certified apps can run without data virtualization.
Also check the status bar of EvoScan, EvoScan when first run, should be setting the ACLs on the EvoScan folder for full R/W access. Check the status bar for Vista security status when you first open EvoScan.
Last edited by evo4mad; Jul 27, 2009 at 02:07 AM.
#637
Evolving Member
iTrader: (1)
Join Date: Apr 2007
Location: Jersey
Posts: 261
Likes: 0
Received 0 Likes
on
0 Posts
@evo4mad - Thank you! I figured it was some Vista security thing (and I even changed the permissions on my real Program Files\EvoScan directory to try to circumvent this), but I'll try your suggestion about running it in compatibility mode tonight. Damn Vista.
I'm starting to suspect that I edited my ROM ID XML file properly as well, but I suspect that Vista is looking at another copy of this due to the same data virtualization garbage. I'll give it a whirl this evening and let you fellas know.
In the meantime, does anyone have a list of the extra parameters that are loggable with mode 23 enabled ?
I'm starting to suspect that I edited my ROM ID XML file properly as well, but I suspect that Vista is looking at another copy of this due to the same data virtualization garbage. I'll give it a whirl this evening and let you fellas know.
In the meantime, does anyone have a list of the extra parameters that are loggable with mode 23 enabled ?
#641
Former Sponsor
iTrader: (4)
28th July 2009: EvoScan v2.6 Beta18 released!
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
#642
Evolving Member
iTrader: (1)
Join Date: Apr 2007
Location: Jersey
Posts: 261
Likes: 0
Received 0 Likes
on
0 Posts
28th July 2009: EvoScan v2.6 Beta18 released!
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
#644
Evolving Member
iTrader: (2)
28th July 2009: EvoScan v2.6 Beta18 released!
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
Download EvoScan Beta18 here(registered users only. Unregistered users get your registration number from www.evoscan.com)
- Auto selects "OpenPort" cable for ecu logging when a openport cable as well as usb-serial adapter is connected.
- New USDM Mode23 Items
- New JDM Mode23 Items
- New JDM RS Mode23 Items
(thanks mrfred/SiC)
#645
The difference is exactly what evo4mad posted. The auto-select and new mode23 data items that you can log. I haven't personally looked into it to see what additional data items it can log.
Last edited by LaXGSR; Jul 27, 2009 at 04:35 PM.