Sentinel Superpro Driver Installer Problem System

Sentinel System Driver Installation OptionsThis document describes the installation methods for the Sentinel System Driver on anyWindows 95/98/ME/NT/2000/XP system. All the methods described below are suitable fordevelopers using the Windows Installer.Note: The Sentinel USB driver is not supported on Windows 95.Installation Procedure WARNING: When you run setup.exe to install thedriver, it will automatically update your version of the Windows Installer if necessary.It will not provide any prompts before doing this. If you are not sure you want to updatethe Windows Installer—do not run this program.IMPORTANT NOTE: Remove the USB keys, if any, before continuing the installation.See for details.If you have the driver on CD, place the CD inthe computer. The installation program should automatically run; otherwise, run setup.exefrom the root directory of the driver media. You will be required to upgrade if an olderversion of driver is detected on your system.Select either Complete or a Custominstallation. Complete will install both the parallel and USB driver (as long asthe operating system supports it).

• Sentinel System Driver Installer
• Safenet Superpro Driver

If you select Custom (and if the operatingsystem on which you are installing supports USB), you can choose whether to installparallel, USB, or both.Click Install and follow theinstructions shown. When complete, you may be asked to reboot depending upon the operatingsystem and the configuration of your computer.Upgrade Note: To be able to use Sentinel SuperPro version 6.3 (or higher) orproducts protected with the same, you are required to upgrade to the latest version of theSentinel System Driver.Modification/Removal Instructions.Go to Start Settings Control Panel and select Add/Remove Programs.Double-click Sentinel System Driver 5.41.0(32-bit) to start the installation wizard. It will allow you to modify, repair, orremove the installation.Select the option you want and follow theinstructions shown. Depending on the operating system and the configuration of yourcomputer, you may be asked to reboot.How Do I Add the Driver Installation to My Own Installer?There are four basic methods of installing the Sentinel System Driver on yourcustomer's computer:.Have the users run thedriver install themselves–Since the supplied installer contains a full step-by-stepinstallation just like any application, most end users will be able to install the driverthemselves.

This can easily be added to autorun menus or automatically run at the end ofthe application installation. It can be included on your own application CD withinstructions on how to install. You can also burn your own copies of the Sentinel SystemDriver CD and distribute them with your product. If you are trying to run the installationfrom a menu or your own installer, you need only call the Sentinel System Driver's setup.exefile.Run the driverinstallation quietly–Either during your installation, or after your installerfinishes, you can call the Sentinel System Driver installation in quiet mode. The driverinstallation is then run without any required user-interaction. Are used to do this. This method is very similar to the first method, exceptyou call setup.exe yourself with the required switches to run without outputtingmessages (quiet mode).Your Windows Installerpackage calls the Rainbow Windows Installer package–If your installer is writtenfor Windows Installer, you can easily call the Sentinel System Driver installationdirectly from its.msi file.

This is a supported custom action built into WindowsInstaller. The trick to using this method is allowing the installer to find the files itneeds to install.The Sentinel System Driver, written using InstallShield for Windows Installer, has all itsfiles placed in the archive data1.cab. It is very possible that if you useInstallShield for Windows Installer you also have a.cab file. In this case, thetwo files would have to be merged together (since all the files have to reside in onedirectory). If your installer does not require a data1.cab file, just include thisfile on your CD.

You will then place the Sentinel System Driver 5.41.0 (32-bit).msifile in the same directory as your own.msi file. After you add a custom action tocall the Sentinel System Driver's.msi file from your installer, the driver will beinstalled quietly right along with your application in a seamless fashion.Use the Sentinel SystemDriver merge modules–In order to do this, your installation package must useWindows Installer. This method is probably the most difficult, but allows you the mostflexibility with installation options.

With this method, the Sentinel System Driver is notjust installed alongside your own installer; it actually becomes part of your installer.One of the advantages of this method is that the Sentinel System Driver cannot be removedunless your application is uninstalled. Thus, even if other applications try to remove theSentinel System Driver, Windows Installer will realize that another application requiresthis component. The driver is not removed until all applications that require it areremoved first.

Is fully documentedin this installation guide.When including the Sentinel System Driver on your own CD, only six files are required,totaling about 4 MB:.Sentinel System Driver5.41.0 (32-bit).msi.Data1.cab.Setup.exe.Setup.ini.Instmsia.exe.Instmsiw.exeIf you are using 3 rd method, then you need only two files that total about800 KB:.Sentinel System Driver 5.41.0 (32-bit).msi.Data1.cabWe recommend, however, that you include the entire contents of the Sentinel SystemDriver CD onto your own application CD as long as you have room. This keeps thedistribution complete. Most developers make a subdirectory on their CD for the driver andplace the entire CD contents in that folder.

The entire driver CD takes up less than 10 MBof space.Another alternative is to point your customers to the Rainbow Technologies Web site ( they can download the latest version of the Sentinel System Driver themselves.Assuming your customers are on the Internet already—this gives them an easy way toobtain the latest version.Installation OptionsThe setup.exe program checks your version of the Windows Installer, updates itif necessary, and then calls on the Windows Installer to install the Sentinel SystemDriver from the.msi file. You can pass on any command-line options to the WindowsInstaller via setup.exe using the /voption. Multiple options are placed with quotation marks; any option that requires aquotation mark should be prefaced with a forward slash ( ).For example:Setup.exe /v'/qnINSTALLDIR='C:Program FilesDriver'The above line will install the driver quietly (without prompts) into the C:ProgramFilesDriver directory. For more information on the Windows Installer and itscommand-line options, go to Microsoft's MSDN Web site.For msiexec.exe, use the option given in the example below, where /i option is for installing the package:msiexec.exe /i 'Sentinel System Driver 5.41.0 (32-bit).msi'INSTALLDIR='C:Program FilesDriver'For more information on the Windows Installer and its command-line options, go to theMicrosoft's MSDN Web site.

Sentinel System Driver Installer

Some valid Windows Installer command-line options are describedbelow (see the MSDN Web site for complete information on all options):Note: The column titled '/v Argument?' Indicates whether theoption must be placed within the /v quotation marks or whether it is used outside of the/v option. OptionDescription/vArgument?/f p o e d c a u m s vRepairs or reinstalls missing or corruptedfiles.

This option is available only with msiexec.exe.

I've successfully used this thread to fix an issue with MecSoft's VisualCAM for Solidworks 2014. I had a similar problem to that at the top of this thread; my hardware key (a sentinel SuperPro) stopped working when the newest Windows 10 update was installed (Build 1803).

Safenet Superpro Driver

I would get an error when launching SolidWorks 2017 was trying to load the add-in from MecSoft, that the dongle was not connected; this would cause the add-in to load in demo mode, and I couldn't export anything from the add-in. MecSoft told me that my software is out of support status, and suggested I buy their newest version (for $2500!!).

Thanks to this thread, I noticed that my issue is similar to what others have experienced after this Windows update, and that VisualCAM also uses the sx32w.dll library. I downloaded the libraries linked above by GauravBhanot, extracted them, and replaced the sx32w.dll inside the VisualCAM folder within the C:Program Files with the one from the download. Everything works now, without paying $2500!

I hope others can use this info to solve this problem as they update their machines, as well! Hi Michael,Here is our feedback:1.