Breadfan
10-24-01, 04:14 PM
Have a computer here that seems to get a Run32.dll invalid page fault on startup. Its on this guys computer that has like all these freeware programs and screensavers, the "weatherbug" program, "yahoo tickter" yada yada yada running on it.
BTW, its a Pentium II 266mhz with 96mb RAM yet he insists on having all this junk running...suffice to say a reboot takes FOREVER.
I should be more of a pain at work, and demand that he take this stuff of his computer, but in reality, if it works, I dont care cuase I don't have to deal with it. Right now I'm not gonna bother with a format/reinstall...
Anyway, I got everything working, but the run32.dll error still comes up. There is a reference in the details to another .dll, but I can't remmeber which one and I doubt I could find where its attached.
I think you'll agree taht this would be wonderful:
Imagine a program that could trace the fault at the dll and tell you exactly what program caused the problem...or driver. That way you'd know exactly whats causing the fault so you could remove some funky freeware program or reinstall/update a bad driver.
I'm not a programmer, but it doesn't sound too tough...one would expect that the error that causes the fault could just be traced back to the program or "module" that it originated from. Then it could atleast tell you more about whats cuasing it....I really don't see much of a point in seeing the memory hex addresses which is what MS give ya...
I'd love to see that...but maybe it exists. I've never seen anything like that, but I think it'd be a pretty hot diagnostic too. Did I explain it correctly? Does something like that exist? If not, is it really tough to do and is that why we don't see something like that?
Mike
BTW, its a Pentium II 266mhz with 96mb RAM yet he insists on having all this junk running...suffice to say a reboot takes FOREVER.
I should be more of a pain at work, and demand that he take this stuff of his computer, but in reality, if it works, I dont care cuase I don't have to deal with it. Right now I'm not gonna bother with a format/reinstall...
Anyway, I got everything working, but the run32.dll error still comes up. There is a reference in the details to another .dll, but I can't remmeber which one and I doubt I could find where its attached.
I think you'll agree taht this would be wonderful:
Imagine a program that could trace the fault at the dll and tell you exactly what program caused the problem...or driver. That way you'd know exactly whats causing the fault so you could remove some funky freeware program or reinstall/update a bad driver.
I'm not a programmer, but it doesn't sound too tough...one would expect that the error that causes the fault could just be traced back to the program or "module" that it originated from. Then it could atleast tell you more about whats cuasing it....I really don't see much of a point in seeing the memory hex addresses which is what MS give ya...
I'd love to see that...but maybe it exists. I've never seen anything like that, but I think it'd be a pretty hot diagnostic too. Did I explain it correctly? Does something like that exist? If not, is it really tough to do and is that why we don't see something like that?
Mike