As MOM said, the I/O Configuration Errors can be blocked by commenting each driver in the DRIVERS section of C:\KRC\ROBOTER\INIT\IOSYS.INI.
Each driver that is not commented out (;) will be started when the robot boots, and since you have none of the hardware this robot was originally configured to communicate with, each of those drivers will throw an error.
Once you're ready to try connecting devices to the robot, you will need to examine the motherboard to see what I/O cards the robot still has.
[DRIVERS]
RSI=50,rsiLibInit,rsiLib.o
SSBDRV=22,SSBDRV1CPInit,ssbdrv.o
RSIATI=100,rsiATIFTSensInit,rsiATIFTSens.o
RSIFTC=102,rsiFTCFTSensInit,rsiFTCFTSens.o
RSIFT=103,rsiFTCtrlInit,rsiFTCtrl.o
;CNKE2=21,cnke2CPInit,cnke2drv.o
;DNSC6=20,dnsc6Init,dnsc6drv.o
;DNSC5=19,dnsc5Init,dnsc5drv.o
;DNSC4=18,dnsc4Init,dnsc4drv.o
;DNSC3=17,dnsc3Init,dnsc3drv.o
;CNKE1=16,cnke1CPInit,cnke1drv.o
;INTERBUSPCI=15,ibsCPPciInit,ibpcidrv.o
;DSEIO=14,dseIoInit,dseiodrv.o
;DNSC2=13,dnsc2Init,dnsc2drv.o
;DNSC1=12,dnsc1Init,dnsc1drv.o
PBMASL=11,pbmsInit,pfbmsdrv.o
;DEVNET=2,dnInit,dn2drv.o
;INTERBUS=1,ibusInit,ibusdrv.o
;MFC=0,mfcEntry,mfcdrv.oThe Mastering errors are b/c the axes need to be re-zero'd. Unless you have an EMT, you'll probably have to do this using the Dial Mastering method. This should be done using the correct dial indicator adapter, but can be done by feel if you're careful.
