SCOUG-HELP Mailing List Archives
Return to [ 01 |
April |
2003 ]
<< Previous Message <<
>> Next Message >>
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
I've been experimenting with making an OS/2 boot CD to replace booting
from floppies.
I've tried two different methods and each runs into a different problem.
One method is to create a virtual 2.88 floppy disk and use Bootos2 to
create a bootable floppy on the virtual floppy. I then add the file,
CD_BOOT.FLT to the virtual floppy and edit config.sys to include a basedev
statement for that file. I then use RSJ to burn the virtual floppy to a CD
as an image.
When I boot from this CD, I get the error message:
Unable to find Resource.sys in default path or path specified . . .
The other method was to put the files from the first two installation
floppies (there are three altogether) into the virtual 2.88 disk and
create the boot image file from that. In this case I get the first big
screen asking me to Insert Disk #1 and press Enter. From there nothing
happens.
I'm not sure how to get around these issues, and wonder if anyone has any
suggestions.
Thanks,
Sandy
=====================================================
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
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 01 |
April |
2003 ]
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.
|