There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
 
Tag Cloud
access audio avg avg 8 bios blue screen boot bsod computer connection cpu crash css dell desktop dma driver drivers dvd email error excel explorer firefox firefox 3 freeze gimp graphics hard drive hardware hijackthis hjt install internet internet explorer itunes keyboard laptop macro malware monitor motherboard network networking outlook outlook 2003 outlook 2007 outlook express pio problem problems router seo server slow sound sp3 spyware trojan usb video virtumonde virus vista vundo windows windows vista windows xp winxp wireless
Software Development
Search
Search in:
 
Advanced Search
Tech Support Guy Forums > Software & Hardware > Software Development >
Runtime errors with Visual Studio 6.0


HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free! Click here to join today! We highly recommend that you print a copy of our Guide for New Members. Enjoy!

 
Thread Tools
Dr. Michael's Avatar
Senior Member with 129 posts.
 
Join Date: Mar 2003
Location: St. Louis, Missouri -- U.S.A.
22-Jun-2003, 12:46 AM #1
Runtime errors with Visual Studio 6.0
Hi,

I work with Windows XP home edition.

I recently installed Visual C++ 6.0 from the Visual Studio 6.0 Enterprise edition.

Since then, I've started to get runtime errors when performing the most mundane of tasks.

For instance, I'll be logging into eBay and a box will popup that says: A runtime error has occurred, Do you wish to debug? Line 1587, syntax error.

I have no doubt that this is related to the Visual software, and I've since uninstalled it.

Any thoughts??

Thanks so much,
Dr. Michael
blynken_182's Avatar
Junior Member with 15 posts.
 
Join Date: Jun 2003
22-Jun-2003, 01:29 PM #2
Hi

I also had the same problem that you are having, do you use internet explorer by any chance?
If this is the case, I think you can solve this problem by going into tools>>internet options>> advanced
and check of the box "disable script debugging"

There could be a few other boxes about debugging that you may wish to remove also.
Hopefully this should work.

Dan
Dr. Michael's Avatar
Senior Member with 129 posts.
 
Join Date: Mar 2003
Location: St. Louis, Missouri -- U.S.A.
22-Jun-2003, 02:12 PM #3
Hi,

Thanks for your reply. Yes, I'm noticing this when using Internet Explorer.

If I disable these debugging options in IE, will my wife lose any debugging capabilities or other features when writing programs for her class with C++ 6.0?

And, was it the installation of Visual that enabled these debugging options in IE?

Thanks,
Dr. Michael
Dr. Michael's Avatar
Senior Member with 129 posts.
 
Join Date: Mar 2003
Location: St. Louis, Missouri -- U.S.A.
22-Jun-2003, 08:05 PM #4
Hi again,

If you don't mind me asking, I do have one more question about Visual C++ 6.0

After installing, it recommends that you go to the tools section and run a program that installs the system symbols.

When starting the installation, I get a message that says that "some of the symbol files could not be located in the input directory. Do you wish to continue?" I went ahead and pressed yes, and continued.

Then, while installing the symbols, I am confronted with messages that state that "the version of the file x.dbg does not match the corresponding dll on your machine. Do you want to copy it?" The choices are yes, yes to all, no or exit. I pressed no, and had to repeat this for about 8-10 different .dbg files that it came across that did not match.

Should I have pressed yes when I encountered the first message about some of the files not being located in the input directory? And if so, should I have pressed "no" or "yes to all" when it asked me about those .dbg files that didn't match the dll's on my machine? Obviously, by pressing no for each one of these that didn't match, not all of the symbols were installed.

Thanks again for taking the time to help.

Dr. Michael
TimCottee's Avatar
Senior Member with 186 posts.
 
Join Date: Oct 2001
Location: Southampton, England
23-Jun-2003, 06:23 AM #5
The reason for the debugging errors you find are because the installation of Visual Studio includes the Visual Studio IDE. This is an IDE which can be used to generate and debug HTML and ASP pages (amongst other things). If this is installed it can be used to debug all sorts of different applications including those that you may access on the web. However if it is a remote application it is unlikely that you will be able to satisfactorily be able to debug it. Turning off the debugging flag in IE as suggested will have no effect on the ability to debug applications that are developed. As for the C++ question. Unfortunately I know nothing about C++ so cannot help there.

Don't worry about the debug message. It is safe to turn it off as suggested and you will lose nothing important by it unless you want to debug your own web applications created using the Visual Studio IDE.
__________________
TimCottee
I know a little about a lot of things and a lot about very little.

Brainbench MVP For Visual Basic
http://www.brainbench.com

MCP, MCSD, MCDBA, CPIM

Visit http://flame2006.org.uk or http://www.timcotte.tk
Dr. Michael's Avatar
Senior Member with 129 posts.
 
Join Date: Mar 2003
Location: St. Louis, Missouri -- U.S.A.
23-Jun-2003, 11:38 AM #6
Thank you so much for your reply.

That was extremely helpful!!

Thanks again,
Dr. Michael
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are Off
Refbacks are Off

You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -4. The time now is 02:40 PM.
Copyright © 1996 - 2008 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.1.0
Powered by Cermak Technologies, Inc.