Ammendment: Change padding to end of GF files (appendix B) Ammendment number: 03 Submitted by: Don Hosek Date: 22 July 1990 Currently says: Status: O post p[4] ds[4] cs[4] hppp[4] vppp[4] min_m[4] max_m[4] min_n[4] max_n[4] post_post q[4] i[1] 223's[>= 4] [and later] Most operating systems permit random access to individual words or bytes of a file, so the GF reader can start at the end and skip backwards over the 223's until finding the identification byte. Then it can back up four bytes, read q, and move to byte q of the file. Change to read: post p[4] ds[4] cs[4] hppp[4] vppp[4] min_m[4] max_m[4] min_n[4] max_n[4] post_post q[4] i[1] 223's[>= 4] 0's [>=0] | [and later] Most operating systems permit random access to individual words or bytes of a file, so the GF reader can start at the end and skip backwards over any 0's inserted due to file transfer then | skip over the 223's until finding the identification byte. Then it can back up four bytes, read q, and move to byte q 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 GF 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.