If your two robots are the same in their I/O setup with their welding systems, you can probably copy most (all?) of the settings from the good robot to the bad one.
Probably the best way to do this is grab the Kawasaki manuals available at
http://www.robot-forum.com/robotforum/kawasaki_robots/d_controller_operations_manual-t3316.0.html, particularly the AS reference manual. Then make a full backup of each robot. Pull the backups onto a computer (they should be .AS files, which are simply text files that contain most of the settings in a Kawasaki), and compare them using a program like UltraCompare (expensive) or KDiff3 (free). You'll have to work out which differences are important (the AS language manual will help here). One of the nice things about Kawasakis is that you can add/remove chunks to an .AS file, then load it back into the robot -- as long as you have the syntax and the header/footers correct, it'll take. You can copy programs or certain settings between robots this way.
You could also put the teach pendants side-by-side and go through all the setup menus, setting the new robot to match the old one.
One thing: the SPG program runs on a separate board from the "main" program board (actually, the SPG runs on the I/O board). The SPG program you see in your .AS file is a text "source code" file that resides in the main board's memory, but the SPG that
runs is a compiled version that runs on the I/O board. This means that if you copy the SPG program from one robot to another, or make an edit to the SPG program, you have to complete one more step to have the new SPG actually running: download the SPG from the main board to the I/O board. There's an Aux menu function that will do this. You can also do it using the command "sd" from the terminal screen or over KC-Win. You will have to Stop the SPG, then Download, then Start it again.
The sections of the AS Reference Manual that deal with Editor Commands and Monitor Commands will tell you a lot about how you can use KC-Win and/or the terminal screen on the pendant. Using KC-Win is a lot like logging into an old 1970 mainframe over a serial terminal, but it can be very handy for troubleshooting and code debugging.