Under certain circumstances such as a system failure, the results file and the progress file could be out of synchronisation. When THINK restarts it now checks that the files are compatible and if not restarts from after the last recorded hit. This should reduce or eliminate jobs being rejected because the results file is missing data.
Under battery power with 1.30b, THINK goes to sleep (after a short delay) and FaDsetup will not attempt to wake it until mains power resumes. This contrasts with 1.30a when loader would not start the software and FaDsetup put THINK to sleep.
Some internal and algorithmic changes have also been made.
Under Linux, "file not found" messages no longer occur during initial startup of the software.
It is now possible to run more than one copy of server. This is intended for use under Linux when manual downloads of jobs and uploads of results can be executed without stopping the "main" copy.
|Running networked clients as a service
A problem with networked clients has been resolved in 1.30b providing members specify a username that has network access when the software is installed/configured for those clients.
|Running networked clients as a service under Win9x
It is no longer necessary to specify as username and password (they weren't used anyway).
|Startup errors for networked clients
If something went wrong starting up the software on a network client, it was not possible to display a message (no access to desktop) or write to the logfile (no local network access). Under 1.30c, the software attempts to send an e-mail as well as write to loader.log in the same folder as loader.exe.
|Jobs often failed when upgrading from 1.25 to 1.30
1.30b resolves this problem.
|Jobs complete immediately when continued after no hits
This problem was reporting under Linux and has been resolved in 1.30b.
|Query name and CPU time omitted from .tip files
Under Linux with 1.30a the computer.tip files did not include the query name or CPU time. This has been resolved under 1.30b.
|fadsetup.scr can crash THINK
Under Windows XP when FaDsetup is configured as the screensaver, it often causes THINK to crash when it starts. Under 1.30b fadsetup.scr is no longer present in Windows XP!
Under Linux there are no messages written to the screen during an upgrade (although there are to server.log and loader.log). This can cause confusion.