| Title: | Microsoft Visual Basic |
| Moderator: | TAMARA::DFEDOR::fedor |
| Created: | Thu May 02 1991 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2565 |
| Total number of notes: | 10453 |
I have a PC Installation kit that has been created with the VB Setup Wizard under Windows 95. Does anyone know of any problems with the SETUP.EXE included in this kit when the installation is performed on NT ? The reason I ask is that the kit seems to work fine on some PC's running NT, but on others it immediately exits with an "Unexpected error: Quitting..." message and seems to get absolutely nowhere. Anyone any ideas as to what may be causing this ? Steve.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2545.1 | NPSS::GLASER | Steve Glaser DTN 226-7212 LKG1-2/W6 (G17) | Wed Apr 30 1997 11:45 | 25 | |
I had a similar problem trying to install VB4 and Visual SourseSafe.
Everything else installed just fine but these would crash with various
random errors (usually a GPF followed by an endless set if dialog boxes
containing an obscure error message and asking me to click OK -- it was
not consistent and reinstalling the same program would generate
different errors).
Turns out something had installed a bogus version of control 3d in my
System32 directory.
NT 4.0 supplies ctl3dv2.dll. Apparently some setups look for
ctrl3d.dll (or something similar -- I deleted the file and don't
remember the exact name) and will use it if found in preference to
ctl3dv2.dll.
Something I installed noticed the absence of ctl3d.dll and installed an
ancient one that crashed later setups of unrelated applications. At
the time of the problem, there wasn't much non-Microsoft stuff on my
system (I was rebuilding from scratch) so it could be an errant
Microsoft application. I don't know which install was the culprit.
Microsoft support was particularly useless in helping find this. They
wanted me to reinstall everything from scratch.
Steveg
| |||||
| 2545.2 | Still no further on | CHEFS::geyzuh.reo.dec.com::Steve_Marshall | Wed Apr 30 1997 13:13 | 20 | |
I have now found a Windows95 system that does the same thing, so the fact that the machine was running NT was a red herring. It looks as though something is upsetting SETUP.EXE during its initialisation processing. As SETUP.EXE is a 'standard' Microsoft bit of kit, I don't have a clue what it is doing, and therefore don't really know what to look for upsetting it. As usual it is a really helpful message ... All the user does is double-click the SETUP.EXE (no other applications running on the PC at all) and after about 10 secs it just barfs and gives up. Nothing useful is output by it at all. This is going to be a bit of a needle-in-a-haystack job ... Steve. | |||||