03-25-2019, 01:45 PM | #574 | |
Registered
0
Rep 2
Posts |
Hi Tony, thank you so much for creating the Rearm! I have a question though...I am using the correct launcher and Esys (according to shawn Sheridan) and I ran the rearm as an admin and all seemed fine. When I connected my car and initiated the launcher and Esys, I could not get to edit fdl (was greyed out) until I clicked read coding data" (which still seems fine). Edit FDL now was available, but when I clicked it, Esys through an error: token was manipulated. Did I do something wrong? Is there any way to get around this? All I want to code is my fog light switch. Thanks!
Quote:
|
|
Appreciate
0
|
03-25-2019, 02:19 PM | #576 | |
First Lieutenant
106
Rep 348
Posts |
Quote:
If you want to enable full use of the widely distributed versions of E-Sys then you can request a validation code from TokenMaster for his E-Sys Launcher program, and good luck with that! If you want to use what's currently available to the rest of us then there are basically two options: 1. Find an online seller of a pirated, patched version of the Launcher, for which you'll pay. 2. Download the best current versions of E-Sys and Launcher (get a link from shawnsheridan) and Tony's rearming script, and follow the instructions to the letter. Once it's working, it's less hassle than anything else. |
|
Appreciate
1
minimega9.00 |
03-25-2019, 04:46 PM | #577 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
One thing I'm particularly curious about is whether creating a new (second) Windows account and starting my script + Launcher from there has any effect on the C157 error. I still haven't had any feedback on that, either positive or negative. Also, make absolutely sure that your system date is still reverted and stays that way when you get this error in E-sys. This is paramount, so double check this when you get the error! In Windows 10 don't stop or disable the Time service, as it will recover after a few minutes and reset time to 'now' when you're connected to the internet (thanks cjn for testing and reporting this!). Instead, rather go to the Date/Time-settings by right-clicking on the system clock in the lower right corner and disable the option "Set time automatically". Please report if this solved your C157 error. Cheers, Tony |
|
Appreciate
0
|
03-25-2019, 08:32 PM | #578 | |
Major
486
Rep 1,325
Posts |
Quote:
Launcher would crash on start up citing kernalbase.dll error, seemed to be caused by having .NET version which was unstable (4.7.x I think) so I installed 4.6.x reboot and used re-arm and now it all works so far. Will try on the car tomorrow |
|
Appreciate
0
|
03-28-2019, 04:06 PM | #579 |
Registered
0
Rep 2
Posts |
Hello Tony i have a problem with your script.
I'm using Win7 Ultimate. When i start as admin your script its waiting and giving error about the C:\Users\kaank\AppData\Local\Temp*. What is the actual problem. I didn't get it. Thank you. |
Appreciate
0
|
03-28-2019, 05:56 PM | #580 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
Can you copy and paste the actual error? Some apps and programs are holding locks on files in the TEMP-folder. This is preventing my script from redating them. Try closing all apps and programs before running my script. You might also want to disable your antivirus to see if that solves the problem. You can also explore that folder with Windows file explorer to maybe get a clue what's holding the lock. In the next update I've made a few checks that will update the TEMP folder only when needed. I think that will make things a little bit easier for most people. Cheers, Tony |
|
Appreciate
0
|
03-29-2019, 09:24 PM | #581 |
New Member
0
Rep 6
Posts |
Tony,
First I want to thank you for making this tool easy to use. I have a question about an issue that I hope someone may be able to answer. The rearm script runs great now that i stopped a process that was keeping files open in the *\Temp directory however, I am now getting an error when I run the launcher that says "Invalid provider type set". I look in the system logs and it looks like it is related to the date manipulation error that some people are reporting. anybody else having this issue as well? Install info: Win 10 Esys 3.27.1 E-Sys Launcher Premium 2.8.2 Rearm script 2.0 system time set to a date/time between the recomended dates 15 Jun 18 and 31 Dec 18 |
Appreciate
0
|
03-30-2019, 06:13 PM | #582 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
When googling the error you mention it seems to be related to cryptography and RSA keys, so I don't think it's related to the date manipulation error. If you see the date manipulation error in the event viewer as well it's probably 2 separate issues. Does the first error you mention stop occuring when you restart the process? If so, it's probably related to that process. For Launcher 2.8.2 the TEMP folder doesn't have to be redated anyway, so if you want to remove that line from my script you can safely do so. If you're still getting the date manipulation error, it could mean that either my script's not working correctly or it's missing some unknown check that's being performed on your system, but it's hard to tell based on your description. Cheers, Tony |
|
Appreciate
0
|
03-30-2019, 10:28 PM | #583 |
Lieutenant
114
Rep 524
Posts |
error running script v2.0
Hi, ran your script as admin, works fine and then get an error redating the
C:\users\username\ documents. Didn't have this problem with the earlier script- but never got passed to fully getting eSys to work either. I am using Norton AV. Any help will be appreciated. Thank you. |
Appreciate
0
|
03-31-2019, 09:23 AM | #584 |
Lieutenant
221
Rep 481
Posts |
Running into problems as well. (used esys before many times in the past)
Have: Esys: 3.27.1 PSDZdata: 4.12.20 Launcher premium: 2.8.2.155 Rearm script 2.0 Set the date back, run the script, start Esys (generate token) all works fine. Than connecto to VIN, also works, I get the confirmation that I'm connected. When I try to "read" Vehicel Order from "Coding" I get the error "Read FA failed! Possibly there is no FA stored in the VCM." Anyone got an idea? I've searched the forums, found the error a couple of times but no solution. |
Appreciate
0
|
03-31-2019, 02:20 PM | #585 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
Cheers, Tony Last edited by Tony Twoclicks; 03-31-2019 at 02:25 PM.. |
|
Appreciate
0
|
03-31-2019, 02:30 PM | #586 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
Cheers, Tony |
|
Appreciate
0
|
03-31-2019, 08:05 PM | #587 |
New Member
0
Rep 6
Posts |
Tony,
Thanks for the reply. Not sure what is going on with it on this computer but I have another laptop that everything worked flawlessly on for some reason. Now if i can just figure out how to code properly and unf*&k what I did today lol -Jason |
Appreciate
0
|
04-07-2019, 12:47 PM | #589 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
See post #265 Cheers, Tony |
|
Appreciate
0
|
04-07-2019, 12:58 PM | #590 |
Second Lieutenant
124
Rep 274
Posts |
Updated version
Version 2.0.4 is out!
Minor update to resolve some issues that were reported on the previous version:
Cheers, ---------- Tony Twoclicks |
Appreciate
0
|
04-08-2019, 09:58 AM | #591 | |
First Lieutenant
106
Rep 348
Posts |
Quote:
|
|
Appreciate
0
|
04-08-2019, 03:23 PM | #592 |
New Member
0
Rep 9
Posts |
Hello, I am located in France and I write to you via a translator
I can not get esys and rearm I think I do not use the right versions with the right dates thank you for your support |
Appreciate
0
|
04-08-2019, 03:59 PM | #593 | |
Second Lieutenant
124
Rep 274
Posts |
Quote:
https://www.bimmerfest.com/forums/sh...php?p=10193333 You can find the valid dates to use in the readme.txt that's included with my Rearm script. Cheers, Tony |
|
Appreciate
0
|
04-08-2019, 04:02 PM | #594 |
Second Lieutenant
124
Rep 274
Posts |
|
Appreciate
0
|
Post Reply |
Bookmarks |
Tags |
clock, date, esys, launcher, premium |
|
|