[ ghc-Bugs-1206355 ] System.Cmd.system fails on Win9x

Bugs item #1206355, was opened at 2005-05-21 18:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1206355&group_id=8032

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libraries/base
Group: 6.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: System.Cmd.system fails on Win9x

Initial Comment:
Vivian McPhail
vivian.mcphail@xxxxxxxxxxxxxxx

>From a ghci session (6.4):

Prelude> System.Cmd.system "dir"
*** Exception: C:\WINDOWS\SYSTEM\CMD.EXE: runCommand:
does not exist (No such file or directory)

System.Cmd.system tries to run cmd.exe but on Win9x
this is command.com.

These executables are both mentioned in the
documentation so the distinction is not unknown.

I see that the source code for System.Process.Internals
has code for detecting this, but for some reason it
does not appear to be working:

-- Find CMD.EXE (or COMMAND.COM on Win98).  We use the
same algorithm as
-- system() in the VC++ CRT (Vc7/crt/src/system.c in a
VC++ installation).
findCommandInterpreter :: IO FilePath
findCommandInterpreter = do
  -- try COMSPEC first
  catchJust ioErrors (getEnv "COMSPEC") $ \e -> do
    when (not (isDoesNotExistError e)) $ ioError e

    -- try to find CMD.EXE or COMMAND.COM
    osver <- c_get_osver
    let filename | osver .&. 0x8000 /= 0 = "command.com"
                 | otherwise             = "cmd.exe"
    path <- getEnv "PATH"





----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1206355&group_id=8032