SECTION 9
APPLICATION COMMAND INTERFACE PROGRAMMING GUIDE
2-9
ACI_E_OPEN_CCB_ALREADY_IN_USE:
An attempt to establish a logical connection to a physical device is refused by the Application
Command Interface due to the fact that the Command Control Buffer is already used for a logical
connection to a device.
ACI_E_OPEN_ILLEGAL_INQUIRY_MODE:
An illegal inquiry mode has been specified. Probably, an invalid major or minor interrupt number,
or an illegal Interrupt Request Level has been specified, or an illegal Exception Vector Number
has been specified. The value is also returned when the data within the inquiry mode are not
consistent. For example, if the MAILBOX mode is specified but one or more of the most significant
16 bits are set.
ACI_E_OPEN_ILLEGAL_RESPONSE_MODE:
An illegal response mode has been specified. Probably, an invalid major or minor interrupt
number, or an illegal Interrupt Request Level has been specified, or an illegal Exception Vector
Number has been specified. The value is also returned when the data within the response mode
are not consistent. For example, if the MAILBOX mode is specified but one or more of the most
significant 16 bits are set.
ACI_E_OPEN_ILLEGAL_DATA_EXCHANGE_MODE:
An illegal data exchange mode has been specified. This status is returned whenever one or
more of the least significant 30 bits are set.
ACI_E_OPEN_ILLEGAL_LOGICAL_DEVICE_NUMBER:
An illegal logical device number has been specified which cannot be translated to its
corresponding physical device code by the Application Command Interface.
ACI_E_OPEN_INSUFFICIENT_CCBS:
The Application Command Interface is not able to allocate a Command Control Buffer within its
internal Command Control Buffer list.
ACI_E_OPEN_DEVICE_ALREADY_IN_USE:
Another application already owns the physical device and no other can gain the ownership of this
device until the certain application releases the logical connection to the device.
ACI_E_OPEN_INSUFFICIENT_MEMORY:
The Application Command Interface cannot allocate the memory required by a device driver when
the device driver has to be activated upon the receipt of an OPEN.
ACI_E_OPEN_CANNOT_ACTIVATE_DEVICE_DRIVER:
The Application Command Interface cannot activate the device driver dealing with the physical
device.
Summary of Contents for SYS68K/CPU-40
Page 2: ...INTRODUCTION...
Page 3: ...This page was intentionally left blank...
Page 6: ...iii This page was intentionally left blank...
Page 8: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 1 2 Figure 1 1 Photo of the CPU Board...
Page 9: ...SECTION 1 INTRODUCTION 1 3 Figure 1 2 Block Diagram of the CPU Board...
Page 34: ...SECTION 1 INTRODUCTION 2 21 Figure 2 2 The Front Panel of the CPU Board...
Page 35: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 2 22 This page intentionally left blank...
Page 37: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 3 2 This page intentionally left blank...
Page 42: ...INSTALLATION...
Page 43: ...This page was intentionally left blank...
Page 45: ...This page was intentionally left blank...
Page 47: ...ii This page was intentionally left blank...
Page 53: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 1 6 This page intentionally left blank...
Page 57: ...HARDWARE USER S MANUAL...
Page 58: ...This page was intentionally left blank...
Page 64: ...vi This page was intentionally left blank...
Page 66: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 1 2 This page intentionally left blank...
Page 83: ...SECTION 3 HARDWARE USER S MANUAL 3 13 Figure 3 2 Location Diagram of the System EPROM Area...
Page 92: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 3 22 3 5 6 Location Diagram of Jumperfield B16...
Page 141: ...SECTION 3 HARDWARE USER S MANUAL 3 71 Figure 3 25 Location Diagram of Header B12...
Page 152: ...SECTION 3 HARDWARE USER S MANUAL 4 3 Figure 4 1 Front Panel of the CPU Board...
Page 153: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 4 4 This page was intentionally left blank...
Page 172: ...SECTION 3 HARDWARE USER S MANUAL 6 17 Figure 6 2 Location Diagram of Jumperfield B19...
Page 179: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 6 24 Figure 6 4 Location Diagram of B13...
Page 187: ...APPENDIX TO THE HARDWARE USER S MANUAL...
Page 188: ...This page was intentionally left blank...
Page 190: ...ii This page was intentionally left blank...
Page 194: ...SYS68K CPU 40 41 FORCE COMPUTERS B 2 This page was intentionally left blank...
Page 202: ...SYS68K CPU 40 41 FORCE COMPUTERS C 8 This page was intentionally left blank...
Page 204: ...SYS68K CPU 40 41 FORCE COMPUTERS D 2 This page was intentionally left blank...
Page 206: ...SYS68K CPU 40 41 FORCE COMPUTERS E 2 This page was intentionally left blank...
Page 207: ...SECTION 4 APPENDIX TO THE HARDWARE USER S MANUAL E 3 E 1 Circuit Schematics of DRM 01...
Page 208: ...SYS68K CPU 40 41 FORCE COMPUTERS E 4 This page was intentionally left blank...
Page 209: ...SECTION 4 APPENDIX TO THE HARDWARE USER S MANUAL E 5 E 2 Circuit Schematics of SRM 01...
Page 210: ...SYS68K CPU 40 41 FORCE COMPUTERS E 6 This page was intentionally left blank...
Page 213: ...SECTION 4 APPENDIX TO THE HARDWARE USER S MANUAL F 3 Location Diagram for All Jumperfields...
Page 214: ...SYS68K CPU 40 41 FORCE COMPUTERS F 4 This page was intentionally left blank...
Page 226: ...SYS68K CPU 40 41 FORCE COMPUTERS I 2 This page was intentionally left blank...
Page 228: ...COPIES OF DATA SHEETS...
Page 229: ...COPIES OF DATA SHEETS RTC 72423 DUSCC 68562 PI T 68230...
Page 230: ...USERS NOTES...
Page 231: ...USERS NOTES...
Page 232: ...USERS NOTES...
Page 233: ...OPTIONS APPLICATIONS MODIFICATIONS...
Page 234: ...INTRODUCTION TO VMEPROM IN USE WITH THE SYS68K CPU 40 41...
Page 246: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 1 10 This page was intentionally left blank...
Page 252: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS 2 6 This page was intentionally left blank...
Page 264: ...SYS68K CPU 40 41 FORCE COMPUTERS 4 10 This page intentionally left blank...
Page 268: ...APPENDIX TO THE INTRODUCTION TO VMEPROM...
Page 285: ...SYS68K CPU 40 41 USER S MANUAL FORCE COMPUTERS D 4 This page was intentionally left blank...
Page 319: ...THE APPLICATION COMMAND INTERFACE PROGRAMMING GUIDE...