User manual

128
devices that it determines are capable of fax communications. If SCD is making two calls to all
numbers, use checkmodems.exe to make sure that your particular modem supports SCD.
• While trying to add a range of numbers to a profile, PhoneSweep only adds a sub-range of
the numbers. This is probably due to a boundary condition. Add the numbers that were missed
separately, and contact Sandstorm Enterprises to report the problem. Note that in a single
command, PhoneSweep Basic won't add more than 800 numbers, and PhoneSweep Plus won’t
add more than 10,000 numbers.
• The system crashed while PhoneSweep was running and the database became corrupted.
This is an extremely rare condition, as the SQL database is tolerant of most system crashes.
However, recovery tools are available. Before using them, make a copy of the corrupted
directory. Then run the program dbfix.exe that is in the top-level PhoneSweep directory. Select
the corrupted database from the list and the recovery tools will be run on the database.
• The PhoneSweep report lists the scan as incomplete, even though the program says it is
100% complete. When scanning for both fax machines and modems, if calls to a modem in data
mode all result in Busy and PhoneSweep has made the maximum number of redials allowed,
PhoneSweep will not be able to initiate a fax call to the number and will not be able to complete
the scan. You can increase the value of Busy Redial on the Dialing sub-tab to complete the scan.
• On the Status tab, the Elapsed Time shown does not correspond to the Time Until Finished.
This is normal. The Elapsed Time increases after PhoneSweep starts sweeping whether or not
PhoneSweep is actually making calls, while Time Until Finished doesn't change unless calls are
being made.
• Call estimates seem unusually high. The Calls Remaining value is estimated as a worst-case
scenario. Before starting a sweep, it assumes that PhoneSweep will find a modem or fax machine
on every number called. If a Single Call Detect (SCD) call doesn’t find Fax or Carrier,
PhoneSweep takes care of two projected calls with that one call and the Calls Remaining are
reduced by two. For example, if you are running PhoneSweep in SCD mode to sweep two
numbers, the initial value of Calls Remaining is four. If both numbers respond as Voice or
Timeout, Calls Remaining will drop to two after the first call and zero after the second call.
• checkmodems.exe finds the Modems, but PhoneSweep does not (when I check under the
Modems sub-tab, the COM Ports are wrong). When running checkmodems.exe, note what
COM ports the modems are actually on. Then, go to the Modems sub-tab, and click on the box
under Port column for the modem in question. This brings up a pull-down menu where you can
select the correct COM port for each modem. Once you save any changes, PhoneSweep will find
the modems. Further documentation can be found in Section 4.5, Setting up your Modems. If
PhoneSweep continues to give you problems after this, please call PhoneSweep support.
PhoneSweep Error Messages
Error messages on install
• “A required DLL file WS2_32.DLL was not found”: This means that you do not have
WinSock 2.0 installed on your computer. Run the WinSock 2.0 installer w95ws2setup.exe that is
located in the top-level PhoneSweep directory. You will need to reboot your computer after
installing WinSock 2.0.
• “Move data error”: This error indicates a problem with the installation CD-ROM itself. The
CD-ROM could be scratched or have a defect that was not spotted during testing. If you
encounter this error, contact Sandstorm Enterprises and request a replacement CD-ROM. In rare