Re: Panic Button Hit! Need Help!
From: dnagel (NOTGrandNagel_at_hotmail.com)
Date: 04/23/04
- Previous message: Robert: "Re: Windows File protection (WFP) error in setup (using Visual Studio 6.0 SP6 Merge Modules MSM)"
- In reply to: cfshuhl: "Re: Panic Button Hit! Need Help!"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 23 Apr 2004 14:18:31 -0700
cfshuhl wrote:
> Well, I tried to break compatibility, and that did nothing. On a whim, I tried to change the DLL addresses, thinking maybe there was some internal memory boundary that was being violated. Again nothing. Then I tried the P-Code idea, and lo that worked.
>
> However, because our applications are very performance sensitive (milliseconds can be, on occasion, the difference in whether we can do something or not), I am hesitant to employ this as a fix. I know it will be a tough sell to my bosses. I guess the question is, have I discovered a compiler bug?
for S&G, try all the normal clean out procedures....
Grab all the source files from their folders, place them into a new
folder set. Note, do not grab anything that is not your source... (i.e.
only take the bare minimum necessary files, VBP, FRM/X, CLS, BAS, CTL/X
...)
Make sure every module (all src files) have Option Explicit.
Fix everything it complains about
The next steps get messier as I go along
Pull everything out of a form that needs to get stuffed into an FRX
(same for Controls - CTX) This consists of everything that you
might have set in the properties window for images, pictures, etc.
Start adding conditional compilation constants/checks into the code to
hide large portions of your code from the compiler. If you get a clean
native code compile after any part, you have a good place to start
narrowing down the spot thats causing the problem.
I've seen a line of code (that was narrowed down to be the root of the
problem) get cut and pasted back in and the problem goes away!
Goog luck...
D.
heres a few thougts from some OP's post
The Symptoms:
- VB crashes whilst writing EXE (toward end of process)
- Also: VB sometimes crashes when merely viewing the
Project Properties\Make tab !?!?!
- NO messages or events whatsoever!
- Object files (.OBJ) are left in the compilation folder
- Error occures under Windows 2000 only (same project!)
- Same project code compiles to EXE without error under
Windows NT4 (in my case)!!!
- The exact error also appeared with VERSION 5 (as well as
VB6)!!!
- Uninstalling, rebooting and re-insalling does NOT help.
- I can compile an nearly new project OK (not fully tested
though)
Following my search for help today... things I am going to
try:
- Disabling Options\Environment\Prompt to Save Changes
(see Q214427)
- Disabling Options\General\Background Compiling
- compiling without Optimisations
- compiling with P-code option enabled
- Try setting Project Name to something WITHOUT dots
(i.e. "MyProgName" rather then "My.Prog.Name")
- Reducing length of Comments property
- Make sure I have OCX files registered correctly
- Uninstall VB6 and VB5m reboot, reinstall VB6 only
- Disable Addins...
===============================
To prevent add-ins from being loaded when Visual Basic
starts:
Start Notepad.exe.
Edit the VBAddin.INI file in your Windows directory and
set all of the entries to zero (0). For example:
Original: AppWizard.Wizard=1
Modified: AppWizard.Wizard=0
Save VBAddin.INI.
Restart Visual Basic.
================================
- Rebuild project by adding forms and modules to a NEW
project
- Pull my hair out and jump out of a window !!! (joke) :)
What I am doing:
- Compiles OK under Windows NT4 (never has been a problem)
- Using Windows 2000 (SP2)
- Using VB5 and VB6 (currently together)
Conclusions / thoughts:
- Error occurs in VB5 and VB6 under NT4 and 2000 (so does
not seem version related?)
- Thus, the problem could be PROJECT related (perhaps
corrupt files?)
VB Project Info:
- Project is 10,000 lines or so (including comments) !!!!!
- Contains version 5 common controls (tried 6, same error)
- [too tired and fed up to list anymore, boo hoo] :(
- Previous message: Robert: "Re: Windows File protection (WFP) error in setup (using Visual Studio 6.0 SP6 Merge Modules MSM)"
- In reply to: cfshuhl: "Re: Panic Button Hit! Need Help!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|