|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Visual BASIC has encountered a problem ...Every time I close VB6 SP6 with Common Controls update, VB6 "crashes" with
this error message. This occurs on several PCs. Running on WIN XP SP2. I always click "Send Error Report" but never get a response (sometimes I do get a response for other problems). AppName: vb6.exe AppVer: 6.0.97.82 ModName: vb6.exe ModVer: 6.0.97.82 Offset: 0003f08f I guess MS does not care anymore. "Lorin" wrote: If you are talking about the "Error Reporting" dialog, then you will be > Every time I close VB6 SP6 with Common Controls update, VB6 "crashes" with > this error message. This occurs on several PCs. Running on WIN XP SP2. > I always click "Send Error Report" but never get a response (sometimes I do > get a response for other problems). > > AppName: vb6.exe AppVer: 6.0.97.82 ModName: vb6.exe > ModVer: 6.0.97.82 Offset: 0003f08f > > I guess MS does not care anymore. waiting a very long time before you here anything back from MS. The report it does is just a slimmed down Dr Watson summary, which MS collects and stores in a database by OS, Application, Component, etc. No 'identity' information is supplied. MS has no clue "who" you are or cares. It uses this information to determine if there is some specific pattern of errors with MS components and the OS. 'Unknown' or custom applications are essentially ignored. This feature should always be turned off on a development computer, and usually for a corporate computer running mostly proprietary software as well. Better to use a runtime debugger (such as Dr. Watson or WinDbg). As for the exact nature of your problem - it is impossible to guess. There are known issues with SP6. There are known issues with XP. There has always been problems associated with applications not properly working on some boxes. (I think those started back in the Win3 days.) You need to round up the usual suspects and discover the source yourself, don't expect a call from MS. -ralph I guess I was wondering if many others are having the same result when
exiting VB6 SP6+. This has nothing to do with the app being worked on in the IDE. MS must be getting a flood of these reports from VB developers. Show quoteHide quote "ralph" wrote: > > > "Lorin" wrote: > > > Every time I close VB6 SP6 with Common Controls update, VB6 "crashes" with > > this error message. This occurs on several PCs. Running on WIN XP SP2. > > I always click "Send Error Report" but never get a response (sometimes I do > > get a response for other problems). > > > > AppName: vb6.exe AppVer: 6.0.97.82 ModName: vb6.exe > > ModVer: 6.0.97.82 Offset: 0003f08f > > > > I guess MS does not care anymore. > > If you are talking about the "Error Reporting" dialog, then you will be > waiting a very long time before you here anything back from MS. The report it > does is just a slimmed down Dr Watson summary, which MS collects and stores > in a database by OS, Application, Component, etc. No 'identity' information > is supplied. MS has no clue "who" you are or cares. > > It uses this information to determine if there is some specific pattern of > errors with MS components and the OS. 'Unknown' or custom applications are > essentially ignored. > > This feature should always be turned off on a development computer, and > usually for a corporate computer running mostly proprietary software as well. > Better to use a runtime debugger (such as Dr. Watson or WinDbg). > > As for the exact nature of your problem - it is impossible to guess. There > are known issues with SP6. There are known issues with XP. There has always > been problems associated with applications not properly working on some > boxes. (I think those started back in the Win3 days.) > > You need to round up the usual suspects and discover the source yourself, > don't expect a call from MS. > > -ralph > Lorin wrote:
> I guess I was wondering if many others are having the same result when Lots (most?) VB6 users didn't update to SP6, because a) there were no fixes> exiting VB6 SP6+. This has nothing to do with the app being worked > on in the IDE. MS must be getting a flood of these reports from VB > developers. relevant to their lives, and/or b) all the bug reports that hit as soon as it did. >>> I guess MS does not care anymore. That, you got exactly right. They don't give a damn about VB6, and in factwould far prefer that it not work for you. I know that doesn't help, but that's the way it is. On Tue, 7 Mar 2006 16:05:47 -0800, "Karl E. Peterson" <k***@mvps.org> After observing the effects of SP6 on commerfcial app development, Iwrote: >Lorin wrote: >> I guess I was wondering if many others are having the same result when >> exiting VB6 SP6+. This has nothing to do with the app being worked >> on in the IDE. MS must be getting a flood of these reports from VB >> developers. > >Lots (most?) VB6 users didn't update to SP6, because a) there were no fixes >relevant to their lives, and/or b) all the bug reports that hit as soon as >it did. acme tot he conclusion that SP6 is a virus. It s*cks grand time. >>>> I guess MS does not care anymore. **********************************************************************> >That, you got exactly right. They don't give a damn about VB6, and in fact >would far prefer that it not work for you. I know that doesn't help, but >that's the way it is. >-- >Working without a .NET? >http://classicvb.org/ > > Richm***@sympatico.ca Dog thinks: they feed me, they take care of me: they are gods. Cat thinks: they feed me, they take care of me: I am god. http://www3.sympatico.ca/richmann/ http://www.geocities.com/richmannsoft/ ********************************************************************** "Lorin" wrote: <snipped>> I guess I was wondering if many others are having the same result when > exiting VB6 SP6+. This has nothing to do with the app being worked on in the > IDE. MS must be getting a flood of these reports from VB developers. > > "ralph" wrote: > LOL Actually it has been my experience that c and C++ developers have that record. The ability to abuse uninitialized pointers at will gives them a marked advantage. <g> -ralph You are going to have to debug this yourself. The problem could be almost
anything from memory cleanup to a stack overrun where you set things to nothing over and over again until you run out of stack. I would bet you do not get the problem in development mode but do when compiled and run outside of the VB IDE. What you want to do is set breakpoints or msgboxes step by step until you narrow the range of the error to a single line of code... then rewrite the code or the exit routine. Show quoteHide quote "Lorin" <Lo***@discussions.microsoft.com> wrote in message news:49583B31-E0E4-4C83-90EF-E52662AF0CAA@microsoft.com... > Every time I close VB6 SP6 with Common Controls update, VB6 "crashes" with > this error message. This occurs on several PCs. Running on WIN XP SP2. > I always click "Send Error Report" but never get a response (sometimes I do > get a response for other problems). > > AppName: vb6.exe AppVer: 6.0.97.82 ModName: vb6.exe > ModVer: 6.0.97.82 Offset: 0003f08f > > I guess MS does not care anymore. |
|||||||||||||||||||||||
Other interesting topics