Also, remove the com5 and 6 that you added, its only going to cause problems down the line

Excellent! Glad you got it sorted out.

Hey NYET,

I found this discussion http://nefariousmotorsports.com/forum/index.php?topic=4491.15 and my jaw dropped...I downloaded the program from ftdi and did a scan with command prompt and it cannot find the device, which makes me think that ultimately I may not have the proper cable for using argdub's tool. What do you think?

Here's a screen shot:

FT:>SCAN
Scanning for devices...
No devices found!
FT:>

doesnt it have to be in boot mode to write to the 95040 over OBD?

I know... I've just kept on reading on the cable issues, and by now this probably should be categorized as such. Ok, so now I just needed to know what is up with the cable; I opened the cable and found an FTDI 245BL chip in it(lead free). (Probably why I couldn't even get the cable to scan with FTPROG.)

From FTDI; discontinued are the "B" series. So, an FT232r or FT245r can be used (the 232 is a USB UART IC and the 245 is a USB FIFO IC). It seems that most people are having success with the 232R.

I tried my XP laptop for chuckles and I couldn't even get the VCP to take with the 245B, the destination folder would appear empty. Then I tried to see if the driver would load from the supplied cd and it did! thought this was version 1.6, which started me thinking that this was very old. So I tried installing the driver again from my folder and same result: even thought the files are in the folder, once I browse the folder for installation, the folder is empty( no, it's not hidden). Because of this, argdub's tool is useless since I can't assign a comport to it.

So, today I'm going to purchase another cable from "gameadvance" in Ebay, listed as a compatible cable (he/she seems to know the issues with the cables) and try again.

Man, all I want to do is disable this damn Immobiliser in the new/used ecu and get this car on the road....tuning and mod's will come later but I need to get past this first! 

All right!, success.....Ok Boys, sit back and enjoy, this is how I've finally connected.

So, I got the new cable (ft232r), I'm thinking, no prob, easy from here on.....hahaha, think again. I connected the cable to my windows 7 laptop and wala! cable found! no need to install drivers as the updated driver from FTDI was already installed. I went to the car tried connecting with the vag 409.1 and test the connection...no device found, (or something to that effect, BTW the cd that came with the cable is awesome as far as directions are concerned)  same thing if I tried argdubs tool.

Now I'm depressed, what the heck? so, I thought I should try windows xp mode, but first maybe I should remove the driver in my machine and re-install it with the cd that came with the cable...sure enough, that was the key, the vag com 409.1 connected immediately! So even thought that FTDI says that the updated drivers are the ones to use, I have a feeling that the driver in the cd is different (I haven't completely checked it out).

So now I decided that for insurance, in order to work with argdubs tool, I should download xp mode...that was also a trick! for a great work around go to http://www.tomshardware.co.uk/windows-xp-mode-windows-7-win7,news-33258.html the problem that a lot of people are having is verifying their copy of windows. Without verification, you CAN'T download it. Long story short, I was using CHROME as a browser; I decided to try it with EXPLORER as the browser, and bang! verification went through, and XP mode downloaded perfectly (mind you, I'm on a 30 day trial, which I think I can convert to permanent...more on that later).

So, I downloaded the driver to my virtual (XP mode) machine, downloaded argdubs tool and went to work. When you connect with Xp mode, you want to make sure that the USB connection is enabled on the Tab on the desktop. I was finally able to connect with argdub's tool and read both ECU's, (the stock and the replacement). So now I have both SKC's and I can either ADAPT with the vag com 409.1 or disable the Immo on the replacement ECU. I'm leaning to the disabling of the Immo, however, since I used all the available power in my remaining brain cell, could somebody let me know what the actual steps in in backing up the info and disabling? do I now use the nefmoto software or can I use argdub's tool?....I think ddillinger was saying that doing it through OBD was tedious, but possible....I just happen to be over the big hump and haven't gone to deep in the actual process for disabling the Immo. I just don't want to wipe out a perfectly good ecu. Geez, I hope this helps somebody!

Argdub for read/writing the ECU eeprom (small) to disable immo.

Nefmoto is only for flashing ECU software (the large flash) to say, flash ECU software that does not require immo (different "box").

Thanks for the reply nyet, not sure how I missed it yesterday anyway, this is where I show my inexperience with cmd....I'd like to back up the contents of my used ecu eeprom, but I don't know how to write the cmd line. Where does it save it to and or how do I retrieve it? Should I be using a redirect command to do this? ie:
>desktop\me7_95040 --OBD -r -p 3 95040.bin > C:\Users\Owners\Documents\Passat ECU

I think the way to write the cmd for the Immo off file is: >desktop\me7_95040 --bootmode -w -p 3 immodef95040  where I'm using ddilingers Immo off file. I also downloaded the Dd's immo off vlc file but I can't get that to open...

Thanks for all your input!