Easydis Base V44 V10
Dec 19, 2014 - How to install DIS w/ EasyDIS v44 step-by-step easydis-base-v44-t6965931.html.
Metal gear solid rom. It's a weird debate to have; few creative endeavors are more nakedly commercial than video games and it shows: individual studios, let alone designers, are rarely afforded the opportunity to have their names associated with games, no matter how popular. As an industry, video games have had a strong self-conscious streak about whether or not they are 'art.' Most likely, it's just pragmatism.
Mirror: Download (Uploading).
• MediaFire 619.45MB • MediaFire 1.48GB *EDIT 7 May 2018: OK, thank you everyone who left a comment, I am glad so many people have found this guide helpful. Due to the high volume of traffic and unreliability of the DropBox links, I have finally added the files to MediaFire and Google Drive.
NEW USERS: This is a guide on how to install DIS using the instructions that come in the.zip files, not a detailed guide. The complete procedure to install DIS is quite complicated and has so many variations that will end up with it not working or need the whole thing installing again to change, so follow through them as per the guide below and you should get it going, as many others have. Read the troubleshooting section at the bottom, particularly the first part.
The Windows install on some laptops simply will not work with the virtual networking needed to set DIS up and/or routing of the COM ports, yet another laptop running the same Windows version will work fine. If you find yourself unable to complete the installation or connect the hardware as shown below after a few tries, switch to another laptop or do a fresh install of Windows. Installation procedure that worked for me: [ Obviously refer to the installation guides / videos for detailed instructions.] • Disable Windows Firewall and Anti Virus.
• Install drivers for your USB-OBD cable and USB-serial adapter, making sure it is set as port COM1. • Install / update INPA / EDIABAS, using ADS interface, not OBD. • Change environment path in Windows to c:/ediabas/bin.
• Install ADS Setup. • Install OBD setup. • Edit ediabas.ini, change remote-host and port. • Install VM Ware [version 5.5 or higher]. • Edit VM Ware network bridge in network editor. • Set up the new virtual machine with ethernet set to the network bridge. • Install Diag Head Emulator.
• Install easy_DIS and the DIS programs. • Load DIS, open/run Diag Head and open IFHsrv32.exe. • In DIS, enter Administration > Calibrating Touch Shield, change the processes to off and make sure it passes the API test. • Enter Administration > Diagnostic Head, click on the IP-address / computer-name and click the OK button. • Enter Administration > Connection Setup, click on the IP-address / computer-name and click Connecting.
Once connected the IP-address should appear in the bottom right and both sets of lights are lit up. • Go back into Administration > Calibrating Touch Shield, set the vm process back to off and change translator to Fister. • Edit ediabas.ini again, changing the interface to STD:OBD instead of ADS.
• If you have access to more than one laptop, try installing DIS again on one of them, rather than wasting days on a problematic install. Some just don't want to work with virtual networking, but will probably work first time on another, similar laptop. [ Reformatting the HDD and doing a fresh install of Windows XP SP2 may also fix the problem on a machine that will just not play ball.] • If API-test fails - Check ediabas.ini has the right remote-host and port set / check VM network settings / try out this fix by changing addresses in Unix itself [] / ensure firewall is off and re-install DIS. • If API-test passes, but DIS does not communicate - Check INPA is communicating and reboot DIS / check ediabas.ini has interface set to STD:OBD / check USB-serial port is set as COM1. • DIS ERROR 200.19 - Battery is below 12v, connect a float-charger / check IP address is right for Diagnostic Head in DIS, Admin / check API-test passes. • INPA ERROR IFS-0009 - Ensure USB-serial port is set as COM1 / check ediabas.ini has interface set to STD:OBD / make sure cable is working and fuse 25 has not blown. At first, I was extremely happy to find this page.