Rob

>I wish I could execute the  'Smalltalk listLoadedModules' after 
>executing the statement 'Win32Shell explore: 'C:\'' there is no 
>Squeak anymore: it crashes without warning or other message.


I opened up a fresh 3.0 image (3.0 - 4 February 2000 - #3545) from the
server and tried

Win32Shell new shellOpen: 'C:\'

It opens a Windows explorer.


Win32Shell new shellOpen: 'winword.exe'.

worked fine as well.


(BTW OT: Why not use Squeak as a shell program which is started at boot
time
instead of the explorer and have a Squeak GUI with buttons for the
necessary
programs outside of Squeak.)

A 'print-it' on
Smalltalk listLoadedModules 

gives

#('shell32.dll' 
'SqueakFFIPrims 15 March 2001 (e)' 
'B2DPlugin 15 March 2001 (i)' 
'FloatArrayPlugin 15 March 2001 (i)' 
'Matrix2x3Plugin 15 March 2001 (i)' 
'BitBltPlugin 15 March 2001 (i)'
'LargeIntegers v1.2 15 March 2001 (i)' 
'SecurityPlugin 15 March 2001 (i)'
'FilePlugin 15 March 2001 (i)' 
'MiscPrimitivePlugin 15 March 2001 (i)')




Hannes Hirzel





P.S. An additional question (to anybody): 

I would like to do something like

Win32Shell new runCommand: 'wordpad c:\temp\test.rtf'.

But I don't know how to implement #runCommand.

There are examples in Win32Shell how to do this kind of things. 
But I don't yet see the pattern.