• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Wireless G Network Card Problem

M

mt2568

Member
Hey all, whoever out there is good with drivers I would gladly appreciate the help...

I recently purchased a 802.11G wireless system for 2 desktops (1 hardwired) and 1 notebook - the router and wireless desktop work great, but the laptop is giving me a bit of trouble.

Little background...this is a hp paviliion prefab with XP home bought about 2 years ago new...the card is the D Link DWL-G630

Summary of problem...basically every time i boot up the computer thinks the wireless card is new hardware, but if i unplug and replug the card back in everything works fine (i.e. all the drivers are fine) until i shut down and then i have to do it again when I boot up...

What problem I think may be involved...there is another cardbus controller on this laptop (internal) named 02 Micro 0Z6912 Cardbus Controller - I think they are interrupting each other...does anyone know what could cause a piece of hardware with perfectly good drivers and good functioning to decide to forget it has those drivers when you restart unless you unplug and plug it back in?
 
Make sure that you have the most recent Drivers installed for the card and check HP support to see if they have any firmware upgrade.

I come across many old Laptops that do the same and I could not find a solution. I basically tell people to take the Card out before they start that computer and to insert it after the boot is done.

:sun:
 
What would a firmware upgrade do? And when you say that firmware upgrade you mean on the internal cardbus that came with the laptop right?

The only reason I'm trying to avoid the pull in and out scenario is because eventually the card is going to get worn out.

Thanks for your help though man.
 
Hey just to make the situation a little clearer I checked the xp event log and this is what is going on...

While validating that \Device\Serial0 was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers. The device is assumed not to be a serial port and will be deleted.

anyone know what to do with this?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top