Re: DOS program works in Admin account but not in a User account

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



On Sat, 03 Jun 2006 13:23:59 +0100, Robert M Jones wrote in
microsoft.public.win2000.cmdprompt.admin:

Michael Bednarek wrote:
On Sat, 03 Jun 2006 07:32:33 +0100, Robert M Jones wrote in
microsoft.public.win2000.cmdprompt.admin:

Newbie to WinXP-Home but otherwise fairly competent.
I have a legacy DOS program (Bible software) that runs fine in my XP
Home Admin account which is the one I installed it in (simply by copying
across the folder from an old win98HDD into the new C drive) but when I
run the shortcut or the exe file in my user account it just opens the
initial menu screen - if I click on one of the choices the screen
flashes off and that's it - finished = the problem is associated with
the underlying *.exe file - if I click that it just flashes on and off.

I've adjusted the underlying exe file as well as the bat file that the
shortcut runs, to be compatible as for Win98.

Can anyone give me any pointers to why this would happen in a user
account when the program works fine in an Admin account, and what can I
do about it? Is it associated with the fact that I just copied the
folder rather than running the full install from the floppies?

I've tried making the relevant folder and sub folders shared for all
users and also tried dragging it into the Shared documents folder (which
produces failures because of dud path entries in the various bat files)
but that doesn't improve things.

I assume it has something to do with access rights.

Open a command line window (Run... cmd), and navigate to the directory
where your program is; let's assume that directory is C:\Bible, then:
CD /D C:\Bible

Then run this command to show the access rights:
cacls .
and
cacls *.exe

Then post the output of these commands - you can cut and paste from the
command line window by: Alt+Space Edit Mark Shift+Arrow keys to
highlight, Enter to Copy, switch to your News Reader, Ctrl+V to paste.

Alternatively, you can inspect the access rights through the Graphical
User Interface in Explorer: navigate to the directory, highlight the
directory itself, right click (or press Shift+F10), select Properties,
Security. Give full access to Users.


Many thanks for your response.
I did the above in my User account where the program doesn't work, for
the exe file that flashes on and off quickly -

file = bmaster.exe
directory = c:\bmaster\

C:\BMASTER>cacls .
C:\BMASTER Everyone:(OI)(CI)R
BUILTIN\Administrators:(OI)(CI)F
NT AUTHORITY\SYSTEM:(OI)(CI)F
MANSEOFFICE\Robert Admin:F
CREATOR OWNER:(OI)(CI)(IO)F
BUILTIN\Users:(OI)(CI)R
BUILTIN\Users:(CI)(special access:)
FILE_APPEND_DATA

BUILTIN\Users:(CI)(special access:)
FILE_WRITE_DATA



C:\BMASTER>cacls bmaster.exe
C:\BMASTER\bmaster.exe Everyone:R
BUILTIN\Administrators:F
NT AUTHORITY\SYSTEM:F
MANSEOFFICE\Robert Admin:F
BUILTIN\Users:R

When logged in as Administrator, execute the following command from the
directory C:\BMASTER
cacls . /e /g Users:f

This will give ordinary users on your system the rights to delete files
in that directory; it will not grant that right for existing files. I
suspect that BMASTER wants to write and delete some temporary files. Log
in as a non-Administrator and try it.

If that doesn't solve the problem, you have to issue the command
cacls *.* /e /g Users:f
which will grant full rights to Users to all files in that directory.

When trying as a non-Administrator, use Explorer to navigate to
C:\BMASTER and double-click on the program (bmaster.exe).

Out of interest: how do non-Administrators normally start the program?
By clicking on an icon? If so, the access rights to that icon might also
be restricted.

--
Michael Bednarek http://mbednarek.com/ "POST NO BILLS"
.



Relevant Pages

  • Re: DOS program works in Admin account but not in a User account
    ... I have a legacy DOS program that runs fine in my XP Home Admin account which is the one I installed it in but when I run the shortcut or the exe file in my user account it just opens the initial menu screen - if I click on one of the choices the screen flashes off and that's it - finished = the problem is associated with the underlying *.exe file - if I click that it just flashes on and off. ... I assume it has something to do with access rights. ... Open a command line window (Run... ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: DOS program works in Admin account but not in a User account
    ... I have a legacy DOS program that runs fine in my XP Home Admin account which is the one I installed it in but when I run the shortcut or the exe file in my user account it just opens the initial menu screen - if I click on one of the choices the screen flashes off and that's it - finished = the problem is associated with the underlying *.exe file - if I click that it just flashes on and off. ... I assume it has something to do with access rights. ... Open a command line window (Run... ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: [opensuse] Post installation queries (FIRST successful installation of Linux)
    ... The easiest way to manage users on opensuse is with yast. ... You can also do the same with the command line commands of: useradd userdel and usermod. ... -c comment Set the GECOS field for the new account ... One more note -- and I hate this about the recent openSuSE installs -- you must tell the installer to set a traditional root account and password during setup or it just creates a 'Super User' out of the user account used during install. ...
    (SuSE)
  • Re: Home Wireless Networking and File Sharing
    ... Browstat and run it but it just shows the command prompt for a sec and then ... Then I put in net config workstation and got ... You do not need to be logged into the same account ... and Vista:" I have done that on all of the laptops and main PC and called ...
    (microsoft.public.windowsxp.network_web)
  • Re: Local System Account
    ... I checked on Windows Server 2003 and Vista Beta 2. ... run following command from command line: ... one can specify it to run as localsystem account. ... administrator is not same as Local System. ...
    (microsoft.public.win2000.security)