MASsoft and ESPsoft set up (continued)
The following information represents experience setting up communications between a Hiden instrument and a PC. Most problems have been found to be due to the set up of the PC, and thus are readily overcome. This is by no means a comprehensive list of all possible problems, but may provide some help. An attempt has been made to link solutions with problems, but some solutions apply to more than one problem, so you are advised to read the whole document if your problem resists a listed solution. Windows can sometimes be a tricky environment to set up (usually it's not), so if you initially get problems, don't worry too much, they can usually be solved fairly easily.
Specific problems - MASsoft or ESPsoft does not launch or gives errors on launch (6 possibilities).
- MASsoft starts up but most of the menu options are grey
- MASsoft starts but will not run a scan.
- MASsoft starts but the Mass Spectrometer is Unavailble
- ESPsoft starts but the instrument is “Not found”
- MASsoft fails to re-interrogate on a serial connection
- MASsoft fails to re-interrogate over a network
- MASsoft gives errors during re-interrogation
- MASsoft starts but gives “Unknown Logical Device” error when run.
- MASsoft or ESPsoft starts but gives “Comm Port Error” dialogue when run.
- MASsoft or ESPsoft starts but gives “Status Change” dialogue when run.
- MASsoft crashes frequently
- MASsoft won't acquire data
- The same Mass Spectrometer appears twice in the "MassSpecs" menu list
- RS232 communication doesn't work.
- LAN communication doesn't work.
 (you are here - this section covers 17 - 22)
- Using MASsoft with Windows 3.1
- Using MASsoft with Windows For Workgroups 3.11
- Using MASsoft with Windows 95
- Using MASsoft with Windows 98
- Using MASsoft with Windows Me ( Millennium Edition )
- Using MASsoft with Windows NT 4.0 or greater
- Windows fails to start up.
- Windows fails to shutdown.
- Gateway Colorbook2 known problems
- MSIU beeps - Toshiba Satelite 1620 CDS Known Problem
- Mitac computers and PCI cards.
- Using MASsoft V 2.3 or earlier with Microsoft Office
17. Using MASsoft with Windows 3.1 PROBLEM You may only use Windows 3.1 with an RS232 link to the MSIU.
MASsoft setup will insert a line in the \WINDOWS\SYSTEM.INI file which WIN 3.1 cannot understand, and this must be changed before MASsoft is run.
SOLUTION Ensure that the line in the \WINDOWS\SYSTEM.INI file which reads netmisc=PATH\vdlcd.386
is changed to device=PATH\vdlcd.386
where PATH is the path to the MASsoft home directory (default c:\hiden).
[index]
18. Using MASsoft with Windows For Workgroups 3.11 MASsoft will install and run correctly under Windows For Workgroups 3.11.
In some cases it will be necessary to change the comm.drv driver driver to comm.drv=C:\HIDEN\COMM.DRV ( all versions of MASsoft )
if MASsoft crashes while interrogating the mass spectrometer or as soon as it starts to down-load a scan and displays a message box such as:- *C001* Command Error 1 "Unknown Command" *C003* Command Error 3 "Command Truncated"
[index]
19. Using MASsoft with Windows 95 MASsoft will install and run correctly under Windows 95.
In some cases it will be necessary to change the comm.drv driver driver to comm.drv=C:\HIDEN\COMM.DRV ( for MASsoft 3.5.3 )
or comm.drv=C:\Progra~1\Hidena~1\Common\Comm.drv ( for MASsoft 3.7 or later )
if MASsoft crashes while interrogating the mass spectrometer or as soon as it starts to down-load a scan and displays a message box such as:- *C001* Command Error 1 "Unknown Command" *C003* Command Error 3 "Command Truncated"
[index]
20. Using MASsoft with Windows 98 MASsoft will install and run correctly under Windows 98.
Unless you are using a serial card with special device drivers the comm-drv= line in the [boot] section of SYSTEM.INI should be comm.drv=comm.drv Prior to CD version 1.34 installing Hiden software changed this line to comm.drv=C:\HIDEN\COMM.DRV
or comm.drv=C:\Progra~1\Hidena~1\Common\Comm.drv
This can cause “Comm port error” dialogue boxes to be displayed and increases the chance of over run errors. This line should be changed back to comm.drv=comm.drv
[index]
21. Using MASsoft with Windows Me ( Millennium Edition ) MASsoft will install and run on a serial connection under Windows Me.
As Windows Me no longer supports Real Mode drivers the 16 bit version of MS DLC can not be loaded, nor can the DLCHLP.EXE file necessary to use the 32 bit version of DLC. Therefore LAN communication can not be used. Some other problems have been reported with Windows Me so Hiden do not currently recommend using it. The comm.drv entry in SYSTEM.INI should be changed if necessary, as per Windows 98.
[index]
22. Using MASsoft with Windows NT 4.0 or greater PROBLEM #1 MASsoft runs the first time you try to run it. If you exit MAssoft then try to run it again nothing happens. On the third attempt MASsoft runs again.
CAUSE The problem appears to be associated with the NTVDM ( NT Virtual DOS Machine ) which NT uses to run 16 bit Windows applications. This remains running when MASsoft exits. When you try to run MASsoft the second time, it terminates. When you run MASsoft a third time a new NTVDM is started and MASsoft runs.
SOLUTION Change all MASsoft shortcuts to run in their own address space
PROBLEM #2 Windows NT does not support the VXD MASsoft uses to help it communicate over the network, as a result MASsoft fails to launch.
SOLUTION This problem has been fixed in all releases since MASsoft 3.5.3. Upgrade to the current release of MASsoft. Accessms.Nt is no longer required.
PROBLEM #3 MASsoft acquires data intermintently. It appears to stop for several seconds and then catches up.
CAUSE This problem occurs on dual processor NT systems. It is due to the spin-lock that prevents more than one program using the serial port at a time.
See Microsoft knowledge base articleQ174234, "Computer Hangs with Intensive 16-bit Code Running in a VDM"
http://support.microsoft.com/support/kb/articles/Q174/2/34.ASP
SOLUTION MASsoft will be more responsive if the Mass Spectrometer status bar window is disabled. Failing this display as few as possible devices in this window.
Ensure that the latest service pack is installed ( at least SP4 for NT4 )
[index]
  
| 
