История изменений

There are also critical sections that need to be observed when running in a
; multitasking environment.  These sections are:

; ; This should *NEVER* return an error.	The transient is MUCH bigger than
; the batch segment.  This may not be true, however, in a multitasking system.
; G This error will occur with nesting of batch files.	We also need to
; G make sure that we don't overlay the transient.
;

;	WARNING NUMBER TWO:
935	;	    IF A MULTITASKING PRE-EMPTIVE SYSTEM SCHEDULES AND RUNS
936	;	    AN APPLICATION WHICH RELIES ON THE 1 MEG ADDRESS WRAP
4701	;
4702	; WARNING: IF A PRE-EMPTIVE MULTITASKING SYSTEM SCHEDULES A TASK WHICH
4703	;	IS USING THE ABOVE BOARD DURING THE TIME THIS DRIVER IS IN THE

;
;   Note that there is no multitasking interlock.  There is no race when
;   examining the entrys in an in-core FAT block since there will be no
;   This method is obviously useless (because it is non-reentrant) for
;   multitasking, and will have to be changed.  Storing the required value on
;   the stack is recommended.  Setting sf_firclus at the PACK of cluster 0

There are also critical sections that need to be observed when running in a
; multitasking environment.  These sections are:

; ; This should *NEVER* return an error.	The transient is MUCH bigger than
; the batch segment.  This may not be true, however, in a multitasking system.
; G This error will occur with nesting of batch files.	We also need to
; G make sure that we don't overlay the transient.
;

;	WARNING NUMBER TWO:
935	;	    IF A MULTITASKING PRE-EMPTIVE SYSTEM SCHEDULES AND RUNS
936	;	    AN APPLICATION WHICH RELIES ON THE 1 MEG ADDRESS WRAP
4701	;
4702	; WARNING: IF A PRE-EMPTIVE MULTITASKING SYSTEM SCHEDULES A TASK WHICH
4703	;	IS USING THE ABOVE BOARD DURING THE TIME THIS DRIVER IS IN THE