[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::objectbroker

Title:	ObjectBroker - BEA Systems' CORBA
Notice:	See note 3 for kits; note 5 for training; note 1134 for releases
Moderator:	TLE::PARODId

Created:	Tue Jul 11 1989
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1413
Total number of notes:	6391

1403.0. "Unable to get 2.7-11 installed on NT 3.51 with Intrigue 3.0" by PEACHS::SELBY (I am Pentium of Borg. Prepare to be approximated.) Fri May 16 1997 16:31

One of my customers has several Windows NT systems running
3.51 Build 1057.  These systems have a software package
called Intrigue installed.  Apparently Intrigue provides
the NT system with an X Server and allows Unix clients to
access NT.  (I do not know how and the customer could not
explain it.)  It apparently is much more than just an X
Server.  If you Select "About Program Manager" from the 
Help menu on the Program Manager it identifies itself as
Intrigue V3.0 Build 179.

Now when the customer tries to install ObjectBroker 2.7-11
it errors out saying that they are running Build 179 and 
need to be running 1057 for ObjectBroker to install.

Well they are running Build 1057.  Also if the customer
makes the windows API call get_version it returns 

	Windows NT 3.51 Build 1057


How can we get OBB to install on these systems?  The
customer is MacNeal-Schwendler in Los Angeles.  They have
been working hard to get OBB installed into an OBB hostile
environment.  So far we have their AIX environment running
but are unable to get the NT environment running.

As expected, if the system does not have Intrigue installed,
ObjectBroker installs fine.


Any suggestions?  How can we bypass or hack the version check?


Dale Selby
CSC Atlanta

T.R Title User Personal
Name Date Lines

1403.1 PEACHS::SELBY I am Pentium of Borg. Prepare to be approximated. Fri May 16 1997 17:16 17

T.R	Title	User	Personal Name	Date	Lines
1403.1		PEACHS::SELBY	I am Pentium of Borg. Prepare to be approximated.	`Fri May 16 1997 17:16`	17
	Well let me answer my own note (with help from Mr. Bower). The installation gets the version number from the NT registry. Apparently Intrigue is modifying the portion of the registry Microsoft/Windows NT/CurrentVersion. Tsk tsk. The options are either modify the registry (on all machines effected) or edit the OEMSETUP.INF to remove the version check. Then use this kit across all effected nodes. The officical response is 'go back to Intrigue and tell them to provide you with a package that does not monkey around with Microsoft's portion of the registry'. 8^) dale

Well let me answer my own note (with help from Mr. Bower). 


The installation gets the version number from the NT registry.
Apparently Intrigue is modifying the portion of the registry
Microsoft/Windows NT/CurrentVersion.  Tsk tsk.  The options
are either modify the registry (on all machines effected) or
edit the OEMSETUP.INF to remove the version check.  Then use
this kit across all effected nodes.


The officical response is 'go back to Intrigue and tell them
to provide you with a package that does not monkey around with
Microsoft's portion of the registry'.   8^)


dale