Fax store panics in Fax Store

Fax store panics are caused by incorrect use of the API — e.g. passing bad or contradictory values to class constructors or member functions.

The thread causing the panic is terminated.

0	This panic is raised as a result of an attempt to index a non-existent scan line. For example, if there are 200 scan lines in the store, and the user issues a `CReadFaxPages::SeekScanLine()` call for the 201st scan line, this panic will be raised.
1	This panic is raised as a result of an attempt to index a non existent band. Fax pages are constructed, and stored as, a collection of bands - for efficient storage and fast display.
2	This panic is raised as the result of an attempt to index a non-existent page. For example, if there are 5 pages in the file, and the user issues a SetPageL() call for the 6th page, this panic will be raised.
3	This panic is raised as the result of an attempt to decode a scan line which is not correctly aligned. A scan line is misaligned if the 2 lowest significant bits of the first byte are not set to 1 - usually due to corruption.
4	This panic is raised as the result of an attempt to encode a scan line which is not correctly aligned. A scan line is misaligned if the 2 lowest significant bits of the first byte are not set to 1 - usually due to corruption.
5	This panic is raised if there is an attempt to set the compression parameter as anything other than EModifiedHuffman or EModifiedRead. This is most likely to occur when using CFaxT4::PageInitialise().