MN-510/ Windows ME problems

I am working on setting up my dad's new computer for a
network. The computer itself isn't "new", but the system
had to run a version of Windows with the NT 4 Shell, and
ME (sadly) was the choice.

Now after we got my dad's old program and everything
loaded onto the computer everything was working great.
Then, after a quick install of the MN-510 (USB Adapter),
nothing involving Windows Explorer (i.e. My Computer,
Internet Explorer, Control Panel) would operate. I would
click the icon for Internet Explorer, and it would start
to come up but then the system would lock.

I only actually got into the browser without freezing
once, and that was the first time. At first I figured it
was because I changed the homepage to www.comcast.net (a
very flash-intensive site) but afterwards NOTHING (see
examples) worked.

Is this a known bug, and if so is there a hotfix? Your
help is much appreciated.

-Fred Dulson

I don't understand the reference to NT4 here. Is this computer running
Windows ME? If yes, can you use system restore and go back to before
you installed "dad's old program" and start from there and install the
MN-510? Does this resolve the problems (before installing whatever
caused the conflict?)

On Sun, 11 Apr 2004 11:25:18 -0700, "Fred Dulson" <(E-Mail Removed)>
wrote:

>I am working on setting up my dad's new computer for a
>network. The computer itself isn't "new", but the system
>had to run a version of Windows with the NT 4 Shell, and
>ME (sadly) was the choice.
>
>Now after we got my dad's old program and everything
>loaded onto the computer everything was working great.
>Then, after a quick install of the MN-510 (USB Adapter),
>nothing involving Windows Explorer (i.e. My Computer,
>Internet Explorer, Control Panel) would operate. I would
>click the icon for Internet Explorer, and it would start
>to come up but then the system would lock.
>
>I only actually got into the browser without freezing
>once, and that was the first time. At first I figured it
>was because I changed the homepage to www.comcast.net (a
>very flash-intensive site) but afterwards NOTHING (see
>examples) worked.
>
>Is this a known bug, and if so is there a hotfix? Your
>help is much appreciated.
>
>-Fred Dulson

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)

When I said NT4, I meant the NT4 Shell (at least I think
that is what it is referred to). Isn't WinXP like NT5.1?
Well anyway, "dad's old program" is not the cause of the
conflict. The cause is the MN-510 (hardware and/or
software). I am positive because as soon as I uninstalled
it, everything went back to normal. My question was if
this was a known bug in Windows ME (and how could I fix
it if it was), or if it was a bug with my hardware or
software.

Hopefully that cleared some things up.

Since you are the only one reporting this, I have to think it is a
conflict between "dad's old program" and either the BNU or 510 driver.
The only way to tell is to perform the system restore and try the 510
without having "dad's old program" on the machine. This is just good
trouble shooting. You have an unknown program that needs to be ruled
out before proceeding. Your references to "shell" in this context are
not accurate but lead me to believe even more that the conflict is
"dads old program".

On Sun, 11 Apr 2004 18:49:33 -0700,
<(E-Mail Removed)> wrote:

>When I said NT4, I meant the NT4 Shell (at least I think
>that is what it is referred to). Isn't WinXP like NT5.1?
>Well anyway, "dad's old program" is not the cause of the
>conflict. The cause is the MN-510 (hardware and/or
>software). I am positive because as soon as I uninstalled
>it, everything went back to normal. My question was if
>this was a known bug in Windows ME (and how could I fix
>it if it was), or if it was a bug with my hardware or
>software.
>
>Hopefully that cleared some things up.

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)