|
24
Hour Online Technical Support
HealthKeeper
Performance Diet Technical Support Policies
-
Limited
Technical Support For Free Evaluation Copies
-
Priority
Technical Support for Registered Users
Error Messages and Error Fixes for both Free Trial
and Registered versions:
(Back
to FAQ)
Fix
one: easy and works often: (Back
to Top)(Back
to FAQ)
Click
OK in the Error box and try the feature again. If this
doesn't work, click OK in the Error box and switch to
another mode then back to the original mode and try the
feature again. If this doesn't work, close the program,
re-open it and try the feature once more. Many times these
simple procedures will solve the problem or clear the
memory etc. so you can re-enable the feature. If the problem
still persists, go to fix two below.
Fix
two, works most of the time: (Back
to Top)(Back
to FAQ)
It
is simple and takes less than 3 minutes.
-
Open the Control
Panel and go to Add and Remove programs.
-
From the list
of programs that shows up Select HealthKeeper (or Health-RunR
depending on your version.)
-
Click the
Add/Remove button.
-
Answer
“Yes” to the pop up telling you it is going to de-install.
-
The next
screen offers you 3 options, Modify, Repair and Remove.
Select Repair and click Next.
-
Reboot the
computer at the end of the Repair. That’s it and, let me
know if this fixed it!
Fix
three, Specific fixes for specific error messages that
almost always work: (Back
to Top)(Back
to FAQ)
Error
380: Failure to Reboot right after the installation is
complete in versions 3.0.6 and below
When
the installation process has been successfully completed
in versions 2.3 and below, a dialog box appeared and you
were instructed to select the "Finish" button
to automatically reboot your computer. When you do not
reboot at the end of the installation, it will cause the
program installation files to register incorrectly in
the Windows Registry. This will also result in a stream
of error messages that will prevent the program from loading
properly or functioning properly when you open it for
the first time.
The
most common error message if this is the problem, is error
380. If you receive error 380 or notice the NutriCode
color bars look like garbled letters on the first screen,
you know the installation files did not register properly
in the Windows Registry. To fix it reboot the computer.
If you have a older version 3.0.6 and below and the reboot
does not fix it email us for additional fix options for
error 380 for versions 3.0.6 and below.
Error
Message: 3447 (Back
to Top)(Back
to FAQ)
The text
of this message reads “The jetvba file (vbajet.dll for
16 bit versions or vbajet.dll for 32 bit versions) failed
to initialize when called. Try reinstalling the application
that returned the error.” This means the jetvba file (vbajet.dll
for 16 bit versions or vbajet.dll for 32 bit versions)
did not register correctly during installation. In this
case re-install the program again to re-register the file
after completely de-installing it first.
If this
file still won’t register, check to see if you are using
some non-standard hard drive configuration such as having
20-30 partitions on a hard drive or are running multiple
operating systems on one hard drive. Sometime with these
unusual configurations the registration is more difficult.
Error
Message 3022 (Back
to Top)(Back
to FAQ)
The message
text is “Duplicate entry key etc error in data base.”
This error usually occurs when a user has used an out-of-date,
changed or not-in-sync personal data file (profiles.mdb
medical.mdb or recipe.mdb). There are entries in the database
from earlier data that clash with other data. This usually
only happens when a user has opened up the database manually
with some other program and has changed something or they
have installed one copy of the software version 3.0.6
or below over another copy without de-installing the other
copy using the instructions in the readme. This usually
requires a manual fix of the database by sending us a
zipped copy of your personal databases. Fixing can't usually
be done through h the software on your computer. Most
individuals de-install and reinstall and lose the older
personal data files with those data conflicts to fix this
problem. If we fix the data base corruption and determine
it was due to a corruption occurring on your computer
system and not with the software there will be a $30.00
charge to fix your personal data bases.
Error
13 Type Mismatch (Back
to Top)(Back
to FAQ)
This
is an error that sometimes occurred in versions 3.0.6
when inappropriate text or numbers were typed in fields
that required text or numbers only or occurred when your
personal databases were corrupted on your computer or
during an upgrade process. This usually requires a manual
fix of the database by sending us a zipped copy of your
personal databases. Fixing can't usually be done through
h the software on your computer. Most individuals de-install
and reinstall and lose the older personal data files with
those data conflicts to fix this problem. If we fix the
data base corruption and determine it was due to a corruption
occurring on your computer system and not with the software
there will be a $30.00 charge to fix your personal data
bases.
Other
common reasons for errors and bugs suddenly appearing
in functions that had been running correctly: (Back
to Top)(Back
to FAQ)
One reason
a bug may appear in a program that has been running well
for some time is that a file in the program has been corrupted
or fragmented by the normal wear and tear of regular hard
drive use. Problems of corrupted or fragmented files bugging
out your programs can me minimized by regularly doing
computer "housekeeping" by running the Microsoft
System Tools Scan Disk and Disk De-fragmenter.
Another
reason a bug may appear in a program that has been running
well for some time is that another program has been recently
installed on your computer that has overwritten key HealthKeeper
<.ocx> or <.dll> files with older or newer
incompatible versions of similar Microsoft <.ocx>
or <.dll> files. This type of new bug in a program
that has been running well can often be fixed by de-installing
the software and reinstalling it. If this simple procedure
has fixed the bug, it was most likely a corrupt or fragmented
file or am incompatible <.ocx> or <.dll> file
overwritten by another program you installed after installing
our software.
Errors
involving the screens not fitting on the display properly:
(Back
to Top)(Back
to FAQ)
Go to
your Windows Control Panel. Select Display. Go to Settings
and select the 600 x 800 resolution. The program will
run at 480 x 640 resolution 600 x 800 and 768 x 1024 resolution.
On most computers that have any screen sizing problems,
it seems to run best at 600 x 800. At resolutions ABOVE
768 x 1024, the program will run but sometimes does NOT
size properly, so run it at 768 x 1024 or below.
Errors
involving the NutriCode color bars looking a lot different
from the ones displayed on the web page: (Back
to Top)(Back
to FAQ)
Your
computer monitor may not be set up to show all the necessary
colors. Go to the Display settings option in the Windows
Control Panel and select high color 16 bit or other higher
color options (the NutriCode colors will not display properly
at 256 colors or less levels.)
Errors
involving text and/or color bars seeming too small: (Back
to Top)(Back
to FAQ)
Try switching
to the 640 x 480 screen resolution or use the large font
features in Windows 95. You will find these under the
Display icon in the Control Panel under the tabs called
Settings (go to the Fonts section) and in Appearance under
Schemes. Use the Windows Standard Large or Windows Standard
Extra Large options. Also check the Accessibility Options
in the Control Panel for additional vision impaired features.
Errors
involving the program running slow: (Back
to Top)(Back
to FAQ)
Although
the program will run on a 486-processor machine with 16
megabytes of memory, it was designed to run much faster
at Pentium speeds with 16-32 megabytes of memory. Keep
in mind that this is a large program with calculation
intense data base features that are not available in any
other program.
Fix
four, if the above fixes did not resolve the problem,
we will need more information to help get this fixed: (Back
to Top)(Back
to FAQ)
You
will need to fill out the bug report at the end of this
email and return it to us. In filling out the bug report
you may even discover some other likely causes for the
problem that you are experiencing. If you have the Pro
version, use the HK bug report. If you have the Basic
version, use the Basic bug report.
As
soon as we get your bug report our technical support and
if necessary programming staff will review it and get
back to you with solutions.
General
Advise relevant to most error messages: (Back
to Top)(Back
to FAQ)
Error
messages or error dialog boxes have appeared and a feature
won't work Click OK in the Error box and try the feature
again. If this doesn't work, click OK in the Error box
and switch to another mode then back to the original mode
and try the feature again. If this doesn't work, close
the program, re-open it and try the feature once more.
Next, reboot the computer and retry the feature. Many
times these simple procedures will solve the problem so
you can re-enable the feature. If the problem still persists,
e-mail us using the Bug report in a later section of this
email.
Other
reasons for bugs suddenly appearing in functions that
had been running correctly: (Back
to Top)(Back
to FAQ)
One reason
a bug may appear in a program that has been running well
for some time is that a file in the HealthKeeper program
has been corrupted or fragmented by the normal wear and
tear of regular hard drive use. Problems of corrupted
or fragmented files bugging out your programs can me minimized
by regularly doing computer "housekeeping" by
running the Microsoft System Tools Scan Disk and Disk
De-fragmenter.
Another
reason a bug may appear in a program that has been running
well for some time is that another program has been recently
installed on your computer that has overwritten key Performance
Diet <.ocx> or <.dll> files with older or
newer incompatible versions of similar Microsoft <.ocx>
or <.dll> files. This type of new bug in a program
that has been running well can often be fixed by de-installing
the HealthKeeper and reinstalling it. If this simple procedure
has fixed the bug, it was most likely a corrupt or fragmented
file or am incompatible <.ocx> or <.dll> file
overwritten by another program you installed after installing
the HealthKeeper.
Strange programs pop up while I am attempting to install
Performance Diet:
(Back
to Top)(Back
to FAQ)
Do not save to, or
install from, "My Documents" or any similar Windows
default directory.
What we need to achieve is
that your HK400.exe is not in the default Windows download
directory. Please try this.
Search your machine for
HK400.exe
Move HK400.exe to a different directory folder.
Launch HK400.exe from the new directory folder.
|
