Opinions on which PCMCIA for lowest CPU utilization?

For simple web work 98 perhaps and the Orinoco or linux as that chip worlks well

Hi,

As I mentioned, I have tested an Orinoco Silver, but that's just 11b.

I was hoping that someone could recommend an 11g PCMCIA also.

Jim

Ummm... when the laptop is idle, the CPU utilization is close to zero. Whatever is eating CPU cycles is not the wireless card. Go unto the Task Manager and display the list of processes. Sort them in order of CPU usage by hitting the "CPU" at the top of the column. Find the process that's burning CPU cycles. It could easily be a virus or insane process.

Better yet, use either Process Explorer:

or even better, System Explorer:

Note that the latest version won't work with W2K, but version 1.4 will.

Is it that high when nothing is happening? See what the CPU usage is like when browsing through the wired connection [assuming it has one]. It may just be using the browser that causes CPU spikes. Task Manager should show which process is hammering the CPU.

Hi Jeff,

When it was running at/near 100%, a big chunk was SERVICES.EXE, then Reg.exe, then Airplus.exe (this was with the Dlink DWL-G650).

If I killed Reg.exe, it went down some, but was still around 60-80%, mostly SERVICES.EXE.

If I killed Airplus.exe, the strength icon in the Systray disappeared, then CPU utilization went back to pretty much nothing.

From searching, I found that that Reg.exe could be killed, but as I said, killing the Airplus.exe meant no more icon in the Systray (which may be ok).

All of the above was with not doing anything on the machine (in answer to alexd's post), except running Task Manager.

I have a feeling that these problems would have been resolved if I had used WinXP and zero configuration or whatever it's called, but I think that would have been stretching it with this laptop (233Mhz, 96MB RAM). I think those Dlink utilities were not good :(...

So, I'm still wondering: Anyone have any good experience with any 11G PCMCIA adapters, running on Win2K?

Thanks, Jim

I don't think the Dlink DWL-G650 drivers are very good. Methinks your testing has adequately pinpointed the culprit (Dlink drivers). I also vaguely recall seeing the 100% CPU utilization problem with some DLink PCMCIA device, but can recall or Google for the reference. This is for a USB device, but I think the problem is similar:

Uninstall the Dlink drivers and try something else.

The DWL-G650 is a 32 bit CardBus device, not a 16 bit PCMCIA device. Therefore, any 32 bit Card Bus device, that has a Windoze 2000 driver should fit and work.

Off the top of my head, the following qualify: Linksys WPC100 Linksys WPC54G Netgear WG511 (and various mutations) I've used all of these with good success under W2K. Among the losers were an assortment of Dlink and Belkin PCMCIA cards all of which had driver problems.

"Troubleshooting High CPU Utilization"

Before you ask about WPA encryption for Windoze 2000, see the last article in:

and:

Hi Jeff,

Thanks for the suggestions.

What about the SMC SMCWCB-G? Have you (or anyone else) had any experience (good or bad) with those wrt utilization?

Thanks, Jim

No experience with SMCWCB-G.

You got me curious, so I fired up my Panasonic Toughbook CF-M34 (Pentium III/800MHz), running W2K SP4, with a Netgear WG511 v2 card. When I connect to my access point, and there's no traffic, the CPU utilization is nearly zero. When Windoze decided this would be the right time to catch up on all the updates I didn't bother installing, it bounced around between about 10% and 90%, averaged about 30%, never hit 100%, and never got stuck at 100%. This is fairly typicial of such cards.

Incidentally, the WG511 v2 card and driver for W2K support WPA-TKIP and WPA2-AES, which are quite important.

Under "Secure WDS" you can add the D-Link DWL-G700AP (F/W v2.10 Thr, 30 Mar 2006) and the ASUS WL-330gE Pocket Router/AP.

I've used a D-Link DWL-650+ (802.11b/g) 32bit PC Card on a Thinkpad 570 (128MB RAM) running W2K SP4. The supplicant was Buffalo's Client Manager

You can use supplicant from different makers, this often works quite well with W2K. You have to experiment.