Video

Thanks. M50B20NV

It's in the description. For HDD the setup and install time is around ~120min.

@@azrael3203 yes, I got it working thanks to your guide👌only need to try with the car now

It should work if everything is set as in the video. The identification process after selecting a model is faster if the PC has good specs and your car has EWS(built after 1995 or 1996 depending on model).

@@azrael3203 it’s a Dell Latitude D400 and a BMW E36 Convertible from 95

I hope it will work. The notebook you are using is below recommended specs.

XP Professional 32bit SP3 (it's something i've had in my old PC toolkit for more than a decade). You can see additional info at 13:10.

Follow the video step by step and it will work if there are no hardware issues with your PC. Make sure to use the exact software versions as shown in the video and Windows XP x32/x86bit. Good luck!

@@azrael3203 I do all step by step but regretably i obtainen a error "Control unit selected has not been found!" Maybe my home made ADS interface have a problem or try other DIS config. Anyway great video. Do you know if INPA can read errors in my car (e36 1992 325 td (DDE2 or DDE2.1 I'm not sure)) Thanks for all!

@@alexandrefisterra1720 you need to buy an ADS cable from Amazon, homemade wont work(converted from another brand for example or multibrand) and OBD2 cable converted to ADS with OBD1 adaptor also wont work. And no, INPA usually works on E36 from 1996 and up.

@@azrael3203 You're a master, i got it working with your setting, the problemas was in the homemade interface i forgot to conect one positive wire in one transistor. DIS v44 can read the errors and identify the DDE in 1992 e36 td car, and say that is a e34 m51 tds (i change the ecu so it's correct) but INPA can`t conect. Thanks for the video!!! MASTER

No. You need the ediabas and ifhsrv to make the VM communicate with the DME through Windows device management. The system is based on Unix. You would need a special device on which to install it and use it. This software is made for a dealership device not a regular PC. Feel free to experiment but this is a old software and doesnt support common PC hardware. You can see that the UI is made for a touchscreen and the device was most likely built specifically for BMW following certain system requirements. The device which had this OS was probably built by BOSCH or Siemens when it was made and was available just for dealerships and end-of-line(when car is completely assembled) changes and checks.

@@azrael3203 okay thanks for the reply. I tried installing it with the vm ware following your instructions on my Windows 7 32 bit laptop since i already use Inpa with ADS on the device and dont wont to change the operating system but after the restart DIS won't start, there is just a blackscreen after the text at 25:49 in your video. Have you ever installed it on a WIN7 device? Do you have any idea, what could be wrong? I am currently starting from the beginning...

@@pascalschutt3201 Yes, i have tried installing on a secondary W7 PC to have a backup. It doesnt work on W7. I bought a secondary 128gb SSD just for DIS to swap the main SSD with the DIS one . That's the best workaround. Also, the PC should fully support Windows XP, which means a PC config that's not newer than 2011-2012. I made multiple builds until i managed to make everything work as it should. Maybe there are other workarounds but i got tired after 3 weeks of building PCs, debugging, setting everything and checking if it works.

@@azrael3203i got it Running ob my Win 7 32 Bit Laptop. Testet it with my m52 e36 and a M50 E34 with MS40.1 since that wasn‘t working properly with Inpa. Still have Problems with the airbag module tho but I have also read, that the one used in my E34 cant be diagnosed since all components are in the Steering Wheel.

@@azrael3203 Connection only works every 5th try or so, with everything I click in the administration menu (System or calibrating touchscreen) or if i click diagnose I get the hourglass logo and nothing happens. Do you know a solution or is it maybe because of W7?

Haven't used it for coding. My car still has the same factory options. It should work but i am not entirely sure how to do it since i didn't need it. I used it only for reading faults and reading live data. But then again, it should work for coding too.

There are a lot of possible causes including that DIS doesnt like your computer configuration. You need to check if your ADS interface is available in DIS and do a connection test in DIS. Other than that: - set Signal power in DiagHead to 100% - launch ifhsrv as administrator prior to launching VmWare and also make sure that ediabas.bin has the correct ip adresses written - make sure that in DIS you have Fister set as Translator (21:25) - make sure you have all DIS services set correctly (21:03) - your computer(windows) has reserved COM1 for other applications (common issue for most computers) and in that case i just used another PC - make sure that the COM ports are enabled in BIOS and are correctly configured for baud rate and bits, and COM1 is not reserved (some BIOS versions let you select COM1 as user default instead of letting Windows manage it) There is a lot of debugging to be done. That is why i said in the description that it does not work on all configs since i had a lot of issues with different configs that i had built. Eventually i made it work on 2 configs out of 5. If you can, use another PC, install everything step by step using this video and see if you have the same issue. I can understand the frustration, it took me 4 weeks of trial and error to make it work and find all the resources that i needed, build mutiple PC’s and see what works and what doesn’t.

That's not a problem. There are no errors stored on DME (if there were any errors you should see them in Read fault memory) . I guess 131ms is the default value for an M50 NV that's IDLE; my engine runs perfectly.

Open diff. If i wanted to look ridiculous i would dress up as a clown. Thx.

@@azrael3203agree, why can't just enjoy driving a classic e36 in the rain

wet asphalt + high rpm + sudden gear change. it's not rwd, that's how fwd cars act in those situations due to losing traction and gaining it fast...