| || |
Silk 5 and DCOM
My coworkers and I have encountered an interesting situation with Silk 5.0. With Silk installed, when we install the product we are developing, at the close of the install we are consistently getting a Dr. Watson in dcomset.exe. This never happens unless Silk 5.0 is installed on the system. With no Silk, or earlier releases of Silk, the "Watson" never happens.
Re: Silk 5 and DCOM
The installation of SilkTest does modify some files. try to get a copy of GDI32.DLL from a system that has NEVER had SilkTest installed on it. Backup the GDI32.DLL on the problem system (you may have to share the WinNT\System32 directory, logout, and then backup the file form another system). Put the good file in it's place. Try your install again. Does it work? If it works with an orginal GDI32.DLL, then contact Segue to see if they will fix the problem.
The problem may be else were, this is just a likely location.
333 Moffett Park Drive
Sunnyvale, CA 94089