On Mon, 10 Jul 2006 12:53:02 -0700, Turbo500 wrote:
> First of all, let me say THANK YOU if you can help me with this and if you
> respond.
>
> OK, my roommate brought over her Mom's HP Pavilion 6736 desktop computer.
> 667 MHz, 256MB RAM, 20GB HDD, Windows ME. We are trying to install a network
> card in it. It's the Network Everywhere NC100 NIC Card. Basically we got it
> installed, but here's the problem:
>
> When I am PHYSICALLY connected to the router, meaning a CAT5 cable is going
> from the computer to one of the ports on the router, the computer will NOT
> open up Internet Explorer, or Windows Explorer (meaning My Computer), also it
> will NOT even open up the control panel. The computer IS GETTING an IP
> address from the router because when I log in to the router, I see the
> computer, plus, when I run "winipcfg", it shows the connection and the IP
> "192.168.1.whatever".
>
> When I physically DISCONNECT the cable from the back of the computer and
> reboot, everything is fine again, IE opens fine, so does My Computer, and so
> does the Control Panel.
This is weird because the Explorers (Internet and Windows) should start,
or not, independent of what is happening on the LAN.
> It sucks because we are trying to get this connected to a LAN, but it
> obviously won't do it.
>
> Should I have her re-install Windows ME? Does anyone maybe know what the
> problem is?
You want to reinstall _her_ Windows because _your_ computer has a
problem? I am not sure that I follow the logic.
When both computers are connected tot the LAN, does Windows Explorer
seem to hang with the search icon up, or does it just not start? Either
way, is there an instance running in the task list after the failure to
start?
Do you get the same IP address when MSIE starts (stand alone connection)
as when it fails to start (two computers connected to the router)? It
the router configured to assign IP addresses to the LAN using the
built-in DHCP servers? Or do you configure the LAN IP addresses by hand.
> I used to use Windows ME back in the day and contrary what 99% of the world
> says (which is that Windows ME sucks), I disagree, I never had a problem with
> Windows ME, and I actually loved it, at the time. I got Windows ME for free
> back in August 2000 because I was working for a computer retailer that sold
> Microsoft products and I got it at one of the now non-existant Microsoft Road
> Show's.
>
> Anyways, I have used this exact same NIC card in my old Windows ME computer
> and it worked fine, in fact the card we put in this HP Pavilion is my
> roommate's old NIC card and that ran fine with Windows ME as well. So I know
> it's not a defective card, at least I'm like 99.999999999999% sure. It's
> getting an IP address.
>
> I think it may have something to do with the fact that this computer was
> setup for dial-up access and at first it would ask to dial the connection, I
> would say cancel, and it would just sit there. So I went into "internet
> options" and said "never dial a connection" that helped to NOT bring up the
> dialog box but now it just sits there when physically connected.
Which computer are you speaking of? And I don't see how the former
dial-up connection would be an issue in the original problem; though it
is easy enough to remove references to dial-up connections and force the
computer to always use the LAN for Internet access.
Post 'ipconfig -all' for each computer.
> Also, after I installed the NIC card it brought up that "enter name and
> password" box so I DID NOT put in a password, like you're suppossed to if you
> don't want to see that box again, but the box shows up still, it's weird.
>
> I haven't used "ME" in a long time so I kindof have forgotten all the little
> ins-and-outs of it. So thanks for the help if you can provide some.
>
> Once again, I never got Windows ME to crash and I used it for almost 2 years
> I think. (I'm just defending Windows ME.)
>
> Thanks everyone.
>
> - TC
One very lucky man. Windows ME is shy on resource capacity; I can crash
a Windows ME system in under thirty minutes. I can recover from a low
resource condition that would bring Windows 98 to its knees; but, once
Windows ME goes below 10% free resources, recovery via a normal shutdown
is less than fifty-fifty.
Windows ME is basically Windows 98 with boot to DOS removed, and System
Restore added. It is still, like Windows 98, a 32-bit graphical shell
overlaying a 16-bit operating system; nothing at all like a 32-bit,
multi-threaded OS. It still suffers the limitations of MS-DOS.
That said, I can run it for up to three days without a reboot, if I am
careful about which programs I run when.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
Similar Threads
Linear Mode
