G
Guest
Guest
Archived from groups: microsoft.public.windows.networking.wireless (More info?)
This problem only happens with IBM wireless cards on T40p's, usually happens
in places where there more than one AP available, and it is bouncing between
them. Will produce bad_pool_caller error blue screen, which usually points
to bad driver. The Cisco or Intel cards have never had the problem. The
firmware and software have all been updated on the AP's. Seems to come and
go. Doesn't matter what IBM driver, T40 bios version, Windows level,
anything we can put a finger on. The IBM engineers didn't know either; they
wanted to have it 100% re-produce able before they would look at it. We
thought it was the XP zero configuration wireless service running, stopping
it didn't seem to help.
Any one experiencing similar problem?
Thanks,
John
This problem only happens with IBM wireless cards on T40p's, usually happens
in places where there more than one AP available, and it is bouncing between
them. Will produce bad_pool_caller error blue screen, which usually points
to bad driver. The Cisco or Intel cards have never had the problem. The
firmware and software have all been updated on the AP's. Seems to come and
go. Doesn't matter what IBM driver, T40 bios version, Windows level,
anything we can put a finger on. The IBM engineers didn't know either; they
wanted to have it 100% re-produce able before they would look at it. We
thought it was the XP zero configuration wireless service running, stopping
it didn't seem to help.
Any one experiencing similar problem?
Thanks,
John