Version 1.0
	
      - Initial version

    Version 1.01

      - New features:

	New command-line option: -m, which tells P to do minimal
        escaping and thus somewhat improve the throughput in some
	cases. Refer to README.TXT for detailed information.

	An ICON, not really an important feature, but had some spare
	time and didn't feel like coding...

      - Changes:

	Ymodem-g, Ymodem and Xmodem transfers can now be cancelled
	remotely with 5 consecutive CAN (Ctrl-X) characters. Version
        1.0 needed only 2 CANs. The reason for this change is to make
	the cancellation consistent with Zmodem's, which has always
	needed the 5 CANs.

      - Bugfixes:

	BUG: Received last modification time information with Zmodem,
	     Ymodem and Ymodem-g transfers was not used. Received
	     files' time was always the time of receiving.

	FIX: Now it will be what the sender tells it should be.

	BUG: P changed the communication device configuration (timeout
	     processing, etc.), but didn't restore the original
	     settings always upon program exit.

	FIX: Now the original parameters are restored unless a serious
	     error occurred.

	BUG: Some Zmodem implementation don't follow the specification
	     I have. For example TE/2's internal Zmodem	sends the file
	     information block without a null-termination. This caused
	     P to abort the transfer with an error message and
	     therefore prevented Zmodem file transfers from TE/2 to P.

	FIX: This version of P gives only a warning message if a null
	     termination is missing from a place where it isn't
	     absolutely necessary.

	BUG: If there wasn't enough disk space for the file received
	     with Zmodem, the transfer wasn't aborted properly and the
	     sending program might have thought that the transfer was
	     succesful.

	FIX: Now it will be aborted.

	BUG: P didn't support ZCRC headers and when one was received
	     an error message with beeps was displayed and the transfer
	     was probably unsuccesful. probability

	FIX: When a ZCRC request is received, a dummy ZCRC response
	     header will be sent quietly.

	BUG: P didn't recognize escaped ASCII 127 and ASCII 255
	     characters and gave the message "Invalid ZDLE escape
	     sequence received" for them and prevent the transfer from
	     proceeding. This error occurred at least with Simplex/2's
	     internal Zmodem.

	FIX: Those characters are recognized and de-escaped properly.

	And some minor cosmetic fixes that I don't consider worth
	mentioning...

				- - -