Kbase 1293: TUNE.exe Debugging techniques and when to use
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
TUNE.exe Debugging techniques and when to use
901031-hjb01DEBUGGING PROBLEMS WITH ECLIPSE 3.82 TUNE.EXE UTILITY
To execute Progress V6 Protected Mode it may be necessary to run the
Eclipse Utility for tuning of the Protected mode module for the
particular machine you're running on. Follow the instructions as
stated in the Installation Notes for version 6. If when attempting to
invoke Protected Mode, you receive errors like " os286 Bios Checksum
does not Match, ...please reconfigure .. "pmode loader: init machine
failed.error = 10 (c)" then it it time to try running TUNE.EXE as
supplied from Eclipse and distributed with our V6 Protected mode
product.
The correct way to run TUNE.EXE is to type in:
tune -k _pprogrs.exe
Tune.exe is generally run only once on a machine. It builds into the
_pprogrs.exe some of the information that was previously stored in the
config.286 file. Since it is only run once, use the -i switch if you
want to run it a second time. This tells tune.exe that even though it
was run once, run it again and overrride the previous settings. It
does not override the previous settings by default. Here's the syntax
in case you need to run it a second time:
tune -k _pprogrs.exe -i
In fact, there are several different switches you can use with
tune.exe. To see what they are type:
tune foo
All the different parameters appear.
KNOWN TUNE.EXE ERRORS:
If you encounter " TUNE CANNOT FIND KERNAL FILE OS386.EXE" then
You probably forgot the ".exe" on the _pprogrs command. Retype:
tune -k _pprogrs.exe
If you encounter "..CANNOT FIND A WAY TO DISABLE A20 then:
1. Remove all device drivers and TSRs from the config.sys and
autoexec.bat if there are any. These are not necessary when
running tune.exe and sometimes in fact, create
incompatibilities. A known incompatibility exists if an IBM
tape device is loaded.
2. If it still does not work, check the BIOS type. American
Megatrends produced a BIOS version late in 1989 which is "BAD"
BIOS version according to Eclipse/Ergo. This BIOS version is
dated somewhere between late 1989 and March of 1990. It is
known to have problems with other products as well. To see how
it is dated, the Norton SYS INFO utility may be of help in
reading the file that contains the date. If the date falls in
this time frame, an upgrade to a later BIOS may be recommended.
Try step three, first however.
3. To Force TUNE.EXE to run with shortcuts to normal checking,
use the -f (as in force option) .
If the machine is a 386: (but not a PS2 or HP) try this:
tune -k _pprogrs.exe -f 2/2/4/0/0
If the machine is an HP 386 try:
tune -k _pprogrs.exe -f 1/1/4/0/0
If the machine is a PS2 386 try:
tune -k _pprogrs.exe -f 3/3/4/0/0
Be aware that since normal checking is not done, the _pprogrs.exe
that is created by using the force option may or may not work
correctly. It should then be tested.
If Progress Protected Mode does not run correctly, or you still
get errors and the BIOS is not AMI then contact Tech Support or
ERGO at (508)535-7510 for further debugging techniques.
If the error produced by TUNE.EXE is: "..CANNOT FIND A METHOD TO
ENABLE A20" - Then refer to the section for "..CANNOT FIND A WAY TO
DISABLE A20 (above) and try steps 1 and 3.
Progress Software Technical Support Note # 1293