> I can now ping websites... however... no application requiring
> access to the internet connection will run without fatal error...
[quoted text clipped - 3 lines]
> as previously. OE fails with MSIMN caused an invalid page fault
> in module <unknown> at 0000:00580404.
> A good first step with any error message is to do a google search on the error message. For example:
http://www.google.com/search?hl=en&q=MSIMN+caused+an+invalid+page+fault+in+modul
e+%3Cunknown%3E&meta=
I had tried this but couldn't find anything which appeared relevant on the
first few pages of links returned.
> One of those results is this: http://support.microsoft.com/kb/238585 Read that and see if it applies to you.
Discounted this as I don't have CleanSweep installed.
Running down your list of probable reasons why my win-98 system is unstable:
> 1) Your hard drive is more that 5 years old, and has developed bad sectors. Run Scandisk and do a surface scan.
The HD is definitely over 5 years old. But running Scandisk produces no
errors whatsoever. The scan completes and it reports everything to be fine.
> You may have to replace damaged files from their original CD or from the internet.
I have the original CD. But how would I go about locating damaged files ?
> 2) You haven't run scandisk for more than a year, and you have crosslinked files. Again, run scandisk. You may have to replace some system files that have become corrupted.
File corruption is where I think this is at, as this IE/OE misbehaviour
started occurring after I installed the network card to get LAN connectivity
to get on the Router. Prior to this it all worked fine on dial-up... although
it only ran at 33Kbps. But Scandisk didn't report any "crosslinked files" and
I don't know how to check, detect and replace corrupt files.
> 3) The memory in your system has become faulty, or needs to be re-seated. ... If your system has less than 128 mb of memory, try to add more to bring it up to at least 128 mb, and 256 mb if you can. ... If there's lots of dust in your computer ... then try to blow out all the dust.
The RAM was upgraded to 512Mb last year and looks to be seated firmly, and
inside gets cleaned out regularly and was last done some 6 months ago.
> 4) There are some things running at startup that are causing problems or otherwise don't need to be running.
I'd run msconfig and have removed all that doesn't look to be required.
> 5) Your system needs to be updated via the WindowsUpdate website. See if your system can access the website http://v4.windowsupdate.microsoft.com/en/default.asp (using IE).
Ironically, it got updated by dial-up whenever required, but since this
problem started a couple of weeks back I've not been able to access any web
resource.
> 6) Your system has been infected with a trojan, worm or virus. There are a few things you can do, but I won't outline them here until all of the above have been eliminated as possibilities first.
Prior to installing the LAN card, I'd removed NAV to replace it with AVG and
run a new scan with AVG and removed anything that looked dubious... which
wasn't much.
I really want to avoid a complete op/sys replacement as I have 7 years of
stuff on here which I'd very much like to leave as is. I see my problem as
needing to understand what's become corrupt during the LAN card installation
and how I can replace these files. Or am I barking up the wrong tree... ?
btw, many thanks for all the help so far.
Paradoxdb3 - 23 Oct 2007 01:45 GMT
I'm not going to be much help as I don't know much about troubleshooting
these kinds of problems. But I will tell you what I do in cases like these
and it works 100% of the time. I reformat and reinstall! Not only does
everything run nicely again, but the registry is brand new and my computer is
zippity fast! Just make sure you have all your drivers for your ethernet
card/sound card/video card and all other hardwre connected to your computer.
Oh, and of course, make sure you have all your installation files/discs!
> > A good first step with any error message is to do a google search on the error message. For example:
> http://www.google.com/search?hl=en&q=MSIMN+caused+an+invalid+page+fault+in+modul
e+%3Cunknown%3E&meta=
[quoted text clipped - 51 lines]
> and how I can replace these files. Or am I barking up the wrong tree... ?
> btw, many thanks for all the help so far.
Witsend - 24 Oct 2007 11:07 GMT
I'd (reluctantly) reformat & reinstall IF the machine was performing poorly,
but it's not... it's pretty zippity as it is actually. All I've done is to
install a network card and now some 98 apps don't want to connect to the
internet. The rest of the machine is absolutely fine and just as I want it. A
complete rebuild seems overkill (...and I doubt I could locate all the
required drivers anyway.) Isn't there a better way to be able to
correct/reinstall just the failing apps... ?
98 Guy - 25 Oct 2007 01:16 GMT
> I'd (reluctantly) reformat & reinstall IF the machine was
> performing poorly, but it's not...
Go spend $50 for a new 80 gb hard drive and swap it into your computer
as the primary (C) drive and remove your existing drive. Then install
98 on the new drive. If you get it working, you can re-connect your
existing drive in the secondary or slave position and copy all of your
personal files from the old drive to the new drive.
Yes, you'd also have to re-install your apps to the new drive as well.
Witsend - 27 Oct 2007 11:35 GMT
>
> > I'd (reluctantly) reformat & reinstall IF the machine was
[quoted text clipped - 7 lines]
>
> Yes, you'd also have to re-install your apps to the new drive as well.
So... that's it then... ? A complete operating system and application
install on a brand new HD is the only way to get a couple of Windows apps to
see a working internet connection... ?! We're back to "designed obsolescence
.vs. operator stupidity." If you ask me, it seems pretty stupid to have to
reinstall an entire operating system just to get IE to see a network
connection...sigh...
Oh well, it wasn't completely without learning opportunity, so thanks v.
much for your help, it was appreciated and I thought for a short while that
we might actually fix it.
Cheers, Witsend.