what is GLBSSTUB ?

[MavrickStl]

Guys,

I am trying to install a 16-bit application on Windows NT workstation with SP6. 80% in install I am getting this error "GLBSSTUB caused a general protection error in module KRNL386.EXE at 0001:1E2E". My question is:

1) What is this GLBSSTUB? I have read somewhere that it a wise file? I have no idea. May be it is part of Win installer I am using. I have only Setup.exe, and no other information is available. Installation went well on most of the PC's, but I am getting this error on few of them.

2) May be this error is caused by a missing file in the installation set (setup.exe)? But then why I am not getting this error on all the machines.
Thanks,

Mav


2)

 

[wolluf]

Mav,

You've got 3 posts (2 in this forum, 1 in 2k pro) which look to be the same problem. Are they? And does this mean you're getting setup failures on NT & 2k - but that its also working on both in some cases? (because if it is, that seems to rule out missing installation files).

 

[MavrickStl]

wolluf.

Thanks for your reply. Yes, they are part of the same problem. I posted it in both the forms because I am experiencing the same problem on NT and Win2000. After doing little more research I found out that the install set for the application (16 bit VB application) was prepared using Windows Installer software designed by Great Lakes Business Solutions hence the name GLBSSTUB. This company is no longer in business ( I think it is bought by Microsoft) hence I cannot seek any help from the vendor. I think that it is trying to use the same memory address (cause error is caused in module KRNL386.EXE) already used by some other program running on NT or 2000 machine during the install. Since I can not find, which other program is using the same memory address only think I can do at this moment is to somehow clean the memory by stopping all other programs using task manager ctl-alt-del and end process. Delete all temp files and try to install the application again. Let me know if you can think of something else? Another possibility is that some of the 16 bit DLL’s are not able to self register at the end of the install ( just a guess).

Thanks,

Mav

 

[wolluf]

Other than making sure as little as possible is running, only other thing I can suggest is making a shortcut to setup.exe, going into its properties and ticking the run in separate memory space box (presuming setup is 16-bit if its installing 16-bit app) to see if that makes a difference.