Newbie question regarding installation of EASYDIS v.44 onto 32bit WinXP laptop

[jcwhy]

Good Day,

I own three E34's ('90 535iM, '92 535iM, and '94 530iA) and recently took on the challenge too setup a diagnostic computer using an old model laptop running 32bit WinXP Service Pack 3. The laptop has a single-core Intel Pentium-M 7465 running at 1.8GHz with 1GB DDR SDRAM and native serial port.

I've read through numerous instructions and postings to help identify the correct hardware and software for connecting to the OBD1 diagnostic connector in the E34 engine compartment.

I purchased the TinyADS cable off Ebay (Tiny ADS Interface with diagnostic connector for BMW - INPA/DIS/EDIABAS). Seems this is the right one.

Based on what I've read, my goal is to first get EASYDIS loaded in a virtual window. First challenge was to find older versions of the software to run on 32bit WinXP. I managed to locate EASYDIS V.44 base and program ISO's. I also found a DAEMON Tools Ulta that allows mounting the ISO's as virtual drives.

The problem is VMWARE version 6.x. Can't find a version that is loadable on 32bit WinXP anywhere.

I tried getting this to work using Virtual BOX with no luck. I encounter an error during the installation of EASYDIS-base as follows:

- Harddisk partitioning failed
- Installation aborted
- Check CD and drive

Out of curiosity, I burned the EASYDIS base ISO to a CD and booted the laptop. DIS V.44 Base got fully installed (used a separate hard drive because it whips WinXP) to the point where the Diagnosis and Information System screen is displayed. Then under Administration I was able to load EASYDIS Program. Everything looked good but when I try to communicate to the TinyADS cable, it doesn't detect it. Messed about with this for a while and gave up.

The other sticking point is once I get the virtual window working with EASYDIS, what if any software is needed on the host (WinXP) side? Seems something is needed (INPA/EDIBAS?) is required to tunnel down through COM1 to the diagnostic cable using the correct protocol. Complicated stuff for someone just getting started.

So, now I'm stuck looking for a version of VMWARE that will install on 32bit WinXP. Any help?

I'm a complete newbie to BMW diagnostic software. Most of what I read on the forum/etc is for new models and software. Just looking for some guidance from experts so see if I'm on the right track.

Many thanks in advance.

[jcwhy]

Managed to find a trial version of VMWare (v 6.5) but installation fails with the following error:

“Setup failed to generate the SSL keys necessary to run VMWare Server”

Thinking to uninstall WinXP Service Pack 3. Everything I read says to use SP 2.




Sent from my iPhone using Tapatalk

[jcwhy]

No replies yet... Challenging problem to solve I guess.

Turns out CPU needs to support virtualization which Pentium does not. Switched to machine with different processor that supports the virtualization instruction set.

VMWare 6.5 now installed (required IT support from a friend to get through install errors). DIS-base and DIS-program now running in virtual window.

Instructions now say to install EDIBAS so DIS can communicate to the serial port/cable. Also need Net Framework - another challenge. Is this all required?

Hoping this is not a wasted effort.

Definitely weren't joking when they said it takes hours.






Sent from my SM-N900V using Tapatalk

[rdl]

The best, easiest way to install EDIBAS is to look for an INPA installation package. That will automatically install EDIBAS. INPA & EDIBAS run at Windows level, not inside the VM & is much easier to install, configure and prove your cable etc. is able to communicate with the car before starting a DIS install. Further INPA will do a large majority of anything DIS can. I used INPA much more often than DIS. And you'd have some immediate +ve results.

VMware Personal is VMware's free version of v6.5 - so no authentication to worry about. It lacks some v6.5 features but worked well to install EasyDIS on a Vista machine for me. I don't know where you are in overall installation and configuration, but are you aware that you must start IFHSrv32.exe at Windows level before starting DIS? It serves as a pass though for EDIBAS between Windows and the VM; unless IFHSrv32 is running, DIS won't be happy.

However, if I were you, I'd ditch EasyDIS and go to ISTA instead, which replaced DIS in the dealerships. ISTA runs as a native Windows program so configuration is much easier. I spent hours & hours over several days getting my DIS configured & running. ISTA on Windows 10 took an hour, and most of that was spent waiting for the downloaded files to decompress and copy onto the 256GB SD card I used for the install (ISTA is very large & I didn't want to give up so much space on my hard drive. A USB drive would work too. I picked an SD card so I didn't have a USB drive sticking out the side of the laptop while maneuvering it around in the car)

[jcwhy]

rdl - thanks for your reply!

You’ve inspired me to take another shot at this. I pretty much convinced myself the TinyADS cable is broken but maybe not. Asked the seller if the cable wad tested before shipment but no reply.

Much simpler if I can stay away from the VM and run everything in Windows.

Jeff






Sent from my iPhone using Tapatalk

[jcwhy]

Another follow-up question if you don’t mind.

I’ve not been able to find much information in terms of the hardware set up required to interface to the OBD1 on an E34. For whatever reason, I came to the conclusion I needed to run through a native RS-232 port and that’s the reason I purchased the TinyADS cable and loaded WinXP with EasyDIS. Maybe I’m way off here but information for the older model BMW’s is sketchy at best.

Can you provide any guidance on the hardware side? Should I give up on the TinyADS cable and take a different approach?

Many thanks.

Jeff






Sent from my iPhone using Tapatalk

[rdl]

My only experience is with my 2003 E39 which uses only the OBD II plug, no 20 pin round plug in the engine bay. And I've no experience with ADS. I vaguely recall that some platforms with the 20 pin plug need ADS, and other don't. But I'm afraid I've no idea which, when or where.

Perhaps someone else will jump in with advice for your E34.
Or you might try starting a new thread asking for advice on cables and adaptors specifically for an E34 . The key is to get INPA working to prove the connection works. Then ISTA will be a breeze - just follow installation instructions.

I don't know it this will help, but my experience was as follows.
In 2010 I bought a generic BMW compatible serial port cable which included an OBDII to 20 pin round plug adaptor, that I have never used. My 32 bit Vista laptop had no serial ports so I used a Belkin serial -> USB adaptor that folks said would work properly. The pair worked without a hitch for INPA, NCS Expert, EasyDIS and SSS on my E39.

The Vista laptop died and I bought a Win10 64bit machine. The cable and USB adaptor worked with INPA and NCS Expert. But it would sometimes lose connection or fail to find data in INPA - for instance sometimes it would fail to indicate the battery and ignition status but then find it if I simply restarted INPA. But I'd also gone to a newer version of INPA and EDIBAS with Win10 so perhaps that was the problem. Or the signaling speed was mismatched, or, or, or.

When I decided to try ISTA I bought a USB diagnostic cable with the FTDI chip, which is considered the gold standard for BMW & EDIABAS. With this cable INPA was flawless. So was ISTA, the very first time I connected to the car.

I should clarify a point in my earlier post that I should have mentioned. I never got EasyDIS or SSS working on the Win10 machine. But that wasn't a cable issue; I couldn't figure out the network settings inside the VM for EasyDIS to talk to Windows nicely. However, at one point I was considering buying an EasyDIS package with guaranteed install. I found a vendor who said he would sell it to me only reluctantly. He would assure that he would get it running ... once. But after a Win10 automatic, and impossible to stop, update it would likely stop working. And I would be on my own. He claimed that all the vendors selling EasyDIS in Win10 were selling empty promises. That's when I decided ISTA was the way to go.

[jcwhy]

I installed EDIABAS and INPA 4.4.7.

Best I can tell INPA does not support E34. There are no config files for E34 in C:\INPA\CFGDAT.

What, if any, diagnostic software works with the E34?

Seems purchasing this TinyADS cable was a waste.

Thanks all.



Sent from my iPhone using Tapatalk