I need to deploy the latest 3DxWare Driver through our software deployment suite. I was planning on using the 3DxWare64_v10-0-20_r1721 build but it seems the /Q switch is broken and/or needs additional switches. Is there a known issue or are there additional switches to be used in order to quielty install the software? - e.g. 3DxWare64.exe, which is packed inside the 3DxWare64_v10-0-20_r1721.exe?
In addition extracting the 3DxWare64.exe and creating a setup.iss ("setup.exe /r") and using the "setup.exe /s" switch won't do the job either.
Any help or suggestion is welcome.
Regards,
Rob
unattended installation 3DxWare64_v10 (v10-0-20_r1721)
Moderator: Moderators
Re: unattended installation 3DxWare64_v10 (v10-0-20_r1721)
Hello Rob -
For a silent install the .MSI files need to be used instead of the .exe. 3DxWare64.exe contains the compressed . MSI files.
You can find steps for using the Windows Installer .MSI files in the file ‘silent_install.txt’ [C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\silent_install.txt]
Extract 3DxWare64.exe from 3DxWare64_v10-0-20_r1721.exe then extract again for the component folders - Components64 and Components32Shared. In the folder ...\Components64\3DxWinCore you will find 3DxWinCore64.msi. Install 3DxWinCore64.msi first - this is the basic driver, then you can add any other components or add-ins for the applications you are using - ie 3DxSolidWorks64.msi.
-------------
Barbara
For a silent install the .MSI files need to be used instead of the .exe. 3DxWare64.exe contains the compressed . MSI files.
You can find steps for using the Windows Installer .MSI files in the file ‘silent_install.txt’ [C:\Program Files\3Dconnexion\3DxWare\3DxWinCore64\silent_install.txt]
Extract 3DxWare64.exe from 3DxWare64_v10-0-20_r1721.exe then extract again for the component folders - Components64 and Components32Shared. In the folder ...\Components64\3DxWinCore you will find 3DxWinCore64.msi. Install 3DxWinCore64.msi first - this is the basic driver, then you can add any other components or add-ins for the applications you are using - ie 3DxSolidWorks64.msi.
-------------
Barbara
Re: unattended installation 3DxWare64_v10 (v10-0-20_r1721)
Hi Barbara,
I did that for 3DxWare64_v10-2-9_r2043 - but there are some problems after the installation the user has that shows, that something is different when installing the package with a direct call of the MSI's instead of the Setup.exe.
First: if I am installing the package via MSI-Installation, i have for e.g. within the 3DxWare About-Screen, that 3DxWare 10 Version is "Not Installed" but 3DxWinCore Version "17.2.9.11812". When installed the same software package via setup.exe (manual installation), the about screen shows: 3DxWare 10 Version "10.2.9" and 3DxWinCore Version "17.2.9.11812". Probably, the 10.2.9 is just being shown, because the setup.exe was executed manually, but: there is a problem also when the software is installed just via MSI: keys that are defined as special keys for example for SPLM NX are not working - means: it seems that the tool doesn't care about such an key definition. But: when the 3DxWare software is installed manually via executing the Setup.exe, the definition of special keys is working without any problems. So can you please tell me, where the differences are?
Thx and BR!
Harry
I did that for 3DxWare64_v10-2-9_r2043 - but there are some problems after the installation the user has that shows, that something is different when installing the package with a direct call of the MSI's instead of the Setup.exe.
First: if I am installing the package via MSI-Installation, i have for e.g. within the 3DxWare About-Screen, that 3DxWare 10 Version is "Not Installed" but 3DxWinCore Version "17.2.9.11812". When installed the same software package via setup.exe (manual installation), the about screen shows: 3DxWare 10 Version "10.2.9" and 3DxWinCore Version "17.2.9.11812". Probably, the 10.2.9 is just being shown, because the setup.exe was executed manually, but: there is a problem also when the software is installed just via MSI: keys that are defined as special keys for example for SPLM NX are not working - means: it seems that the tool doesn't care about such an key definition. But: when the 3DxWare software is installed manually via executing the Setup.exe, the definition of special keys is working without any problems. So can you please tell me, where the differences are?
Thx and BR!
Harry
Re: unattended installation 3DxWare64_v10 (v10-0-20_r1721)
Hello Mr.Goose -
The difference in installing from the .msi files and setup.exe is that 3DxWinCore64.msi installs only the basic driver. Each of the plug-ins you plan to use has to be installed manually from it's .msi file. Setup.exe installs the driver package including the plug-ins and has the option for a complete or custom install.
It is the installation of the NX plug-in that makes NX button mapping available.
After extracting the compressed files there will be folders 'components64' and 'components32shared'. Each of the plug-in .msi files is in its own folder. 3DxNX64.msi is in the folder 3DxNX in the 'components64' folder.
The current 10.3.0 version is available on our downloads page.
-----------
Barbara
The difference in installing from the .msi files and setup.exe is that 3DxWinCore64.msi installs only the basic driver. Each of the plug-ins you plan to use has to be installed manually from it's .msi file. Setup.exe installs the driver package including the plug-ins and has the option for a complete or custom install.
It is the installation of the NX plug-in that makes NX button mapping available.
After extracting the compressed files there will be folders 'components64' and 'components32shared'. Each of the plug-in .msi files is in its own folder. 3DxNX64.msi is in the folder 3DxNX in the 'components64' folder.
The current 10.3.0 version is available on our downloads page.
-----------
Barbara