said:
>>Did I find the right file--27 pages dated 8-95.
>That's pretty old. The version that comes with v3.03 is:
>12-21-01 3:03 222,587 0 4os2.txt
>>Setting up seems simple, but putting all
>>files in place and changing PATH and DPATH in config sys don't give me a
>>working system.
>It is simple. 4os2, like cmd.exe, is a standard os/2 application and
>follows all the same rules.
>---
>Regards,
>Steven
4OS2 is now my default command processor. A dir command on a folder with many files now gives me a listing where before it wouldn't, but I still get an insufficient memory error when I try to drag a folder with too many subfolders and files to an RSJ-attached CDROM. There's nothing in the RSJ manual addressing this problem. An xcopy from a 4os2 command line doesn't complete either, but the 4os2 command copy /s does the job--all 25000 files in about 40 folders totaling over 200 Mbytes. Is there a way have 4os2 operate with drag and drop from one tree or icon view to another on the desktop?
My problem installing 4os2 was that I kept editing a libpath line in config.sys that had been rem'd out instead of the active line. Amazing how long it took to spot that.
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 [ 01 |
May |
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.