![]() | |
|
Welcome to the ABXZone Computer Forums forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 |
| Registered User Join Date: Feb 2001
Posts: 5
| Hello, The Direct Memory Access Controller is flagged (yellow exclamation) under System Devices in Device Manager in Windows ME. Properties show: "Device Status: The VDMAD.VXD 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." Of course I've done this, and it says its already using the best driver. Its currently using the Microsoft Driver (6/8/2000), and I've also tried the Intel driver. Bootlog.txt shows successful loads, ininits, etc. for all instances of DMA / VDMAD.VXD. Everything is working fine, but I'd prefer not to have any devices flagged. Any ideas? Thanks in advance. Dave Windows ME Asus CUSL2-C motherboard PIII 866 256MB PC133 SDRAM IBM 45GB ATA100 Adaptec AHA-2940UW Seagate ST32550W HP 9200 CD RW ATI Rage Pro Turbo AGP 8MB Mitsumi 48x IDE CD SoundBlaster Audio PCI CNet Pro200 10/100 NIC |
| (Offline) | |
| Advertisement | [Remove Advertisement] |
| |
| | #2 |
| I need a job. Join Date: Feb 2001 Location: Virginia Beach, VA
Posts: 677
| Is there another DMA Controller listed that does not have the exclamation point? If so, delete than one and restart your computer. |
| (Offline) | |
| | #3 |
| Registered User Join Date: Feb 2001
Posts: 5
| No, there are no other instances of the DMA controller. I've removed the existing one & rebooted - its redetected and still has the same status. I've also renamed the drivers that seem to be involved (vdmad.vxd & vmm32.vxd) then extracted new copies from the .cab files. Also - just to make sure the hardware is ok - I did a clean install of ME on a different hard drv. No problem then! I hate to have to do that on my main drv though - TOO much stuff on it! |
| (Offline) | |
| | #4 |
| I need a job. Join Date: Feb 2001 Location: Virginia Beach, VA
Posts: 677
| Ok, do this: Boot into safe mode. Click on "start" and the "RUN" and type regedit. Select HKEY_LOCAL_MACHINE and delete the "ENUM" folder. Then reboot, it should then try to redetect all your hardware. |
| (Offline) | |
| | #5 |
| Registered User Join Date: Feb 2001
Posts: 5
| Problem Solved! Thanks darkwish - I think your suggestion would have worked, but I used a slightly less radical approach: Emailed Microsoft Support - They actually replied: said to boot in safe mode, and to remove all duplicated items, and all devices that don't actually exist from device manager. On reboot, it detected a few items, one more reboot and everything is fine! Apparently this is a way to get rid of registry entries for hardware that's no longer installed. Seems to boot faster too. Dave |
| (Offline) | |
![]() |
| Thread Tools | |
| Display Modes | |
| |