Missing SPTD driver after PAVD install
-
I’m having an issue with SPTD option in PowerArchiver 2011. When I use the SPTD option and try to use the burner the drives are not detected even after installing PAVD. When I installed the PAVD driver from PA Burner, the StarPort Lite driver is installed but the SPTD driver failed to install. There is no sptd.sys driver in the c:\windows\system32\drivers folder. I’m running Windows 7 64-bit edition. When I try to run sptd.exe in the PowerArchiver folder it says not a valid Win32 application.
-
I have no trouble getting the VDs to load with the latest version (.59).
But I did have the following odd behavior.
If I unmount it from the shell, I get a message near the system tray saying that the VD was successfully uninstalled.
However, it still showed in my list of drives in Windows Explorer – even after a reboot.
If I open Burner and then tell it to uninstall the VD, all is fine.
-
with what version?
-
@Keith:
I’m having an issue with SPTD option in PowerArchiver 2011. When I use the SPTD option and try to use the burner the drives are not detected even after installing PAVD. When I installed the PAVD driver from PA Burner, the StarPort Lite driver is installed but the SPTD driver failed to install. There is no sptd.sys driver in the c:\windows\system32\drivers folder. I’m running Windows 7 64-bit edition. When I try to run sptd.exe in the PowerArchiver folder it says not a valid Win32 application.
do you get some message during installation? only with final? we didnt change that part of PA in a long time, there should be nothing new happening with SPTD drivers.
-
I haven’t used PAVD for a long time, I waited until after final came out and then when I installed PAVD there was a warning message from Duplex Secure asking to install the driver and even when I click the Install button, the sptd.sys driver is still not installed to the c:\windows\system32\drivers folder and the SPTD option in the configuration causes the burner to not detect any drives. PAVD is a separate download from the main PA and is installed via PatchBeam when using Virtual Drive for the first time. The only workaround for this issue is to download the SPTD v1.78 driver from http://www.duplexsecure.com/en/downloads and install it manually. Can you bundle the PAVD driver with SPTD v1.78 in the next PAVD update on PatchBeam? SPTD v1.78 fixes BSODs during file copy on some systems.
-
I tried PAVD on 32-bit and it automatically installs SPTD 1.62 when I install PAVD but on 64-bit it fails to install SPTD and there is no installing SPTD 1.62 message on the screen during installation of PAVD as it does on 32-bit and thus the SPTD driver is missing on 64-bit. This is a 64-bit specific issue.
-
@Keith:
I tried PAVD on 32-bit and it automatically installs SPTD 1.62 when I install PAVD but on 64-bit it fails to install SPTD and there is no installing SPTD 1.62 message on the screen during installation of PAVD as it does on 32-bit and thus the SPTD driver is not missing on 64-bit. This is a 64-bit specific issue.
did you use sptd from their own site, and that works?
-
I didn’t use SPTD from their own site during this test for this issue on 64-bit. Can you reproduce the issue on the 64-bit issue. Uninstall PAVD if already installed, then uninstall SPTD with the standalone SPTD installer from its own website and reboot and then reinstall PAVD from the Virtual Drive link in PA Burner. When I install PAVD from the Virtual Drive link on 32-bit it automatically displays SPTD v1.62 setup and installs the SPTD driver just before the StarPort driver installation. The 64-bit OS is my main OS and the 32-bit OS is a guest OS on VirtualBox. I was testing 32-bit temporarily to see if the issue only occurs on 64-bit. I later installed SPTD v1.79 from its own site after this testing on 64-bit and it works. The sptd.exe file in the PowerArchiver folder in 32-bit OS is 860KB and has a DuplexSecure icon and then when I double-click it it shows the SPTD v1.62 setup screen with a button to install/update, uninstall, or cancel and the one in 64-bit OS is 512KB and only has plain Windows icon and when I double-click it it says invalid Win32 application. I then removed the 32-bit guest when this testing is completed.