Making sense of INPA, EDIABAS, NCSExpert, NCS Dummies, DIS/GT1, EasyDIS, & Progman

Does anyone do this under linux? Does that eliminate any of the problems with the windows/vmware stuff? Is installing inpa/edabas any different? Which flavor? Ubuntu? Fedora, Red Hat? Suse? Others?

Seems to me, if you're going to install this on a dedicated laptop for that purpose anyways, why wouldn't you?

Originally Posted by mrshort77

Does anyone do this under linux? Does that eliminate any of the problems with the windows/vmware stuff? Is installing inpa/edabas any different? Which flavor? Ubuntu? Fedora, Red Hat? Suse? Others?

Seems to me, if you're going to install this on a dedicated laptop for that purpose anyways, why wouldn't you?

None will run in linux outside of a virtual machine.

INPA, NCS Expert, and WinFKP are Windows programs, run best in XP.

DIS is programmed in SCO UNIX.

SSS/Progman is a Windows XP Embedded system.

DIS may work in Linux but not without extensive modification. The hardware emulation, as it is used by everyone right now, involves using EDIABAS in Windows as a bridge between the software and the interface cable. A dedicated Linux box will not satisfy this unless you were to change it to your needs.

Jeffstri, Quick99si,

That is pretty much what I thought, but I just thought it was a good question to ask. Given the problems I have been having with VMware and all.

Just out of curiosity, will any older versions of VMware, like 5 work? That one is pretty inexpensive on ebay...

Originally Posted by mrshort77

Jeffstri, Quick99si,

That is pretty much what I thought, but I just thought it was a good question to ask. Given the problems I have been having with VMware and all.

Just out of curiosity, will any older versions of VMware, like 5 work? That one is pretty inexpensive on ebay...

I have EasyDIS and Progman working with the free VMware Player from VMware's site.
The attached JPGs show the network settings required. These can be adjusted using vmnetcfg.exe which is included with Player. Found in
C:\Program Files\VMware\VMware Player
after Player install.

As mentioned several times in this thread, make sure that you have INPA working before trying to install EasyDIS &/or Progman, i.e. your OBD plug is functioning & talking to the car.

Regards
RDL

Thanks,
I will give the VMware player a shot. It might be good to update the VMware section of the first post too.

Originally Posted by mrshort77

Thanks,
I will give the VMware player a shot. It might be good to update the VMware section of the first post too.

It (belatedly) occurs that I may be able to help somewhat more. It seems that VMware Player stores everything it needs in a set of files, maybe. See the attached JPG for my directory. Perhaps one could:
1 download my set of files
2 install VMware Player
3 set up VMnet settings with vmnetcfg.exe
4 use Player to run a virtual machine from my files
EasyDIS might just start up without any of the installation agony.

Or, perhaps someone knows in advance if this approach will work - yes or no? There may be machine specific setting that I'm oblivious to - oops, Bluebee may be watching - to which I am oblivious. Probably yes, or others would have been uploading "installed" file sets already.

Now for the snag. I have zero experience uploading large files. I have BitTorrent but only ever downloaded; never made a link to start an upload. Don't have an account at a file server such as 4Shared. Not aware of other options. (When I need to transfer large files I use a USB key - the modern version sneaker net)

If someone provides detailed, step by step instructions, I'm willing to make the attempt. If all works and EasyDIS starts up for someone - great. If not, only a little time lost.

FYI, the RAR archive for my ~4GB EasyDIS directory is 691 MB (724,682,924)

Regards
RDL

@RDL,
That is an interesting idea. The info about vmware player says it will run virtual machines created elsewhere, however, it looks as though you are running DIS 57 and Progman. I was planning on the DIS 44 route, as I dont have the disk space to run Progman, and I am still trying to keep it (relatively) simple.

I am wondering though, I created the virtual machine using VMware workstation (it did let me do that, just not start it). I am wondering if I could just use it instead of creating a whole new one using VMware player.

This just gets better all the time...

Originally Posted by mrshort77

@RDL,
That is an interesting idea. The info about vmware player says it will run virtual machines created elsewhere, however, it looks as though you are running DIS 57 and Progman. I was planning on the DIS 44 route, as I dont have the disk space to run Progman, and I am still trying to keep it (relatively) simple.

I am wondering though, I created the virtual machine using VMware workstation (it did let me do that, just not start it). I am wondering if I could just use it instead of creating a whole new one using VMware player.

This just gets better all the time...

I have EasyDIS (which I put in a file set labeled GT1 - to my regret), Progman & DIS V57 all installed and running. I pick which to use from the Player menu. So, what you see listed in directory GT1 is in fact EasyDIS, i.e. V44. Also the one in the RAR archive I described.

I then copied the V44 directory, as a separate directory/file set, and upgraded it to V57 with more recent car files which does diagnostics only. Mostly to see if there was any difference in diagnostics for my E39 - none that I've observed. V57 is about 5GB on disc.

Progman is 22 GB on disc.

Regards
RDL

RDL, do you know how to use FTP? I should be able to free up some space where you can upload the 700mb file for others to test, including myself. I've seen full hdd images floating around, though they were for T30 laptops, but never such (relatively small) vm images.

Originally Posted by Quick99Si

RDL, do you know how to use FTP? I should be able to free up some space where you can upload the 700mb file for others to test, including myself. I've seen full hdd images floating around, though they were for T30 laptops, but never such (relatively small) vm images.

FTP - that brings back memories. And gopher, telnet, whatis, etc. But it's been ages.

I don't have an FTP program installed at the moment. But I could follow the IE procedure described in the attached JPG image. Does that work for you?
Send me an address (& p/w if you wish) I'll give it a shot.

I'll try other suggestions if they suit you better.

Regards
RDL

OK, guys, I really do appreciate all the help and info, etc. But, the first post lists a 40gb HD to do the inpa/ediabas, with EasyDIS44. That looked like an OK option to me. To go the extra distance and do the Progman thing, it calls for an additional 100gb. So, now, RDL is talking 5gb for DIS V57, which may make sense, since the coding/programming stuff isnt there in that version. But the 22gb for Progman is a long way off of what I was expecting.

Am I missing something here?

-- and the plot sickens....

Really, I am having fun, honest...

Originally Posted by mrshort77

OK, guys, I really do appreciate all the help and info, etc. But, the first post lists a 40gb HD to do the inpa/ediabas, with EasyDIS44. That looked like an OK option to me. To go the extra distance and do the Progman thing, it calls for an additional 100gb. So, now, RDL is talking 5gb for DIS V57, which may make sense, since the coding/programming stuff isnt there in that version. But the 22gb for Progman is a long way off of what I was expecting.

Am I missing something here?

-- and the plot sickens....

Really, I am having fun, honest...

It is 4 GB for EasyDIS V44 giving you diagnostics, coding and programming. EDIABAS & INPA combined are 0.25 GB. VMware Player another 0.25 GB. So call it 5 GB total.

I think the 40 GB was a result of original DIS versions being installed on computers with 40 GB drives. So the hackers set up virtual machines with 40 GB pre-allocated to avoid any size problems. But I've found that EasyDIS / Player is quite happy with dynamic sizing which works out to 4 GB for EasyDIS.

I've said in earlier posts that Progman is not worth the time & effort for E39s, at least in my opinion. And it does take a lot more space.
V57 maybe; it is a simple upgrade to do once V44 is running, but I haven't seen the benefit, at least so far. And you lose coding and programming functionality unless you keep a separate copy of V44.

Your choice of course, but it's 5 GB not 100 +. And that gives you the same capability the dealers had until the mid to late 2000's.

Hope this clarifies the matter of drive space you need.

Regards
RDL

Need your help guys! Trying to install progman and am stuck at the part were the instructions say to open regedit and load hive then point to z:\ drive.



As you can see, my regeditor can not see the z: drive. What am I doing wrong? Any help or advice in solving the problem would be greatly appreciated.

PS. This maybe a stupid question but here goes. Since i have the available hard drive space and more to install Progman, why not install a cracked WINDOWS XP PRO full version in VMWare and once done install Progman the normal way? Is it even possible? I do see a installation file on the installation DVD.

Originally Posted by rdl

It is 4 GB for EasyDIS V44 giving you diagnostics, coding and programming. EDIABAS & INPA combined are 0.25 GB. VMware Player another 0.25 GB. So call it 5 GB total.

I think the 40 GB was a result of original DIS versions being installed on computers with 40 GB drives. So the hackers set up virtual machines with 40 GB pre-allocated to avoid any size problems. But I've found that EasyDIS / Player is quite happy with dynamic sizing which works out to 4 GB for EasyDIS.

I've said in earlier posts that Progman is not worth the time & effort for E39s, at least in my opinion. And it does take a lot more space.
V57 maybe; it is a simple upgrade to do once V44 is running, but I haven't seen the benefit, at least so far. And you lose coding and programming functionality unless you keep a separate copy of V44.

Your choice of course, but it's 5 GB not 100 +. And that gives you the same capability the dealers had until the mid to late 2000's.

Hope this clarifies the matter of drive space you need.

Regards
RDL

I will echo what RDL posted above. Further, Progman does not actually use the full 80gb once installed. However, the installation package calls for ~80gb of free space and will not proceed until the space is available. As mentioned, this may not be worth the effort unless you have a need to code new modules, which is why we are concentrating on INPA/DIS for the time being. I can tell you right now that INPA will likely be your tool of choice for most things.

Also keep in mind that RDL's 5gb estimate doesn't include the hdd space use by the OS, paging file, etc.. so if you're putting a laptop together, always opt for the larger drive if you have the means.

Originally Posted by jayster0966

Need your help guys! Trying to install progman and am stuck at the part were the instructions say to open regedit and load hive then point to z:\ drive.



As you can see, my regeditor can not see the z: drive. What am I doing wrong? Any help or advice in solving the problem would be greatly appreciated.

Make sure you've done the following:

Stop the VMware server.
Double-click the VM hard drive
Select Utilities > Map
Select the first partition, uncheck read-only and press Ok.

From: http://forums.bimmerforums.com/forum....php?t=1401774

Those steps basically map the virtual machine OS to the Z: drive on your laptop so that you can manipulate the registry hive.

For those trying the EasyDIS image from Quick99Si site

1 the VMware Player settings that are working on my computer can be seen in the attached images.

2 you must set VM network settings as described in post #105 above before starting the virtual machine

Good luck

Originally Posted by Quick99Si

Progman may not be worth the effort unless you have a need to code new modules, which is why we are concentrating on INPA/DIS for the time being.

I must commend RDL & Quick99Si for the wonderful expert advice they're dispensing (as this thread is currently far beyond my capabilities).

However, I do have one small question:

To those installing Progman: Why?

Q: Why do you feel you need to install progman?

(As mentioned many times, it just might not be worth it's effort.)

OK, I tried to install VMware player on my dell D600. It would not install with an error saying that my computer did not have certain features necessary. So I started going back in the versions from 4.0, backwards. The older versions gave me more specific messages, like exactly what CPU instruction was necessary, like CMOV, etc. When I got to 2.5, it finally installed. But it doesn't look like 2.5 will create a virtual machine, it will only run them or an "appliance" if you already have one.

Which version of VMware player works? I might try RDL's image, but I only have a 40Mb HD, so I am not sure how if that will work well.

For that matter, what versions of the VMware workstation might work? Are these untested? I hate to think I bought a computer that is just short of being able to do all this stuff.

Originally Posted by mrshort77

OK, I tried to install VMware player on my dell D600. It would not install with an error saying that my computer did not have certain features necessary. So I started going back in the versions from 4.0, backwards. The older versions gave me more specific messages, like exactly what CPU instruction was necessary, like CMOV, etc. When I got to 2.5, it finally installed. But it doesn't look like 2.5 will create a virtual machine, it will only run them or an "appliance" if you already have one.

Which version of VMware player works? I might try RDL's image, but I only have a 40Mb HD, so I am not sure how if that will work well.

For that matter, what versions of the VMware workstation might work? Are these untested? I hate to think I bought a computer that is just short of being able to do all this stuff.

I'm using all the software that came with Randomy's package. I purchased a Dell D610 to use with the software but I did have to upgrade the ram to 2gigs and the hard drive to 120gigs. All and all the computer and the upgrades costs all together about $150. Once upgraded all the software provided installed correctly with no errors, except for progman. Still working on that one. Allthough, INPA and DIS are all you need to really diagnose the vehicle. Answer to your question ; using VMWare workstation 6.0.2.

Hi, above you said:

5th INPA 5.0.2 update

INPA 5.0.2 update (480MB): http://quick99si3.home.comcast.net/b...02_Updated.rar
Warning: It is unknown as yet whether this upgrade will work with the E39 (needs to be tested & reported back by someone).
This probably isn't worth the risk & effort to install.


This version is customized by me and works ok on E39 ...
So, the last one looks like in the picture attached (1.5 Gb)
In addition, now and DIS with the full working TIS and more.... (Not installed by me...only updated)

I will upload all these goods in my 4 shared very soon.

BTW: original archieve logo was replaced ))

Originally Posted by djdeeablo

This version is customized by me and works ok on E39 ...

Thanks for confirming that.

Originally Posted by djdeeablo

I will upload all these goods in my 4 shared very soon.

I'll change the first post once you get a link up so that others aren't confused.

Just let me know what the resultant links are ... (thanks)

Thanks
I will upload only the "Step 3" because this one is relevant ...the rest, you guys have them already. Just follow step1, step2 and ...this one.. Take all, unarchieve and finally you will get the righ one.

Here is the link:
http://www.4shared.com/dir/Mkx2DmQf/BLUEBEE.html

The magic word is INPA

Originally Posted by djdeeablo

I will upload only the "Step 3" because this one is relevant

Drat. The two-month period for updating the first post has expired (we opened it on 08-12-2011 and edited it over a hundred times before it closed on us on 10-12-2011, less than a week ago).

So, the interested user will have to, unfortunately, read forward to find the update.

Thank you very much for your information about it working well on the E39 (that was our biggest concern), and for making it available to the tribe!

It's people like you (and Quick99Si & RDL in particular for this thread) who make this forum work for the rest of us!

Much appreciated and thanks for nice words.