Idiots guide to IDS

[Danbrad]

Hi all.....I'm having a problem doing a native install of Ford IDS v110. After going through all steps and i try to load it i get the message "waiting for windows network services".
Does anyone know how i can overcome this, i have set the date and done a restore but still getting it. Perhaps someone can help me through remote access. Unless there is an easy fix.
Thanks in advance
Dan

[Danbrad]

Just an update, I managed to start Ford IDS. I had to go into services and start detection manager automartically as it was stopped. Now i have a different problem, When the program loads i get a tab-man error.
I have tried compatibility mode but still the same. i have Ford IDS 106 in vmware but would love this as native install if anyone can help.
Regards
Dan

[loot]

I don't think ids likes w10 and so w7 vmware might be better. If you have a decent laptop you shouldn't need to worry about vm. Plus vm removes all traces when you reset.

I'm still on v96 vmware so what do I know though

[Danbrad]

All sorted now. Did a fresh install and all up and running.
Thanks for the input loot.
Regards
Dan

[loot]

Fez install is recommended after any failed install.

So is yours native? What os and how are you freezing it?

[Danbrad]

It is a native install on v110 with windows 7 64bit. what do you mean freezing it?
Why do i need to freeze it? Is it because of the updates?
Regards
Dan

[loot]

Ids needs a licence and it was cracked on v86 but then v91 it went to a 3 day trial so we used freeze programs to stop the date going forward. I have v96 on vmware and a special patch that turns my time and date back when starting vm.

Unless there's a new method I suspect in a few days you'll be locked out?

[Danbrad]

Thanks for the info, I guess i'll find out tomorrow then. If thats the case then vmware it is. is it runasdate you use or something else?
Regards
Dan

[loot]

I paid someone to do mine, mine is a slightly older vcm2 so the serial change only works until I think v98. I know v99 doesn't allow access to pcm and that's because it knows the vcm has different chips in.

Anyway the guy made an exe file that changes the pc time and date to the install date and also starts vmware. It reverts the pc date to correct when I close vmware. May be a cab file?

You can manually set the time and date and turn off auto update time and network time in control panel. You have to majestic sure you set the date to the install date every time, then you'll have 3 days trial on ids, but with vmware it can be reset each time with snapshot and it purges any remnant reg keys etc unlike native.

But if you Google the latest info because there may be a patch or simple method available. Until I buy a newer vcm I don't need to know

[Danbrad]

Thanks for the info, good to know. Will give an update tomorrow whether i've been locked out and turned to vmware.
Regards
Dan

[Danbrad]

Well loot, I'm on my 5th day and not locked out. I have downloaded a vm image of 112.04. Would i need to update my vcm firmware with that version. If so and i wanted to use say v110 would i have to reflash for that version again?
Regards
Dan

[loot]

If yours is working then keep it, you only need to update when you need to connect to a new vehicle that requests it. It's easy enough to downgrade the vcm anyway. I did a big post but swiped the page away

[Danbrad]

Ok, well it worked with 112 without firmware update. will stick to 110 thou as its native install.
Thanks for the input.
Regards
Dan

[Airthies]

Awright then.
back to V86
anyone seen this? "Error: DB"
on a fresh install of W10pro?

Error DB V86.PNG

[loot]

Yes I did the other day, bloody windows 10.

Although I might have used the same 1 so it could be broken.
Do you have the disk?