Print

[dfunked]

Are you another user which has been set as Administrator?

You might want to just trying logging in as the super Administrator, ie. Login = Administrator

If you know the details, try that.

[derson]

QUOTE

ERROR Unable to install the program Make sure you have ADMINISTRATOR Rights on this PC!

I logged out and logged in as the local account: user.
As expected I received the same error message.

I then logged in as the user: admin.
Without hesitation, the installation started and completed succussfully.  I then had to manually copy the desktop and start menu files into my profile instead of the newly created local account: admin.  After logging back in under my normal cached domain based account, I verified that XLink functioned as expected.  

I then attempted to run the installation using the Windows XP Run As... functionality.   Entering the admin user account (not the real local Administrator), the setup routine bypassed the error message and continued successfully.

The setup routine uses QSetup.  From what I can tell, there is nothing in the QSetup files to enforce administrator rights, but many conditions can be requested for each action that the installer takes.  Thus, I believe the conditional statements manually entered into the setup routine are not 100% correct and could be modified to reduce the occurances of this false error.

Hope this helps others :-)

[derson]

After being really curious why Administrative rights are really needed, this is what I found - may not be 100% accurate (might have missed a few things), but this should be pretty close.  Only changes that require Admin rights listed:

- I didn't have the following files:
%SystemRoot%\System32\COMCT332.OCX
%SystemRoot%\System32\IJL11.DLL
%SystemRoot%\System32\MSWINSCK.OCX
%SystemRoot%\System32\PACKETX.DLL
%SystemRoot%\System32\TABCTL32.OCS
%SystemRoot%\System32\VB6STKIT.DLL
%SystemRoot%\System32\WINPCAP.EXE

- these 2 files were back-reved to older versions
%SystemRoot%\System32\MSCOMCT2.OCX
%SystemRoot%\System32\MSCOMCTL.OCX

- These files were the same version as I had installed:
%SystemRoot%\System32\MSVBVM60.DLL
%SystemRoot%\System32\OLEPRO32.DLL
%SystemRoot%\System32\PACKET.DLL
%SystemRoot%\System32\PTHREADVC.DLL
%SystemRoot%\System32\STDOLE2.TLB
%SystemRoot%\System32\WPCAP.DLL
%SystemRoot%\System32\Drivers\NPF.SYS

For those wondering what some of these do:
PacketX.DLL - packet sniffing, probably to capture the XBOX network traffic.
MSWinSCK.OCX - MS WinSock Control
COMCT332.OCX - Visual Studio 6 common controls - tool bar
TABCTL32.OCX - MS tabbed dialog control

Registry entries for PacketX.DLL,  MSWINSCK.OCX, COMCT332.OCX, and TABCTL32.OCX (HKLM\Classes).

- HKLM\Software\MS\Windows\CurrentVersion\App Management\ARPCache\XLink Messenger RC2
- HKLM\Software\MS\Windows\CurrentVersion\App Paths\xlink.exe
- HKLM\Software\xboxlink.co.uk\XLink Messenger RC2\RC2 2.2.2

There were many other registry entries, but they were related to those above - and obviously I didn't list every value and data field that changed in the registry.

The only part that concerns me is the installation of older MS common controls over later versions that I already had installed.  But so far, so good.

[flat235]

Anywhoo - Kai doesnt have any deps. - it's just one EXE - so that should sort out any lingering problems

Cheers

TD

[flat235]

\ \  etc..

[derson]