Excuse butinski - According to :-
http://www.mondoplast.ro/download/pl...M-WL3552V1.pdf

Planet WL-3552 Wireless PCMCIA Card - User Manual
Chap 2, page 6 - Installation Procedure.

Did you run the setup.exe program (on the CD) BEFORE inserting the card?
(Important! - Do NOT use the "Add New Hardware" wizard in Control Panel to
install it)

Start over and be sure to read the note immediately preceding section 2.1
(Also! Check for and "Remove" any/all existing (PCMCIA WiFi) drivers shown
in Device Manager in SAFE MODE before you start to re-install)

On hind-sight, as you are also having problems with your other PCMCIA
devices, "Remove" any/all PCMCIA devices from Dev.Man (IN SAFE MODE) before
re-booting into Normal Mode and then make sure that there are no further
error reports before you start the fresh installation process.

Mart



"jj mac" jj wrote in message
...
Mike

Thank you for your prompt reply.

I have tried to update the device drivers in Device Manager using an
updated
driver supplied by the vendor of the PCMCIA wireless card and the drivers
supplied with the card.(the Microsoft proposed fix.) Likewise with the
USB
to Fast Ethernet Adapter.
In each case I got a message to say that the best driver was already
installed.
I also deleted/removed the devices in Device manager & reinstalled them
from
scratch using the Add New Hardware Wizard. No resolution was found. The
ubiquitous "NDIS.VXD,NTKERN.VXD device loader(s) for this device could not
load the device driver." Error message remains.

I have Googled NDIS.VXD,NTKERN.vxd and find that many others have similar
problems with these device loaders. There are a number of solutions
mentioned that have worked for some but not for others. In one of your
posts
you mentioned that NTKERN.VXD was a core device driver built into the
monolithic file vmm32.vxd. One solution which caught my eye was to
refresh/replace NTKERN.VXD in vmm32. It was described for a win.98
machine
but it could also work for WIN ME. The solution is described as follows:
Run sfc to extract NTKERN.VXD from the Windows 98 SE disk into
C:\windows\system and C:\windows\system\vmm32, and reboot. That's it.
AND this statement which I do not understand followed.
To resolve this behavior, remove the following two lines of code in the
C:\Autoexec.bat file by using a text editor,
SET windir=C:\WINDOWS
SET winbootdir=C:\WINDO

Should I give it a try. I would like your opinion. Where would I find a
SFC program?
Many Thanks

--
JJ MacA


"Mike M" wrote:

Let's concentrate on the Code 2 error:

KB125174 "Explanation of the error codes that are generated by Device
Manager for Windows 2000, Windows Millennium, Windows 98, and Windows 95"
(http://support.microsoft.com?kbid=125174) lists two possible causes for
a
Code 2 error, the second of which appears to be the case here.
"Code 2
Depending on which device is failing, you may see either of two different
messages.
snip
When the device is not a root bus DevLoader, the following message is
displayed

The type device loader(s) for this device could not load the device
driver. (Code 2)

To fix this, click Update Driver to update the device driver.

where type is the DevLoader such as FLOP, ESDI, SCSI, and so on.

Solution button: Update Driver

In addition to following the recommended solution, try removing the
device
from Device Manager, and then running the Add New Hardware wizard."

So there you have it, update the driver but first try booting to Safe
Mode, deleting the two devices in Device Manager that are giving you Code
2 errors and then reboot back to Normal Mode. Win Me will redetect the
devices and, if the drivers are Win Me compatible, reload them and enable
the devices. Alternatively follow the method in the KB article, remove
device(s) and then use the Add New hardware wizard.
--
Mike Maltby



jj mac jj wrote:

Mike I did follow the very detailed instructions you gave me in your
previous post. Because on this Computer the CD drive & the floppy
disk drive share a single module bay and furthermore when booted to a
Dos prompt or in Safe mode the Computer will not log the CD drive at
all, even when it is installed in the module bay. That presented me
with some difficulty when I tried to follow the procedure set out in
MS KB 265371. The difficulty was probably surmountable but I did not
pursue it further as the alternative MSConfig method that you
described of extracting the files from "a subfolder of
Windows\Options" (actually from Windows\Options\Install\Base2) was
straight forward and was successfully completed.

I have now extracted the 3 system files from the WinME installation
disk to a subfolder which I created in the Windows\System32\Drivers
folder. Rebooted the Computer to a Dos Prompt and copied the files
from the subfolder into the Drivers folder overwriting the existing
files.
Sorry to record that the devices are still shown disabled in Device
Manager. The NDIS.VXD.NTKERN.VXD error message is still displayed.

Thanks again for your help.