background preloader

Windows tips

Facebook Twitter

Créer une clé USB d’installation Windows bootable en 1 clic. Bonjour, Votre PC n’a pas de lecteur CD/DVD, et vous voulez installer Windows via votre clé USB ?

Créer une clé USB d’installation Windows bootable en 1 clic

Les logiciels sont trop compliqués ? Et vous cherchez toujours l’outil magique qui permet de créer une clé USB bootable Windows en un seul clic ? Vous êtes tombé sur le bon choix alors Vous allez découvrir dans ce tutoriel deux outils magiques permettant de créer une clé USB Windows Bootable à partir du fichier ISO de Windows que vous pourrez obtenir légalement et gratuitement ! Les deux outils de ce tutoriel s’appellent : Windows 7 USB/DVD Download tool et WiNToBootic Remarque : J’ai déjà mis un tutoriel sur un autre méthode en utilisant le Universal USB Installer > Allons-y ! Microsoft Windows 7 USB/DVD Download tool Le premier utilitaire est developpé par Microsoft elle-même, et voici le lien de téléchargement (pas le lien officiel) : Une fois le programme est téléchargé, vous n’avez qu’à l’installer et passer à l’étape suivant.

Cliquez ensuite sur “Next“. Cliquez sur “USB device“. Et voilà ! Google Guide Quick Reference: Google Advanced Operators (Cheat Sheet) The following table lists the search operators that work with each Google search service.

Google Guide Quick Reference: Google Advanced Operators (Cheat Sheet)

Click on an operator to jump to its description — or, to read about all of the operators, simply scroll down and read all of this page. The following is an alphabetical list of the search operators. This list includes operators that are not officially supported by Google and not listed in Google’s online help. Each entry typically includes the syntax, the capabilities, and an example. Some of the search operators won’t work as intended if you put a space between the colon (:) and the subsequent query word. Allinanchor: If you start your query with allinanchor:, Google restricts results to pages containing all query terms you specify in the anchor text on links to the page.

Anchor text is the text on a page that is linked to another web page or a different place on the current page. Allintext: allintitle: allinurl: In URLs, words are often run together. Why my 32 bit applications cannot see the ODBC DSNs that I created on my 64 bit machine ? - A Support Engineer's Guide to the "Data Access" Galaxy. As we all database developers know that a ODBC DSN is an entry that we created through "ODBC Data Source Administrator" that we reached from Start/Control Panel/AdministrativeTools or typing "odbcad32" from Start/Run .

Why my 32 bit applications cannot see the ODBC DSNs that I created on my 64 bit machine ? - A Support Engineer's Guide to the "Data Access" Galaxy

On a 64bit machine when you run "ODBC Data Source Administrator" and created an ODBC DSN, actually you are creating an ODBC DSN which can be reachable by 64 bit applications only. But what if you need to run your 32bit application on a 64 bit machine ? The answer is simple, you'll need to run the 32bit version of "odbcad32.exe" by running "c:\Windows\SysWOW64\odbcad32.exe" from Start/Run menu and create your ODBC DSN with this tool. The key point here to remember is a 64bit machine should be considered as a "64 bit Windows + 32 bit Windows" at the sametime. That's why the folder that our developers put the 32bit "odbcad32.exe" under C:\Windows\SysWOW64\ . "C:\Windows\SysWOW64\wscript.exe C:\scripts\myscript.vbs". "C:\Windows\System32\wscript.exe C:\scripts\myscript.vbs". Windows xp - Lotus NotesSQL Driver - cannot install.

WMI. Cqgclub / WMIC. SC.EXE. This is a free tool from Microsoft (comes with the version 2 "Windows Installer SDK"). It can be used to add service information that can't be set up in the MSI "ServiceInstall" table (such as recovery and security information). If required it could be packaged with your product and called via a custom action script (perhaps generated with "VbsCa").

Note that it was written by an idiot so when it fails due to a syntax error it really won't say why and you can't trust the return code. See the "Testing Under the Local System Account" section for how "SC.EXE" can be used to open a command prompt running under the local system account. A bit of testing shows that "\"" should be used to escape double quotes where required. DESCRIPTION: SC is a command line program used for communicating with the NT Service Controller and services.

DESCRIPTION: Changes the actions upon failure USAGE: sc failure [service name] <option1><option2>... Modifies a service entry in the registry and Service Database.