PDA

View Full Version : Runtime Error



newcster68
03-06-2003, 09:11 AM
http://domania.us/LWN2003/IMAGES/Junkie3.gif

Can anyone tell my what is going wrong with my xp or computer. Over the last week every time a go to a website or even surf different topics in this forum, no matter where I go on the internet I keep getting a popup error telling my there is a runtime error and if I wish to debug. This is getting really annoying now...

DARKSHADOW
03-06-2003, 09:40 AM
if u enter the internet options then click the advanced tab
look for an option,disable script debugging and place a tick next to it.

and that should sort it hope this helps

DARKSHADOW
03-06-2003, 09:44 AM
ps also in the advanced,internet window uncheck
display a notification abouscript error :)

newcster68
03-06-2003, 11:09 AM
http://domania.us/LWN2003/IMAGES/Junkie3.gif


Thankyou soo much, lets hope this works. It never started doing this until I put Office XP SP2 on my pc. Wonder if that has anything to do with it? <_<

Yanks0826
03-06-2003, 11:18 AM
Originally posted by DARKSHADOW@6 March 2003 - 10:40
if u enter the internet options then click the advanced tab
look for an option,disable script debugging and place a tick next to it.

and that should sort it hope this helps
You can try what he suggested but I also had the samre problem.
I had to re-install windows. There was a file that got corrupted, if that happens, you will get some error messages.

Spindulik
03-06-2003, 12:12 PM
I have been writing programs for a few years now (as a hobby).
Here is a possible reason for the &#39;RunTime Error&#39;.

A runtime error usually occurs when a program accesses a bad DLL file.
A bad DLL file could exist due to a virus, shutting Windows down improperly, uninstalling a program and unstalling the DLL. Many programs share the same DLL. For example, when uninstalling a program, you may be ask something like this, "Do you want to uninstall this file? Leaving it on your computer will not harm anything.".

Installing a program that has obselete DLL files can overwrite the newer DLLs and cause problems. Usually can happen with homemade programs that you install. Can happen with illegal hacked software that forces installations.

Another reason for the runtime error is just poor programming. I have created a few programs before, and completely forgot to include the correct coding and runtime files as well.

A hacked DLL file can will cause a runtime error.
---------------------------

My best suggestion, is to reinstall Windows. Backup eveyrthing important now.

newcster68
03-06-2003, 12:58 PM
http://domania.us/LWN2003/IMAGES/Junkie3.gif


Thanku Spindulik&#33;&#33; I now realize that you are 100% correct about my problem. Just this past week I did uninstall a couple of programs which it came up asking me if I wanted to delete certain files that were sharing with the program and I said yes. I bet I should have said no. Thanks again. Do I really need to reinstall windows again or just keep everything the way I have it now? I did what DARKSHADOW told me to do and I haven&#39;t had that error message yet. YET&#33; :angry:

Lamsey
03-06-2003, 04:04 PM
try reinstalling Internet Explorer.

Supernatural
03-08-2003, 08:59 AM
You don&#39;t need to reinstall anything. The problem is fixed, the script debugging notice was disabled. Same thing happened to me and other people who install Office XP. Disabling script debugging fixed it everytime.

Lamsey
03-09-2003, 06:07 PM
You don&#39;t need to reinstall anything. The problem is fixed, the script debugging notice was disabled. Same thing happened to me and other people who install Office XP. Disabling script debugging fixed it everytime.
But won&#39;t the error still be happening? He&#39;ll just not be being told about it.

DARKSHADOW
03-10-2003, 11:12 AM
[But won&#39;t the error still be happening? He&#39;ll just not be being told about it]

no because he disabled script debuggin and the notifcation of script debuggin :)

CornerPocket
03-10-2003, 01:25 PM
Originally posted by Lamsey@9 March 2003 - 12:07

You don&#39;t need to reinstall anything. The problem is fixed, the script debugging notice was disabled. Same thing happened to me and other people who install Office XP. Disabling script debugging fixed it everytime.
But won&#39;t the error still be happening? He&#39;ll just not be being told about it.
Technically yes, however using the disable method it will be ignored as if it did not happen.