I've had VB installed for over a year and I was installing something
else and when i ran VB32 later on I got an "Unexpected Error: Quiting"
error.  I deleted VB and reinstalled, but that didn't help.  Any
ideas?  (Grrr..I hate computers sometimes) :-(

Thanks

 here's the latest :)

I get that error whenever I try to run vb32.exe or any compiled vb
program.  I can run the 16 version, but not the 32 bit.  The error
occurs right after the vb intro screen shows up.  I've deleted and
reinstalled to many times to count. Someone suggested running
regclean, but it's written in vb, hence I get the same damn error.
Obviously I installed something my pc doesn't like, because I've been
using that installation of vb for over a year without having to
reinstall.  God knows I'm not about to call micro$oft and pay them 60
bucks an hour to solve this problem, so I turn to you :)
Any help, suggestions, or m{*filter*}support would be greatly appreciated..

NT4.0 uses MSVCRT40.DLL that is different from WIN95.  The NT4.0 one is
called a wrapper .DLL and calls another .DLL.  WIN95 doesn't have this
called .DLL.  If the install includes the NT4.0 MSVCRT40.DLL its version
is newer and the install replaces the old .DLL.  It just doesn't work.

Uninstall won't help, and finding it is a real problem.  Take a look at
the Win95/system directory.  If MSVCRT40.DLL is about 64K you have the
problem.  (It should be about 306K.)  If so, you need to get the
original and replace it.

There is also a problem with the file OLEPRO32.DLL.  Microsoft has a
knowledge Base article about this and how to prevent it.  Article Q15976

Jack Linder

: >
: > I've had VB installed for over a year and I was installing something
: > else and when i ran VB32 later on I got an "Unexpected Error: Quiting"
: > error.  I deleted VB and reinstalled, but that didn't help.  Any
: > ideas?  (Grrr..I hate computers sometimes) :-(
: >
: > Thanks

: Here's a possibility:
: There is a problem with VB4 applications where the setup
: program/installed files are created on an NT4.0 workstation and then
: installed on a WIN95 system.  If done incorrectly it will corrupt your
: Win95 system and will give you the error you just mentioned.  (BTW,
: don't you just love the "Unexpected Error: Quiting" message.  What goes
: through someones head when they write an error message like this.  Is
: there an "Expected Error"??)

Of course there are expected errors -- but these are trapped, so you
never see them.  "Unexpected" in this context simply means that the
error is not one the software is prepared to handle, so it aborts.
The alternative is to go on and hope everything is OK anyhow -- which
often leads to crashes or lockups.
--
*------------------------------------------------------------------*
* Bill Stockwell          | "The President will keep those         *
* Computing Science       |  promises he INTENDED to keep"         *
* U. of Central Oklahoma  |       -- George Stephanopoulos         *
*------------------------------------------------------------------*