Thanks Missie
Reply 1 : mtd-0002
The fix depends on the operating system you are using, (you didn't give us that information), but see the links below:
Google Search For "mtd-0002"
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;319326
Hope this helps.
Grif
Google Search For "mtd-0002"
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;319326
Hope this helps.
Grif
Reply 2 : mtd-0002
I am very sorry, I am using win. xp, on a toshiba a45-s120, I guess this would make a difference. when I insert any card in pcmcia slot I get this message (mtd-0002). can anyone help. Thanks Missie
Reply 3 : mtd-0002
If you can access your notebooks BIOS, check the devices you have set in the "Boot" sequence. Most notebooks allow about 5 typical devices:
1. Floppy drive (old school, but works like a charm)
2. cdrom/dvdrom/cdrw (Optical drive)
3. Hard Drive
4. Built-on Ethernet (comes inside the notebook when it was built)
5. Add-on Ethernet (installed after-market by you or a guru.)
The add-on Ethernet could also be called a "Cardbus NIC" or "Cardbus Ethernet" "ADD-On Controller" or something along that line. It basically says the same thing: its a Network Interface Controller that was placed in the PCMCIA slot by you or a PC tech for some reason, USUALLY wireless access.
While the problem may be CAUSED by a flaw in PCMCIA.SYS, it can be circumvented by going into the BIOS and looking at the PC boot Sequence. If the Hard Disk is listed AFTER the Cardbus NIC, then the problem will likely happen. To resolve this, place the Cardbus NIC at the BOTTOM of the boot-time sequence: Floppy, CD, Hard Disk, Onboard NIC, Cardbus NIC. (In fact, MOST REGULAR PEOPLE never need the ability to boot with the NIC, so you COULD get away with disabling them both in the boot-time, and start Floppy, cd, hard drive.) That SHOULD HELP alleviate the issue.
Whats happening is, the device is activated at boot time, and the device fails to reach a bootable signal, so the hard drive is requested to boot, but while the hdd is booting windows, the device may still be trying to boot or locate a signal, and the driver is ignored or not loaded properly because the device is not ready, then the device times out, windows completes its load, SEES the device, but since it was not ready, it was assigned incorrect memory addressing, (Wrong memory range) so Windows misunderstands what it is, and the hilarity ensues. Sometimes popping the card out, and reinserting it will fix it, but taking it out of the boot sequence, or placing it at the bottom of the sequence should help avoid the issue altogether. I hope this helps.
1. Floppy drive (old school, but works like a charm)
2. cdrom/dvdrom/cdrw (Optical drive)
3. Hard Drive
4. Built-on Ethernet (comes inside the notebook when it was built)
5. Add-on Ethernet (installed after-market by you or a guru.)
The add-on Ethernet could also be called a "Cardbus NIC" or "Cardbus Ethernet" "ADD-On Controller" or something along that line. It basically says the same thing: its a Network Interface Controller that was placed in the PCMCIA slot by you or a PC tech for some reason, USUALLY wireless access.
While the problem may be CAUSED by a flaw in PCMCIA.SYS, it can be circumvented by going into the BIOS and looking at the PC boot Sequence. If the Hard Disk is listed AFTER the Cardbus NIC, then the problem will likely happen. To resolve this, place the Cardbus NIC at the BOTTOM of the boot-time sequence: Floppy, CD, Hard Disk, Onboard NIC, Cardbus NIC. (In fact, MOST REGULAR PEOPLE never need the ability to boot with the NIC, so you COULD get away with disabling them both in the boot-time, and start Floppy, cd, hard drive.) That SHOULD HELP alleviate the issue.
Whats happening is, the device is activated at boot time, and the device fails to reach a bootable signal, so the hard drive is requested to boot, but while the hdd is booting windows, the device may still be trying to boot or locate a signal, and the driver is ignored or not loaded properly because the device is not ready, then the device times out, windows completes its load, SEES the device, but since it was not ready, it was assigned incorrect memory addressing, (Wrong memory range) so Windows misunderstands what it is, and the hilarity ensues. Sometimes popping the card out, and reinserting it will fix it, but taking it out of the boot sequence, or placing it at the bottom of the sequence should help avoid the issue altogether. I hope this helps.
Reply 4 : mtd-0002
First I established that it wasnt the card by placing it in another system;
Then I ran the XP SP3 Update;
When that failed I replaced the System32Driverspcmcia.sys with one from a different copy (same attributes, etc);
I checked the Phoenix BIOS (Current - A16) for a way to 'disable the Soundblaster' - no setting;
I disabled every boot device in the boot sequence and moved the HDD (only active device) to the top, then floppy, CD, Onboard NIC;
I moved the floppy back to #1, enabled it too;
I enabled each additional device one at a time, rebooting each instance with the NIC always last;
I even uninstalled and reinstalled the PCMCIA card driver in Device Manager(which wasnt one of the published troubleshooting steps) in hopes that perhaps I had registry problems instead.
There are no further permanent troubleshooting solutions to this problem. I started having it after my system clock reset (I assume my BIOS reset to factory default was the problem.) After that, I did a Virgin reinstall of XP and SP3.
No matter what combination of boot sequences I use (Ive tried at least SEVEN) no combination of sequence/enabling would fix it. The KB article doesnt provide anything further on this. I understand that there is some kind of 'hot fix' but searches at the microsoft site have not resulted in a download link.
Any assistance beyond web searches would be much appreciated as I havent been able to run some important peripherals for the past week.
Then I ran the XP SP3 Update;
When that failed I replaced the System32Driverspcmcia.sys with one from a different copy (same attributes, etc);
I checked the Phoenix BIOS (Current - A16) for a way to 'disable the Soundblaster' - no setting;
I disabled every boot device in the boot sequence and moved the HDD (only active device) to the top, then floppy, CD, Onboard NIC;
I moved the floppy back to #1, enabled it too;
I enabled each additional device one at a time, rebooting each instance with the NIC always last;
I even uninstalled and reinstalled the PCMCIA card driver in Device Manager(which wasnt one of the published troubleshooting steps) in hopes that perhaps I had registry problems instead.
There are no further permanent troubleshooting solutions to this problem. I started having it after my system clock reset (I assume my BIOS reset to factory default was the problem.) After that, I did a Virgin reinstall of XP and SP3.
No matter what combination of boot sequences I use (Ive tried at least SEVEN) no combination of sequence/enabling would fix it. The KB article doesnt provide anything further on this. I understand that there is some kind of 'hot fix' but searches at the microsoft site have not resulted in a download link.
Any assistance beyond web searches would be much appreciated as I havent been able to run some important peripherals for the past week.
Reply 5 : mtd-0002
If this is that important, why not call dell.com and pay up for their support?
I have a few ideas about fixing this but it involves a fresh install after testing that the hardware is good from a bootable CD such as Ubuntu.
Bob
I have a few ideas about fixing this but it involves a fresh install after testing that the hardware is good from a bootable CD such as Ubuntu.
Bob
No comments:
Post a Comment