I've had windows give some weird errors with fork and some other non supported perl things. What does your code look like.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
The error seems to occur when a home page is loaded that does not call to perl. I checked the html and there is nothing that should be calling to perl at all in fact. Any ideas?
Very Possible. The computer has been having issues with RAM lately. I hope that I do not have to replace it. If anyone else has any idea as to what it is, please let me know.
Home page?? Like your loading a web page and it is calling perl locally on your machine? Or you are trying to call local perl scripts from IE or something?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
Well, I think one thing is almost for sure, it has nothing to do with perl. Try removing one RAM module at a time until the error no longer occurs. Then replace that module.
I would love to be able to remove the ram, but there is only one stick for that computer and I am just planning on buying several more, so when those come in, I will attempt the swap. The odd thing is that this error only occurs when the website is loaded. Other sites that actually do use perl do not cause the error.
It definitely seems to be a software (windows) error. If you google for 0xc06d007e you'll find some postings (including yours) on the subject. However there is no clearly identified cause of the error (someone blames the Windows Media Manager 11, others have other stories).
Did you any other installations before running that perl program? Do you have a previous checkpoint to fall back on? what do you mean when you write: I have updated all software?
I'm afread you'll have to perform a clean install of windows.
_________________________________
In theory, there is no difference between theory and practice. In practice, there is. [attributed to Yogi Berra]
Yeah, there is no way that I am re-installing windows, and it is not a windows Media Player 11 issue since that isn't even installed. The deffinition of all software is the following:
*MS Windows XP Updates including SP3 (problem occured before SP3 installed)
*Perl
*IIS
*Other non-related softwares that were disabled at time of issue
I have also googled the problem and the only thing that I came across that might be of interest was that Dreamweaver might at some code in to activate options that might cause perl to act up. I am still looking in on it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.