said:
>>Can now do a dir command, but don't find much guidance on setting up 4os2
>>to be the default command processor.
>Did you miss the guidance on page 57 of 4os2.txt?
>>Is that good to do?
>Works for me, but I say that a lot. :-)
>>The online
>>help refers to more information in printed documentation which probably
>>is not available as a digital file.
>Sure it is. See 4os2.txt.
>>Is more than putting SET
>>COMSPEC=c:\4os2.exe in config.sys required?
>Only a little. This is the from:
>REM 11/5/99 SET OS2_SHELL=F:\OS2\CMD.EXE
>REM 11/5/99 SET COMSPEC=F:\OS2\CMD.EXE
>and to:
>SET COMSPEC=D:\USR\BIN\4OS2.EXE
>SET OS2_SHELL=D:\USR\BIN\4OS2.EXE
>on this box.
>Regards,
>Steven
I had looked at 4 different 4OS2 archives; none included the file 4os2.txt. But having the name of the file, I did a Google on 4os2.txt and turned up 6 hits.
Thanks again. I think I'm good to go now.
Ben
--
-----------------------------------------------------------
Benedict G. Archer
-----------------------------------------------------------
=====================================================
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 [ 30 |
April |
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.
