World: r3wp

No need for me to press enter.
Pekr, is your error true for all types of files?
Is capitalization a problem here? (try capital "C:".)

Are you on Vista, isn't the "windows" directory a protected system 
directory - perhaps that's causing an issue.

Vista, 32 bit. No difference with capitalisation ... I will try with 
fresh console ...

dir C:\
 - no difference ...

it does not seem to know Dir - maybe a path lookup problem?

Try just "dir".

Try other commands: call "cmd" ...

hehe, interesting - I run call "cmd.exe" and now I seem to get the 
mixture of windows shell and rebol one or so? :-) REBOL history is 
gone, when I try print "ahoy", it returns czech message, telling 
me PRN can't be initialised :-)

Cmd invaded your rebol shell.

Calling just "dir" returns still the same message ...

Use "exit" to get out - (I hope).

cmd  invaded
 - is that correct and/or desired behaviour?

Probably, I wouldn't worry about it.

>> print "aaa"
Zaøízení PRN nelze zinicializovat.

c:\!rebol\altme\worlds\r3-gui\files\rebdev>dir c:\
** Script error: dir has no value


>> exit

the strange thing, that once being in cmd console, dir c:\ did not 
worked and returned "dir has no value" message ...

hmm, maybe we have few bugs to haunt in this area ...

That's a rebol error message, obviously, not a cmd one.

yes, but at that time, I was in CMD shell, no?

Press Windows key + R, then type "cmd" and enter.

what do you want me to try? that dir works in normal shell? It does, 
I tried ...

I don't know if you were in a cmd shell or a rebol one (!)

(Start with a fresh rebol console.)

Try   call "start dir"

Fresh R3 console, typing call "dir", getting still the same error

the same for "start dir"

Try   call "cmd dir"

>> call "cmd dir"
== none

>> Microsoft Windows [Verze 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. Všechna práva vyhrazena.

c:\!rebol\altme\worlds\r3-gui\files\rebdev>

boots me in the cmd shell imo ...

but in that shell, dir returns script error message about dir having 
no value ...

ah, consecutive call works, interesting ...

>> call "cmd dir"
== none

>> Microsoft Windows [Verze 6.0.6001]

Copyright (c) 2006 Microsoft Corporation. Všechna práva vyhrazena.

c:\!rebol\altme\worlds\r3-gui\files\rebdev>dir
** Script error: dir has no value


>> dir
 Svazek v jednotce C nemá žádnou jmenovku.
 Sériové èíslo svazku je 0054-60D0.

 Výpis adresáøe c:\!rebol\altme\worlds\r3-gui\files\rebdev

13.08.2009  12:12    <DIR>          .
13.08.2009  12:12    <DIR>          ..
02.07.2009  15:38    <DIR>          base

Hmm.. weird, looks like one line is taken by cmd, the next is taken 
by rebol.

(I mean the other order..)

so:

1) call "cmd dir" boots me into cmd shell - notice single >
2) calling dir there boots me back to ... where? Notice >>
3) then mysteriously dir works from there ...

Ok, I would avoid calling cmd directly in rebol. I just wanted to 
know if anything could be successfully called.

if that would be e.g. path problem, then for e.g. calling icacls 
would not work, but it works ... any other cmd commands to try?

I have forgotten how to get the path in windows console, is it
	echo %PATH
?

and to get and set the current directory. CD ?

Anton: my comment may be dismissive, but the point I'm making is 
that that is just my opinion, I'm not sure why I should be forced 
to "like" a heredoc syntax :) I understand that it is very handy 
on occasions, but the price is a ugly script, which I'd rather not 
pay if I can avoid it easily enough (for example, if I were generating 
a lot of PHP or JS, I would just build a dialect to do that, instead 
of using strings). Again, though it's funny for me to have to repeat 
it again and again, this is just IMHO, Robert should be free to do 
things his own way, and if REBOL can provide a syntax for heredocs 
without creating other problems I'm fine - I'll just avoid it (and 
I'll hope not many people start using it ;)

Anton - just simple "path" does it ...

Some commands work, some don't call "path" does not work, call "help" 
works, etc.

Gabriele, I had a look at a few of the heredoc formats and some of 
them do look quite ugly. I admit that I actually haven't used heredocs 
myself yet, only come across a few snippets here and there recently, 
so I guess I don't have much experience with them yet, and can't 
tell what problems they may cause. My initial thought was that they 
would be a good idea, since you could just paste foreign code straight 
into your script.

Or you could use an editor which hides all the ugliness

Pekr, commands like dir and path are built into cmd.exe - they aren't 
separate programs. So CALL "cmd.exe /c dir" should work.

At a command prompt, call cmd /? to get help on cmd.exe and its commands.

Brian - "help" does it too ...

Brian - what's the mess with intermixing cmd shell, and rebol one? 
See above output. And why do I need to hit enter to get back to rebol 
console?

R2 intermixed the cmd shell with CALL - with R3 you do that manually 
if you need to.

As for your other question, look at this:

>> call "cmd.exe /c dir"
== none

>>  Volume in drive E is APPS
 Volume Serial Number is 7845-7730

 Directory of E:\REBOL\2.100

01/14/2009  03:17 PM    <DIR>          .
01/14/2009  03:17 PM    <DIR>          ..
01/14/2009  03:24 PM    <DIR>          base
01/15/2009  12:17 PM    <DIR>          updates
07/12/2009  03:08 PM                56 blah.txt
02/25/2009  08:09 PM               492 user.r
03/02/2009  10:22 PM    <DIR>          work
04/09/2009  08:41 PM                66 test.r
06/13/2009  12:09 AM                28 mod1.r
06/13/2009  12:09 AM                28 mod2.r
06/13/2009  12:10 AM                47 mod.r
08/10/2009  08:39 PM    <DIR>          plugin
08/13/2009  03:35 PM           613,376 r3.exe
08/13/2009  07:08 PM    <DIR>          extension
08/13/2009  08:46 PM            20,480 ext-test.dll
               8 File(s)        634,573 bytes
               7 Dir(s)   4,893,769,728 bytes free
1 + 1
== 2


I did that 1 + 1 to show that I didn't have to hit enter to get back 
to REBOL. You only have to hit enter to see the prompt. The extra 
>> above the dir outpt is the result prompt that you aren't seeing 
below. This is because CALL on Windows returns immediately, rather 
than waiting for the called process to finish its work, including 
its console output.

Keep in mind that this behavior may change in the future: CALL is 
in the host code.