Unable to Install Driver

Yeah - my inclination is that way as well

OT - I'll be in touch later..... Norton(??)-induced problem on an XP box

--
Noel Paton
CrashFixPC

Nil Carborundum Illegitemi
www.crashfixpc.co.uk
"Mike M" <No_Spam DeleteThis @Corned_Beef.Only> wrote in message
news:%237%23zif$6JHA.3860@TK2MSFTNGP05.phx.gbl...

>> ..I'd still love to find out what prevented 'normal' installation
>> working properly though.
>
> As would I and, showing my known bias, I can't help feeling that Norton
> had a hand in the problem.
> --
> Mike
>
>
> Noel Paton <noeldp(spamless)@crashfixpc.co.uk> wrote:
>
>> Well done that man!
>> 10/10 for persistence!
>> ..I'd still love to find out what prevented 'normal' installation
>> working properly though.
>

Mike,

I am having a similar problem with trying to install a Sabrent G802 pci
wireless card in my HP6745C (Windows ME). On initial installation the
install program would hang just before completing (the progress bar extended
all the way to the end). On restart, hardware showed as recognized, and the
green light on the card blinks on. The problem appears to be with the Ralink
wireless utility installation.

I do get a startup alert that AeGise2.dll is missing. FYI, the Sabrent card
has a Ralink 2561 (RT61). I went on the Ralink site and downloaded and
installed that driver (version 1.2.6.0), but it still hung on the Ralink
utility installation. I have to force the install program closed every time.
After reading the posts here, I thought perhaps installing the most recent
version of the Ralink utility might work, but it did not (it was a 2009 USB
RT7x driver package).

Last night I decided not to force kill the hanging install and went to bed.
I woke up to a different message this morning: an error has occured in your
program IS_ap_sta_6x_d_1.

Upon reboot, I didn't see the usual Aegis2.dll missing notice, but instead,
that Is_ap_sta_6x_d_1 has caused an error in I81XDW9.DRV, which I found out
is for the Intel 82810 graphics controller. I updated the graphics
controller to the most recent version I could find (my previous was dated
2000, the update...I think v6.7, was dated 8/23/2002), and tried to reinstall
the WAN card driver and Ralink utility (both the RT6x and RT7x versions), but
it hung again. Keep in mind, that throughout all these reinstalls, the card
is recognized upon restart (hardware install window briefly opens), and the
green light is blinking.

Ralink exists in the start menu, and there is a Ralink folder in my
programs, but upon execution, I get a missing Aegise2.dll message (I'm not
sure where to look for this dll, but it is not in the Ralink folder)

So my problem is that I think I have a properly installed WAN card (it shows
as properly installed in Device manager, and the green light is on), but I
don't have a functional utility to get myself connected. I can't find
anything to manage the connection on the ME system which is similar to my
other wireless XP systems.

I thought there might be a 3rd party wireless management utility, and I
thought I found one (BVRP Connection Manager Lite 1.0), but the several
dowload sites I found actually download v1.1, which upon install alerts an
incompatable OS and shuts down the install.

Since I think my wireless card works, is there a simple solution to getting
myself connected to my network? I have a Robotics USR5461 wireless g router,
using a WEP key.

"Mike M" wrote:

> Noel,
>
> I first sent John the RT73 chipset driver files from my install and got John
> to point the unknown device in Dev Man (which was the wi-fi device) at where
> they were located and they then installed as they should and the device was
> then recognised in Dev Man. However due to Win Me (unlike XP and later)
> having no native capability of handling wi-fi I had a further look at the
> Aegis folder created by the driver installer on my system and established
> that AegisI2.exe was the Aegis installer. I therefore sent John a copy of
> the Aegis folder and on executing AegisI2.exe Aegis installed and I
> understand John was then able to configure and use a wi-fi connection using
> the Edimax device.
>
> > ..I'd still love to find out what prevented 'normal' installation
> > working properly though.
>
> As would I and, showing my known bias, I can't help feeling that Norton had
> a hand in the problem.
> --
> Mike
>
>
> Noel Paton <noeldp(spamless)@crashfixpc.co.uk> wrote:
>
> > Well done that man!
> > 10/10 for persistence!
> > ..I'd still love to find out what prevented 'normal' installation
> > working properly though.
>
>