Салям!
27-Мар-2004 12:50 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
>> >> LG> Bad news: the new build batch files don't do anything in 4DOS, probably
>> BO> it's picky about
>> BO> call config
>> BO> instead of
>> BO> call config.bat
>> And? [BTW, just check under freecom - also all works.]
>> PS: I not against of using explict extensions, but wonder what wrong in
>> given case?
BO> I looked a bit further, it was strange indeed...
BO> default is a builtin keyword in 4dos.
Aha, yes, I see. I have the same problem with ATTRIB under NDOS: I
can't call it directly ("ATTRIB" or "ATTRIB.COM", only ".\ATTRIB"), because
this is built-in command.
BO> So all that was necessary was to replace "call default" by "call
BO> default.bat".
No. :(
______________O\_/_________________________________\_/O______________
c:\>ver
4DOS 6,02B DOS 6,22
c:\>call default
Command only valid in batch file "DEFAULT"
c:\>call default.bat
Command only valid in batch file "DEFAULT"
c:\>call .\default
test
c:\>attrib.com
Invalid path "c:\temp\ttt\.com"
_____________________________________________________________________
O/~\ /~\O
Better solution will be to rename batch file to, say, DEFAULTS.BAT. Or
CONFIG2.BAT.
BO> Anyway, now we're consistent and guard against future 4dos versions having
BO> "config" as a keyword too...
No - see above. :(
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
