Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

NT 4.0 MSI Installation error


5 replies to this topic

haroldxious

haroldxious
  • Full Members
  • 70 posts

Posted 31 May 2007 - 09:21

I have copied the exact words of the poster in macrovisio forum ecause we have the same problem and we encountered the same scenario.
http://community.mac...ead.php?t=46395

This is the problem:
After running my install on an NT 4.0 machine, everyting is alright until I
reboot. Once rebooted, NT itself is so scrambled that the only way to
recover is to format (or ghost) the machine and reinstall the OS. The
installation makes very limited number of registry calls into a small section of HKEY_LOCAL_MACHINE and just adds a small number of keys
with values in one area.

The first error NT will throw up right at Login will be

Services.exe
"Entry Point Not Found. The Procedure entry point SethandleContext could
not be located in the Dynamic Linked Library Kernel.dll"

Then follows about 10 more of these pertaining to seperate DLL's. I lose
netowrk connectivity and the system bascially is corrupted.
Does this look like a registry issue? I'm thinking that it may have to do
with some the files I'm self-registering rather than some of the files I'm
just overwriting in the system directory.

===============================================

That is the post, currently there are no answers, hope to have a solution for this.

Thank you very much in advance

Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 31 May 2007 - 10:07

This sounds quite messed up. You are not overwriting Kernel.dll in your setup I hope?? (shouldn't even be possible).

I would disable any services you install and verify that the machine works correctly after this. Then I would use dependency walker to check all service files to see if they depend on the missing export from kernel.dll (SethandleContext).
Regards
-Stein Åsmul

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 31 May 2007 - 17:30

Double check your setup to make sure it doesn't replace any system files. In NT4 there was no system file protection so it is possible to damage the OS this way. Suspect are all files that go to Windows (WinNT) or System(32) directories.
Viruses or Trojans could be another cause for the problem.

Before you reboot, check the pending file rename operations. You can do this in registry or using the PendMoves tool:
http://www.microsoft.../PendMoves.mspx

haroldxious

haroldxious
  • Full Members
  • 70 posts

Posted 01 June 2007 - 06:39

Thank you for your reply guys, i followed your instructions and it went well...

I double checked my installer and tried some test...i have found that i have this following.

Feature 1
Component1 (files: ws_32.dll for NT) condition: VersionNT=400
Component2 (files: ws_32.dll for 98) condition: Version9x=410
Component3 (files: ws_32.dll for ME) condition: Version9x<>410

Stated above i have a wrong condition on installing the ws32.dll for ME, it must be Version9x=490. because of the wrong condtion i guess but im not sure that whenever the OS is NT it installs the ws_32.dll for NT and also for ME, the dll for ME overwrites the dll of NT and then the pc crashes after reboot..

Then i corrected the condition and everythings works fine


Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 02 June 2007 - 04:18

Those files look like winsock files, isn't there a Microsoft redistributable installer that you can use instead?
Regards
-Stein Åsmul

haroldxious

haroldxious
  • Full Members
  • 70 posts

Posted 04 June 2007 - 05:07

i dont know if there is any Microsoft redistributable installer that i can use