greetings,

I am coming from win xp and trying out win7

there are a couple of cmd shell programs I use regularly in particular mutt (email) and mcabber (im)

if I setup the the shortcut to point directly to the executable I get an error

if I setup the shortcut like this cmd /k path to executable the program runs opening two cmd shells

and when closed leaves a cmd shell open on the desktop.

if possible I would like to explore some other options to run these programs

thank you

Try running the programs as Administrator. (Right click on the program shortcut, Run As Administrator)

cmd /k path to executable the program runs opening two cmd shells

and when closed leaves a cmd shell open on the desktop.

What about cmd.exe /c :

http://ss64.com/nt/cmd.html

jaclaz

I changed to cmd /c and although it still opens two cmd shell windows both close when i exist the application (mutt) which is better

thanks - also here is the screen error if I just click on the mutt.exe (doesnt matter if run as admin is used) from google i get the impression this is an access violation

Problem signature:

Problem Event Name: APPCRASH

Application Name: mutt.exe

Application Version: 1.5.19.0

Application Timestamp: 49c8dd75

Fault Module Name: mutt.exe

Fault Module Version: 1.5.19.0

Fault Module Timestamp: 49c8dd75

Exception Code: c0000005

Exception Offset: 0015a89a

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104...mp;clcid=0x0409

I cannot tell you exactly what the problem is, however to run a Unix application in Windows 7 I'd expect you to be using it through a Linux API emulation layer such as Cygwin. However, as far as I'm aware Windows 7 is only supported in the current beta testing version of Cygwin. You are therefore running a beta version of Mutt, which isn't even the most recent version (heavily fixed), through a beta version of your emulation software and getting errors.

I'd suggest that you try to redirect the questions through the beta test channels of your application software.

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104...mp;clcid=0x0409

WHY should I?

jaclaz