>>> KGL Error   : page: 1, image: ), after occurance 0 of 'KDKImageOptions'
>>> KGL Error   :  [11] - no image(s) found
>>> Job ABORTED by KGL Interpretor

We have seen this error in the field.  In our case, the error page printed only when print jobs were sent to the iR110
The problem was the iR110 SPC licence key was for a Duplicator only.  You cannot print to a Duplicator.

Another clue to this type of situation is the iR110 startup page.
A duplicator will not print any connectivity information on the startup page.
TCP/IP and IPX information will not be on the startup page.
 
 

2.  How do I check the SPC licence key to verify the current iR110 configuration?
Right click on the desktop
Right click on programs
Left click on file manager
Browse to /etc directory
Type K or browse to the KEY_DATA file
Double click on the KEY_DATA file
The file should open up in a simple text editor
In brackets is the key machine configuration.
Confirm you do not have just a Duplicator
 
 

3.  There are so many ways to shutdown or restart the SPC.  What are they?
 
 

4.  Why are commands like "stop a" and "halt" so dangerous?
The Unix file system uses hard disk(s) and RAM.
Syncronization between RAM and the hard disk is very important.
Using aggressive commands like "stop a" and "halt" will stop this synchronization which can easily lead to a corrupt file system.
 
 

5.  I'm confused.  The trainers, training material and EOS tell me to use "Stop a" and "halt" freely
This information is incorrect.  Sorry.
Any knowledgable Unix person will agree.
These commands should only be used in Emergency situations.
Use gracefull commands instead
 
 

6.  What does the term Gracefull and Un-gracefull shutdown or reboot mean?
When a machine or application is shut down or rebooted properly, it has the chance to clean up after itself.  This is considered a Gracefull shutdown or reboot
An aggressive shutdown or reboot of a machine or application does not allow it to clean up.  This is considered an Un-gracefull shutdown or reboot.

Commands like Init 0, Init 5, Init 6 are considered to be gracefull since they allow the operating system time to properly shutdown.
Commands like "Stop A", and "Halt" are considered un-gracefull for they do not care about the proper shutdown.
 
 

7.  I need to get the SPC to an OK prompt, what do I type?
 

My SPC is running the OCI interface and I can start a new terminal window.
Right click desktop
Right click programs
Left click command tool
Type su - and hit enter
Type the root password
Type init 0

My SPC is not running the OCI interface and I can start a new terminal window.
Right click desktop
Right click programs
Left click command tool
Type su - and hit enter
Type the root password
Type init 0

My SPC is not running the OCI interface and I cannot start a new terminal window.
This is a dangerous situation.  Your only hope may be 'STOP a'
Keep in mind that the Unix file system can be potentially corrupted
On the SPC keyboard, hold the keys "Stop" and "a" together
You should be at an ok prompt

8.  I need help with  # Prompt Commands like hostid and more key_data
 

9.  I need to adjust the TTYA Bit rate.  I need help.
Use Init 0 to get a gracefull OK prompt
Type obdiag
Type printenv to see current TTYA settings.
Type setenv ttya-mode 38400,8,n,1,-
Type printenv to confirm if changes took place
 
 

10.  What are the popular iR110 configurations?
 

11.  Is an ASPI layer required with the iR110 scanner?
Yes, ASPI32.exe must be installed.   Click here for more ASPI information
 
 

12.  When I try to run Netscape (EOS) the performance is very slow.  I am also getting a Netscape Lock file error.

You are probably getting an error similar to this one

Netscape has detected a /xx/xx/xx .netscape/lock file
This may indicate that another user is running netscape using your /xx/xx/xx .netscape files.
It appears to be running on xx under process-ID xxx
You may continue to use Netscape, but you will be unable to use the disk cache, global history or your personal certificates
Otherwise, you may choose cancel, make sure that you are not running another netscape navigator, delete the /xx/xx/xx .netscape/lock file and restart Netscape

13.  What is a Netscape Lock file and how does it get created?
Lets say a user named ISGSP starts Netscape to use EOS
Netscape spawns a process which is assigned a process ID (PID)
This (as well as all other processes) require resources.
Netscape requires access to the file system for caching, history...
It will create a lock file stored in the home/.netscape directory of the user ISGSP
The Lock file is identified by an IP address and the Process ID (PID)
The lock file identifies what part of the file system is locked and inaccessable for future instances of the process
If for example ISGSP starts a second Netscape process, a warning indicating caching, history will not be available.
The warning error will actually point to the location of the lock file.  Write it down!!!!
You can still run this second instance of Netscape but without access to caching and history it will run very slowly.

Normally, if Netscape is shut down gracefully, the lock file is also deleted.
The lock file will however remain in non-gracefull shutdowns  (Halt, Stop A, Power off...)

If a lock file error occurs, it is necessary to find and delete the lock file
 
 

14.  How do I delete the Netscape lock file?
Close all instances of Netscape.
Start a new terminal Window (Right click desktop, Right click programs, Left click command tool)
Do not use SU to switch user.  Service is the owner of the Netscape lock.  You should still be logged in as "service".  You can type "who" to confirm
Type the following;
rm $HOME/.netscape/lock
This command deletes any lock file located in the home/.netscape directory of the current user.
 
 

15.  I need to see the Logs created on the SCS
A utility called capture_logs is available to create a tar.z compressed file of many logs on the SCS
The only file you need to obtain is loginfo.tar.Z
Once created, you can connect your laptop and use an internet browser to get the file

Here is a quick Log file creation and transfer method

Creating the Log file
1.  On the SCS, open a command or shell tool
2.  Type su - and type the root password
3.  Type  capture_logs
4.  You will be prompted for a directory name.  Use logfile for simplicity
5.  After about 15 seconds, the log file will be ready.  It is normal for several errors as it processes

Transferring the Log file
1.  Connect your laptop to the iR110 so you can ping the SCS.
2.  Start an internet browser
3.  Type ftp://root@xx.xx.xx.xx         xx.xx.xx.xx is the IP of the SCS
4.  You will be prompted to enter the root password
5.  Browse for the folder /var/logfile
6.  Double click on loginfo.tar.Z and save the file on your computer (2.5MB)

Opening and reading the Log file
1.  Use Winzip or equivalent to decompress the file
2.  Use Notepad or equivalent to read the file
 
 

17.  I need help installing the CoXist filter on the iR110
(This is currently a rough collection of my notes.  I hope to clean it up soon)

1.  Obtain the correct version of coXist filter and documentation.
2.  Copy *.tar.z downloadables to floppy and use SCS file manager to mount floppy, copy files to /tmp, uncompress and extract install.cus
3.  Install.cus instructions are provided in coXist 3.0 PDF.  Main undocumented issue is licencing the filter.  Program is filter.xrx.v1 enter correct password for host ID
4.  Vi commands are diffuculy for any newcomer.  Recommend using setenv EDITOR textedit and much simpler editing tool.
5.  Run launcher.prt
6.  Creat print queue xrx_jobs, Total job size bytes checked, Accepting Releasing.  No entries to Printer type, Printer were done.  Normal executable
7.  Create another queue Name is coXist  Process Q  Change path to executable to /opt/HDcustom/7025/bin/filter.xrx
8.  Three filters after completion

coXist  with filter
XRX_jobs with our default filter
default_IR110 (native)

18.  I need help using the Tape Backup on the iR110
Click here for help with the iR110 Tape Backup

19.  I need some help with viewing and editing cron
"cron executes commands at specified dates and times. Regularly scheduled commands can be specified according to instructions found in crontab files in the directory /var/spool/cron/crontabs. Users can submit their own crontab file via the crontab(1) command. Commands that are to be executed only once can be submitted using the at(1) command."

Here is a quick way to view/edit the root crontab entry
su to root
#sh
#EDITOR=vi   (If vi scares you try EDITOR=textedit)
#export EDITOR
#crontab -e
Do your edits and save
File is saved (you cannot edit it directly) to /var/spool/cron/crontabs/root

20.  I'd like to trap print jobs on the SPC for troubleshooting purposes.  I need help
Trapping a print job is pretty easy.  All you have to do is toggle the Queue releasing state to non-releasing and browse the SCS for a particular file
If you have more than one Queue, you should start at the top Queue first
A print job waiting in a Queue will have 3 files.
These files start with the letters cf, pf and df
They reside in /var/spool/kodak_print/Kdefault_iR110
The df file is linked to a hch or kgl file
Here is a ls of the /var/spool/kodak_print/Kdefault_iR110 directory

BenCourt# ls -la
total 18
drwxrwsrwx    2 daemon   daemon       512 Aug 29 10:22 ./
drwxrws---    3 daemon   daemon       512 Jul 19 09:57 ../
-rw-rw---x    1 root     daemon         5 Aug 29 10:22 .seq*
-rw-rw----    1 daemon   daemon       202 Aug 29 10:22 cfA0013BenCourt
lrwxrwxrwx    1 root     daemon        51 Aug 29 10:22 dfA0013BenCourt -> /var/spool/kodak_resources/rsrc_data/hch.4701.22544
-rw-rw-r--    1 root     daemon       897 Aug 29 10:16 ipslog
-rwxrw----    1 root     daemon        21 Aug 29 10:16 lock*
-rwxrwxrwx    1 root     daemon       749 Aug 29 10:22 pfA0013BenCourt*
-rw-rw-r--    1 root     daemon        37 Aug 29 10:16 status

You may have to use the date of the file to determine which is the one that you want
You can use FTP to transfer the file you require to your laptop.

21.  I am getting the error /var partition is full.  What can I do?
Files may sometimes be "orphaned" in /var/spool/kodak_resources/rsrc_data and/or /var/spool/kodak_resources/rip_data.
This can occur if there is a failure or reset sometime during the spooling/printing process.
These may be complete or partiial files.

Files that have been"orphaned" in rip_data, should be removed automatically after they have been there more than 5 days (Rel 4.x)

Release 5.x will provide cleanup of invalid files in rsrc_data.

Keep in mind that whenever there are jobs in the server queues (including "hold" queue) there will be valid files in rsrc_data that are the actual data files.
When manually removing files from rsrc_data, if data files for queued jobs are deleted, those jobs will not be able to print.