Can't run old CMD/DOS .exe as Non-Admin

[bru]

I have an old .exe that I want to run in a Command window.
It works OK for "Admin" users, but not for non-Admin users.

Is there something I can set to allow non-Admin users to
execute the old .EXE files?

TIA

 

[Pegasus \(MVP\)]

I have an old .exe that I want to run in a Command window.
It works OK for "Admin" users, but not for non-Admin users.

Is there something I can set to allow non-Admin users to
execute the old .EXE files?

TIA

- What is the exact command line you type in the Command Prompt?
- What do you see on the screen when it does not work?

 

[bru]

Further info... It isn't working on an NTFS partition but
it works on a FAT32 partition.

 

[bru]

- What is the exact command line you type in the Command Prompt?
- What do you see on the screen when it does not work?

It's an old compiled database program in which displays a generic
"Error 92" message and I don't have the source/compiler
available to determine what the error actually means.

 

[Pegasus \(MVP\)]

Further info... It isn't working on an NTFS partition but
it works on a FAT32 partition.

If it works on FAT32 partitions but not on NTFS partitions
then you are probably dealing with access rights issues.

 

[Homer J. Simpson]

Further info... It isn't working on an NTFS partition but

it works on a FAT32 partition.

Sounds to me like a classic DOS app that thinks it owns the box and can do
whatever it pleases. Of course, XP can't enforce any sort of access
restriction on FAT32 partitions.

I know this won't help you any, but it IMO you won't have much choice but to
let it run under an admin account.

 

[bru]

If it works on FAT32 partitions but not on NTFS partitions
then you are probably dealing with access rights issues.

All the files (and the folder it is contained in) are
created by the same user, though from a Windows application
(Access). What type of rights issues could there be?

 

[Pegasus \(MVP\)]

All the files (and the folder it is contained in) are
created by the same user, though from a Windows application
(Access). What type of rights issues could there be?

Since administrators can run the application but non-admins
can't, the application most likely accesses a folder that is out
of reach for non-admins. It may, for example, attempt to
create a temporary folder such as c:\TempDatabase, which
is no problem for an admin but could be prohibited for non-admins.

 

[Bruce Chambers]

I have an old .exe that I want to run in a Command window.
It works OK for "Admin" users, but not for non-Admin users.

Is there something I can set to allow non-Admin users to
execute the old .EXE files?

TIA

You may experience some problems if the software was designed for
Win9x/Me, or if it was intended for WinNT/2K/XP, but was improperly
designed. Quite simply, the application doesn't "know" how to handle
individual user profiles with differing security permissions levels, or
the application is designed to make to make changes to "off-limits"
sections of the Windows registry or protected Windows system folders.

For example, saved data are often stored in a sub-folder under the
application's folder within C:\Program Files - a place where no
inexperienced or limited user should ever have write permissions.

It may even be that the software requires "write" access to parts
of the registry or protected systems folders/files that are not normally
accessible to regular users. (This *won't* occur if the application is
properly written.) If this does prove to be the case, however, you're
often left with three options: Either grant the necessary users
appropriate higher access privileges (either as Power Users or local
administrators), explicitly grant normal users elevated privileges to
the affected folders and/or part(s) or the registry, or replace the
application with one that was properly designed specifically for
WinNT/2K/XP. You've already stated that granting your son elevated
privileges is a very bad idea.

Some Programs Do Not Work If You Log On from Limited Account
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307091

Additionally, here are a couple of tips suggested, in a reply to a
different post, by MS-MVP Kent W. England:

"If your game or application works with admin accounts, but not with
limited accounts, you can fix it to allow limited users to access the
program files folder with "change" capability rather than "read" which
is the default.

C:\>cacls "Program Files\appfolder" /e /t /p users:c

where "appfolder" is the folder where the application is installed.

If you wish to undo these changes, then run

C:\>cacls "Program Files\appfolder" /e /t /p users:r



--

Bruce Chambers

Help us help you:


http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot