Van professionele vertalers, bedrijven, webpagina's en gratis beschikbare vertaalbronnen.
the handler should be a function that accepts a generic object that will have type , errortype , code , and info properties:
le gestionnaire devrait être une fonction qui accepte un objet générique avec les propriétés type , errortype , code et info :
table 1______________________________________sc - start chaptertype of frame 2 bytes 000hvolume name 12 bytesidentifier 2 bytes chapter number in ascii (01 for the first one)ip station 2 wordssdt chaptertype of frame 2 bytes 100hvolume name 12 "identifier 2 " chapter number in asciisdt chapter frame mask 1 " 1 bit set per framesdt chapter max frame mask 1 " all the settable bits setfirst data segment 2 "second data segment 2 " 0 if noneoffset in sdt the following 2 "cards are to be put innumber of following cards 2 "cards 8 " each sdcsdc sector description cardsector number 2 bytessector alias 2 " (o if none)offset 2 " offset in floppy cache (segment indicated by segment number bit)filling value 1 bytestatus 8 bits 7 6 5 4 3 2 1 0 x----------------- received-x--------------- used---x------------- keep forever-----x----------- segment number-------x--------- filling value----------------x specifique data sector (used by server program, not transmitted)______________________________________ table 2______________________________________sdt errortype of frame 2 bytes 200hvolume name 12 bytesidentifier 2 bytesip station 2 wordssdt chapter 1 byteframe masksdc - specific data chaptertype of frame 2 bytes 401hvolume name 12 bytesidentifier 2 bytes chapter number in asciioffset of 1st 2 bytessdt cardoffset of 2nd 2 bytes (o if none)sdt cardethernet address 6 bytesdata 512 ou 1024 bytesde - data errortype of frame 2 bytes 800hvolume name 12 bytesidentifier 2 bytes chapter number in asciinumber of sectors 2 bytesmissingsectors numbers 2 bytes for each sectorec - end chaptertype of frame 2 bytes 1000hvolume name 12 bytesidentifier 2 bytes chapter number in ascii______________________________________ table 3______________________________________erb - end remote boottype of frame 2 bytes 2000hvolume name 12 bytesidentifier 2 bytes chapter number in asciissd specifique sector requesttype of frame 2 bytes 4000hvolume name 12 bytesidentifier 2 bytes chapter number in asciisector number 2 bytesssr - specifique sector replytype of frame 2 bytes 4001hvolume name 12 bytesidentifier 2 bytes chapter number in asciisector number 2 bytesdata 512 bytes_____________________________________
note : les segments 0d000h et/ou 0e000h, s'ils sont utilisés, ne sont par libérés après la réception de "end remote,boot", c'est à dire précisément, que : sur réception de la sdt du chapitre 1, après reconnaissance des segments de travail 0d000h et/ou 0e000h, ces mêmes segments sont validés. sur réception de "end_remote_boot", ces segments ne sont pas dévalidés. d'autres modifications, à la portée de l'homme de métier font également partie de l'esprit de l'invention