pesadillo.com » .BAT

COMPRIMIR DESDE LINEA DE COMANDOS COMPACT y ZIP CON .BAT

pesadillo — Tue, 11 Jun 2013 22:06:20 +0000

COMPACT permite que un archivo o un directorio se compriman en cuanto a su forma de almacenarlos en el disco, es decir, que no comprime la información de los archivos o carpetas sino que utiliza una forma comprimida de almacenarla. Por eso exige que el disco donde se almacenan esté formateado de una forma específica (concretamente en NTFS). Una vez que se elige que un archivo es de tipo comprimido (se marca con una “C” en los atributos que señala el comando COMPACT) lo seguirá siendo hasta que se le cambie su carácter. De modo que si editas y modificas un archivo comprimido al guardarlo se guarda como archivo comprimido. Si comprimes un directorio, todo lo que se guarde en él se guardará en forma comprimida. No sé en que consiste la compresión que hace el comando COMPACT pero no es como la de Winzip o la de Winrar. Estos programas compresores comprimen la información utilizando combinaciones de algoritmos de encriptado y otros que permiten detectar repeticiones y sustituirlas por algo como la cuenta de repetición y el texto repetido (algo como sí en lugar de “abcabcabcabcabc” guardaras “5abc”). Pero los archivos comprimidos de esta manera son archivos “normales” para el sistema operativo. De hecho se puede ver la información comprimida (que no se parece en nada a la original y resulta ilegible).
Dicho lo anterior debería quedar claro que si copias archivos de un directorio comprimido con COMPACT a un directorio normal los archivos en el directorio normal estarán descomprimidos. Si copias un archivo comprimido en otro archivo, la copia estará descomprimida. Si sobreescribes un archivo comprimido con el contenido de otro archivo, el archivo comprimido seguirá estando comprimido pero con la información cambiada. De alguna manera al escribir sobre un archivo comprimido se comprime y al leerlo se descomprime, sin que podamos ver el resultado. El explorador de Windows sabe si un archivo o un directorio están comprimidos y los muestra en azul.

compact c:\”nombre de archivo”/u

compact /?
Muestra o altera la compresión de los archivos en particiones NTFS.

COMPACT [/C | /U] [/S[:dir]] [/A] [/I] [/F] [/Q] [filename [...]]

/C Comprime los archivos especificados. Los directorios serán marcados para que los archivos agregados después sean comprimidos.
/U Descomprime los archivos especificados. Los directorios serán marcados para que los archivos agregados después no sean comprimidos.
/S Efectúa la operación especificada en los archivos del directorio dado y todos los subdirectorios. De forma predeterminada, “dir” es el directorio actual.
/A Muestra los archivos ocultos o los atributos del sistema. Estos archivos se omiten por defecto.
/I Continua efectuando la operación especificada incluso después de que hayan ocurrido los errores. De forma predeterminada, COMPACT para cuando se encuentra un error.
/F Fuerza la operación de compresión en todos los archivos especificados, incluso en los que ya están comprimidos. Los archivos ya comprimidos se saltan por defecto.

/Q Informa sólo de la información del nombre de archivo más esencial.

Usado sin parámetros, COMPACT muestra el estado de la compresión del directorio actual y cualquier archivo que contenga. Puede usar múltiples nombres de archivo y comodines. Debe poner espacios entre los parámetros.

SI QUIERES COMPRIMIR EN ZIP:
Descarga el quit de herramientas para administradores desde la siguiente página:

http://www.microsoft.com/en-us/download/details.aspx?id=17657

El comado sería de la siguiente forma:

C:\>compress /?

Syntax:

COMPRESS [-R] [-D] [-S] [ -Z | -ZX ] Source Destination
COMPRESS -R [-D] [-S] [ -Z | -ZX ] Source [Destination]

Description:
Compresses one or more files.

Parameter List:
-R Rename compressed files.

-D Update compressed files only if out of date.

-S Suppress copyright information.

-ZX LZX compression. This is default compression.

-Z MS-ZIP compression.

Source Source file specification. Wildcards may be
used.

Destination Destination file | path specification.
Destination may be a directory. If Source is
multiple files and -r is not specified,
Destination must be a directory.

PARA COMPRIMIR CON ZIP DESDE LA LINEA DE COMANDOS, NECESITAMOS CREEAR UN SCRIPT:

::Opcional, creamos un fichero
echo HOLA>c:\fichero.txt

:: indicamos el fichero a comprimir
set FILETOZIP=c:\fichero.txt

::creamos un directorio temporal donde mover los ficheros
set TEMPDIR=C:\temp738
rmdir %TEMPDIR%
mkdir %TEMPDIR%
copy %FILETOZIP% %TEMPDIR%

::Creamos el scrip
echo Set objArgs = WScript.Arguments > _zipIt.vbs
echo InputFolder = objArgs(0) >> _zipIt.vbs
echo ZipFile = objArgs(1) >> _zipIt.vbs
echo CreateObject("Scripting.FileSystemObject").CreateTextFile(ZipFile, True).Write "PK" ^&

Chr(5) ^& Chr(6) ^& String(18, vbNullChar) >> _zipIt.vbs
echo Set objShell = CreateObject("Shell.Application") >> _zipIt.vbs
echo Set source = objShell.NameSpace(InputFolder).Items >> _zipIt.vbs
echo objShell.NameSpace(ZipFile).CopyHere(source) >> _zipIt.vbs
echo wScript.Sleep 2000 >> _zipIt.vbs
:: Comprimir el directorio en un fichero .zip
CScript  _zipIt.vbs  %TEMPDIR%  C:\comprimido.zip

::ejecutamos el explorador de ficheros para localizar el comprimido
start c:\
exit

Acceso a directorios especiales desde la linea de comandos (bach)

pesadillo — Sun, 10 Mar 2013 23:00:28 +0000

I just came across a big problem in the Spybot S&D thread again, which should be addressed once and for all — if anyhow possible: Windows’ “Special Folders” like %APPDATA% or “All users Application Data”.

Windows addresses special folder locations via so-called CSIDLs, and starting from Vista, it uses what we call KNOWNFOLDERIDs. It is vitally important to use these instead of trying to hard-code stuff like

%ALLUSERSPROFILE%\Application Data\whatever

into PA installers. Because they will fail on many systems!

For instance, let’s take the “local application data” (an easy one):

On an English-language Windows XP system, this will (usually) be

C:\Documents and Settings\username\Local Settings\Application Data

On a German-language Windows XP, it would look like

C:\Dokumente und Einstellungen\username\Lokale Einstellungen\Anwendungsdaten

Or on a Spanish system

C:\Documents and Settings\username\Configuración local\Datos de programa

Or even

C:\Users\username\AppData\Local

if you’re running Windows 7 with the English locale active. See what I mean?

To further complicate things, some of them are now file system junctions under Windows 7, which have special access settings. (Actually, much like symlinks on Linux.) Plus, users do have the possibility to actually move some of these locations (like putting their personal profile data onto another drive).

It seems the only universally working way is to always ask the operating system for the real names and locations of these “special places”. Because that will always return correct results, and we could be sure that a Portable App will function correctly, be it under Windows XP, or a foreign-language Windows 7.

I lately had this discussion over at Piriform’s CCleaner Forum. You might want to read my article “Getting Special Folders right on ALL systems” over there. It also contains some VBScript code (yuk!) to show what should be done. (In a clumsy way, by setting up environment variables.)

I strongly feel that the Portable Apps Platform should do this right from the beginning. I haven’t had a look yet on which of the (possibly) needed variables the NSIS system already provides, but I strongly suggest we should have at least most of the CSIDL-based plus some of the KNOWNFOLDERID-based (Vista and newer) in order to provide users with the greatest and most glitch-free PA experience — even on foreign-language systems, and all versions.

Getting hold of these “special locations” from the operating system within some part of NSIS code, and providing them as variables to use in PA development would be great. (And much better than setting up a zillion large environment variables!) I offer my help in getting this straight.

Here’s a list of the ones I currently address with the environment variables set by my VBScript. We might need a few more to address each and every issue correctly, though. I strongly feel using the “official” special paths would make the developers’ and the users’ lives much easier …

—

1. VARIABLES THAT MAKE SENSE WITH PORTABLE APPS (YOU SHOULD USE THESE)

These are most useful to use with Portable Apps/NSIS file operations. They will access the “right” special folders on almost any Windows 2000, XP, Vista or 7 machine, independent of its locale settings.

%CDBurning% (CSIDL_CDBURN_AREA, 0x3b)

V6.0: The file system directory that acts as a staging area for files waiting to be written to a CD.
A typical path is C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\CD Burning.

%CommonFavorites% (CSIDL_COMMON_FAVORITES, 0x1f)

The file system directory that serves as a common repository for favorite items common to all users.

%CommonOEMLinks% (CSIDL_COMMON_OEM_LINKS, 0x3a)

This value is recognized in Windows Vista for backward compatibility, but the folder itself is no longer used. I’ve seen it come back in Windows 7, though.

%CommonStartup% (CSIDL_COMMON_STARTUP, 0×18)

The file system directory that contains the programs that appear in the Startup folder for all users.
A typical path is C:\Documents and Settings\All Users\Start Menu\Programs\Startup.

%Cookies% (CSIDL_COOKIES, 0×21)

The file system directory that serves as a common repository for Internet cookies.
A typical path is C:\Documents and Settings\username\Cookies.

%DesktopDirectory% (CSIDL_DESKTOPDIRECTORY, 0×10)

The file system directory used to physically store file objects on the desktop (not to be confused with the desktop folder itself).
A typical path is C:\Documents and Settings\username\Desktop.

%Favorites% (CSIDL_FAVORITES, 0×06)

The file system directory that serves as a common repository for the user’s favorite items.
A typical path is C:\Documents and Settings\username\Favorites.

%History% (CSIDL_HISTORY, 0×22)

The file system directory that serves as a common repository for Internet history items.

%InternetCache% (CSIDL_INTERNET_CACHE, 0×20)

V4.72: The file system directory that serves as a common repository for temporary Internet files.
A typical path is C:\Documents and Settings\username\Local Settings\Temporary Internet Files.

%LocalAppData% (CSIDL_LOCAL_APPDATA, 0x1c)

V5.0: The file system directory that serves as a data repository for local (nonroaming) applications.
A typical path is C:\Documents and Settings\username\Local Settings\Application Data.

%Music% (CSIDL_MYMUSIC, 0x0d)

The file system directory that serves as a common repository for music files.
A typical path is C:\Documents and Settings\User\My Documents\My Music.

%Personal% (CSIDL_PERSONAL, 0×05)

V6.0: The virtual folder that represents the My Documents desktop item. This is equivalent to CSIDL_MYDOCUMENTS.
Previous to V6.0: The file system directory used to physically store a user’s common repository of documents.
A typical path is C:\Documents and Settings\username\My Documents.
This should be distinguished from the virtual My Documents folder in the namespace. To access that virtual folder, use SHGetFolderLocation, which returns the ITEMIDLIST for the virtual location, or refer to the technique described in Managing the File System.

%Pictures% (CSIDL_MYPICTURES, 0×27)

V5.0: The file system directory that serves as a common repository for image files.
A typical path is C:\Documents and Settings\username\My Documents\My Pictures.

%Profile% (CSIDL_PROFILE, 0×28)

V5.0: The user’s profile folder.
A typical path is C:\Users\username.
Applications should not create files or folders at this level; they should put their data under the locations referred to by CSIDL_APPDATA or CSIDL_LOCAL_APPDATA. However, if you are creating a new Known Folder the profile root referred to by CSIDL_PROFILE is appropriate.

%ProgramData% (CSIDL_COMMON_APPDATA, 0×23)

V5.0: The file system directory that contains application data for all users.
A typical path is C:\Documents and Settings\All Users\Application Data.
This folder is used for application data that is not user specific. For example, an application can store a spell-check dictionary, a database of clip art, or a log file in the CSIDL_COMMON_APPDATA folder.
This information will not roam and is available to anyone using the computer.

%ProgramFiles% (CSIDL_PROGRAM_FILES, 0×26)

V5.0: The Program Files folder.
A typical path is C:\Program Files.

%ProgramFilesCommon% (CSIDL_PROGRAM_FILES_COMMON, 0x2b)

V5.0: A folder for components that are shared across applications.
A typical path is C:\Program Files\Common. Valid only for Windows XP.

%ProgramFilesCommonX86% (CSIDL_PROGRAM_FILES_COMMONX86, 0x2c)

%ProgramFilesX86% (CSIDL_PROGRAM_FILESX86, 0x2a)

%PublicDesktop% (CSIDL_COMMON_DESKTOPDIRECTORY, 0×19)

The file system directory that contains files and folders that appear on the desktop for all users.
A typical path is C:\Documents and Settings\All Users\Desktop.

%PublicDocuments% (CSIDL_COMMON_DOCUMENTS, 0x2e)

The file system directory that contains documents that are common to all users.
A typical path is C:\Documents and Settings\All Users\Documents.

%PublicMusic% (CSIDL_COMMON_MUSIC, 0×35)

V6.0: The file system directory that serves as a repository for music files common to all users.
A typical path is C:\Documents and Settings\All Users\Documents\My Music.

%PublicPictures% (CSIDL_COMMON_PICTURES, 0×36)

V6.0: The file system directory that serves as a repository for image files common to all users.
A typical path is C:\Documents and Settings\All Users\Documents\My Pictures.

%PublicVideos% (CSIDL_COMMON_VIDEO, 0×37)

V6.0: The file system directory that serves as a repository for video files common to all users.
A typical path is C:\Documents and Settings\All Users\Documents\My Videos.

%Recent% (CSIDL_RECENT, 0×08)

The file system directory that contains shortcuts to the user’s most recently used documents.
A typical path is C:\Documents and Settings\username\My Recent Documents.
To create a shortcut in this folder, use SHAddToRecentDocs.
In addition to creating the shortcut, this function updates the Shell’s list of recent documents and adds the shortcut to the My Recent Documents submenu of the Start menu.

%RoamingAppData% (CSIDL_APPDATA, 0x1a)

V4.71: The file system directory that serves as a common repository for application-specific data.
A typical path is C:\Documents and Settings\username\Application Data.
This CSIDL is supported by the redistributable Shfolder.dll for systems that do not have the Microsoft Internet Explorer 4.0 integrated Shell installed.

%Startup% (CSIDL_STARTUP, 0×07)

The file system directory that corresponds to the user’s Startup program group.
The system starts these programs whenever any user logs on.
A typical path is C:\Documents and Settings\username\Start Menu\Programs\Startup.

%System% (CSIDL_SYSTEM, 0×25)

V5.0: The Windows System folder.
A typical path is C:\Windows\System32.

%SystemX86% (CSIDL_SYSTEMX86, 0×29)

A typical path is C:\Windows\System32.

%Videos% (CSIDL_MYVIDEO, 0x0e)

V6.0: The file system directory that serves as a common repository for video files.
A typical path is C:\Documents and Settings\username\My Documents\My Videos.

%Windows% (CSIDL_WINDOWS, 0×24)

V5.0: The Windows directory or SYSROOT. This corresponds to the %windir% or %SYSTEMROOT% environment variables.
A typical path is C:\Windows.

—

2. VARIABLES THAT ARE USEFUL FOR SPECIAL REQUIREMENTS

These are intended for more special cases, or declared obsolete, and might not function as intended. You should know what you do, it’s all upon your own risk!

%AdminTools% (CSIDL_ADMINTOOLS, 0×30)

V5.0: The file system directory that is used to store administrative tools for an individual user.
The MMC will save customized consoles to this directory, and it will roam with the user.

%AltStartup% (CSIDL_ALTSTARTUP, 0x1d, obsolete, use “Startup”)

The file system directory that corresponds to the user’s nonlocalized Startup program group.
This value is recognized in Windows Vista for backward compatibility, but the folder itself no longer exists.

%CommonAdminTools% (CSIDL_COMMON_ADMINTOOLS, 0x2f)

V5.0: The file system directory that contains administrative tools for all users of the computer.

%CommonAltStartup% (CSIDL_COMMON_ALTSTARTUP, 0x1e, obsolete, use “CommonStartup”)

The file system directory that corresponds to the nonlocalized Startup program group for all users.
This value is recognized in Windows Vista for backward compatibility, but the folder itself no longer exists.

%CommonPrograms% (CSIDL_COMMON_PROGRAMS, 0×17)

The file system directory that contains the directories for the common program groups that appear on the Start menu for all users.
A typical path is C:\Documents and Settings\All Users\Start Menu\Programs.

%CommonStartMenu% (CSIDL_COMMON_STARTMENU, 0×16)

The file system directory that contains the programs and folders that appear on the Start menu for all users.
A typical path is C:\Documents and Settings\All Users\Start Menu.

%CommonTemplates% (CSIDL_COMMON_TEMPLATES, 0x2d)

The file system directory that contains the templates that are available to all users.
A typical path is C:\Documents and Settings\All Users\Templates.

%Desktop% (CSIDL_DESKTOP, 0×00)

The virtual folder that represents the Windows desktop, the root of the namespace.

%Documents% (CSIDL_MYDOCUMENTS, 0x0c)

V6.0: The virtual folder that represents the My Documents desktop item.
This value is equivalent to CSIDL_PERSONAL.

%Fonts% (CSIDL_FONTS, 0×14)

A virtual folder that contains fonts. A typical path is C:\Windows\Fonts.

%LocalizedResourcesDir% (CSIDL_RESOURCES_LOCALIZED, 0×39)

%NetHood% (CSIDL_NETHOOD, 0×13)

A file system directory that contains the link objects that may exist in the My Network Places virtual folder. It is not the same as CSIDL_NETWORK, which represents the network namespace root.
A typical path is C:\Documents and Settings\username\NetHood.

%PrintHood% (CSIDL_PRINTHOOD, 0x1b)

The file system directory that contains the link objects that can exist in the Printers virtual folder.
A typical path is C:\Documents and Settings\username\PrintHood.

%Programs% (CSIDL_PROGRAMS, 0×02)

The file system directory that contains the user’s program groups (which are themselves file system directories).
A typical path is C:\Documents and Settings\username\Start Menu\Programs.

%ResourceDir% (CSIDL_RESOURCES, 0×38)

Windows Vista: The file system directory that contains resource data.
A typical path is C:\Windows\Resources.

%SendTo% (CSIDL_SENDTO, 0×09)

The file system directory that contains Send To menu items.
A typical path is C:\Documents and Settings\username\SendTo.

%StartMenu% (CSIDL_STARTMENU, 0x0b)

The file system directory that contains Start menu items.
A typical path is C:\Documents and Settings\username\Start Menu.

%Templates% (CSIDL_TEMPLATES, 0×15)

The file system directory that serves as a common repository for document templates.
A typical path is C:\Documents and Settings\username\Templates.

—

3. VARIABLES THAT ONLY RETURN CLSIDs

These are not primarily useful for Portable Apps (but can be for other purposes), because they only return CLSIDs. CLSIDs are globally unique identifiers that identify COM class objects, for instance “%RecycleBinFolder%” will return a CLSID of

::{645FF040-5081-101B-9F08-00AA002F954E}

which is the virtual folder that contains the objects in the user’s Recycle Bin. (Try typing this into Windows Explorer’s address bar!)

%ComputerFolder% (CSIDL_DRIVES, 0×11)

The virtual folder that represents My Computer, containing everything on the local computer: storage devices, printers, and Control Panel. The folder can also contain mapped network drives.

%ComputersNearMe% (CSIDL_COMPUTERSNEARME, 0x3d)

The folder that represents other computers in your workgroup.
Usually (only) contains a Workgroup or Domain Name.

%ConnectionsFolder% (CSIDL_CONNECTIONS, 0×31)

The virtual folder that represents Network Connections, that contains network and dial-up connections.

%ControlPanelFolder% (CSIDL_CONTROLS, 0×03)

The virtual folder that contains icons for the Control Panel applications.

%InternetFolder% (CSIDL_INTERNET, 0×01)

A virtual folder for Internet Explorer.

%Network% (CSIDL_NETWORK, 0×12)

A virtual folder that represents Network Neighborhood, the root of the network namespace hierarchy.

%PrintersFolder% (CSIDL_PRINTERS, 0×04)

The virtual folder that contains installed printers.

%RecycleBinFolder% (CSIDL_BITBUCKET, 0x0a)

The virtual folder that contains the objects in the user’s Recycle Bin.

—

If you’re interested and wish to “peek around” a little, here are links to my VBScript example and it’s ReadMe text:
ReadMe for SetEnvVars (text file)
SetEnvVars.zip (ZIP; as written for use with CCleaner)

Hint: If you play around with SetEnvVars.vbs, set

debug = TRUE

first in line #19. It will then show you everything it does (as message boxes). The WHS (Windows Scripting Host) must be enabled if you wish to execute the VBS via double-clicking. You can of course also invoke wscript.exe (in System32) manually to run it.

Hint 2: SetEnvvars.vbs modifies the User Environment — it stores environment variables there. These can be unset again later, if you wish. You can do that on the command line or using Computer Properties/Environment Variables/User Variables.

If you wish to keep a “snapshot” of your environment before running SetEnvVars.vbs, you can use

set > environment.txt

from a command prompt, which will save all environment variables in a text file.

Leer archivo de texto desde batch (BAT)

pesadillo — Thu, 13 Sep 2012 08:01:38 +0000

A la pregunta de como “coger texto de linea con un bat”, aqui teneis el código.

@echo off
setlocal enabledelayedexpansion

:reader
set c=0
for /f "tokens=*" %%a in (f.txt) do (
set /a c+=1
call set lin!c!=Linea_!c! = %%a
)
echo Archivo Leido
pause
for /l %%n in (1,1,!c!) do (echo !lin%%n!)
pause
endlocal
exit

si quisiera almacenar la informacion que el programa capturo de cada linea en una variable como seria????

echo %var% >archivo.txt

para cada linea tienes una variable que puedes usar mas adelante…antes del ENDLOCAL…..cuya sintaxis seria Linea_Numero, asi para la primera linea del Texto que ha sido leido usarias….

ECHO %Linea_1%

Despues de que el archivo a sido leido…

Fuente: http://foro.el-hacker.com

Quitar usb de forma segura.bat

pesadillo — Wed, 20 Jun 2012 23:29:02 +0000

%SystemRoot%\System32\RUNDLL32.EXE shell32.dll,Control_RunDLL hotplug.dll

Cambiar la dirección IP dinámica a estática con BAT

pesadillo — Fri, 13 Jan 2012 15:14:39 +0000

Cambiar la dirección IP dinámica a estática

Introduce en la consola:

netsh interface ip set address “Conexion de area local” static (dirección IP) (mascara de subred) (puerta de enlace) métrica
Los paréntesis no se ponen, son solo para que no te confundas.
─ Los datos de la máscara de subred y la puerta de enlace los obtienes con el comando IPCONFIG /ALL.
─ La dirección IP es la que vas a asignar, tiene que estar en el mismo rango que la puerta de enlace, hay varios grupos pero para que no te confundas simplemente súmale dos números al valor final de la puerta de enlace que tienes asignada.
Un ejemplo de cómo quedaría finalmente:

Interface ip set address "Conexion de area local" static 192.168.1.3 255.255.255.0 192.168.1.1 1

Crear un archivo batch para cambiar de forma sencilla tu dirección IP

Para crear un archivo batch que permita cambiar la dirección IP estática a dinámica, escribe lo siguiente en el Bloc de notas:

netsh interface ip set dns "Conexion de area local" dhcp
netsh interface ip set wins "Conexion de area local" dhcp
netsh interface ip set address "Conexion de area local" dhcp
ipconfig /renew

Para crear otro que permita cambiar la dirección IP dinámica a estática, escribe solo la línea que utilizaste en el ejemplo anterior.
Guárdalos con los nombres: dinámica.cmd y estatica.cmd, asegúrate que queden con la extensión de archivo .cmd. De ahora en adelante puedes cambiar tu dirección ejecutando cada batch alternativamente de acuerdo a tu necesidad.

Al trabajar para varios clientes, una de las cosas más engorrosas era tener que modificar sistemáticamente la configuración de la red para acceder a los diferentes servidores en función del cliente que me encontraba.

Windows XP

Podeis copiar el siguiente texto y copiarlo en un fichero con extensión bat o cmd para ejecutarlo.

Para asignar una dirección estática

netsh interface ip set address name="Conexion de area local" source=static 192.168.1.130 255.255.255.0 192.168.0.1 1
netsh interface ip set dns name="Conexion de area local" source=static 192.168.1.1 primary
netsh interface ip add dns name="Conexion de area local" addr=195.219.118.16

Entre comillas debeis poner el nombre del adaptador (Atención porque en castellano normalmente viene de serie “Conexión de área local” con acentos, y hay que modificar el nombre de la conexión yquitarle los acentos).

Para asignar una dirección dinámica

netsh interface ip set ADDRESS  "Conexion de area local" DHCP
netsh interface ip set DNS  "Conexion de area local" DHCP

WINDOWS 7 / SEVEN

netsh interface ipv4 set address name = "Conexion de area local" source=static address=172.0.0.181 mask=255.255.255.0 gateway=172.0.0.121
netsh interface ipv4 add dnsserver name="Conexion de area local" address=192.168.1.1 index=1
netsh interface ipv4 add dnsserver name="Conexion de area local" address=192.168.1.10 index=2

MUY IMPORTANTE: ES IMPRESCINDIBLE EJECUTARLO COMO ADMINISTRADOR, SI NO, NO SE EJECUTA

El gran cambio respecto a Windows XP, es que se cambia el parámetro IP por IPV4, y se añaden los nombres de los parámetros.

Para asignar una dirección dinámica

netsh interface ipv4 set ADDRESS  "Conexion de area local" source=DHCP
netsh interface ipv4 set DNS  "Conexion de area local" source=DHCP

Si quereis crear un bat para la conexión wifi, yo recomiendo modificar el nombre de la conexión inalámbrica, y poner un nombre corto como “wireless”.

Nueva tecnica de convertir decimal en hexadecimal con BAT MS-DOS

pesadillo — Thu, 16 Jun 2011 23:53:27 +0000

:: Hola, he ideado una nueva forma realmente rápida de convertir un número de decimal a hexadecimal usando una variable no documentada llamada =ExitCode

:: Versión final 2.
::Se quitaron carácteres innecesarios.

::Código:

@echo off
:: Llamamos al procedimiento  ec2Hex enviandole el decimal 10554896 almacenando resiltado en "ret"
call  ec2Hex 10554896 ret
echo.%ret%
pause
goto :eof

  ec2Hex
"%ComSpec%" /d /c exit /b %~1 >nul
for /f "eol=0 delims=0 tokens=*" %%# in (
"%=ExitCode%") do if not "%%#"=="" (
set %~2=%%#) else (set %~2=0)
goto :eof

Fuente: http://foro.el-hacker.com/f82/f-bat-nueva-ta-cnica-convertir-decimal-hexadecimal-177837/

Comandos interesantes de Ms-dOS

pesadillo — Thu, 28 Apr 2011 23:39:37 +0000

echo (on ó off)—para poner o quitar mensajes
set — establecer
for (in)—-repite un comando para archivos o directorios
goto—brinca a otra parte de el archivo bat
if—para poner condiciones
pause—detiene la acción y manda un mensaje a pantalla
rem–para insertar comentarios
shift–le resta un uno a los parametros
activate–activa otra ventana
beep—produce un sonido
call–llamar a otro archivo externo tambien .bat
cancel–termina el proceso entero
cls–limpia la pantalla
color–para activar colores
drawbox—dibuja una caja en la pantalla
drawline—dibuja lineas verticales en la pantalla
playsound–toca sonidos de windows
input–almacena lo escrito en el teclado en variables
gosub–ejecuta una subrutina
return–termina una subrutina

Convertir un número de decimal a hexadecimal (.BAT)

pesadillo — Tue, 26 Apr 2011 23:39:34 +0000

Hola, he ideado una nueva forma realmente rápida de convertir un número de decimal a hexadecimal usando una variable no documentada llamada =ExitCode

Código:

@echo off
:: Llamamos al procedimiento  ec2Hex enviandole el decimal 10554896 almacenando resiltado en "ret"
call  ec2Hex 10554896 ret
echo.%ret%
pause
goto :eof

  ec2Hex
"%ComSpec%" /d /c exit /b %~1 >nul
for /f "eol=0 delims=0 tokens=*" %%# in (
"%=ExitCode%") do if not "%%#"=="" (
set %~2=%%#) else (set %~2=0)
goto :eof

Fuente: http://foro.el-hacker.com/f82/f-bat-nueva-ta-cnica-convertir-decimal-hexadecimal-177837/

Variable de entorno de Windows.

pesadillo — Tue, 19 Apr 2011 23:39:41 +0000

Aqui les dejo algunas variables de sistema que se pueden consultar desde la consola CMD y si se requiere modificar las variables se encuentran en propiedades de PC (WindowsXP), para que te puedar dar una idea de como funcionan entra al Boton INICIO/Ejecutar y escribe cmd y le das enter

cmd

Luego solo escribes el siguiente comando con la variable, la variable debes encerarlo con el simbolo de porcentaje %variable% y echo te devolvera el valor.

echo %Windowsversion%

ALLUSERSPROFILE
APPDATA
CLIENTNAME
CommonProgramFiles
COMPUTERNAME
ComSpec
EICDDrive
FP_NO_HOST_CHECK
HOMEDRIVE
HOMEPATH
LOGONSERVER
NUMBER_OF_PROCESSORS
OS
Path
PATHEXT
PROCESSOR_ARCHITECTURE
PROCESSOR_IDENTIFIER
PROCESSOR_LEVEL
PROCESSOR_REVISION
ProgramFiles
SESSIONNAME
SystemDrive
SystemRoot
TEMP
TMP
USERDOMAIN
USERNAME
USERPROFILE
VBOX_INSTALL_PATH
windir
Windows guarda las variables de entorno en la clave de registro: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Eliminar viejos controladores del registro.

pesadillo — Thu, 07 Apr 2011 23:50:35 +0000

Cuando vamos cambiando de hardware, quedarán instalado viejos drivers
y controladores que de vez en cuando es conveniente borrar del registro. La pega
es que los dispositivos viejos ya no podemos verlos en el Administrador de dispositivos
y por tanto no podemos desinstalarlos.
(Únicamente hay que tener cuidado con los dispositivos de red……. esos…. mejor no tocarlos
hay que borrar ÚNICAMENTE dispositivos en gris o difuminados que sepas que TU has instalado.
Nunca los del sistema, o los que haya instalado el propio sistema)

Para que aparezcan y por tanto poder borrarlos, crea, con el Block de Notas,
un archivo bat ,lo guardáis lo ejecutas (doble clic) llamado por ejemplo:
BorradorDevices.bat con el contenido:

@echo off
set devmgr_show_nonpresent_devices=1
cd %SystemRoot%\system32
start devmgmt.msc

lo guardas y lo ejecutas con doble clic.