>The error message is stating that the NT kernal virtual device drivers are unable to load the ACPI drivers. Did this message appear after you installed the drivers from the link I had posted? Makes ure that there are absolutely no other conflicts or errors listed in your device manager first. Also check and make sure that there are no IRQ conflicts. Past that, make sure you try removing the IBM PM device and then reboot. That way Windows can go ahead and reinstall the device before trying to load it. The one thing I am curious about is if IBM PM device refers to APM or ACPI or both depending on what you have enabled in the BIOS. Does your BIOS have APM and/or ACPI settings? Wish I could just slam you out an answer eright away Michel but these problems are never fun. :)
Yes, it went well. However, when I looked under the Device Manager under System Devices, it showed a conflict.
Yes, we have a conflict. This is why we are updating some components. I was at the IBM store today and I talked with the technician. He said in order to fix our conflicts, that I need to install the Fast-swap Driver for Windows Me. This might be the reason why we have a conflict on the Hard Disk Controllers list. It shows a conflict for Intel 82371AB/EB PCI Bus Master IDE Controller followed by two identical entries for Standard Bus Mastering IDE Hard Disk Controller. He mentioned that I should only see one entry in the Hard Disk Controller. He mentioned that installing the Fast-swap Driver for Windows Me might solves it.
However, I can't install the Fast-swap Driver for Windows Me as it says that it can't be installed on this machine.
The reason we want to update is because the flash card are difficult to be read as is. Whenever we insert the flash card, it may took up to 20 retries until it is read as a new drive. He says that it might be well the situation as we have a conflict with the Hard Disk Controller. This is why we want to solve it.
I updated the Bios today. We are running the latest version. I also updated the 3COM modem driver for the latest one in order to fix a small occasional bug when shutting down a modem connection from a dialup. That part went well. It's just the last part now that I can't solve.
