How to resolve "Driver Communication 3" or "No drive left"

[Charles [PM]]

For TotalMounter and TotalMounter Pro, appear this error indicate virtual storport / scsiport driver is not installed or not installed successfully, most possibility reason is unclean uninstall, such as, having previous version of the product installed, not reboot computer after uninstall etc.
For this reason please confirm the following ways to resolve:
1. Uninstall currently version, as the installation is failed, you need re-install it.
2. If you have previous version of TotalMounter, INetDisk client installed, you need uninstall them and you must reboot your computer.
3. Confirm there is no old controller: In windows device manager, expand the tree to "Storage Controller" , if you found node like "KernSafe SCSI Controller", delete it and reboot, this is an optional step just in case of successfully uninstall.
4. After reboot, please do new TotalMouner or TotalMounter Pro install again.

Another reason is not select driver installation, when install the software, there are two windows will popup to ask you install drivers, you need agree to install them.

[tyrotex]

Charles, Thank you for responding to this problem.
As I stated in my post on this (viewtopic.php?f=6&t=11309):

I have installed TotalMounter v2.0 on a 32-bit Windows 7 Professional VM running under SmartOS KVM.
When I attempt to mount any new device (burner, safe file, VHD), I receive the popup saying "No Device Left". "The status line says SCSI Controller 0 - Driver communication error: 3".
If I select "Virtual CD/DVD_ROM", I receive the "Driver communication error: 3" message on the status line with no popup.
I can see that the KernSafe SCSI Controller is installed in Device Manager, which reports that the driver is working...

Since my post, I have successfully installed and used TotalMounter v1.50 on this system, so the problem appears to be with the v2.0 installation.
At the time of my original installation,
- I had no previous version of TotalMounter installed,
- During the installation, I agreed to install both drivers (SCSI controller & Virtual System Bus)
- KernSafe SCSI controller was installed (and reported to be working).
So, I believe that I had followed the installation procedure correctly.

However, I have now re-installed v2.0, attempting to follow your instructions to the letter:

...For this reason please confirm the following ways to resolve:
1. Uninstall currently version, as the installation is failed, you need re-install it.
2. If you have previous version of TotalMounter, INetDisk client installed, you need uninstall them and you must reboot your computer.

I had already uninstalled v2.0 & installed v1.50. So, I uninstalled v1.50 using the TotalMounter 1.50 Setup from TotalMounter.exe, not "Uninstall" in the Control Panel.

3. Confirm there is no old controller: In windows device manager, expand the tree to "Storage Controller" , if you found node like "KernSafe SCSI Controller", delete it and reboot, this is an optional step just in case of successfully uninstall.

Before rebooting at the end of the uninstall, I checked Device Manager to confirm that both Kernsafe SCSI controller & KernSafe Virtual System Bus were removed from the "Storage controllers" and "System devices" sections.

4. After reboot, please do new TotalMouner or TotalMounter Pro install again.
Another reason is not select driver installation, when install the software, there are two windows will popup to ask you install drivers, you need agree to install them.

"After rebooting, I confirmed again that both Kernsafe SCSI controller & KernSafe Virtual System Bus were removed from the "Storage controllers" and "System devices" sections of Device Manager. I manually deleted the (empty) directories C:\Program Files\KernSafe and C:\Users\<userid>\AppData\Local\Temp\TotalMounter.
I then installed TotalMounter v2.0, using the supplied defaults and accepting the installation of both drivers. Device Manager confirmed the presence of:
- "Storage controllers/KernSafe SCSI controller" with Properties of Device status: "This device is working properly"; Driver Date: "23/06/2009"; Driver Version: "1.7.623.0"; Resources/Conflicting device list:"No conflicts."
- "System devices/KernSafe Virtual System Bus" with Properties of Device status: "This device is working properly"; Driver Date: "23/06/2009"; Driver Version: "1.7.623.0".
Even though it was not requested by the installer, I rebooted the system and, again confirmed the status of the two KernSafe drivers.

However, when running TotalMounter v2.0, I still encountered the same errors "No device left" and "Driver communication error: 3" described by myself, CatLover and ectospasm.

My apologies for the long post. I wanted you to be sure that all of your suggested actions had been correctly followed. However, the problem is not resolved.

My next action will be to uninstall v2.0 and revert to v1.50.

[tyrotex]

After my earlier (lengthy) post responding to Charles' suggestions for correct installation, I was moving between installations of v2.0 and v1.50 of TotalMounter, and noticed a few things about them:
1. The driver versions are the same between the two releases.
2. When starting TotalMounter v1.50, it drops to the User Account Control prompt before displaying itself.
3. TotalMounter v2.0 does not give a UAC prompt. The application just starts and results in the "No device left" message and "Driver communication error: 3" status.
4. If I start TotalMounter v2.0 as Administrator, I _do_ get the UAC prompt . The program still fails with the "No device left" message, but the status now says "Driver communication error: EA"

It would seem that the TotalMounter v2.0 application just cannot talk with the drivers, even if they are correctly installed.

I hope the problem can be fixed soon. Until then, v1.50 seems to work for me in Win 7 Pro.

[Charles [PM]]

The driver files in 2.0 are completely new, however, I think you are right, the same driver version in .inf should be the reason.
Even you uninstalled the old version, windows still saving previous version of driver in its driver store, it won't be overwrite by new version because they have the same version info.
We will check more and make an update.

[tyrotex]

Charles, I'm happy to report that TotalMounter 2.01 seems to work fine on my Windows 7 install.
The drivers are updated to version 2.0.800.0, dated 12/12/2013.
Thank you for getting that fixed so quickly.