|
DataMuseum.dkPresents historical artifacts from the history of: CR80 Hard and Floppy Disks |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CR80 Hard and Floppy Disks Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 4886 (0x1316)
Types: TextFile
Names: »RELDESCR.T«
└─⟦1dc3ed39a⟧ Bits:30005066 8" CR80 Floppy CR80FD_0003 ( Id. O.K Vol. FLOPPY VOL: NSS )
└─⟦02b6ff5ea⟧
└─ ⟦this⟧ »TDXDR.851216.D!RELDESCR.T«
«ff»
Release description.
====================
Module id number: 0314
Module name: AMOS TDX Driver
Actual release: 0109' Release date: 851216
Previous release: 0109 Release date: 821019
New facilities:
>> Release 0109' <<
0109' APE/851216 NEW FIKS-VERISION - MORE RESOURCES
MAXLINES := 100, MAXTPC := 100
TDXDR MADE TO FIKS-DRIVER PROCESS
>> Release 0109 <<
0109 TLM/821018 - A NEW VERSION, WHICH IS ABLE TO RUN ON A
CPU WHICH DOES NOT SWAP THE PAGE BITS IN THE
PSW.
NOW FOUR VERSIONS EXIST :
STANDARD
DORA
FIKS
STANDARD FOR NON-BIT-SWAPPING CPU
- THE PSW USED, WHEN SWITCHING BETWEEN PAGES
IS CHANGED FROM #E800 TO #E000, SO THAT
EMERGENCY ACTION IS NOT CAUSED.
- EXECUTION LEVEL IS SET TO ONE, TO CONFORM
TO XAMOS CPUS, WITH BOUND CHECK.
>> Release 0107 <<
0107 TLM/820505 IN SOME SPECIAL CASES, THE TDX DRIVER WOULD
RETURN A COMPLETION CODE EQUAL TO 0 AND
TRANSFERRED BYTES EQUAL TO 0 AS A RESPONSE
TO AN OUTPUT COMMAND. THIS CONDITION CAUSES
THE AMOS I/O SYSTEM TO CONVERT THE COMPLETION
CODE TO END-OF-FILE (#201).
THIS TDX DRIVER ERROR IS CORRECTED IN THIS
VERSION (EVEN THE DORA SPECIAL PROTOCOL).
>> Release 0106 <<
0106 BB/820211 ***- INDIVIDUAL OUTPUT TIMER.
*** IT IS NOW POSSIBLE TO SET THE
*** OUTPUT-TIMER-PRESET PER CHANNEL AT
*** CREATION TIME (ONLY WITH FIKS OR DORA
*** VERSIONS)
>> Release 0105 <<
0105 TLM/811023 - IT IS NOW POSSIBLE TO START A DATA
TRANSMISSION, WITH THE TLE POINTING
TO THE UPPER BYTE OF A WORD.
- THE CONSTANT OUTPUT-TIMER-PRESET, WHICH
DEFINES THE MAX WAITING TIME FOR TIMEOUT
ON OUTPUT OPERATIONS, IS MADE A VARIABLE
SO THAT IT IS EASY TO CHANGE BY PATCHING.
AT THE SAME TIME THE VALUE IS DECREASED
FROM #7F TO #3F.
- A MAXIMUM WAITING TIME FOR A HOST INTERFACE
ASSIGNMENT IS IMPLEMENTED. NOW IT ONLY
WAITS FOR THE MAX TIME, AND IF THE HOST I/F
HAS NOT BECOME READY WITHIN THAT TIME, AN
ERROR MESSAGE (#603) IS RETURNED TO THE
CALLING PROCESS.
AT PRESENT THIS MAX TIME IS SET TO TWO
MINUTES.
LKN/811023 - THE END OF PACKET INDICATION IN THE LAST
DATA BUFFER LINK OF A PACKET IS NOW SET
BEFORE THE LAST DATA BUFFER LINK IS
LINKED TO THE LIST (BY USING 'QUEUE LAST
DATA BUFFER LINK' (QLDBLI/QLDBLO) WHEN
INSERTING THE LAST DATA BUFFER LINK.
>> Release 0104 <<
WORD 12 OF A PROTOCOL DESCRIPTOR IS
NOW CLEARED IN EACH CREATION OF A
NEW LOG. LINE
>> Release 0103 <<
If a parity error is discovered in the Host Interface memory,
the TDX Driver makes a reset of the Host, and terminates
with the code #602.
>> Release 0102 <<
Cancel implemented. This demands a change in TDX Host Interface
firmware, which is not implemented yet (actual date is 810512).
>> Release 0101 <<
Initial release.
«ff»
Changes:
>> Release 0108 <<
The input cancelling is changed to reduce the time spent by
applications waiting for cancel reply.
Errors corrected:
>> Release 0108 <<
Changed host i/f processing for flow control had introduced a critical
hazard between driver and host i/f. This error has been removed by
changing the driver processing when setting up transfers.
>> Release 0103 <<
If there were retransmissions in the actual transfer, the TDX Driver
would return an incorrect bytecount of transferred bytes.
>> Release 0102 <<
With two or more channels open to the same device, dismantling of
one of them would imply total closedown of the channel.
Reported errors, not corrected:
>> Release 0103 <<
It is not possible to transfer data correctly, if the transmission
is to start with an upper byte of a word.
Comments:
«ff»
«ff» «a5»