We use different ini files for different groups of users and this has

worked exceptionally well for many years under both Novell and NT.

A curious issue arose when creating a new ini file for a client

under NT.

Signed in as Administrator and copied one ini file under different

name (8x3 format) and changed the specific setting required.

Created a batch file for the user as always thus …..

set arev etc

Arev user /x /m4096

Tested the batch file via a shortcut on the NT Workstation and all

worked well under admin sign on.

Went to the user station (new NT Workstation) and signed in under the

user name to no avail.

An error occurred in that the ini file could not be activated hence

the environment was not available as planned.

Logged into same station as administrator, activated the exact same

shortcut and consequent batch file and all worked fine as intended.

Must have been a user rights issue so promoted the user to admin for

trials and same error condition occurred under the user's sign-on.

Reverted to admin sign on and again all OK.

Question:-

When the user rights have been changed at the NT level how is it

possible for this error to occur under these controlled conditions?

Somewhat mystified!

Regards,

Kevin Gray

Graycorp

(email [email protected])

Doesn't NT create a separate desktop file for each user on the workstation (in the folder Profiles I believe)?

Are you sure you are updating the proper PIF etc?

Warren,

Thanks for your response.

Yes, separate desktop for each.

Same batch file called from shortcut in each case!

Seems more an NT permissions issue but we are somewhat

stumped at this stage.

Regards,

Kevin Gray

Situation resolved by resetting the particular user's

NT access rights.

Seems a quirk in user right assignments between NT station

and the NT Server.

Off and running now!

Kevin Gray

View this thread on the forum...