Command.com hosed. OS.system python modules won't execute properly

[David LeBlanc]

I believe you must set your COMSPEC to the same as the SHELL so that the
additional env space is available for command interpreters invoked by other
programs. "Shell" is only for the initial interactive command interpreter
and COMSPEC is for other invocations.

HTH,

David LeBlanc
Seattle, WA USA

  -----Original Message-----
  From: python-list-admin at python.org [mailto:python-list-admin at python.org]On
Behalf Of Tony C
  Sent: Thursday, November 07, 2002 20:14
  To: python-list at python.org
  Subject: Command.com hosed. OS.system python modules won't execute
properly




  In order to get my Python environment variables, and path working
correctly, under Windows 98, I had to add the following to my config.sys,
because my environment ran out of space

  shell=C:\command.com /p /E:4096



  Now, when I try to execute modules in OS, such as OS.system('cls'), python
reports the following error

   >>> import os
  >>> os.system('cls')
  Invalid COMMAND.COM
  Enter correct name of Command Interpreter (eg, C:\COMMAND.COM)


  If I don't add the /p to the shell= statement, a "File Creation Error"
message is displayed before Windows 98 loads, and the DOS prompt is
displayed.

  I found the /P solution to the "File creation error" message problem on
Google:groups. Apparently a lot of people had the same problem, in Win 95
days.



  Does anyboy have some insight to my command interpreter problem ?

  thanks









----------------------------------------------------------------------------
--
  Do you Yahoo!?
  U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20021107/6092b6be/attachment.html>