The driver can generate some error messages.
Runtime errors (in numerical order):
(note, that the last 3 digits clearly identify the error within the
drivers messagemap)
Name (declared in FARC.H) | Number (dec) | Cause |
E_FARC_DRIVER_NOT_STARTED | 2 | Driver currently not started |
E_FARC_ABORT | 995 | Request cancelled due to Init/Deinit or reconfigration of network |
E_FARC_INCOMPLETE | 996 | Request pending (this is not an error) |
E_FARC_PENDING | 997 | Request pending (this is not an error) |
E_FARC_DRIVER_OPTION | 3758425001 | IoDeviceControl -Code not supported |
E_FARC_NO_TOKEN | 3758425008 | No token seen. (ARCNET Controller does not detect a valid token. May occur, if busrate does not match) |
E_FARC_NOT_INITED | 3758425018 | No IOCTL_FARC_INIT yet performed |
E_FARC_EXCESSIVE_RECON | 3758425021 | controller reconfigures network (No other nodes are on the net) |
E_FARC_BUFFER_TOO_SMALL | 3758425022 | output buffer size too small in call to DeviceIoControl |
E_FARC_NO_PARAMETERS | 3758425023 | dcb-struct invalid |
E_FARC_BAD_PACKET_SIZE | 3758425024 | WriteFile: wrong packetsize, ReadFile: wrong buffersize |
E_FARC_NO_ACTIVITY | 3758425029 | no netactivity deteced (ARCNET Controller does not detect any activity on the net) |
E_FARC_PERFORMING_DISABLE | 3758425031 | IOCTL_FARC_DISABLE_RECEIVE not yet finished |
E_FARC_NO_DISABLE | 3758425032 | no previous IOCTL_FARC_ENABLE_RECEIVE performed |
E_FARC_NOT_ACCESSIBLE | 3758425033 | only with sharcalyzer driver: COM20022 not accessible (sharcalyzer not started or COM20022 defective) |
E_FARC_READ_TIMEOUT |
3758425034 | ReadFile timeout occured. No
ARCNET data received within the previously set timeout (see also IOCTL_FARC_SET_READ_TIMEOUT) |
E_FARC_BAD_SID | 3758425037 | WriteFile: wrong Source ID (SID) |
E_FARC_NETMAP_ERROR | 3758425045 | no node or illegal node set for checking in IOCTL_FARC_NETMAP_SETTINGS |
E_FARC_NETMAP_PENDING | 3758425046 | IOCTL_FARC_GET_NETMAP just pending |
E_FARC_NETMAP_NO_CHANGE | 3758425047 | No netmap change detected |
E_FARC_DUPID | 3758425052 | duplicate node-id detected (another node is online with the same node id) |
E_FARC_NO_RESPONSE | 3758425055 | destination node does not respond |
E_FARC_NO_LONG_PACKETS | 3758425056 | destination node does not support long packets |
E_FARC_INIT_FORCED | 3758425058 | init forced, inspite of no token or no netactivity |
E_FARC_NO_NEXTID | 3758425059 | no new-next-id received during initalization (see also FAQ) |
E_FARC_WRITE_DENIED | 3758425061 | currently no transmission page free |
E_FARC_NAK_TX | 3758425070 | destination node does not acknowledge transmitted packet |
E_FARC_INITIALIZING | 3758425071 | ReadFile/WriteFile not accepted, because init running |
E_FARC_BAD_PARAMETER | 3758425087 | wrong parameters in dcb detected (e.g. nodeid = 0) |
Startup Errors (during start of driver):
Number in Windows NT |
Number in Windows 2000 (Event ID) |
Cause |
8 | 23 | 90C66 adapters only: DPR of adapter is not visible, setup your BIOS to enable the used ISA memory |
57 | 194 | No ARCNET-adapter found in system at given I/O-Adress. Possible cause: NodeId switch (SHARC66) |
60 | 197 | wrong controllertype (if using a PCI-adapter with NT 4.0, try „Reset Card-ID“ (see also Configuration) |
87 | n.a. | Resource conflict (I/O-Adress or IRQ) or invalid parameters in registry |
317 | 618 | main vendor identification wrong or missing |
487 | n.a. | Resource conflict (memory-mapped adress, check jumpers on adapter) on ISA-Adapter. If using PCI-Adapter, swap the used slot with the slot of another PCI-adapter (Bug in PCI-Bios) |
1018 | 380 | Some or all registry entries missing (reinstall driver) |
1450 | 154 | not enough ressources to start the driver |
1388 | 379 | PCMCIA adapter is not a SH ARC-PCMCIA adapter |
50 | 187 | used ARCNET adapter is not compatible to SOHARD ARCNET adapter |
If you get other errors during startup than listed above, please report with detailed system description to support.sohard.de.