One thing I've found with winME networking has been a little strange.
Following Cary's tips works more often than not. When they don't-- I usually
end up removing the network services and protocol(s), then rebooting and
reinstalling. The NIC driver may also need to be removed in a few cases.
(Older Linksys cards & drivers for one) Basically, you reinstall the
services and protocols one by one, rebooting between each. You normally can
use the drivers etc. already present if you know where they are on the HD.
(Use existing driver) or ignore/cancel the insert cd prompt.
Occasionally, the same sort of thing happens with printer drivers and the
parallel or USB ports. This sort of thing seems to occur (in my experience)
with VIA chipsets and BX440 chipsets. Currently the laptop I use is an older
HP (600Mhz, with a BX440 chip set.) This particular Laptop gave me very
similar symptoms with a PCMCIA ethernet NIC, and later with a wireless NIC.
The ESS modem (semibuiltin on an internal buss) has been a problem as well.
Once you get it working all is well. I've used various Canon and Panasonic
printers with the laptop on both parallel and USB ports. Early USB and
printer drivers were a pain to get working. Later ones seem to be much
better.
We also found an obscure bug in the winME modem system software that can
cause a modem's command reply and status reply strings to not be recognized
properly. This can result in intermittent erroneous connection protocol and
speed reporting, as well as failure to connect or recognize a disconnect.
The modem reply strings on many modems, both internal and external may have
random characters sent before the actual reply string, or the system
software sees noise on the data buss (Don't know which), although the
problem happens less frequently with an external serial modem. The system
software is too dumb to disregard these characters and thus does not always
recognize the response/reply/status string and decode it properly.
"Mike Kay" <mikek-(E-Mail Removed)> wrote in message
news:1107a01c40f1c$56236e40$(E-Mail Removed)...
> Yes - I've worked through your tips at least half a dozen
> times from end to end. That's any easy one so I'm sure
> I've done it right. And as I said I'd been through the
> trouble of getting the MS fix for the problem - which
> didn't help either. I'm kind of stumped. I'll be in to
> hardware swapping next... but since I can see the PC
> announcing itself on the others, I don't think it's a
> hardware problem.
>
> If you could scratch your head for me a bit more I'd be
> grateful.
>
> I really thought, after trying everying else, the VIA
> drivers might cure it..... but they didn't.
>
> Regards
>
> M
>
> >-----Original Message-----
> >Have you tried disabling the Browse Master as explained
> at my site?
> >
> >BTW: Thanks for the kind words.
> >
> >Carey
> >
> >"Mike Kay" <mikek-(E-Mail Removed)> wrote in message
> >news:10d0401c40e85$1b026ec0$(E-Mail Removed)...
> >> I've got a four PC home network - all worked fine. 3xME
> >> and 1x95. All worked fine until I got cable and then on
> >> ME machine blew motherboard (co-incidence).
> >>
> >> Carey's netfixes (www.careyholzman.com/netfixes.htm) is
> >> SUPERB and has got all my network going again - save for
> >> the one PC that's had a new (2nd hand) motherboard.
> Board
> >> is Packard Bell MS61 199VA. Adapter is D Link legacy
> >> ISA. I've followed Carey's tips carefully, been through
> >> them twice... reinstalled ME from original CD, downoaded
> >> 4in1 drivers for board.... and still nothing. The
> >> symptoms are click on My Network Places gives "cannot
> >> browse the network". I've got the ME patch from MS
> >> support (tip 4 and done the browse master fix...)
> >>
> >> If I run NET VIEW from another PC I can see it.... and
> >> sometimes (usually in fact) it appears in My Network
> >> Plances on the other three PCs.... but can't be opened.
> >>
> >> So I guess the hardware is working.
> >>
> >> Any help would be gratefully recieved!
> >>
> >> Thanks
> >>
> >> M
> >>
> >>
> >>
> >
> >
> >.
> >