UNIX Tools for Windows Will Not Run Without .exe File Name Extension

OS: Windows 7 Ultimate running in a VMware Virtual Machine
Toolset: UnixUtils (FIles timestamp, 6/20/2003 4:57 PM, obtained here:
Updates are installed.

Tools are located on the C:\ drive of the virtual machine, in C:\bin.
My MS Windows CMD window PATH is configured to see the C:\bin folder.

In the CMD window, when I run a command such as 'ls', without the .exe extension, an error message appears,

"This version of c:\bin\LS.COM is not compatible with the version of Windows you' re running. Check your computer's system information to see whether you need a x 86 (32-bit) or x64 (64-bit) version of the program, and then contact the softwar e publisher."
NOTE: When I include the file extension, 'ls.exe', it works just fine with or without arguments, so it is NOT a problem with the PATH. Providing the path, such as '\bin\ls' does not work, either.

Is there something I can do to allow the UNIX commands to run in the CMD window WITHOUT the file extension?
Jerry LOperations ManagerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
ls works for me; found in usr\local\wbin
searched the folder tree; no .com files so not sure where yours is coming from
Just a guess ... is there a file ls.com in the directory where ls.exe is located (or somewhere along the path) ?

There's an environment variable PATHEXT, which tells Windows what extensions to try if none is explicit given. My PATHEXT is


Windows tries the extensions in that order, which means if you run


it tries

(... and so on ...)

along the path. If it finds a ls.com, it uses that without searching for another ls.

Try to search for that ls.com and
rename it,
delete it,
remove its directory from the path,
hide it by some other means, or
exchange the precedence of .COM and .EXE in PATHEXT
whichever does the least possible disturbance to your system.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jerry LOperations ManagerAuthor Commented:
@ frankhelk - Yes, that was the problem, so thank you for pointing this out. I never encountered this before so it had me stumped. I created a sub-folder, C:\bin\_com and moved all the *.com files there. I am now able to execute 'ls' etc, without the extension.
Seth SimmonsSr. Systems AdministratorCommented:
don't know where you got this download from
i used the link you provided and there are no .com files; only .exe
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.