Greetings!

 Thank you for the prompt reply.  As it turns out, the root of the problem was my own lack of faith.  Both systems are configured identically and both Mercury installations are identical.  And when I went into the system tools to investigate my problem, lo and behold there was Mercury running as a system service exactly as it should.  Apparently, all I needed to do was to reboot after copying Mecury over to the new server and that was the only thing I had forgotten to do.

 Sorry for the false alarm; I feel like such a Noob!  (And I've been around long enough that I should have known better!)

Greetings!

 I followed the instructions in the FAQ but I ran

into one snag I just can't fix: getting the new installation to start as

a system service like the old one.

 I had Mercury 4.72 running on

an XPpro box as a system service.  I copied the installation to a new

XPpro box and everything went fine, however, it was running in

standalone mode.  I tried INSTM32S but it bombed out on an error. 

Thinking that a fresh exposure to SETUP might cure the problem, I

installed 4.73 over 4.72.  Again, no dice; everything works fine except

that setting up the system service bombs on the same error.

 I am

administrator on both machines so I certainly have the necessary user

permissions.  I am going to go check one more time to make sure that

MERCURY has sufficient permissions to fire off executables and

read/write/delete on the drive, but beyond that I'm stumped.  Any

suggestions would be appreciated.

Unless there is something interfering with your access to Windows, like a very strict antivirus program, the only thing I could think of is some problem with the path to the Mercury installation, or the service name. I assume you use the default for that, though. Is there any error message that could give more information?

/Rolf