A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows ME » Software & Applications
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Problem installing network cards on laptop



 
 
Thread Tools Display Modes
  #11  
Old July 19th 08, 01:22 AM posted to microsoft.public.windowsme.software
Mart
External Usenet User
 
Posts: 1,190
Default Problem installing network cards on laptop

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.





  #12  
Old July 22nd 08, 11:35 PM posted to microsoft.public.windowsme.software
jj mac
External Usenet User
 
Posts: 28
Default Problem installing network cards on laptop

Mart


I have followed the installation procedure as set out in Chapter 2.1 of the
Planet Manual on a number of occasions. The only mistake I think I may have
made was to remove, in Device Manager, the Planet wl-3552 network adapter
(showing an exclamation mark in a yellow blob), without the computer being in
Safe Mode.
I have,however, now gone through the procedure once again. I removed the
Planet wireless card from the PCMCIA socket, booted the computer in Safe
Mode, then in Device Manager I clicked on network adapters & removed the
software for the Planet-WL-3552 PCMCIA Card. I then clicked on PCMCIA socket
and removed the three items listed therein, PCMCIA socket, Ricoh RL/RB5C478
CardBus Controller and a second Ricoh RL/RB5C478 CardBus Controller.
When I restarted the Computer in Normal mode Windows immediately detected
the two Ricoh CardBus Controllers and automatically installed the Ricoh
software from Windows ME. When that completed I was able to run the set-up
wizard from the Planet installation CD, as described in Chapter 2.1 of the
Planet Manual.
Next I inserted the Planet wireless card, in one of the two PCMCIA sockets
in this Computer, and started the Computer in normal mode. Windows searched
for and automatically installed software for the following new hardware it
found
ATMEL AT76C502AR_E
PLANET WL.3552 Wireless PCMCIA Card.

When the installation completed I rebooted the Computer and noted the yellow
blob with exclamation mark in Device Manager shown against the Planet WL-3552
Wireless PCMCIA card. The Code2 issue remains.
(Incidentaly I had previously removed the USB to fast Ethernet adapter,
being the other device showing a Code2 error message, although I probably
removed the software in normal mode?)

The following are the driver file details installed for the Planet Card

Driver Provider Planet
Date 5/20/2002 Not Signed
File Details
C:\Windows\System\NDIS.VXD
| _ - C:\Windows\System\wmm32.vxd (intkern.vxd)
| - fvnete.sys
:- icpic.sys
:- C:\WINDOWS\SYSTEM\VTDI.386
:- C:\WINDOWS\SYSTEM\VIP.386
:- C:\WINDOWS\SYSTEM\VTCP.386
:- C:\WINDOWS\SYSTEM\VDHCP.386
- C:\WINDOWS\SYSTEM\VNBT.386
:. . C:\WINDOWS\SYSTEM\VREDIR.VXD

If I click on resourses I get message “ This device isn’t using any
resources because it is not currently enabled or has a problem.”
The solution still eludes me.

Mart I have attempted to describe in detail the steps I took during the
installation of the software and drivers for this wireless adapter. Please
let me know if you see anything that I have failed to carry out correctly
Thank You

--
JJ MacA


"Mart" wrote:

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.





  #13  
Old July 22nd 08, 11:38 PM posted to microsoft.public.windowsme.software
jj mac
External Usenet User
 
Posts: 28
Default Problem installing network cards on laptop

Mike

Many thanks for your further advice. I agree that I may not have installed
the drivers correctly. I have however started from scratch and reinstalled
the Planet WL-3552 Wireless PCMCIA Card in the manner described in the Planet
Manual. Please have a look at my reply to Mart’s post Unfortunately the
Code2 error remains. Please let me know if I still have not got the
installation of the drivers right.
After installing the software from the Planet CD and noting that the Code2
error remained I clicked on “update driver” and selected the option to
specify the location of the new Win ME driver which I had obtained from the
vendor of the card. I assumed it was an updated driver. The driver file
details are however identical to those found in the Planet CD as included in
my reply to Mart.
I note your comments on the suggested placement of a fresh copy of
NTKERN.VXD in the Windows\System\ vmm32 folder and have not proceeded with
that suggestion.
I suppose it is possible that the Planet Card is faulty. I do have another
new laptop (running on Windows Vista home premium) with a wifi adapter “built
in” which I could possibly use to check out the card but I would be reluctant
to do so in case I messed up the settings of that Laptop

--
JJ MacA


"Mike M" wrote:

Where would I find a SFC program?


It forms part of Windows 98 and Windows 98SE. Use of SFC is irrelevant,
you already know how to extract a file from the Win Me cab files. This
aspect of SFC is now part of Win Me's MSConfig (Extract on the General
tab).

Placing a new copy of one of the files incorporated into vmm32.vxd in the
folder windows\system\vmm32 (rather than windows\system32\drivers) causes
that file to be used rather than the one in vmm32.vxd. This is the
mechanism used to update such files. If your system were to have been
updated you would find an updated copy of ifsmgr.vxd in the vmm32 folder
which is an updated version of the file that was built into vmm32.vxd when
the system was first installed. Details of this particular hotfix can be
found at KB273017 (http://support.microsoft.com/?kbid=273017) although I
only mention this because it illustrates a file built-in to vmm32.vxd
being updated not because it has any bearing on your problem..

Should I give it a try.


Your choice entirely but nothing you have posted suggests a problem with
the files you mention but on the other hand it won't do any harm. Read
the error message again and the KB article to which I referred. It
doesn't say the device loader is missing or broken, it says instead that
the device loader is unable to load the driver files which is somewhat
different. This suggests that the driver file is the one that is damaged.
I still feel you should reinstall the drivers which I'm not sure that you
have done.
--
Mike Maltby



jj mac jj
wrote:

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?



  #14  
Old July 23rd 08, 09:26 AM posted to microsoft.public.windowsme.software
Mart
External Usenet User
 
Posts: 1,190
Default Problem installing network cards on laptop

Hi JJ, briefly ('cause I've got to dash out - I'll try to follow-up later)
amongst other things, I Googled for RL/RB5C478 and found the following :-

http://help.lockergnome.com/windows2...ict373359.html

The response (from a previous, well known MVP to the WinMe Groups) suggested
a couple of MS KB articles, which sadly seem to be no longer available.

Anyway, I'd previously had issues on a Sony laptop which wouldn't recognise
a USB WiFi stick connected thru' a PCMCIA USB 2.0 card ** (although it
would - eventually - recognise the stick thru' the native USB 1.1 socket on
the laptop) and I'd seen reference to these KB articles at that time (and
they were not available then either!). Ended up just having to live with it.

** a set-up which worked perfectly well on a Toshiba laptop.

That doesn't resolve your dilemma but in *might* be an indicator to the
direction we may be heading - the cardbus driver.

I'll try to respond further if I can find anything more.

Mart



"jj mac" jj wrote in message
...
Mart


I have followed the installation procedure as set out in Chapter 2.1 of
the
Planet Manual on a number of occasions. The only mistake I think I may
have
made was to remove, in Device Manager, the Planet wl-3552 network adapter
(showing an exclamation mark in a yellow blob), without the computer being
in
Safe Mode.
I have,however, now gone through the procedure once again. I removed the
Planet wireless card from the PCMCIA socket, booted the computer in Safe
Mode, then in Device Manager I clicked on network adapters & removed the
software for the Planet-WL-3552 PCMCIA Card. I then clicked on PCMCIA
socket
and removed the three items listed therein, PCMCIA socket, Ricoh
RL/RB5C478
CardBus Controller and a second Ricoh RL/RB5C478 CardBus Controller.
When I restarted the Computer in Normal mode Windows immediately detected
the two Ricoh CardBus Controllers and automatically installed the Ricoh
software from Windows ME. When that completed I was able to run the set-up
wizard from the Planet installation CD, as described in Chapter 2.1 of the
Planet Manual.
Next I inserted the Planet wireless card, in one of the two PCMCIA sockets
in this Computer, and started the Computer in normal mode. Windows
searched
for and automatically installed software for the following new hardware it
found
ATMEL AT76C502AR_E
PLANET WL.3552 Wireless PCMCIA Card.

When the installation completed I rebooted the Computer and noted the
yellow
blob with exclamation mark in Device Manager shown against the Planet
WL-3552
Wireless PCMCIA card. The Code2 issue remains.
(Incidentaly I had previously removed the USB to fast Ethernet adapter,
being the other device showing a Code2 error message, although I probably
removed the software in normal mode?)

The following are the driver file details installed for the Planet Card

Driver Provider Planet
Date 5/20/2002 Not Signed
File Details
C:\Windows\System\NDIS.VXD
| _ - C:\Windows\System\wmm32.vxd (intkern.vxd)
| - fvnete.sys
:- icpic.sys
:- C:\WINDOWS\SYSTEM\VTDI.386
:- C:\WINDOWS\SYSTEM\VIP.386
:- C:\WINDOWS\SYSTEM\VTCP.386
:- C:\WINDOWS\SYSTEM\VDHCP.386
- C:\WINDOWS\SYSTEM\VNBT.386
:. . C:\WINDOWS\SYSTEM\VREDIR.VXD

If I click on resourses I get message " This device isn't using any
resources because it is not currently enabled or has a problem."
The solution still eludes me.

Mart I have attempted to describe in detail the steps I took during the
installation of the software and drivers for this wireless adapter.
Please
let me know if you see anything that I have failed to carry out correctly
Thank You

--
JJ MacA


"Mart" wrote:

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.







  #15  
Old July 23rd 08, 04:27 PM posted to microsoft.public.windowsme.software
Mike M
External Usenet User
 
Posts: 2,047
Default Problem installing network cards on laptop

Mart,

I'm not sure as to its relevance given the different error and that JJ is
trying to install a single function PCMCIA adapter but if you were
referring to the now withdrawn KB article 268452 it read as follows:
KB 268452 Multiple-Function CardBus Adapters Are Assigned Overlapped
Resources
Article Last Modified on 9/28/2004
SYMPTOMS
CardBus adapters with multiple functions (such as Ethernet and modem, or
USB and 1394) may not work correctly, or the computer may hang during the
installation. This problem can also occur with PCI add-in adapters that
use CardBus-type PCI bridges.
-or-
Input/Output range overlap:
OsiTech CardBus Ethernet 10/100 + 56K DPI Modem (Jack of Spades)
IBM Microdrive with PC Card Adapter (or CompactFlash Adapter)
CAUSE
Configuration Manager (Configmg.vxd) can erroneously assign overlapping
resources to devices with similar requirements.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article.

[This hotfix is NOT available from Microsoft, support for Win Me having
ended some years ago.]

The English version of this fix should have the following file attributes
or later:
Date Time Version Size File name
-------------------------------------------------------------------------------
08/30/2000 05:17p 4.90.3001 120,845 Configmg.vxd
snip
--
Mike Maltby



Mart wrote:

Hi JJ, briefly ('cause I've got to dash out - I'll try to follow-up
later) amongst other things, I Googled for RL/RB5C478 and found the
following :-
http://help.lockergnome.com/windows2...ict373359.html

The response (from a previous, well known MVP to the WinMe Groups)
suggested a couple of MS KB articles, which sadly seem to be no
longer available.
Anyway, I'd previously had issues on a Sony laptop which wouldn't
recognise a USB WiFi stick connected thru' a PCMCIA USB 2.0 card **
(although it would - eventually - recognise the stick thru' the
native USB 1.1 socket on the laptop) and I'd seen reference to these
KB articles at that time (and they were not available then either!).
Ended up just having to live with it.
** a set-up which worked perfectly well on a Toshiba laptop.

That doesn't resolve your dilemma but in *might* be an indicator to
the direction we may be heading - the cardbus driver.

I'll try to respond further if I can find anything more.


  #16  
Old July 23rd 08, 09:55 PM posted to microsoft.public.windowsme.software
Mart
External Usenet User
 
Posts: 1,190
Default Problem installing network cards on laptop

Interesting Mike, thanks for the follow-up on the KB articles. Nice to know
as to what they actually referred g My impression (although I was rushing
this morning and never had time to pursue) was that they may have been
related to the Cardbus drivers rather than the adapters themselves. I do
recall a USB aspect when I was playing about with my WiFi stick a while
back, but abandoned things once I got it running on the USB 1.x port. I
might re-visit sometime, if I can get hold of a copy of the 4.90.3001
version of Configmg.vxd.

So, back to JJ's problems - well he certainly appears to have the correct
drivers for his Planet WL-3552 Wireless PCMCIA Card (and, according to the
Manual, it is WinMe compatible)

BUT - why similar problems with other Cardbus (PCMCIA) devices? Especially
with same error report??

Sony/Ricoch RL/RB5C478 CardBus Controller drivers perhaps?
http://www.driverfiles.net/Notebooks...6,173,19,.html

Or maybe something corrupted/damaged in WinMe? - Hate to have to suggest it
but when faced with time consuming cul-de-sacs, perhaps a clean install of
WinMe may be the lesser of the two evils. (Not forgetting to backup the hard
disk of course!)

Don't know what else to recommend.

Mart



"Mike M" wrote in message
...
Mart,

I'm not sure as to its relevance given the different error and that JJ is
trying to install a single function PCMCIA adapter but if you were
referring to the now withdrawn KB article 268452 it read as follows:
KB 268452 Multiple-Function CardBus Adapters Are Assigned Overlapped
Resources
Article Last Modified on 9/28/2004
SYMPTOMS
CardBus adapters with multiple functions (such as Ethernet and modem, or
USB and 1394) may not work correctly, or the computer may hang during the
installation. This problem can also occur with PCI add-in adapters that
use CardBus-type PCI bridges.
-or-
Input/Output range overlap:
OsiTech CardBus Ethernet 10/100 + 56K DPI Modem (Jack of Spades)
IBM Microdrive with PC Card Adapter (or CompactFlash Adapter)
CAUSE
Configuration Manager (Configmg.vxd) can erroneously assign overlapping
resources to devices with similar requirements.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article.

[This hotfix is NOT available from Microsoft, support for Win Me having
ended some years ago.]

The English version of this fix should have the following file attributes
or later:
Date Time Version Size File name
-------------------------------------------------------------------------------
08/30/2000 05:17p 4.90.3001 120,845 Configmg.vxd
snip
--
Mike Maltby



Mart wrote:

Hi JJ, briefly ('cause I've got to dash out - I'll try to follow-up
later) amongst other things, I Googled for RL/RB5C478 and found the
following :-
http://help.lockergnome.com/windows2...ict373359.html

The response (from a previous, well known MVP to the WinMe Groups)
suggested a couple of MS KB articles, which sadly seem to be no
longer available.
Anyway, I'd previously had issues on a Sony laptop which wouldn't
recognise a USB WiFi stick connected thru' a PCMCIA USB 2.0 card **
(although it would - eventually - recognise the stick thru' the
native USB 1.1 socket on the laptop) and I'd seen reference to these
KB articles at that time (and they were not available then either!).
Ended up just having to live with it.
** a set-up which worked perfectly well on a Toshiba laptop.

That doesn't resolve your dilemma but in *might* be an indicator to
the direction we may be heading - the cardbus driver.

I'll try to respond further if I can find anything more.




  #17  
Old July 23rd 08, 11:46 PM posted to microsoft.public.windowsme.software
Mike M
External Usenet User
 
Posts: 2,047
Default Problem installing network cards on laptop

Mart,

I agree, this is one of those cases where a clean reinstall of Win Me may
well be called for given that all else seems to be in order unless JJ can
find a more recent version of the Cardbus controller drivers.

I was able to pull up that KB because I still have an October 2005 copy of
the KB articles on Technet at that time installed on this box. If need be
I also have some Technet disks including the KBs going back to the late
90s but PLEASE don't ask me to dig them out. vbg

if I can get hold of a copy of the 4.90.3001 version of Configmg.vxd.


I think the final version was 4.90.3002 released as part of KB281921
"Computer Suspends After Resuming with Keyboard Power Key" (also
withdrawn).
Date Time Version Size File name
----------------------------------------------------------------------------------
12/20/2000 05:14pm 4.90.3002 120,845 Configmg.vxd
12/22/2000 03:06pm 4.90.3004 50,223 Vpowerd.vxd

I would hope, but cannot confirm, that this might contain the fix in 3001.
I think you might be able to obtain configmg.vxd 3002 as part of the
unofficial Win Me service
pack.http://www.msfn.org/board/Service-Pa...ME-t61407.html
--
Mike



Mart wrote:

Interesting Mike, thanks for the follow-up on the KB articles. Nice
to know as to what they actually referred g My impression
(although I was rushing this morning and never had time to pursue)
was that they may have been related to the Cardbus drivers rather
than the adapters themselves. I do recall a USB aspect when I was
playing about with my WiFi stick a while back, but abandoned things
once I got it running on the USB 1.x port. I might re-visit sometime,
if I can get hold of a copy of the 4.90.3001 version of Configmg.vxd.

So, back to JJ's problems - well he certainly appears to have the
correct drivers for his Planet WL-3552 Wireless PCMCIA Card (and,
according to the Manual, it is WinMe compatible)

BUT - why similar problems with other Cardbus (PCMCIA) devices?
Especially with same error report??

Sony/Ricoch RL/RB5C478 CardBus Controller drivers perhaps?
http://www.driverfiles.net/Notebooks...6,173,19,.html

Or maybe something corrupted/damaged in WinMe? - Hate to have to
suggest it but when faced with time consuming cul-de-sacs, perhaps a
clean install of WinMe may be the lesser of the two evils. (Not
forgetting to backup the hard disk of course!)

Don't know what else to recommend.


  #18  
Old July 24th 08, 12:17 AM posted to microsoft.public.windowsme.software
Mart
External Usenet User
 
Posts: 1,190
Default Problem installing network cards on laptop

Thanks Mike, but I'm not too fussed about the WiFi stick. Under the
circumstances (it works on USB 1.x and I don't use it too often these days
g) I might leave well alone.

But this is JJ's thread - not mine

Mart

snipped


  #19  
Old July 25th 08, 12:08 AM posted to microsoft.public.windowsme.software
jj mac
External Usenet User
 
Posts: 28
Default Problem installing network cards on laptop

Mike
I have had another look over this problem and have decided that I might as
well check out the suggested fix of extracting fresh copies of NDIS.VXD &
NTKERN.VXD and saving them in C:\Windows\System|vmm32 - if only to eliminate
it as a possible solution.
Whereas I was able to find the files usbhub.sys, uhcd.sys & usbd.sys in the
Operating System CD nowhere therein can I find the aforementioned .VXD
files. They must be somewhere on the CD if they are part of Windows ME..

Where might I find these files.? Can you
help please.? The three .sys files were in folder \Win9x\Base2 in the CD.
I retrieved an old Windows 98SE computer from the attic and was able to
extract a copy of NTKERN.VXD to floppy disk . I have been tempted to try
installing it in the laptop but thought better not to try.
I know that there is a copy of NDIS.VXD in C:\Windows\System. In the
event that I am unable to extract a fresh copy of NTKERN.VXD is there a way
that I could check that there is at least an existing copy of that file in
vmm32? I have a sneeking suspicion that it might be missing.

Thank you

--
JJ MacA


"Mike M" wrote:

Where would I find a SFC program?


It forms part of Windows 98 and Windows 98SE. Use of SFC is irrelevant,
you already know how to extract a file from the Win Me cab files. This
aspect of SFC is now part of Win Me's MSConfig (Extract on the General
tab).

Placing a new copy of one of the files incorporated into vmm32.vxd in the
folder windows\system\vmm32 (rather than windows\system32\drivers) causes
that file to be used rather than the one in vmm32.vxd. This is the
mechanism used to update such files. If your system were to have been
updated you would find an updated copy of ifsmgr.vxd in the vmm32 folder
which is an updated version of the file that was built into vmm32.vxd when
the system was first installed. Details of this particular hotfix can be
found at KB273017 (http://support.microsoft.com/?kbid=273017) although I
only mention this because it illustrates a file built-in to vmm32.vxd
being updated not because it has any bearing on your problem..

Should I give it a try.


Your choice entirely but nothing you have posted suggests a problem with
the files you mention but on the other hand it won't do any harm. Read
the error message again and the KB article to which I referred. It
doesn't say the device loader is missing or broken, it says instead that
the device loader is unable to load the driver files which is somewhat
different. This suggests that the driver file is the one that is damaged.
I still feel you should reinstall the drivers which I'm not sure that you
have done.
--
Mike Maltby



jj mac jj
wrote:

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?



  #20  
Old July 25th 08, 08:55 AM posted to microsoft.public.windowsme.software
Mart
External Usenet User
 
Posts: 1,190
Default Problem installing network cards on laptop

JJ, as you appear to have an OEM version of WinMe then you might have to do
a little searching.

Clean/fresh copies of NDIS.VXD and NTKERN.VXD are both contained in the
WIN_20.CAB, perhaps located in the \Win9x\ folder.

This CAB file is *normally* located in either the C:Windows\Options\Install
or C:Windows\Options\CABS folders (depending on whether MS or OEM versions.)

However, *some* OEM's may locate the full set of Installation CAB files
elsewhere (\Win9x\?) - or *may not* install them to your HDD at all. And, I
suspect that your OEM version may be the latter.

NB. the full set of WinMe Installation files - if included by your OEM -
should be contained in a folder (mentioned above) containing some 10 or so
other .CAB files, the setup.exe file and be in the order of 150MB.

Personally, I wouldn't attempt to mix 98SE files with WinMe files - but as a
last resort? - your choice! Clean install time?

Good luck

Mart



"jj mac" jj wrote in message
...
Mike
I have had another look over this problem and have decided that I might as
well check out the suggested fix of extracting fresh copies of NDIS.VXD &
NTKERN.VXD and saving them in C:\Windows\System|vmm32 - if only to
eliminate
it as a possible solution.
Whereas I was able to find the files usbhub.sys, uhcd.sys & usbd.sys in
the
Operating System CD nowhere therein can I find the aforementioned .VXD
files. They must be somewhere on the CD if they are part of Windows ME..

Where might I find these files.? Can you
help please.? The three .sys files were in folder \Win9x\Base2 in the CD.
I retrieved an old Windows 98SE computer from the attic and was able to
extract a copy of NTKERN.VXD to floppy disk . I have been tempted to try
installing it in the laptop but thought better not to try.
I know that there is a copy of NDIS.VXD in C:\Windows\System. In the
event that I am unable to extract a fresh copy of NTKERN.VXD is there a
way
that I could check that there is at least an existing copy of that file
in
vmm32? I have a sneeking suspicion that it might be missing.

Thank you

--
JJ MacA


"Mike M" wrote:

Where would I find a SFC program?


It forms part of Windows 98 and Windows 98SE. Use of SFC is irrelevant,
you already know how to extract a file from the Win Me cab files. This
aspect of SFC is now part of Win Me's MSConfig (Extract on the General
tab).

Placing a new copy of one of the files incorporated into vmm32.vxd in the
folder windows\system\vmm32 (rather than windows\system32\drivers) causes
that file to be used rather than the one in vmm32.vxd. This is the
mechanism used to update such files. If your system were to have been
updated you would find an updated copy of ifsmgr.vxd in the vmm32 folder
which is an updated version of the file that was built into vmm32.vxd
when
the system was first installed. Details of this particular hotfix can be
found at KB273017 (
http://support.microsoft.com/?kbid=273017) although I
only mention this because it illustrates a file built-in to vmm32.vxd
being updated not because it has any bearing on your problem..

Should I give it a try.


Your choice entirely but nothing you have posted suggests a problem with
the files you mention but on the other hand it won't do any harm. Read
the error message again and the KB article to which I referred. It
doesn't say the device loader is missing or broken, it says instead that
the device loader is unable to load the driver files which is somewhat
different. This suggests that the driver file is the one that is
damaged.
I still feel you should reinstall the drivers which I'm not sure that you
have done.
--
Mike Maltby



jj mac jj
wrote:

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?





 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem installing Network Card Hamish Morrison Hardware 3 December 28th 06 02:41 PM
W98 Network Cards Ron Badour General 10 November 9th 06 01:16 AM
Can I create a network without a hub/switch or router? I mean, 3 PC and 3 net cards. Starriol Networking 10 February 10th 06 10:16 AM
Can I create a network without a hub/switch or router? I mean, 3 PC and 3 net cards. Starriol Networking 2 February 8th 06 08:54 PM
Lost the ability to Network and also add new networking cards Chef John Networking 0 March 1st 05 04:09 PM


All times are GMT +1. The time now is 11:24 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright 2004-2024 Win98banter.
The comments are property of their posters.