Welcome to Bimmerfest -- The #1 Online Community for BMW related information! Please enjoy the discussion forums below and share your experiences with the 200,000 current, new and past BMW owners. The forums are broken out by car model and into other special interest sections such as BMW European Delivery and a special forum to voice your questions to the many BMW dealers on the site to assist our members!

Ok. Incidentally, I wrote the initial instructions, and the copy I just shared with you, v.2, varies only slight from the original. What you had is something different. Since you mentioned a batch file, I think those are the instructions that go along with one of April1's Install batch files. You should be good to go know though.

I think I just dug around to avoid bothering anyone at first.

Anyway, I went through the new instructions and moved things around a bit. In your instructions you state, "Make sure that there is a "Dist" folder in each of the Chassis (F01/F10/F25) folders etc."

My psdzdata folder (now in it's proper place) has nothing but files with the pattern psdzdata.7z.001 through 030. There are no subdirectories in C:\E-SysData\psdzdata.

I'm also not sure where the cafd* files should be. I guess they should be copied to C:\E-SysData\CAF?

Follow this excatly as written. If you still have problems, let me know.

Shawn,

Per your instrcutions: 10) Run "C:\EC-Apps\ESG\E-Sys\E-Sys.exe"...

However, the shortcut that is created on the desktop during the e-sys install points to "E-sys.bat" in that same folder. The .bat file seems to setup alot of options (e.g. memory setting, etc.) and paths that does not overide any of the parameters we put into the settings following your directions):

-----partial example of e-sys.bat file content:
SET ESYS_DATA_PATH=%ESYS_DATA_PATH:\:=:%
SET ESYS_DATA_PATH=%ESYS_DATA_PATH:\\=\%

set JAVA_HOME=%~dp0jre
set PATH=%JAVA_HOME%\bin;%PATH%;C:\EDIABAS\Bin;C:\EC-Apps\EDIABAS\Bin

Should I set the shortcut to point to the .exe file instead so as to not run the .bat file?

I clicked on the desktop icon (starting using the .bat file) for the first run and then made the following changes per your install instructions (which are still there if I start with the .bat file or the .exe file):

On the PROGRAM TAB, set the Directories - Data Path to C:\ESysData
On the EST Tab, set the Developer-Soft-Token EST Path to "C:\ESysData\e-sys est\Code Away.est"
On the ODX Tab, set the ODX Rule Path to "C:\ESysData\Rules"

I would think we would want to run the .bat file provided with the e-sys install that the shortcut points to for other e-sys default settings, but then we would not be following your instructions exactly as written. Probably does not matter either way...

Question #1: but it would be nice to know if there is a specific reason to bypass the .bat file provided with the e-sys install or if it just does not matter either way?

Question #1A: If I shouldn't be using the .bat file, did I accidentlly change some option that I shouldn't have like the memory setting of 512m that my e-sys is set to even if starting with the .exe file (e.g. should I do a re-install and this time not use the e-sys.bat file / desktop shortcut to start e-sys ever and only use the e-sys.exe in which case I will change the target in the shortcut to the .exe file)?

Question #2: On another subject, I assume it is OK to delete the extracted install folder "E-Sys_EST_PIN" once I have completed all steps of the installation or will I need other files in there readily available during coding (I did keep the original compressed / *.rar files as downloaded in case of a need to re-install)?

However, the shortcut that is created on the desktop during the e-sys install points to "E-sys.bat" in that same folder. The .bat file seems to setup alot of options (e.g. memory setting, etc.) and paths that does not overide any of the parameters we put into the settings following your directions):

-----partial example of e-sys.bat file content:
SET ESYS_DATA_PATH=%ESYS_DATA_PATH:\:=:%
SET ESYS_DATA_PATH=%ESYS_DATA_PATH:\\=\%

set JAVA_HOME=%~dp0jre
set PATH=%JAVA_HOME%\bin;%PATH%;C:\EDIABAS\Bin;C:\EC-Apps\EDIABAS\Bin

Should I set the shortcut to point to the .exe file instead so as to not run the .bat file?

I clicked on the desktop icon (starting using the .bat file) for the first run and then made the following changes per your install instructions (which are still there if I start with the .bat file or the .exe file):

On the PROGRAM TAB, set the Directories - Data Path to C:\ESysData
On the EST Tab, set the Developer-Soft-Token EST Path to "C:\ESysData\e-sys est\Code Away.est"
On the ODX Tab, set the ODX Rule Path to "C:\ESysData\Rules"

I would think we would want to run the .bat file provided with the e-sys install that the shortcut points to for other e-sys default settings, but then we would not be following your instructions exactly as written. Probably does not matter either way...

Question #1: but it would be nice to know if there is a specific reason to bypass the .bat file provided with the e-sys install or if it just does not matter either way?

Question #1A: If I shouldn't be using the .bat file, did I accidentlly change some option that I shouldn't have like the memory setting of 512m that my e-sys is set to even if starting with the .exe file (e.g. should I do a re-install and this time not use the e-sys.bat file / desktop shortcut to start e-sys ever and only use the e-sys.exe in which case I will change the target in the shortcut to the .exe file)?

Question #2: On another subject, I assume it is OK to delete the extracted install folder "E-Sys_EST_PIN" once I have completed all steps of the installation or will I need other files in there readily available during coding (I did keep the original compressed / *.rar files as downloaded in case of a need to re-install)?

I have never used the .bat file to launch E-Sys, and I really do not think after looking at it that it makes any difference whether you launch E-Sys with the .bat or the .exe. file.

I would not worry either about the .bat file changing the default E-Sys settings, as it won't. The .bat file should just be session specific.

You can delete anything that the instruction does not specify it be copied and put in use or is left behind after doing so.

Can you please pm me the link to the files also. I currently have 4.75, Just picked up my 335i yesterday. Dont know if its compatible with it, planning on downloading 47.7. Should I download it or just use your 48.1 stuff? Also how do I go about using the file you sent me. Never coded a car before. I have the steps on how to set up and code though. Also does coding void the warranty, I have extended warranty on my car. Planning on taking to dealer to code the A.S.S. but I also want my windows to keep rolling up when I open the door. Thanks a lot in advance.

Can you please pm me the link to the files also. I currently have 4.75, Just picked up my 335i yesterday. Dont know if its compatible with it, planning on downloading 47.7. Should I download it or just use your 48.1 stuff? Also how do I go about using the file you sent me. Never coded a car before. I have the steps on how to set up and code though. Also does coding void the warranty, I have extended warranty on my car. Planning on taking to dealer to code the A.S.S. but I also want my windows to keep rolling up when I open the door. Thanks a lot in advance.

PM Sent.

Add 48.1 CAFD files to your existing 47.1 PSdZData by copying them to C:\ESysData\psdzdata\swe\cafd folder. Do not waste your time downloading 47.7.

Follow the Getting Started Coding Guide to understand FDL Coding. If you encounter a problem, let me know.

Add 48.1 CAFD files to your existing 47.1 PSdZData by copying them to C:\ESysData\psdzdata\swe\cafd folder. Do not waste your time downloading 47.7.

Follow the Getting Started Coding Guide to understand FDL Coding. If you encounter a problem, let me know.

Simple FDL Coding will not void your warranty.

When you mean simple, what exactly are you talking about? Main things i want to code are:
Windows up when door is open, also up with holding the lock button, tire pressure #, dvd in motion, fold mirrors with keyfob.

When you mean simple, what exactly are you talking about? Main things i want to code are:
Windows up when door is open, also up with holding the lock button, tire pressure #, dvd in motion, fold mirrors with keyfob.