What are the changes Tony?

Rick

Huge success tonight with running the NM flashing software through a virtual machine. I will try to make this brief but informative.

I used a laptop running a host OS of Windows XP Home. I used VirtualBox from Sun for the virtualization. I bought a copy of Windows 7 Ultimate (home most likely?) and installed it on a virtual machine with the following attributes: Intel ethernet controler, 1GB ram, 0 video memory, 10GM disk space, USB devices enable and 2.0 support for USB enabled. Booted the machine and got it to go online and from within the virtualization I downloaded two pieces of software: the NF flasher installer, and the FTDI drivers for Windows 7. More on this last part in a bit.

My host OS already has the FTDI drivers enabled. Therefore, a serial - USB infrastructure already existed, but that did not bother the rest of the functionality. I am using an FTDI-based cable that I bought from ebay some years ago. With this cable I successfully used wbh-diag, RossTec VAG-COM and VCDS, Lemmiwinks, and the NM software on a Windows 7 native (no virtualizatiojn) on a laptop.

Once the virtual machine has booted, I plug the FTDI cable to my laptop. The WIndows XP host OS recognizes it. Then, from the VirtualBox's "Device" menu I enable USB and tied it to what appears as "USB - Serial" on the virtual box. THe virtual box will launch a virtual hardware, that is a USB-related thing I do not fully understand, but a new hardware was installed on the host OS. This required the host OS to go fetch an appropriate driver, which was unsigned from a certificate authority, and to proceed as usual with installation. Once that "hardware" was in place, I get on the virtual Windows 7 machine. This is where things get tricky. I downloaded the FTDI drivers. I used the CDM (Combined Driver Module) and unzippped the files on the virtual OS's desktop. Then, I go under "System > Device Manager" and look for the devices present. The USB-Serial is there and has no driver. Right-click on that and go to a driver installation selection from the menu. Then, tell the OS that you want to install the driver from a local location and point to the Desktop. The installation of the driver will go through. However, the USB-Serial will still be unrecognized. This means that whatever driver we installed did not do THAT JOB that we intended, but something was installed.

Launch the NM flashing software. You should be able to see that port on the right-hand-side. We are in business. Connect the FTDI cable to the car, turn the ignition, and click on the Slow Connect. It worked for me. Then I clicked on the "Read Info" and it correctly read the ECU number, etc, of my CH-box 1.8T 2001.5 A4.

Huge success! All of this worked relatively painlessly for me. If you need any help and this write-up is inadequate, do not hesitate to PM me. I am not a Windows person, but I got it to work. I will do the same on the Linux side virtualization and will report back. But I know that last part has been achieved by others on this forum.

Good work everyone. Good work Tony!

You shouldn't need to set the eBay cable to dumb mode. Can you send me the log file?

Here ya go

I have the same problem no matter what ECU I try to read (S4 or 1.8T).

The logs were from a 1.8T ECU, I tried two different ECU's on the bench both of which read out perfectly fine using Galletto.  One of the ECU's was chipped, the other stock.

The flashing software does not wait long enough for switch to programming session complete!

When the ECU switches to the programming session, it sends several times 7F 10 78
(negative response with reason requestCorrectlyReceived-responsePending).
If this is received, the tester has to reset the communication timer P2 and wait for the next message of the ecu. The ecu will repeat the responsePending every ~40ms until the final
response (positive or negative) can be sent.
For older ecus the switching to programming session takes place nearly immeadiately
(maybe 4-5x responsePending). But newer ecus take a long time for the switch to complete!
This can take approx. 4 seconds, so the tester will receive about 100 times the
responsePending before the positiveResponse comes in.
Best is to count the responsePending and stop only in case the count reaches lets say 150.

I tried this on my Golf IV 2002 which is listed in the Wiki and was not able to get past the initial connect as there was an error each time (diconnects because "tester not present").  Tried slow & fast init. as well as different baud rates.

I'm using a Ross Tech KII-usb cable (any issue there?)

Here's the log:
https://docs.google.com/leaf?id=0B2TsAlvPr7REODJlZGQ1MDgtYTlmMy00MDQzLWFjOTMtOGU4NDRmYTQ4OGEw&hl=en&authkey=COWx85oL

Thanks, Dave