| Microware OS-9 Support Links | ||||||
|---|---|---|---|---|---|---|
| Home | Training | Resources | TECH-CHECK | History | Registered Support | Logout |
Error Messages
Hawk is not showing all the processors it should.
Hawk creates a file called <MWOS>\DOS\BIN\hawkdata.xml. This file contains all the processor settings that Hawk uses in Projects. If you install a newer version of Enhanced OS-9, which adds more processor support, Hawk will not automatically overwrite the old hawkdata.xml file so the new processors will not show up. The solution is to rename/delete the older hawkdata.xml after upgrading to a new Hawk.
This should be fixed in later versions of OS-9® (after 4.4) by having the Installer rename an existing hawkdata.xml file, if found.
My Enhanced OS-9® install fails with a ComponentMoveData error.
This is caused by installing a new package over an existing package. With previous installs, the <MWOS>\OS9000\SRC\SYS directory contained the following folders:
ERRMSG
MOTD
PASSWORD
STARTUP
TERMCAP
UMACS.HLP
Since these folders each only contained one file, these folders have been
removed and replaced with just the files. The installer fails because it
is trying to replace the folder with a file of the same name.
To fix this problem, you can either uninstall your old package (which may
not work since the new package overwrote some of the files) or you can delete
the folders in the <MWOS>\OS9000\SRC\SYS directory, and then reinstall
the new package.
-
Right click on the My Computer icon on your desktop and select properties.
-
Select the Environment tab
-
Look for a MWOS variable with the value of your MWOS directory
-
Edit your autoexec.bat file, and look for a line that sets your MWOS (for example SET MWOS=C:\MWOS)
Make sure that your environmental variable MWOS is set.
Windows NT users:
Windows 9x users:
Hawk needs to be installed by an Administrator on NT systems. If a non-admin user then tries to run Hawk, a few changes have to be made to the registry.
1) Click on the Start menu and select Run.
2) Type "regedt32" (that allows you to edit the registry)
3) At this point you have the Registry Editor window. Click on the "HKEY_LOCAL_MACHINE
on local machine" window.
4) Click on Software-->Microware Systems Corp
4) Click on the "security" menu of the Registry Editor window
5) Select "Permissions"
6) In the Registry Editor Permissions, click on "everyone" and
change your permission from "special access" to "full control"
7) Continue with steps 3) for the "Hawk xxx" subentry inside
"Microware Systems Corp" and repeat recursively for all neccessary
subentries of "Hawk".
8) Do not change any other things inside the Registry if you're not well
experienced.
System or Project Initialization Failed.
This is caused by Version Control being turned on. Edit your mwhawk.ini file located in the <MWOS>\DOS\BIN directory.
You should see something similar to this:
[Editor]
VCSProvider='ClearCase'
VCSVendor=''
Change it to this:
[Editor]
VCSVendor='PVCS'
VCSProvider=''
VCSUserName=''
The debugger-control window (with the "step", "run", "next"... buttons) is empty.
This can be corrected by editing mwhawk.ini. The line with StateBtnPostions is wrong:
StateToolbarCreateTool="Debug",0x40410f,0x20,38,0,0,944,1,277,521,"",1
StateBtnPositions=8
It should be:
StateBtnPositions=8,15006,600,15001,15002,15004,15000,602,15008,15005,15007,15009,15003
This is a known issue and will be resolved in a future product release. During the interim, refer to the Microware documentation provided on your product CD-ROM. The documentation is provided in Portable Document Format (PDF) and is viewable using Adobe Acrobat Reader.
Users with current support contracts may also check the Software Updates page for available help file patches:
http://www.radisys.com/service_support/microware/registered/upgrades/index.cfm
Startup Halts at Splash Screlasen on Windows 2000.The .stg exception is caused when trying to read hawkdock.dat or mwdock.dat, which depends on whether or not you are running hawk or the stand-alone debugger respectively. These files store the locations of your debug windows. The error is caused because one of these files is corrupt which usually happens when you exit Hawk using the task manager or it crashes. This has been fixed for Hawk 2.2. We changed the code to catch the exception before it happens and default to the original setup. In the meantime this error shouldn't cause any problems, you should delete the corrupt file and re-configure their debugging window setup.
On a very few number of Windows 2000 systems, Hawk will halt it's startup process while the splash screen is displayed. We have discovered that this problem is due to a function call Hawk makes to the system's sound device that never returns execution back to Hawk.
Complete the following steps to remedy this problem on versions of Hawk 2.1 or older:
1. Rename the CWCTLS32.DLL file, found in the MWOS\DOS\BIN directory, to CWCTLS32.DLL.OLD.
2. Download the zip file for CWCTLS32.DLL file.
3. Unzip the downloaded file into your MWOS\DOS\BIN directory.
4. Using Windows Explorer, double click on the NOSOUND.REG file to insert the proper registry entry to enable the fix.
Note: If you would like to perform this step manually, you may do so with regedit.exe by inserting a DWORD value named "MenuControlSound" with a value of "0" into the following key :
HKEY_CURRENT_USER\Software\Premia\Codewright\Customize
Hawk should now start up normally.
Complete the following steps to remedy this problem on versions of Hawk 2.2 or newer:
1. Download the zip file for a registry patch.
2. Unzip the downloaded file and doubleclick on the nosound.reg file to insert the proper registry entries to disable sounds in Hawk.
Note: If you would like to perform this step manually, you may do so with regedit.exe by inserting a DWORD value named "MenuControlSound" with a value of "0" into the following keys :
HKEY_CURRENT_USER\Software\Premia\Codewright\Customize
HKEY_CURRENT_USER\Software\Starbase\CodeWright\Customize