wrote:
> I ran both check_cd.sh and check_cd.cmd.
> check_cd.sh ran without errors.
> Check_cd.cmd reported a couple of missing files
> reports which is expected
> given the production process, albeit a bit stupid.
>
> The following errors are expected
--------
> >>Does this mean the cd is suspect ?
>
> It points at the CD or your hardware. You might
> retry the check while
> booted to a different system or a different
> installation.
Thanks, Steven. I'll look into this and let you know
what I find.
Jordan
=====================================================
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 [ 26 |
January |
2006 ]
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.