Can anyone tell me how to quickly copy Files from a mapped network drive?
The windows Copy Paste works very slow and hampers the performance of the system.
I have used XCOPY source destination /i /s /z /q
This was quick enough and copied a few files and later threw an error "The specified network name not available"
I remember somebody using a workaround to copy files quickly from mapped networked drive.
Can any one suggest me a way to do this?
I use Windows XP, so please don't suggest me RoboCopy.
RoboCopy works fine on WinXP. The Windows Server 2003 Resource Kit that contains RoboCopy installs fine on XP.
http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en
There is no reliable, fast and simple way to copy files between Windows computers using only the tools that come with the OS.
Your options are:
Unison
RoboCopy (See this article with instructions on XP)
rsync (comes with Cygwin)
Note that you can download the Windows 2003 server tools and unpack them on XP. It will work on XP.
I have found that Total Commander is significantly faster than any of the built-in copy mechanisms, including when copying files over the network.
use Ipmessanger I can copy at 55 MB /Sec (SATA2 7200 RPMS HDD on both PC's) on my Gigabit Ethernet
Related
Afternoon,
I am currently trying to install RSAT DNS Tools and Volume Activation Tools through DISM using PowerShell on a computer without internet. My environment is widely off the internet and thus not able to do this the normal way. I have the cab files for both downloaded off Microsoft VLSC, of those features but I get an error of: Add-Windows Capability: The source files could not be found.
My code used is"
Add-WindowsCapability -online -name rsat.dns.tools~~~~0.0.1.0 -limitaccess -source C:\Source\BuildSource\Laptop\02-AdminCenter\RSATTools\
I've also set the source path to the overarching CAB file as well (C:\Source\BuildSource\Laptop\02-AdminCenter\RSATTools\Microsoft-Windows-DNS-Tools-FoD-Package~31bf3856ad364e35~amd64~en-US~.cab and get the same error. Any help would be greatly appreciated!
Was able to solve it by mounting the original iso and not going through the specific cab files
Which of these files( in setup folder), if execute can install a program on windows 7 ?
1- setup.com
2-setup.ini
3-setup.inf
COM files are executable in Windows. You should be able to run setup.com from the CMD prompt by cding to the directory setup.com is in, and running setup or setup.com.
Keep in mind, COM files cannot be executed on 64-bit versions of Windows, since these editions lack NTVDM, the MS-DOS-emulating subsystem that handles COM file execution. You would instead need to emulate the 32-bit environment using an emulator like DOSBox.
setup.inf can be used to file copy and installation. I cannot remember setup.com installers for Windows programs.
msdn inf description
I am using Windows 7 and have upgraded to Windows Management Framework 3.0, which includes PowerShell 3. Within the past week or so, I have started getting an error upon starting PowerShell that prevents it from starting until there is a CD in my computer's drive (any CD will do). The only fix I have found so far—and this is only a temporary fix—is to completely uninstall and reinstall the Management Framework. This works until I use the CD drive for something, then PowerShell starts acting up again. The error dialog reads: There is no disk in the drive. Please insert a disk into drive D:.
Does anybody have any suggestions for what might be going on here? I see two possible problems related to configuration settings, but still need guidance about what/where to check and verify:
PowerShell is configured somewhere to check certain drives on startup, and isn't responding well to an empty CD drive
PowerShell is actually trying to open to some path on D:\. I'm pretty sure this is not the problem, since it opens to my %USERPROFILE% when there is a CD in the drive, but of course I could be missing something
Of course, I'm sure there are plenty of other possibilities I haven't considered
Any thoughts on possible fixes? I'd like not to have to uninstall and reinstall the Management Framework every time I use my CD drive!
EDIT: Additional details below copied from my responses to various comments
I can recreate the error by launching PowerShell in multiple ways. Shortcut is one. Starting it from a Command Prompt (cmd.exe) is another. Even trying to call a PowerShell script from a Command Prompt using something like PowerShell -ExecutionPolicy RemoteSigned -File script.ps1 produces the error, and so does PowerShell /?.
I don't see anything pointing to D:\ in $env:PATH and $env:HOMEDRIVE is not set to D:. %windir% is set to C:\Windows, %SystemDrive% is set to C:, and %SystemRoot% is set to C:\Windows.
Re-assigning the CD drive to a different letter resolves the problem, but this isn't a solution because it addresses the symptom and not the underlying cause (whatever that is).
When everything else fails, I can still start PowerShell from Cygwin
Process Monitor (linked below) is showing an attempt to read a non-existant registry entry HKCU\Software\Classes\Local Settings\MuiCache\5E6\52C64B7E\#D:\Windows\system32\AccessibilityCpl.dll,-10. Whatever mechanism is causing that bad read is likely also causing the error dialog. Something must be programmatically changing the system drive within PowerShell itself.
Further thoughts and suggestions are appreciated.
When Powershell first launches, it checks designated folders to import modules. I would take a good look at these. The default var is $env:PSModulePath and acts much like the standard $env:Path var. I would review that path and see if there are any references to the D: drive there.
MSDN - Windows PowerShell Modules
Are you installing .net from the DVD drive? Maybe downloading a fresh copy from MS would clear this up. MS .Net Framework 3.0 is very old, it is actualy designated for Server 2003 or WinXP. Is there a reason you are using it instead of 3.5, 4 or 4.5.1?
I'm trying to compile a program which uses cabarc.exe, but I don't have cabarc.exe. The problem is that the Microsoft Cabinet SDK is no longer available so I can't get it from there either.
Where can I get this file?
P.S. I'm looking for a download from a trusted source such as microsoft.com
It appears that the cabarc.exe utility has been replaced with makecab.exe, which comes with Windows [source].
It should be located in:
C:\WINDOWS\system32
The cabarc documentation can be found here.
The makecab documentation can be found here.
cabarc.exe is available as a part of the Windows XP Service Pack 2 Support Tools.
You can extract only this utility using commands like these (if you don't run XP):
WindowsXP-KB838079-SupportTools-ENU.exe /C /T:%TEMP%
extract /E %TEMP%\support.cab cabarc.exe
You can download the CabSDK from here:
Download the Microsoft Cabinet SDK version 4.71.410.0
In Windows 7 (and possibly Vista) instead of extract you use expand. The syntax is slightly different, but see below for the one that worked for me. Replace %TEMP% in the second command with wherever you want the cabarc.exe file to end up.
WindowsXP-KB838079-SupportTools-ENU.exe /C /T:%TEMP%
expand %TEMP%\support.cab -F:cabarc.exe %TEMP%
You can find cabarc.exe in the Internet Explorer Administration Kit.
Strangely though, IEAK 11 has cabarc.exe version 5.0.2147.1, while IEAK 10 has version 6.2.9200.16521.
For Windows 8 and Windows 8.1 use the Windows ADK
Download and install the Windows ADK from this website.
for the expand.exe command refer to
http://technet.microsoft.com/en-us/library/hh825253.aspx
The destination directory has to exist before executing the expand command. For example:
expand Dell-WinPE-Drivers-A02.CAB Dell-WinPE-Drivers-A02 -f:*
The prompt says that if I install the software into a directory with spaces:
the rebuild build tool used by the D Shared Source System will fail to build
and that I will be
forced to reinstall in a different location
However, I don't like random things in my C:\ drive. D, IMO, belongs in Program Files with PHP and MinGW and so on. How can I get it here?
If it matters, I'm using the Easy D installer package.
You can also use NTFS Link to create junction points (symlinks for all intents and purposes) and hard links on NTFS file systems. The functionality is built into the NTFS drivers, but an interface was never implemented for it, presumably to avoid things like recursive directory structures (endless virus scan loops anyone?). This package exposes an interface to this functionality.
I'd then create a symlink from C:\Program Files\ to something like C:\ProgramFiles\, hence disposing with the problematic space. This means that anything added to one directory will be added to the other, because both directories point to the same place on disk.
More info on NTFS Junction Points.
Info on NTFS symlinks (Vista only, but doesn't need NTFS Link to be installed.)
You could try using the old DOS 8.3 name for the Program Files directory, although this solution is implementation- and locale-dependent, and thus somewhat deprecated. On most US English systems, the 8.3 name of the C:\Program Files directory is C:\PROGRA~1. So, instead of installing to "C:\Program Files\dmd", you'd install to "C:\PROGRA~1\dmd". Hopefully, the configuration files for the misbehaving programs won't know the difference.
You could install it into C:\Program Files, and then use the subst command to make it appear as a new drive letter:
subst x: "c:\program files\d"
I actually use a "c:\Programs" for situations such as this - quite a few applications don't work well in directories with spaces in them.
It doesn't cause confusion since it's different enough from "c:\Program Files" - earlier attempts used "c:\ProgramFiles" (without the space) but this was too similar.
I have a C:\Dev folder on my machine for things like this. That way you only have one folder on the main directory and it stays unclutered.