FAQ: MicroBase System v1.x

 

  What Versions Of Windows Has MicroBase System 1.x Been Tested Under?

MicroBase System v1.x is a Windows 16 Bit application program which was originally intended for use with early Windows versions.

MicroBase System v1.x was tested by DSS under the following Windows Versions:

  • Windows 3.1
  • Windows 95
  • Windows 98
  • Windows ME
  • Windows 2000

MicroBase System v1.x may also run under the following unsupported Windows Versions:

  • Windows XP (32 Bit only)
  • Windows Vista (32 Bit only)
  • Windows 7 32  (32 Bit only)

MicroBase System v1.x is incompatible with 64 bit versions of Windows.

Note: If you are running a modern version of Windows (XP and above) with the MicroVib II Aircraft Analyzer, DSS suggests that you consider upgrading to MicroBase Professional v2.x. Click here for more information on MicroBase Pro. You can read about upgrading to MicroBase Professional v2.x here.


 

Why does MicroBase ask for my registration?

Before using your newly installed MicroBase System, you must enter the factory supplied registration information that came with your license agreement.

When MicroBase starts and cannot find valid registration information, the MicroBase Registration dialog will pop up prompting you to enter the valid User Name and Serial Number. Both the User Name and Serial Number must be entered into the dialog exactly as shown on the license agreement.
 


 

Does MicroBase support long filenames?

Since MicroBase is a Windows 16 bit application, it does not support long filenames. When entering a filename or path statement into MicroBase, you should observe the DOS/Win16 filename restriction of "8.3". In other words, filenames are restricted to eight characters followed by a filename extension of not more than three characters. Folders (directories) used in a path statement are restricted to eight characters.
 


 

How do I uninstall MicroBase from my computer?

You may notice that MicroBase does not contain an uninstaller program and does not create an entry in your Add/Remove Programs selector. This is because MicroBase does not copy files to the system directories and does not make entries in either the system registry or in any of the Windows initialization files.

To uninstall MicroBase, simply run windows explorer and delete the \MBASE folder including any sub-folders located below it.
 


 

Why doesn't MicroBase display the print data dialog?

If you are using MicroBase on a computer which does not have any printer drivers installed, you will not be able to select the Print Data dialog.

To correct this problem, install the printer driver which is appropriate for your printer and then restart MicroBase. The Print Data dialog will now be available.
 


 

How do I connect to MicroBase if my computer is not equipped with a serial port?

Your computer must be equipped with an RS-232 compatible serial port in order for MicroBase to communicate with the MicroVib and MicroVib II Aircraft Analyzers. If your computer is not equipped with such a port, see the FAQ, Using MicroBase With USB Ports.
 


  Why does MicroBase produce errors when I attempt to connect with my analyzer?

MicroBase may produce one of the following errors when it attempts to open a com port for communication with the MicroVib or MicroVib II Aircraft Analyzer:

  • Error: -2 (Device Already Open) The Com port is already in use,  probably by another program. Disable the interfering program and try again.
  • Error: -3 (Device Not Open) The Com port is already in use, probably by another program. Disable the interfering program and try again.
  • Error: -10 (Hardware Unavailable) - The Com port is not available. It may be disabled or it may not exist. Try to enable the Com port or select another and try again.
  • Other Errors - Contact DSS Product Support with the error code.

If opening the com port continues to generate an error, check the com port using the following checklist:

  • Open the Windows device manager (Control Panel - System - Hardware - Device Manager) and select Ports (COM & LPT). Look for an entry which corresponds to the Com port you are attempting to use.
  • If an entry for the desired Com port is shown, double click on the entry and note the device status. Windows will attempt to determine if the port is functioning properly.
  • If no entry exists for the selected port, then close the device manager and choose another Com port for use in MicroBase.

 

Why Can't MicroBase Connect To My MicroVib II Aircraft Analyzer?

If you cannot connect to the model 1300 MicroVib II Aircraft Analyzer, use the following checklist:

  • Make sure you are using the correct procedure to connect to your PC. With the MicroVib II turned on and with the mode menu selected, start the MicroVib II Data Manager Dialog (File - MicroVib II - Data Manager). MicroBase should automatically connect and report that it has found your MicroVib II.
  • Make sure you are using the correct cable to connect your MicroVib II your PC. You should use the 1311 Serial Cable to connect directly from your MicroVib II to your PC.
  • Make sure you have selected the correct serial port in MicroBase (Options - Ports).
  • Make sure that the serial port you wish to use is enabled. On some computers, the serial port may be inactivated due to a setting in the computer cmos or in the Windows device manager.
  • Try to determine if another program is preventing access to the Serial Port even though it is not actively using it. This is a common problem with computers using Hotsync software intended to connect to a PDA. If this is the case, close the interfering program so that MicroBase can have access to the Serial Port.
  • If using an older version of Windows, make sure that you have the correct base port address and hardware interrupt request (IRQ) settings selected in Windows for the serial port you are trying to use.
  • If you are using Windows For Workgroups 3.11 and you are having problems with data transfers, you may need to update your serial communication driver. Look in your \WINDOWS\SYSTEM folder and locate the SERIAL.386 driver file. If this file is dated before 17 Feb 1994, then you will need to obtain a newer version of this file. You can download the file WG1001.EXE from a number of places on the internet to obtain the corrected serial driver. Instructions for installing the corrected serial driver are included with this file.

 

Why Can't MicroBase Connect To My MicroVib Aircraft Analyzer?

If you cannot connect to the model 1001 MicroVib Aircraft Analyzer, use the following checklist:

  • Make sure you are using the correct procedure to connect to your PC. With the MicroVib turned off, select the MicroVib Unload Dialog (File - MicroVib - Unload), then turn on the MicroVib and your data will be automatically unloaded.
  • Make sure you are using the correct cable to connect your MicroVib to your PC. You will need to use the 1025 I/O Cable and the 1026 RS-232 Adapter.
  • Make sure you have selected the correct serial port in MicroBase (Options - Ports).
  • Make sure that the serial port you wish to use is enabled. On some computers, the serial port may be inactivated due to a setting in the computer cmos or in the Windows device manager.
  • Try to determine if another program is preventing access to the Serial Port even though it is not actively using it. This is a common problem with computers using Hotsync software intended to connect to a PDA. If this is the case, close the interfering program so that MicroBase can have access to the Serial Port.
  • If using an older version of Windows, make sure that you have the correct base port address and hardware interrupt request (IRQ) settings selected in Windows for the serial port you are trying to use.
  • If you are using Windows For Workgroups 3.11 and you are having problems with data transfers, you may need to update your serial communication driver. Look in your \WINDOWS\SYSTEM folder and locate the SERIAL.386 driver file. If this file is dated before 17 Feb 1994, then you will need to obtain a newer version of this file. You can download the file WG1001.EXE from a number of places on the internet to obtain the corrected serial driver. Instructions for installing the corrected serial driver are included with this file.

  Why Am I Getting Errors During Data Communications ?

The fastest communications speed possible in Windows is dependant on many factors, including your serial port, computer speed and other programs running on your computer. If you have errors while unloading MicroVib Data or using the MicroBase Data Manager to transfer files, check the following:

  • Make sure your computer is running at its fastest speed. Some computers may run at slower speeds to prolong battery life or to allow games to run properly.
  • Use a serial port that contains a 16550A UART. This type of serial port uses an on-chip data buffer which allows transmission of high-speed data - even on slower computers.
  • Try to determine if another program is interfering with access to the Serial Port even though it is not actively using it. If this is the case, close the program so that MicroBase can have complete access to the Serial Port.

  How Do I Activate The Unload Log (MicroVib Unloading Only)?

You can troubleshoot Unload errors by telling MicroBase to create a log of the steps it performs during the Unload process. MicroBase will automatically write the log to disk for viewing:

  • Quit MicroBase
  • Use a text editor (such as Window Notepad) to open the file mbase.ini that is located in the \WINDOWS (or system root) folder.
  • Locate the line beginning with UnloadLog= that is located in the [Unload] section of the mbase.ini file.
  • Change the text following UnloadLog= from NO to YES.
  • Save the mbase.ini file.
  • Restart MicroBase
  • Unload some data from the MicroVib Aircraft Analyzer.
  • Quit MicroBase
  • Use your text editor to open the file unload.log which is now located in the MicroBase System folder. In the log file you will see a listing showing each step which was performed during the unload process along with the time of occurrence.

  Why does MicroBase complain that "your index file appears to be damaged"?

This error message appears under Windows XP Pro when the user attempting to run MicroBase does not have the required permissions to modify the contents of the MicroBase folder. This problem can be corrected by one of the following methods:

Method #1 - Increase the MicroBase user's privileges:

  • Log on as administrator.
  • Select Control Panel -> Administrative Tools -> Computer Management -> Local Users and Groups.
  • Increase the MicroBase user's privileges.

Method #2 - Run MicroBase with different credentials:

  • Right click on the MicroBase Icon and select the Properties menu.
  • Click on the Shortcut tab and click Advanced.
  • Check the "Run with different credentials" checkbox.
  • Click OK then Apply and OK.
  • When running MicroBase select an administrative user and password followed by OK.

Method #3 - Change the MicroBase folder's permissions:

  • Log on as administrator.
  • Open Windows Explorer and drill down to the MicroBase folder (usually c:\mbase).
  • Right click on the folder and select the Security tab.
  • Observe the contents of the "Group or user names" list and click Add.
  • Enter the new object (user name or group name) and click OK.
  • Select the new object in the "Group or user names" list.
  • Click to allow Full Control for the new group or user name.
  • Click Ok.

Note: If you are using Simple File Sharing on your Windows XP Pro system, method #3 will not be available so you will have to use either method #1 or #2.


 

Why does Windows report the following error message when I run MicroBase?

"The system file is not suitable for running MS-DOS and Microsoft Windows
applications. Choose close to terminate the application."

This error message is produced when the user tries to run a Win16 application, such as MicroBase, on a Windows NT/2K/XP computer which has a damaged Windows 16 bit subsystem.

This is a problem with Windows, not with MicroBase.

Click on the following link to obtain repair information from Microsoft website:

Microsoft Help and Support Article 324767
 


 

Why can't I find the import file (MBX) that I want to import data from?

After having copied an import (MBX) file to a computer running Windows 95/98/ME, you may find that the file cannot be selected from within the MicroBase Import file dialog.

This problem is caused by a bug in MicroBase v1.50.64 which fails to find an MBX file if it is located in the Root folder of a PC running Windows 95/98/ME.

This problem has been corrected in MicroBase v1.50.72. Until you have upgraded your MicroBase software to v1.50.72 (or higher), you can work around this problem by moving the MBX import file to a folder which is not the Root folder and running the import function again.
 


 

Why can't I see the export file (MBX) I just created?

After exporting data to a file on your computer, you may not be able to locate the file after the export has completed.

This problem is caused by entering a filename which exceeds the dos/win16 file name convention of "8.3" or which contains characters which are illegal under dos/win16. 

This problem is caused by the fact that MicroBase currently only supports dos/win16 filenames which are in the form of "8.3". You can correct this problem by exporting the data to a valid dos/win16 filename.
 


 

Why does my remote file listing not match my MicroVib II file directory?

When using the MicroBase Data Manager to view a remote file listing, some files may not display properly if they contain characters which are not permitted under the dos/win16 file name convention of "8.3".

This problem is caused by a bug in MicroVib II firmware v1.30 which permits the user to create file names which contain characters which are not permitted under dos/win16.

This problem was corrected in MicroVib II firmware v1.31. Until you have upgraded your MicroVib II firmware to v1.31 (or higher), you can work around this problem by renaming the file using the MicroVib II File Manager and removing any incompatible characters from the file name.
 


 

Why does my renamed history file seem to be missing some data?

When using the MicroBase Data Manager to rename and then download the current (active) history file in from the MicroVib II , the latest data (runs) collected may not be available for Identification.

This problem is caused by a bug in MicroVib II firmware v1.30 which does not update global variables properly when the current balance history file is remotely renamed. When the file is remotely renamed, the MicroVib II still associates the current history memory image with the old filename and therefore does not flush the memory image to disk when a download is requested.

This problem was corrected in the MicroVib II firmware v1.31. Until you have upgraded your MicroVib II firmware to v1.31 (or higher), you can work around this problem by renaming the file using the MicroVib II File Manager and then re-connecting to the MicroBase Data Manager for downloading.
 


 

Why can't I identify more than one data item under Windows 2000/XP?

If you are trying to unload data from the MicroVib Aircraft Analyzer to MicroBase v1.25 or earlier under Windows 2000 or Windows XP, you may find that the unloaded data list disappears after you have identified the first data item. This failure is due to a bug in the MicroBase file handling code.

This problem was corrected in MicroBase v1.50. Until you have upgraded your MicroBase installation to v1.50 (or higher), you can work around this problem by Unloading the MicroVib, identifying one data item and then unloading the MicroVib again, identifying another item, etc...
 


 

Why does Windows NT/2000/XP complain when I try to import data?

If you are trying to import data into MicroBase v1.25 or earlier under Windows NT, Windows 2000 or Windows XP, you may see a warning that An application has attempted to directly access the hard disk which cannot be supported...  This warning is generated due to a problem in the MicroBase disk access code which is not compatible with Windows NT.

This problem was corrected in MicroBase v1.50. Until you have upgraded your MicroBase installation to v1.50 (or higher), you can work around this problem by clicking on the IGNORE button and proceeding to the import data dialog.
 


 

Why does MicroBase complain about my index file after packing?

If you mark all of the data items in your database for deletion and then Pack the database (creating an empty database), MicroBase v1.25 and earlier will sometimes report that the Index File Appears To Be Damaged. In this case, you will not be able to add any new records to the database.

This problem was corrected in MicroBase v1.50. Until you have upgraded your MicroBase installation to v1.50 (or higher), you can work around this problem by running the MicroBase setup program and selecting the INSTALL option to overwrite your old MicroBase folder with the new installation. This will create a fresh new set of database files which contain several example data items.


 

Why can't I select all of my data items under Windows v3.1x?

If you are using Windows v3.1x or Windows for Workgroups v3.11 and your database contains several thousand or more data items, you may find that some of your data items will not be displayed in the selection list at the bottom of your MicroBase Screen.

This problem is due to the fact that in Windows v3.1x and WFW v3.11 a listbox cannot contain more than 64K of data. When your database contains several thousand items and you choose SELECT ALL in the Selection Filter, MicroBase will try to load more data item headers into the selection list than will fit. As the selection list is overrun with data items you will hear a "ticking" sound each time a record is rejected by the selection list.

This problem can only be solved by upgrading your operating system to Windows 95 or newer. Until you have upgraded your operating system, you can work around this problem by clicking SELECT then FILTER and then choosing a filter setting which will select less than the maximum number of records than will fit in the selection list.
 


 

Why didn't MicroBase Setup create system icons in my computer?

When installing The MicroBase System on a computer which has had Windows 95/98/ME installed over Windows 3.1x, MicroBase Setup may encounter an installation problem when it attempts to create the taskbar groups and Shortcut icons.

This problem is caused when MicroBase Setup calls the old Windows 3.1x shell program (PROGMAN.EXE) rather than the new Win32 shell program (EXPLORER.EXE) when it attempts to create the Taskbar groups and Shortcut icons. When this happens, the Taskbar groups and Shortcut icons will not be created. Following is the workaround to solve this problem:

  • Click on START then PROGRAMS and open Windows Explorer.
  • Locate and double click on the \WINDOWS folder.
  • Locate and click on the program named "PROGMAN.EXE" (you may not be able to see the ".EXE" depending on how you have setup Windows 95).
  • Click on FILE and RENAME then rename the file to "PROGMAN1.EXE"
  • Run the MicroBase Setup program again, choosing the INSTALL option.

 

Why can't I transfer data or files under Windows for Workgroups v3.11?

If you are using Windows For Workgroups 3.11 and you are having problems with data transfers, you may need to update your serial communication driver. Look in your \WINDOWS\SYSTEM folder and locate the SERIAL.386 driver file. If the file is dated before 17 Feb 1994, then you will need an to obtain a newer version of this file. You can download the Microsoft update file WG1001.EXE from the Download Page and a number of other places on the internet to obtain the corrected serial driver. Instructions for installing the corrected serial driver are included with this file.


 

Did you find this article useful? Please tell us.

 

Back to FAQs page.