VIDA 2014D/2015A Windows 11
-
@Vreaper Thank you for the review! I will look into the NET Framework prerequisite.
I think youre issue with the image(s) has to be arbortext isoview.
Isoview is responsible for showing the modules and parts images.You could try uninstalling Arbortex Isoview 7.1 and installing another version of IsoView and see if it resolves the issue.
The latest version is 7.3 and the original VIDA version is 4.0.
-
Ive just installed it on mu windows 11 home.
It works fine!
Except the minor zoom issue in the ecu modules as per others experienced. But that really does not matters.
Other minor issue is on the visual also,
When i perform data trending under vehicle communication, the trend scales number seems to be overlap.
But anyways, the installation is actually my biggers concern and thank you for compiling the installation file so well. The single-click setup works perfectly and makes the whole process very smooth and convenient. I really appreciate the effort you put into making it simple and reliable.
-
Thank you very much @ZaanTerror it worked on my windows 11 pc.
-
This post is deleted!
-
@ZaanTerror, you are a true hero. Installed this both on a VM as bare metal machine (Windows 10), both installed flawlessly. The application is confirmed working and I was able to reset my DTC code at last. Many many thanks!
-
@repeq
Did you let my installer handle the SQL installation? If yes verify that SQL Server Service is started and running.If you installed SQL with the setup from ISSetupPrequisites folder uninstall VIDA and SQL Server and start installation again.
-
@Vreaper I have the same issue with the zoomed in isoview window, but only under Win 10 on a laptop that had another version of VIDA installed before I switched to ZaanTerrors Version. I can zoom in and out with the mouse wheel and with a pinch-and-zoom gesture on the trackpad. But here comes the weird part, if I boot this laptop from a Windows to go USB drive with Win 11 and clean install of VIDA, this issue doesn't occur. So my conclusion is, there is something left from a previous version of Isoview or VIDA that causes this. Maybe a registry entry or some sort of config file.
-
@T5-T6-Schnappi would you mind to share how you remove previous installation file on your win10? I have another laptop with win10 that i installed a failed vida previously, im trying to reinstalled with @ZaanTerror installer, but i could not proceed ad the vida does not recognize to be installed in the setup
-
@sangcXL3 I first stopped VIDA Monitor and all SQL services, then I uninstalled the old VIDA, everything related to SQL, and Isoview with their uninstallers. Rebooted the computer. And then I manually deleted all folders related to VIDA, Volvo, Isoview and Microsoft SQL. This is quite tricky as lots of those folders are hidden. Look into the subfolders of C:/ProgramData/ (hidden); C:/users/{yourWindowsusername}/AppData/ (hidden) press Windows-key together with R and then simply enter AppData and press Enter to open this folder; C:/Program Files (x86)/Common Files/; C:/Program Files/Common Files/. I also removed several registry keys in HKLM\SOFTWARE\ and HKLM\SOFTWARE\WOW6432Node.
After another reboot the new VIDA installed without problems.
