Aimsun Serial Port
Thanks Hairyfool. I looked at the site you supplied - it gave 15 driver files, some of which I eliminated as they were not my operating system. The rest gave no indication of containing a PCI Serial Port driver. However, I have run the most likeliest of them, to no effect. My Device Manager still shows the PCI Serial Port with no driver. I am a relative novice (well a 78y.o. One!), and I don't know what the PCI serial port does.
Kelis Milkshake 320 Kbps Downloader. GPS Troubleshooting Introduction: Serial-to-USB adapters that do two things: They physically connect a serial cable to a USB port. They have software drivers that. Network Licensing depends on three primary components: License Server; Administrative Tools; Working Papers. The License Server can be installed on supported computers (see System Requirements) that is always on. The Administrative Tools can be installed on any workstation computer and can be used.
Everything seems to work alright on the computer, apart from an old (HP 710C DeskJet) printer attached to a printer port (LPT1:). This printer used to work, but has suddenly stopped, and reinstalling it has no effect. Would this be affected by the Serial Port having no driver? I have also totally failed to install this printer through a USB port, despite having got drivers from HP.
Any files sent to the printer via USB disappear into the nevernever with no error message. The USB ports all seem to work correctly otherwise. Files sent to the printer via LPT1: fail to print and give the error message 'This file failed to print', and then have to be deleted from the printer. Further help would be appreciated.
The basic board spec shows it does not have a Serial port. However it does have an Intel Management Engine interface for which the drivers should be. If you read the driver page it informs that if these drivers are not installed it shows as missing drivers for a Simple Communications controller. To be clear serial ports are legacy devices and seldom used today.
If not actually needed the lack of drivers for this specific device would have no effect on the system The specification also says nothing about a parallel port (Lpt1). Do you have an expansion card into which you plugging in the printer. The socket would not be in the main group of connectors but separate and in the vertical slots. Some port expansion cards had both Serial and parallel ports so this might be the missing driver.
If so you would need to identify what the card is and find the appropriate drivers. Unfortunately it is highly likely they would not be available for Windows 7. The spec of the Printer does not show USB so have you got a USB to Parallel converter, In which case that is going to need drivers itself.
Venerable and functional it may be but the 710c is a very old printer and although it may work if set up right is not supported on Windows 7. Have a good look at bios settings and check if serial port is disabled or enabled? If it does not show in bios you probably don't have a serial port. Robert--My PC-window 7 Professional-32-bit: My communication port(com 1)works:My ECP printer port (lpt 1)works: but my Intel (R) Active Management Technology SOL (COM 3) has been stopped by windows((--Window has stopped this device because it has reported problems (Code 43)--)).
There is a yellow triangle at my Device Hardware infomation- My Tower-OptiPlex 755 Dell.
This document attempts to explain how to setup a HASP network license system for DIANA 9.5 and onward. Basic principle One system in the network contains a network license key (SLnet softlock or NetHASP hardlock) that can be used by all systems in the network. The system that contains the license key is called the license server. Systems using the network license key are called client systems.
The license server may also act as a client system. The license server manages, tracks and registers network license usage. Updates to network licenses are installed on the license server only. Communication of license information between license server and client is done by the HASP driver.
This driver needs to be installed and configured both on the license server and the clients for the system to work. Additionally, the firewall on the license server and client system needs to be configured to allow license information exchange between license server and client in both directions. Select your license server carefully. If the license server is not available, the client systems will not be able to use DIANA. Don't use the PC you work on as license server because the license server will become unavailable to other users/client systems when you turn off the PC.
If you have a dedicated server for running large DIANA jobs you might consider using that server as the network license server. That way, the network license will always be available to the server. Tasks to be performed The following tasks need to be performed to get a network license up and running. License keys for DIANA are based on SafeNet Sentinel HASP technology. The DIANA specific HASP driver needs to be installed on the system in order to make the license key available to DIANA. This document attempts to explain how to install the DIANA specific HASP driver on Windows and RedHat/CentOS Linux systems. HASP driver for Windows systems To be able to install the HASP driver you need administrative permissions.
If you don't have these on the system, please ask your system administrator to install the HASP driver for you. Download the latest DIANA specific from the. Unzip/Extract the downloaded file.
Open a Command Box (cmd.exe) and go to the extraction location. Execute the following command: haspdinst.exe -i After installation the following website should be available on the system:. HASP driver for RHEL/CentOS Linux systems To be able to install the HASP driver you need root permissions.
If you don't have these on the system, please ask your system administrator to install the HASP driver for you. Before we start with the installation of the HASP driver we first make sure the required RHEL/CentOS linux libraries are installed on the system. Game Textures Splatter on this page.
Sudo yum install libgcc.i686 glibc.i686 Download the latest DIANA specific from the. Unzip the downloaded tar file. Tar xf aksusbd-7.61.1-i386.tar Go to the exctracted folder and install the HASP driver. Cd aksusbd-7.61.1-i386 sudo./dinst After installation the following website should be available on the system:.
If this is not available you might need to configure the firewall to allow communication on port 1947 for both UDP and TCP. License keys for DIANA are based on SafeNet Sentinel HASP technology. This document attempts to explain how to configure the DIANA specific HASP driver on the license server and client systems in order to make the network license work.
This document assumes the HASP driver is already installed. For information on installing the HASP driver see the. Please note that it may take several minutes before you can see the result of configuration changes. Configure the HASP driver on the license server On the license server we have to allow client systems to access the network license key. In order to do this go to Sentinel Admin Control Center Configuration: Allow Access from Remote Clients Selecting this check box will enable remote machines to access this Sentinel License Manager.
Note: When you select this option, you must also set Network Visibility (on the Network tabbed page) to All Network Adapters. Access Restrictions Defines the restrictions that will be imposed on remote machines accessing this Sentinel License Manager. Enter data in the following format: allow=[item] and/or deny=[item], where item is an IP address or machine name. IP addresses can include '*' or a range of addresses allow or deny multiple addresses.
The value of item can also be all or none. Each entry must be on a separate line. The entries are evaluated in the order in which they are specified.
For example, item can be: 10.24.2.18 a single address 10.24.2.10-50 range of addresses (only 4th number may be a range) 10.24.2.* class C subnet 10.24.*.* class B subnet 10.*.*.* class A subnet 10.24.2.0/24 subnet, number of mask bits specified Click Show Recent Client Access to display a list of remote machines that have recently accessed this Sentinel License Manager. To apply changes in this page, click Submit.
For more information see Sentinel Admin Control Center help: Configure the HASP driver on the client system On the client systems we have to make the HASP driver find the network license key on the license server. In order to do this go to Sentinel Admin Control Center Configuration: Use this page to define the address of the machine that hosts the Sentinel License Manager to which you want this client to connect, and to define how and where searches for Sentinel License Managers may be performed.
The following criteria may be specified: Allow Access to Remote Licenses When selected, enables this machine to search for remote Sentinel License Managers on the local network. Note: When selecting this option, you must also: – Select Broadcast Search for Remote Licenses. OR – Provide values in Specify Search Parameters.
Broadcast Search for Remote Licenses When selected, enables this machine to search for remote Sentinel License Managers on the local network via broadcasts. (Note that the broadcast uses a random UDP port.
This may be an issue with certain firewalls.) If this check box is not selected, every machine on the local network that is to be searched must be specified in the Specify Search Parameters field. Aggressive Search for Remote Licenses When selected, enables this machine to connect to remote Sentinel License Managers, even though they cannot be detected using UDP datagram search methods. Aggressive searching reduces the update frequency of remote Sentinel information, but may enable firewalls to be transversed.
Specify Search Parameters Defines the specific machines that may be searched by this machine for remote Sentinel License Managers. You must enter information in this field if you have not selected the Allow access to remote licenses check box, as follows: • Specify data as IP addresses (for example, 10.1.1.17), Broadcast addresses (for example, 10.1.1.255), or machine names (for example, hklm001.ecomp.com) • When using the IPv6 protocol, use the IPv6 address format.
For example, type FF02::1 to access all remote Sentinel License Managers that are part of the default local group defined in the IPv6 subnet. Each entry must be on a separate line.
To apply changes in this page, click Submit. Configuring HASP driver on many client systems If you have many client systems to configure, you may not want to configure them all using the GUI described above. If so start by configuring one client using the GUI as described above. After that open C: Program Files (x86) Common Files Aladdin Shared HASP hasplm.ini in notepad. As you can see this is a text file that contains the complete HASP driver configuration. If no configuration is done then this file does not exist. Use standard network management tools to install the HASP driver and write/edit this configuration file on all clients.
Please note that the hostname of the client machine is also included in the configuration file. This needs to be edited in the configuration file to match the client on which the file is installed.