Windows 7/Newer laptop ok? GT1...

[E39 Prototype]

Or am I setting my self up already... couldn't find any clear info on it.

Here is what i got going on:

GT1 v.44 torrent downloading.
VMware Downloading ( or do I need this with 7?)
Cables, should I get the good carsoft v6.5 posted in this forum?

And.. is there anything else I should know, plan on following randomy's or the ones on the 4shared site instructions...

Or, is this all a waist of time. haha.

Sorry, I like to ask questions before I do things like this.

[champaign777]

not easy but possible ... kind of 50/50 haha
have fun

[E39 Prototype]

First problem: deaman tools wont work with windows 7, but poweriso does.

GT1 torrent, when you try to extract files, its saying it needs some sort of password.

any ideas.

[Snowcatxx87]

daemon tools works on windows 7.

Do yourself a favour, create an XP partition. 100% easier.

[existsec]

I've had no problems using Windows 7 for all of this. Technically daemon tools isn't even needed. VMWare can mount disc images without help from another application. Unfortunately, a couple of the images out there are .nrg instead of the standard .iso. I just converted it and used VMWare to mount the .iso when needed.

As for Windows 7, there's no reason to go out of your way and create an XP partition. Everything seems to work just fine and I doubt it could get 100% easier using XP. Shoot, INPA almost seems to be fine running under Linux using Wine.

[Snowcatxx87]

Windows 7 doesn't run EDIABAS or IFHSERV..

Unless you ran those in VMWARE

It was so easy creating an XP machine and a lot less headaches.

[existsec]

Windows 7 doesn't run EDIABAS or IFHSERV..

Unless you ran those in VMWARE

It was so easy creating an XP machine and a lot less headaches.

Try again, I haven't had any problems and I know at least one other person that hasn't either. Keeping it simple means a lot less headaches.

[Robstah]

Windows 7 doesn't run EDIABAS or IFHSERV..

Unless you ran those in VMWARE

It was so easy creating an XP machine and a lot less headaches.

The only reason you may have issues with this is if you are running a 64 bit version of Windows 7. If I remember right, the older versions of EDIABAS and IFHSERV were in 16 bit, which 16 bit support has been removed from Windows X64 versions. Your best bet is to find a newer version of EDIABAS tools (version 7 and up *I think* are 32 bit), or run everything in a vmware instance.

[B33rM3]

existsec and Robstah are both correct...

I am running GT1 EasyDIS V44 with INPA from ediabas6.4.3.full on Windows 7 (using a cheap Hong Kong usb-->serial-->OBD-->ADS EDIABAS cable). Both INPA and GT1 are performing diagnostics on my 99 M3 fine. Havent got coding/programming working yet but I think it may be due to an incomplete NCS install. Yet NFS throws a activeX error and bombs at boot which may be a Win7 issue ,but I think it's most likely a incomplete install since NCS Expert is running but seems to be missing profiles. I just installed and connected them today and it will probably take some time to work out the kinks.

There is a lot of misinformation on all of this and all the good stuff seems to be buried and/or hidden.

A few things I learned on my journey today about Win7-EASYDISV44GT1-VMWare WS7.x-INPA cable setup: These things are causing much confusion in these boards.

* Set up and test INPA first. The trick here is to create a obd.ini file with the correct Com port (most likely Com4 for usb-to-serial devices) and put it in the C:\Windows directory (not needed anywhere else). You don't need to be changing the Com port of the usb-serial adapter to com 1 either.

* Using the shoulders EASYDIS guide you don't need to mount the iso with deamon tools (just as existsec said). Just use the iso as the setup media as you do a customized new VM setup.

* You don't need 3 network interfaces with three IPs. Just use VMnet1 (host-only)and set it to the 192.168.68.x subnet using the VMware virtual network editor under the Edit menu of VMWare workstation. Bridging on wired/wireless/loopback interfaces is not necessary and would be a major PITA to allways be changing.

* If you did not set the iso as the install disc for the VMware setup or need to boot from cd you do not need to try to catch to bios post screen. You can simply use VM, Power, Power on to Bios in VMware.

*Use the on screen keyboard as most parts of GT1 do not use a convientional keyboard.

*After initial base install, you can properly shut down GT1 through Administration, Calibrating touch screen , Shut Down DIS. Systems don't like a power off without a proper shut down.

*After the first shutdown you can just change the CD media to the the application disc and agian not have to use deamon tools.

*After base and DIS installs are comple go to Calibrating touch screen (this part does use a keyboard), #3 Configure Protocol Translator, #3 Change translator to FISTER. #9 Exit. Then #7 SCOADMIN NETWORK and remove the AMD PCNet adapter. Then Add Lan adapter and configure TCPIP with host name = gt1ap, IP Address 192.168.68.30, and use default filled in remaining fields. Then exit scoadmin network. After a reboot you should now be able to ping your VM. After a reboot you need to go back to the protocol translator configure screen and run #1 Restart EDIABAS for the changes to be reflected in Ediabas.

* to get out of GT1 and access root in VMware; hold ctrl-alt while tapping spacebar then F1. ctrl-alt by itself is used for letting go of the mouse in VMware. login using root

* it doesnt seem you need to change the port on your windows ediabas.ini and your /etc/ediabas.ini just change the port on the GT1 install vm to match the port on your windows ediabas.ini (mine was 3000) and change the RemoteHost to 192.168.68.1 on your windows ediabas.ini

* you need to run both ifhsrv32 (from NCS/INPA), and diaghead (and start the diaghead connection in the app) Diaghead is a seperate download from NCS/INPA/etc..


I don't understand why information about all of this is so buried, hidden, and locked down...

[David Mc]

E39 try
www.openbmw.org for the torrent password.

B33rM3 the info you have given is great. I don't think that it is a case of it being deliberately hidden, but the wide variety of OS and interfaces in use certainly makes it difficult to find.

It would be far easier if when asking questions, members stated whether they are using conventional or EasyDIS, the type of interface, OS and model of vehicle they are attempting to set up for so that the mods could work on setting up a system of indexed stickies with setup instructions.

[B33rM3]

E39,

VMware is needed. You could accomplish it with one of the other virtualization packages, but it is hard to beat VMware, they are the leaders in virtualiztion since they created the market. That really boils down to being the easiest to use. If you decided another VM package, it would be tough to get help with your install since it doesn't seem that anyone else on the boards has been using anything else.

Your cable slection depends on what you want to spend, what you want to run, and how much you want to tweak with getting it going.

If you dont care about running carsoft and would rather spend some dollars than tweak with using a virtual diaghead,ifsrv32 etc then a true yellow diag head would be an option (but many here have stated problems with reliability and functionality of the chinese knock offs of these).

If you want a low cost option versatile option then the INPA-EDIABAS cables are a good choice. They do require a serial port or usb-to-serial adapter and will have to run ifserver and diaghead in windows to run DIS.

If you don't want to mess with serial adaptions then the Vagcom KKL is a good option.

I don't know much about the carsoft cables but I am guessing that the the benefit is that you can run carsoft also

You are probably going to need to add ediabas and diaghead to your download list too.

If you like computers, like your car, don't like paying someone else to have their computer do work, and like to tinker, Its worth it =-)

Good luck E39...


Thanks David...

I agree for the most part it's not intentionally hidden, and the multitude of variance in the installs is confusing, yet with bmwecu.org being locked down, and a few thread of people speaking of things not working without the secret blahblahblah while giving out the info, or others not helping without wanting some SW in return is all very frustrating and dissapointing to see.

Hopefully we can all work together and sort all this out. Indexed stickes would be great. Breaking down the diagnostic section into sub sections would probably be helpfull too. Such as General, NCS, GT1, Carsoft, Cabling, OBD, etc would be helpfull to organize the content.

[Snowcatxx87]

I am on windows 7 ultimate 64-bit, perhaps I should of made myself clearer.

(and who gets 7 in 32? lol)

[B33rM3]

Snowcat... (who gets 7 in 32?) Those who would only run windows to run these software packages. As soon as I can make diaghead and ifserv32 run in linux under wine (or make a python alternative) the windows partition is probably coming back off. Plus as a really early adopter of 64 bit who has worked in IT for over 15 years, 64 bit can be a major PITA (from years of fighting with the likes of java, flash, codecs, etc...) it isn't always a plus. Basically if you don't need the RAM (or don't use 64 bit games/graphics/video software) its generally not worth it yet.

[Robstah]

Snowcat... (who gets 7 in 32?) Those who would only run windows to run these software packages. As soon as I can make diaghead and ifserv32 run in linux under wine (or make a python alternative) the windows partition is probably coming back off. Plus as a really early adopter of 64 bit who has worked in IT for over 15 years, 64 bit can be a major PITA (from years of fighting with the likes of java, flash, codecs, etc...) it isn't always a plus. Basically if you don't need the RAM (or don't use 64 bit games/graphics/video software) its generally not worth it yet.

Nah. He has a great point. 64 bit is the future. The harder we push it in that direction the quicker people will adapt. Plus, you will always have things like vmware and "XP mode" to bring you back to the stone ages. As for you running things under wine, good luck. I used to do things like that all the time and found out how much of a waste of life it is to achieve such things. It's not worth the headache and invested time to do things like that, trust me.

Snowcatxx87, try finding a setup with EDIABAS 7. The tools should be in 32 bit and should work. The only thing you lose is OBDI compatibility, so if you are mainly looking at OBDI stuff, I would recommend setting up a vmware instance instead.

[B33rM3]

I agree that 64 bit is the future and have been trying to help push it along. Just saying it can cometimes be a PITA, and not always the right choice. Sometimes 32 bit is a better fit (for now).

Running under wine goals are more for having a wider toolset to troubleshoot and inspect the communications and possible integrating some functionality into a carputer. But yeah I also agree that wine is another PITA and do usually try to avoid it.

[Snowcatxx87]

Exactly. The most common thing I hear is "it won't work with 32, drivers, etc". Common, it's not like that at all, and if you do have problem with hardware, time to upgrade.

64 is the future, hop on or get left behind.

I'm using 6.X for EDIABAS, not sure if I want to hop on to 7 due to e46's being "old" cars now.

[Phatfred]

B33rM3 (http://forums.bimmerforums.com/forum/member.php?u=250407) Do you have any info on how these programs may work on a carputer? I am just now researching software and how it works with the car with the hopes of in the next year really grasping the software and runnning it from a carputer in my 95 M3.

[mystert]

So i got everything to work fine and hook up to my car on my craptop T23, too but the screen resolution isnt big enough to see the entire dis screen, so i figured id install it on my new dell with windows 7. Ive got the whole thing working on there too. When i go to run my Diaghead emulator on Windows 7, it keeps telling me-

Unhandled exception has occured in your application.....Access to the registry key..... for DiagHeadEmul is denied.

The program still opens, and connects CMD_MT_FREE. In DIS i was able to get everything going, API test passed, and in the Config/diagnostic head i was able to see it and select it. In Admin/connection setup, i can see it and i try to connect to it but it doesnt respont. Both sets of lights on the top of the screen are lit up correctly.

Like i said before, got the same exact setup working with WinXP w/Vmware 5 on my IBM T23, and have it 90% on my Win7 w/Vmware 6.5.

Have any ideas what up? Thanks for all the help so far

[evotronix]

Just to chime in:
I got INPA and DIS 44 (everything from DavidMC's 4shared) running on Win 7 ultimate 64 bit. Passed API test, not using diaghead emulator, basically I followed David MC's instructions, so it works.
Well, sort of, since I don't have the right interface and I haven't connected to the car yet...I also have TIS running and it runs good, I can get all the info I need, and the menus in DIS seem fully functional.

[mystert]

I searched for the direction on how to NOT use the diaghead, can you post a link to them???

Thanks

[David Mc]

Simple, trash the diaghead emulator, and from the "calibrating touch screen" button in the Administration section of DIS, set the translator to "FISTER", Configure protocol settings so that vm is set to not run, save the changes and restart EDIABAS. You will not have any pretty coloured signal strength bars on the DIS main screen anymore, but you will not need to use a diaghead emulator either.
If you cannot see the full main screen of DIS, just left click inside the screen, hold down CTRL+ALT and hit the ENTER key.

[mystert]

Thats easy enough! Ill try it when i get home today. Thanks

[NikolaiD]

On the original topic in my experience everything works on Win 7.
BUT on Win 7 x64 you cannot run NCS Expert.

[mystert]

I got the thing working without the diaghead emulator. now to get SSS installed....... l

[mystert]

Carsoft 6.5 doesnt work with 64bit Windows 7, or so my computer is telling me. Ive got SSS working, and DISv57 to pass the API test. On my old laptop, that wont run SSS because its too slow, I needed Carsoft to initialize the serial port to get the data flowing. If I cannot install Carsoft 6.5 onto my Windows 7 laptop, how do I get the port initialized?

[Snowcatxx87]

I installed a partition and ran Win XP for all my BMW stuff, but I use an EDIABAS cable, not carsoft.

[IcemanBHE]

If you going to use the Carsoft interface...you need Carsoft to initialize it....

[mystert]

So I got my EDIABAS cable from china finally, and YES, it is possibe to get GT1/DIS to run in VMWare 6.5 in windows 7! Using the ediabas cable i was able to see the vehicle voltage and auto-identify the vehicle. One thing I learned was that you need to run the ifhsrv32.exe and diaghead emulator (if using it) in administrator mode. You need to right click and click run as administrator.

[Robstah]

I don't get you guys. VMware "emulates" a full running computer. Of course you will get things working like that. The only problem is the link created between the guest PC (your VMware instance) and the host PC (your actual PC). IFHSRV is used as a network passthrough (your guest PC talks to your host PC over a virtual network) and IFHSRV talks to your interface which is connected physically to the host PC. VMware removes any compatibility issues because it is like running an "actual computer", BIOS and all.

[champaign777]

Robstah
maybe you can answer why we need 3 Network adapters in VMware to work with Easy DIS GT1 ?

[MaikelK]

Is there a posibility in running Carsoft on Windows 7 64bit?
Or how do i have to make the connection between a VMware XP machine with Carsoft and the VMware XP to the GT1 machine?

Is that possible? I got GT1 up and running in a VMware machine in Windows 7 64bit with API test passing!

[chris98891]

A bump for this! I have INPA and NCS Expert running perfectly on a windows 7 64bit laptop using the Belkin F5U409 USB to Serial (com1) and ebay INPA cables. I had to install them in an XP virtual machine on VMware, as my 64bit laptop wouldn't recognize the F5U409.

Now, since i can get it to connect to an xp virtual machine in VMware even though my laptop doesn't recognize it, can I get it to connect to EasyDIS in VMware without my laptop recognizing the cables? I would really rather not install an XP partition...it'd really be a waste of time/space since I already have it running on VMware and anything that I need to run can run in there.

I already have GT1 installed according to the guides. I'm running VMware 7.1.2

[randomdude]

I got INPA and GT1 working on 7-x64 yesterday.

-Use http://www.clearchain.com/blog/posts/2010/12 for the driver on the belkin.
-Use Alcohol instead of daemon tools.
-Run everything as administrator. I can see that some of you wouldn't want to do this but I only have windows on my computer for my BMW software. I would MUCH rather just use XP but I don't have a copy that will work for more than 30 days.

I haven't tried NCSExpert yet, maybe we'll tackle that today if I get bored.

So far though, I haven't had to use xp-mode or VM for anything other than GT1.

[chris98891]

I got INPA and GT1 working on 7-x64 yesterday.

-Use http://www.clearchain.com/blog/posts/2010/12 for the driver on the belkin.
-Use Alcohol instead of daemon tools.
-Run everything as administrator. I can see that some of you wouldn't want to do this but I only have windows on my computer for my BMW software. I would MUCH rather just use XP but I don't have a copy that will work for more than 30 days.

I haven't tried NCSExpert yet, maybe we'll tackle that today if I get bored.

So far though, I haven't had to use xp-mode or VM for anything other than GT1.

God I love you. INPA was up and running instantly. So many more possibilities! Now I'm working on figuring out how to get GT1 to work, a may also install sss and progman. thank you SO much!

[randomdude]

I took a simple copy of the virtual machine with working gt1 when I had xp and ran it exactly the same on 7 in VM. It fired right up.