Odd behaivour with Regedit on XP

[stuarth]

I'm using regedit to add a .reg file when a User logs on.

So I use in the logon batch file.

regedit /s n:\policyfile\office.reg


However on one of my users machines he gets his XP PC complaining that
the .reg is not a registy file and it refuses to use it.

This very same .reg file works fine in other XP machines.


But the really odd thing is that along side the office.reg file we also
have a Windows 2K version.
If I manually type into a command prompt from the offending XP machine
:

n:\policyfile\>regedit office_w2k.reg

then that works.

But typing in:

n:\policyfile\>regedit office.reg

doesn't! It thinks its not a registry file.
But as I said earlier, if I type the same on a different XP machine, it
works!

This XP machine is running Windows XP Pro SP2 like most of the PCs on
my LAN.

regedit is 5.1 build 2600 as it is on a XP machine that works.

Any clue to what the problem is?

Got me baffled!

All our XP machines run AV software and I did a recent AV scan on it
just in case....
It appears to be clean.

 

[Pegasus \(MVP\)]

I'm using regedit to add a .reg file when a User logs on.

So I use in the logon batch file.

regedit /s n:\policyfile\office.reg


However on one of my users machines he gets his XP PC complaining that
the .reg is not a registy file and it refuses to use it.

This very same .reg file works fine in other XP machines.


But the really odd thing is that along side the office.reg file we also
have a Windows 2K version.
If I manually type into a command prompt from the offending XP machine
:

n:\policyfile\>regedit office_w2k.reg

then that works.

But typing in:

n:\policyfile\>regedit office.reg

doesn't! It thinks its not a registry file.
But as I said earlier, if I type the same on a different XP machine, it
works!

This XP machine is running Windows XP Pro SP2 like most of the PCs on
my LAN.

regedit is 5.1 build 2600 as it is on a XP machine that works.

Any clue to what the problem is?

Got me baffled!

All our XP machines run AV software and I did a recent AV scan on it
just in case....
It appears to be clean.

Your post is a little confusing. You write
===============
If I manually type into a command prompt from the offending XP machine

n:\policyfile\>regedit office_w2k.reg
===============

I assume that you don't mean this but that you're actually typing

regedit office_w2k.reg

For respondents to offer any comments about your problem
you should post the full contents of the offending registry
file. You should also state how you generated it and if it is
an ANSI or Unicode file.