Powerdvd Error 1327
Contents |
Chosen by ianbutty ianbutty Newbie Private Message Joined: Nov 02, 2010 08:42 Messages: 4 Offline Solved by Nov 02, 2010 08:50 Just downloaded the trial version of PowerDirector. When error 1327 invalid drive e I try to install it I get the following error: "Error 1327.
Error 1327 Invalid Drive F
Invalid Drive G:\" I do not have a drive G: on my PC. (WinXp PRO Sp 3). The
Error 1327 Invalid Drive D
installation has not asked me where to install it. The only question I have been asked is the language. I have raised a support call on this but thought I'd
Error 1327 Invalid Drive Z
post this here in case I can get and answer from the user-to-user forums. Thanks Ian. Ian M Butterfield www.imb.biz Reply Solution Chosen by ianbutty Carl312 Senior Contributor Private Message Location: Texas, USA Joined: Mar 16, 2010 20:11 Messages: 8357 Offline Nov 02, 2010 10:27 Download the trial again. It is possible that you got a bad download. Windows 7 64-bit error 1327 invalid drive adobe 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1 GB,WD 1TB HD C free space greater than 100GB http://www.carlmcmillan.com Not responsible for any harm that may come to your wallet This answered my question Reply Solution Chosen by ianbutty ianbutty Newbie Private Message Joined: Nov 02, 2010 08:42 Messages: 4 Offline Nov 02, 2010 12:17 Carl312 wrote: Download the trial again. It is possible that you got a bad download. Downloaded the file again. No errors when it goes through the MD5 check so I don't believe it is a corrupt file. I've tried shutting down and restarting the PC. Still getting the same installation error. This message was edited 1 time. Last update was at Nov 02. 2010 12:18 Ian M Butterfield www.imb.biz This answered my question Reply Solution Chosen by ianbutty Carl312 Senior Contributor Private Message Location: Texas, USA Joined: Mar 16, 2010 20:11 Messages: 8357 Offline Nov 02, 2010 14:23 I found this online. I do not know if it is relevant to your problem. http://social.answers.microsoft.com/Forums/en-US/vistainstall/thread/ccb3a5bf-9d38-4b1c-8f33-d6a53b1c1a36 Windows 7 64-bit 8 GB RAM,AMD P
to : Acrobat Creative Suite CS3 Photoshop Elements Issue When you attempt to install Acrobat 6.x-7.x, Photoshop Elements 5.0, or Creative Suite 3 on Windows, the following error occurs "Error 1327 - Invalid Drive [drive letter here]" Reason error 1327 invalid drive h windows 7 A system folder is mapped to a network drive that has the Reconnect at Logon error 1327 invalid drive g check box checked.You've changed the drive letter for the CD-ROM drive or hard drive where the system folder is located. Solution Adobe Technical error 1327 invalid drive autodesk Support recommends that you temporarily disable startup items and services before attempting to install. After the installation is complete you can re-enable the startup items.Do one or more of the following:Solution 1: Use the subst command to http://forum.cyberlink.com/forum/posts/list/13901.page remove the drive letter.This DOS utility allows a user to connect and disconnect a drive letter to a virtual drive location. Disconnecting the drive letter should allow the installer to proceed without generating a error message. Click Start > Run. Type cmd and click OK. Type subst /D [Driver Letter]: and press Enter. -- If you recieve a error proceed to Solution 2. Type exit and press Enter. Attempt to install Acrobat. Solution 2: Use the https://helpx.adobe.com/creative-suite/kb/error-1327-invalid-drive-drive.html subst command to reassociate the drive letter with a temporary location.This DOS utility allows a user to connect and disconnect a drive letter to a virtual drive location. Connecting the drive letter with a temporary location allows the installer to location that path. Verify the temp folder exists before redirecting the drive to that location. Create it if it does not exist. Click Start > Run. Type cmd and click OK. Type subst [Driver Letter]: C:\temp and press Enter. Type exitand press Enter. Attempt to install Acrobat. Click Start > Run. Type cmd and click OK. Type subst /D [Driver Letter]: and press Enter. Note: This will remove the temporary association that was created previously. Type exit and press Enter. Solution 3: Create a new local administrator account.Log on to the computer using a local account and install the application(s). Log into a new local administrator account. Attempt to install Acrobat again. Solution 4: Disconnect network drive.This information was obtained from http://support.microsoft.com/default.aspx?scid=kb;en-us;282183. This solution will only assist you if network drives appear under My Computer. If none are present proceed to the next solution. Click Start > Programs > Windows Explorer. In Windows Explorer, click Tools and then Disconnect Network Drive. Select the network drive on which the shell folder is located and click OK. On the Tools menu, click Map Network Drive. Unchec
Error 1327 Invalid drive 11 28 Jun 2005 | Development Tags: Installer This error was such an odd one, I thought I'd share it.. We've been creating MSI packages http://coding-insomnia.com/2005/06/28/error-1327-invalid-drive/ using Wise, and they have been running very well on pretty much all computers. So imagine my surprise when I get an email from a guy at the Norweigan it department saying that when he tries to install the package he gets an "Error 1327. Invalid drive h:\" message. He was logging on as domain admin on a setup error 1327 where they have roaming profiles (i.e. the My Documents folder etc is stored on the network). After some investigation, he found that if he changed the registry key for My Documents (Hkey_Current_user\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folder\Personal) to use the complete UNC path instead of "h:\" as was used before, it all worked without any problems. First of all, we don't install error 1327 invalid anything to My Documents or anything else that should be user related. But apparently, the installation uses that path for storing temporary files or something. Anyway, just for the heck of it, he tried changing the registry setting to the complete UNC path instead (i.e. \\servername\etc\etc). And voila, the installation succeeded! It turns out that the server he was using was a Win 2000 instance on MS Virtual Server. After a LOT of searching, I found a couple of articles that mentioned a similar error: MS KB 255582. AppDeploy.com FAQ To sum them up, MSI packages that are installed remotely via Terminal Services on a Win2000 box (and I guess that Virtual Server uses the same functionality) cannot use mapped drives because they are running in a different context (the Windows Installer service is running as a service in the console session , not in the session of the remote user). The solution.. Well, either use UNC names in the registry or upgrade to Windows XP or 2003 where this problem is supposed to b