Ammendment: Change padding to end of PK files (appendix C) Ammendment number: 04 Submitted by: Don Hosek Date: 22 July 1990 Currently says: Status: RO pk_post 245 Beginning of the postamble. This command is followed by enough pk_no_op commands to make the file a multiple of four bytes long. Zero through three bytes are usual, but any number is allowed. This should make the file easy to read on machines which pack four bytes to a word. Change to read: pk_post 245 Beginning of the postamble. This command is followed by enough pk_no_op commands to make the file a multiple of four bytes long. Zero through three bytes are usual, but any number is allowed. This should make the file easy to read on machines which pack four bytes to a word. The pk_no_op commands may further be | followed by a number of 0's which will be a multiple of 4 (these | are generally added during a file transfer operation). | PK-writing programs should never add 0's to the end of the file. | [vertical bars indicate the changed portion] Reason for change: As noted above, when moving files between computers, additional 0's may be tacked on to the end of the file due to file transfers. This modification to the PK file format requires drivers to deal with this appropriately. ----- Ammendment procedure. You may vote "Yes", "No" or "Abstain" on this ammendment. You may change your vote at any time the ammendment is still on the floor. The status of votes on all ammendments will be sent to the voting members of the Driver Standards Group once every 2 days.