Prepackaged VM machines

[LPCapital]

Nla

[Milla]

Loving this idea. Upgrading our current GT1 machine with a new laptop, got my hands on some new software too and was dreading doing the whole GT1 process again.

Thanks!

[dlighty]

This might work, 50GB free.
http://www.adrive.com/

[LPCapital]

This might work, 50GB free.
http://www.adrive.com/

I gave it a try but although the storage limit is 50GB there is a 2GB limit per file so it won't work

[BMWdriverwanted]

How is it backed up? The backed up file itself is 40gb or the drive it is stored on is 40gb? If you clone the drive (for redundant purposes) to another drive then back up the original with ghost, you can set the splits to any size you want, then compact it with RAR. That should make a 2gb split down to 1.7 or smaller and be perfect for the site.

[LPCapital]

cancel cancel

Updated the first thread with the first draft of the procedure... I'll try to have pix up at some point. Someone please try it out to ensure it works...

[LPCapital]

Everything is up... Both DIS and SSS/Progman...

[jslbmw]

Luca, thanks so much for this, it's so much easier than before.... up and running like a dream.

[LPCapital]

I'm glad it worked! Thanks for your feedback

[rondo]

Hi i set this up with the v57 as mine didnt include TIS and it runs perfectly in my vmware good job really makes it quick and easy to set up thanks...

[LPCapital]

Thanks for the feedback!!! I'm glad it works...

[BUGEE]

Thank you LPCapital - it´s so much easier.

I still have a few questions:

1. It is v57 ? because there easy dis v44 when i start it up..

2. Can I use it to encode?

As far as I know, you can not encode with v57, or ? And v57 is for cars from 2005, Is that correct? v44 is for cars by 2005 ?

3. I have a 530d e39 FL model 2001. Does it make sense or is it just there for newer cars


Excuse me my bad English and ask the many.

[LPCapital]

1. It is v57 ? because there easy dis v44 when i start it up..

It is v57. What I did I used the EasyDIS v44 and updated the program version to v57 (that's why the splash screen still says v44). The program version is what allows you to diagnose each model; You can think as the EasyDIS portion as the operating system that allows the program version of DIS to work...

2. Can I use it to encode?

As far as I know, you can not encode with v57, or ? And v57 is for cars from 2005, Is that correct? v44 is for cars by 2005 ?

3. I have a 530d e39 FL model 2001. Does it make sense or is it just there for newer cars

No, you can't: v57 does not have any coding. For that you need Progman (also available in the same prepackaged format... just add water). I have no idea what can be coded on the E39, but you can give it a try since it's just as simple...

I did find this: http://bavarianmachine.com/docs/98E46E52E53R50.pdf that mention some car & key memories that can be changed in the E39.

And thanks for the feedback!!!

[BUGEE]

It is v57. What I did I used the EasyDIS v44 and updated the program version to v57 (that's why the splash screen still says v44). The program version is what allows you to diagnose each model; You can think as the EasyDIS portion as the operating system that allows the program version of DIS to work...

Thanks for the quick Answer. I understand it.
v44 You do not have in the same prepackaged format running just as easy v57? (without update to v57)

No, you can't: v57 does not have any coding. For that you need Progman (also available in the same prepackaged format... just add water). I have no idea what can be coded on the E39, but you can give it a try since it's just as simple...

I thought Progman is for cars from 2005 and not for older cars?
At least I've read it... But ok I'll test it

I did find this: http://bavarianmachine.com/docs/98E46E52E53R50.pdf that mention some car & key memories that can be changed in the E39.

I've also found - thanks



Greetings from Germany

[LPCapital]

Thanks for the quick Answer. I understand it.
v44 You do not have in the same prepackaged format running just as easy v57?

I do not unfortunately.

I thought Progman is for cars from 2005 and not for older cars?
At least I've read it... But ok I'll test it

That's definitely not the case: my X3 is a 2004 and my Z4 is a 2003 and I use Progman on both. It doesn't mean it would work on your 2001, but for sure the 2005 you read is inaccurate. Give it a try and let me know!

[Rocla]

Installed DIS succesfully, seems to work but not yet tested in actual car.

Installed SSS, should the Progman start automaticly or do I have to start it manually?

If I start Progman manually I get the Progman screen every ~3. time and other tries lead to white screen and large "#3" or "#4" text and Vmware is halted(or Progman and can't see VMware running machine under it, alt+ctrl+del does not take affect).

Can you say what is going wrong with Progman?

Thank you very much sharing these.

[LPCapital]

Installed DIS succesfully, seems to work but not yet tested in actual car.

Installed SSS, should the Progman start automaticly or do I have to start it manually?

If I start Progman manually I get the Progman screen every ~3. time and other tries lead to white screen and large "#3" or "#4" text and Vmware is halted(or Progman and can't see VMware running machine under it, alt+ctrl+del does not take affect).

Can you say what is going wrong with Progman?

Thank you very much sharing these.

As I mentioned I did change the Progman which now manually start up by going under Start -> Programs -> Progman.

I'm not sure I completely understand what you're asking in the other point, but I was having similar odds behaviors happening when I had less RAM on my computer. The machine is setup to allocate 1GB of ram to the virtual machine and if you run short it might give you trouble.

Try to start the machine from a fresh computer restart and see if it behaves better.

[genuity]

SSS/Progman seems to be missing USB controller drivers usbui.dll I've tried giving it an XP SP3 CD but had no luck. I was going to load the FTDI drivers to use with my modded Ediabas/INPA cable. I have no serial support on my laptops.

[LPCapital]

SSS/Progman seems to be missing USB controller drivers usbui.dll I've tried giving it an XP SP3 CD but had no luck. I was going to load the FTDI drivers to use with my modded Ediabas/INPA cable. I have no serial support on my laptops.

It's strange it gives you that problem: I've used the machine on multiple computers without any problem. Did you try to point it to C:\WINDOWS\system32\drivers? I remember during the creation of the VM that there was one driver that I had to manually point to that path...

[Rocla]

I was having similar odds behaviors happening when I had less RAM on my computer.

Try to start the machine from a fresh computer restart and see if it behaves better.

Fresh start indeed helped. I quess you are right about the RAM, when the problme occurs WMware boots slowly.

[genuity]

It's strange it gives you that problem: I've used the machine on multiple computers without any problem. Did you try to point it to C:\WINDOWS\system32\drivers? I remember during the creation of the VM that there was one driver that I had to manually point to that path...

Yes I pointed it there and I have searched the entire C drive without any luck

[Thuppu]

If I start Progman manually I get the Progman screen every ~3. time and other tries lead to white screen and large "#3" or "#4" text and Vmware is halted(or Progman and can't see VMware running machine under it, alt+ctrl+del does not take affect).

Hey Rocla,

I also sometimes get that with my old Thinkpad. It seems to happen often if I start Progman(in Vmware) from suspended mode. Seems to happen also if the energy managment is set too restrictive.

[LPCapital]

Yes I pointed it there and I have searched the entire C drive without any luck

I would re-download my machines and unpack it again. You did follow precisely the instructions I gave, right? What computer and OS are you running VMPlayer on?

[genuity]

I would re-download my machines and unpack it again. You did follow precisely the instructions I gave, right? What computer and OS are you running VMPlayer on?

I tried both on both osx running fusion and ubuntu linux running workstation. When I open up the machine and look at the hardware, I see no CD-ROM drive nor USB controller. I added both prior to turning on the computer. It does not really matter when it is added but upon booting up XP it discovers the hardware and finds everything except for that it asks for usbui.dll and by default points me to C:\Windows\i386. I looked in there, looked in drivers, looked all over C but did not find that file. I also tried updating the vmware tools but that did not help.

What kind of cable are you using with your setup? Serial? I don't even see that added in the hardware settings. Are you using one of those yellow head clones?

[LPCapital]

I tried both on both osx running fusion and ubuntu linux running workstation. When I open up the machine and look at the hardware, I see no CD-ROM drive nor USB controller. I added both prior to turning on the computer. It does not really matter when it is added but upon booting up XP it discovers the hardware and finds everything except for that it asks for usbui.dll and by default points me to C:\Windows\i386. I looked in there, looked in drivers, looked all over C but did not find that file. I also tried updating the vmware tools but that did not help.

What kind of cable are you using with your setup? Serial? I don't even see that added in the hardware settings. Are you using one of those yellow head clones?

Let me take a step back.
1) this whole thing works only if the host is a Windows environment. Everything else (OSX, Linux) I don't know and I won't be able to help
2) I'm not sure why you want to add a CD and a USB in the virtual machine. The USB is never needed: the machine doesn't communicate directly to the interface, but it communicates to the host through a TCP connection - i.e. the network adapter. The CD is needed only to install stuff so since the machine is created and operational there's no need to install anything.

What you find here is what is described in several thread, just more simple. The interface used is a simple INPA/EDIABAS interface somehow connected to the computer (either directly to a serial port or through a USB-Serial adapter): but again, the virtual machine doesn't see any of that. The virtual machine communicate with the host through a network connection. IFHServer running on the host interfaces the network connection with the INPA/EDIABAS interface... I hope this helps. Sorry I can't be of much help...