the Millennium Bug Toolkit run on one machine only?
When you purchase our software, you purchase a license
to use it on one PC. It will allow you to test and
re-test this machine as many times as you wish but
it may not be transferred from one machine to another.
For a quote on a large number of machines, including
any on a network, contact Computer Experts (UK) Ltd.
2.Under Windows 3.11 and
MS-DOS the machine hangs during the loading of the
On these older operating systems the amount of memory
that is available to an application is very important.
In these cases the TSR may be taking up too much valuable
base memory (the amount below 640k) Because of this
it's worth loading the TSR in to high memory. If you
are technically minded this can be achieved by changing
the line that loads the TSR in the autoexec.bat file
from `c:\tsrfix.exe' to `lh c:\tsrfix.exe'. If this
is a little confusing call us and one of our engineers
will guide you through the process.
disk claims to have been used before but it's the
In some cases the technique we use to protect our
software conflicts with a given machine. A quick call
to us here and we can have the software running again.
4.After the first
power down test the machine reboots as usual (Not
from the toolkit disk) why?
This is actually due to the setup of the machine.
In the PC's BIOS there is a setting called boot order.
You will find this set to `C,A' This means that the
PC will always look at the hard drive first. By changing
this order to `A,C' the machine will be caused to
look first at the A: drive (containing the Millennium
Bug Toolkit). Some machines have an option labeled
`disable floppy boot', which must be unset. There
are many different BIOSes which differ in their method
of setting this so you may need to consult the manual
that came with your computer for exact instructions
on how to do this.
can I print out the test results?
Please see the end of this FAQ, and request document
do I do if the TSR does not make my PC Millennium
We have a no fix - no fee policy - whereby, if, after
installing our software fix, your machine does not
pass all of our tests we will refund the full cost
of the software. However, please contact us first,
to make sure that there is no way we can help you
to resolve this problem
what machines will the Millennium Bug Toolkit TSR
Although we can provide testing software for most
of the PC hardware on the market today our fix is
only compatible with computers running the following
operating systems : MS DOS v3.3+, MS Windows 3.*,
MS Windows 95. We can, however, provide a self-booting
hardware tester that is independent of operating system.
This means that you can test the hardware of systems
running x86 versions of Windows NT, Unix (Solaris,
Linux, FreeBSD etc.), OS/2, OS/2 Warp, DR DOS and
Plan 9 among others. Do not run the program on Windows
98 beta - our program alters the time and date, and
Windows 98 beta thinks that it's expiry date is up,
and will cease to run. All Apple Macintosh machines
already have compliant Real Time Clocks.
and where are the software scanning results stored?
With the new software scanner there are 3 results
files: * FILES.LST - a list of all known files found
* APPS.LST - a list of all the identified applications
* UNKNOWN.LST - anything not identified With older
versions of the software scanning software, the scanning
results are stored in two separate files dependent
upon their status. It they are files that we detect
and have a compliance statement on they are stored
in `a:\software.log'. Any files not recognised are
stored in a file called `a:\millibug.log' along with
the hardware test results.
I have downloaded the demo version. Can I run it inside
We do not recommend this at all. A lot of people do,
but while the demo runs, it changes the date of the
Real Time Clock. There is a good chance that some
of your software currently running in Windows may
therefore get the wrong date. We therefore recommend
that the demo should be run from the A: drive, and
Windows 3.x should be closed down, while Win95 should
be restarted in DOS mode.
Millennium Bug Toolkit kept restarting Windows. Why?
Probably your boot sequence in the CMOS settings.
Most machines will try to boot from the A: drive before
looking at the C: drive. However this can be altered
so that it starts at the C: drive. In that case, despite
the fact that you have a bootable Millennium Bug Toolkit
in your A: drive, the C: drive will start first, and
the machine will run from that. Simply change your
CMOS settings. (And remember to set them back later
if you wish).
get the error `unable to write to millibug.log'
Check that the floppy is not write-protected.
the Toolkit run on NT?
We supply a hardware tester only which work for all
operating systems, including NT. The standalone version
will NOT test and fix NT, and you should NOT run this
in a command prompt window, as you will receive misleading
and inaccurate results. All versions of the toolkit
from 3.5 upwards can test and fix NT 3.51 or above.
You cannot install the Collation Software onto an
NT 3.51 machine.
happens if you scan my software but miss some programs?
Please send us details (see the manual for more information).
We will continually help you to get total information
on all of your programs.
I use the toolkit to scan my Novell Server?
Yes. Simply down the server, and then run the checks
as normal. You will not, unfortunately, be able to
check any of the files on the Novell Volumes, but
only the files accessible via DOS. We have tested
our TSR with Novell, and have found no problems with
it, so you may use our fix whilst the server is active..
have installed the TSR fix, but my machine still fails
If you have an Award Modular BIOS v4.50PG, then this
cannot be fixed. Award have made a statement to this
effect, and we regret to say that we cannot fix it
with software. Assuming that you don't have this BIOS,
then there are a few other things to check. Firstly,
is the fix in your AUTOEXEC.BAT? (use SYSEDIT to check
this). If it is being loaded here, try loading it
`high' (see question 2). If neither of these solutions
work, please reply to this email (see the end for
manufacturer say that my machine is compliant, but
it still fails one or more of your tests?
Is there something wrong with the testing? The testing
that the Millennium Bug Tool performs is very thorough,
based on a lot of research into Millennium problems
on PCs. We have regularly found that PC Manufacturer
claim that their machines are only compliant at a
given level, whereas our software requires the PC
to be 100% compliant at all levels of the hardware.
does my PC say `altering clock for daylight savings
time' when running Real Time Clock Viewer (Killer)?
If you are running Real Time Clock viewer under Windows
(not recommended) then Windows will think that you
have moved from Greenwich Mean time (GMT) to British
Summer Time (BST). Simply alter your clock. If you
have to run the Real Time Clock Viewer under Windows,
then you can goto Control Panel -> Settings -> Date/Time
-> Time Zone, and deselect `Automatically adjust clock
for daylight saving changes' If your query is not
answered by this FAQ then please use our technical
support form, and we will do our best to solve
How do I test the collation machine?
There are two methods. Either test the machine as
normal, using the Year2000 user login script, or by
running the CLIENT.EXE in the common files area. You
can also create a non-networked disk based client
and use that disk to test the machine. Make sure that
you close the collation software before initiating
testing. If your query is not answered by this FAQ
then please reply to this e-mail, giving us details
of all the steps that you have already taken to try
and fix this problem. Allow 1-3 working days for a
I have tested a network machine, but it hasn't appeared
in the Collation Machine - why?
After testing a network based client, you have to
log back onto the network, and run the toolkit software
again. The reason for this is that we disconnect from
the network (you obviously don't want a machine on
a network with it's date in the year 2000) - but to
copy the results to the collation machine, we need
an active network connection.. The second run of the
toolkit should take 2-3 seconds.