Using Tools: 11 pcs

Up: GEOS SDK TechDocs | Up | Prev: 10 pcget | Next: 12 pcsend

Once you have pccom running on the target machine, invoke pcs on the development machine to send your geode's executable to the proper place on the target machine. The pcs tool figures out which files to send (and which directory to send them to) via a number of rules set up in the ROOT_DIR\INCLUDE\PCS.PAT file. Thus it knows to send applications (files that end in .GEO) to the target machine's WORLD directory. (Note that the "/" and "-" characters in the flags below are interchangeable--hyphens are used with the n, S, and t flags by tradition.)

/I: IRQ
Communicate at a different interrupt level than pccom is presently using (this is a dangerous option).
-S file
Send all files mentioned in the file file.
/b: baudRate
Communicate at a different speed than pccom is presently using (this is a dangerous option).
/c: portNum
Communicate via a different COM port than pccom is presently using (this is a dangerous option).
-h
Get help.
-n
Send non-Error Checking version instead of EC.
-t token
Send all files associated with the named token (see below).

When using a token, pcs looks up the token in the INCLUDE\SEND file to determine which files should be sent. Generally all executables associated with an application, library, or mechanism are sent when the appropriate token is passed. Look in the SEND file to find out what the accepted tokens are and what they send. Suppose your send file consisted of the following lines:

PC		DRIVER/VIDEO/DUMB/HGC/HGC 					GEO
HGCAT 		DRIVER/VIDEO/DUMB/HGC/HGC 					GEO
PCB 		DRIVER/VIDEO/DUMB/HGC/HGC 					GEO
PCB 		DRIVER/MOUSE/LOGIBUS/LOGIBUS 					GEO
PCS 		DRIVER/VIDEO/DUMB/HGC/HGC 					GEO
PCS 		DRIVER/MOUSE/LOGISER/LOGISER 					GEO

Typing

pcs -t pc

would send the file DRIVER\VIDEO\DUMB\HGC\HGCEC.GEO (HGC.GEO if sending non-EC). Typing "pcs -S pcb" would send that file, and also DRIVER\MOUSE\LOGIBUS\LOGIBUSE.GEO (or LOGIBUS.GEO).


Up: GEOS SDK TechDocs | Up | Prev: 10 pcget | Next: 12 pcsend