DOS progam will not run with Limited Rights User

[Guest]

I’m not a very experienced administrator, but I have the task of servicing a
few systems and I’m having trouble with an older DOS program that runs on a
Windows XP Pro computer. I have about 5 total users (4 with admin rights and
1 with limited rights). All of the users with administrator privileges can
click the icon on their desktop and the DOS program launches. However, if any
user with limited rights tries to launch the same DOS program from the
shortcut created on their desktop, the following error is displayed: “16 BIT
MS-DOS SUBSYSTEM C:\Docume~1\Username\Desktop\ProgramName.PIF Temp file
record for INIT could not be created or writtenâ€

Also, if any user with limited rights logs on to their desktop, another
error window is displayed that says “codebase error # -935 #92097 Null Input
Parameter Unexpected d4seek†and an additional DDE Server Window error for
hppdirector.exe fatal application exit registry call resulted in 5.

I’m unsure if these two errors are related to my problem trying to launch
the DOS program, but that is my most immediate problem to try to resolve. Can
anyone help?

 

[Steven L Umbach]

It seems as first glance it would seem that the user has a permissions
problem to his desktop folder in his user profile that by default would be
full control. You could check that by logging on as an administrator and
going to documents and settings\user\desktop and make sure that the user has
full control to that folder. I don't have any clue about the second error
though and found nothing with a quick Google search. . The links below may
help if you need details on configuring permissions and taking ownership. I
would also try adding the user to the power user's group temporarily to see
if the other error goes way or not and it if does it would probably not be
that hard to reconfigure permissions for the regular user to logon without
any problems. Check the logs via Event Viewer to see if any related
errors/warning are recorded at the times the problems occur. Also enable
auditing via Local Security Policy for failure for privilege user and object
access which also may generate failed events in the security log when user
access fails that may help resolve the problem such as lack of user right or
determine that the user must be a local administrator.

http://support.microsoft.com/default.aspx?scid=kb;en-us;308418
http://support.microsoft.com/default.aspx?scid=kb;en-us;308421