SCOUG-HELP Mailing List Archives
Return to [ 14 | 
October | 
2005 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
I downloaded the ISO file, unzipped it, ran the MD5 Checksum program   
against it (and got a matching check sum), and then burned a CD.  
 
I did this on my older PC where I'm still running eCS 1.13.  
 
I put the CD into the drive on my newer PC, where I'm running eCS 1.24,   
and opened it with Drives.  Noticing that there was a file in the root   
named Check-CD.CMD, I ran that.  It seems to compute a checksum for each   
and every individual file on the CD, and check it against the contents   
of file CHECKSUM.MD5, also in the root of the CD.  
 
This process runs for several minutes.  On the newer PC, it displayed   
the name of the last file in PSFONTS\PFM, then aborted.  I didn't write   
down the abort information.  When I look at CHECKSUM.MD5, there are five   
more files after that (all in the root), and the next one in the list is   
README.TXT.  I don't think any of the other files would have anything to   
do with whether the operating system installed correctly.  
 
I repeated this process on the older PC, and got the same result.  The   
output says:  
> PSFONTS\PFM\TNRBI.PFM  
> PSFONTS\PFM\TNRI.PFM  
>   
> SYS1808:  
> The process has stopped.  The software diagnostic  
> code (exception code) is  0005.  
>   
> [S:\]pause  
> Press any key when ready . . .  
 
The last several files named in CHECKSUM.MD5 are:  
> c4323c1e122eb377adcceed82ab31b4b *PSFONTS\TNRI.PFB  
> fef984ee018c4749faf20cacbc5ae7a0 *README.TXT  
> d0245c9886ef600167aa11bc7a2a44b2 *STARTUP.CMD  
> 1af7ba2dd939703e8a9ea40203fd58ae *check-cd.bat  
> f02f7a6591ab651ef50f4e6e79f99cb8 *check-cd.cmd  
> 35abf80d298aff1425a2b493a4368a2c *check-cd.sh  
 
Issuing HELP SYS1808 from a command prompt give the following helpful   
information:  
> SYS1808:  
> The process has stopped.  The software diagnostic  
> code (exception code) is ***.  
>   
> EXPLANATION: The program generated an exception that the system cannot  
> resolve.  The soft ware diagnostic code allows determination of what  
> type of exception was generated.  
>   
> ACTION: Correct the problem or try a different version of the program.  
 
Finally, I get to my question:  
Is my CD "OK" for use to upgrade my systems?  
Thanks,  
Colin  
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"postmaster@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 14 | 
October | 
2005 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
 
 |