Open command prompt with admin access (by press Windows key then type "cmd" then Entre), type
netsh wlan show profiles
It will list all the Wifi network it have connected to. The Profile name is the SSID.
Find the SSID (Profile name) from the list and type
netsh wlan show profile name=”SSID” key=clear
It will show the Wifi password on "Key Content" line
관리자 권한이 있는 계정에서 콘솔창을 열고 (윈도우 키를 누르고 "cmd"라고 친 다음에 엔터를 친다) 다음과 같은 명령어를 입력합니다
netsh wlan show profiles
이때까지 이 컴퓨터에서 연결했던 와이파이의 목록이 쭉 나옵니다. 목록에 적힌 Profile Name이 SSID 입니다.
원하는 SSID 를 찾아서 다음과 같이 입력합니다.
netsh wlan show profile name=”SSID” key=clear
와이파이 암호가 "Key Content" 줄에 표시됩니다.
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Saturday, February 24, 2018
Tuesday, July 23, 2013
How to turn off Autorun on external devices (USB DRIVE)
Windows XP 외장하드 자동실행 끄기
윈도키+R -> gpedit.msc 엔터
-> 컴퓨터 구성 -> 관리 템플릿 -> 시스템
-> 화면 우측에 "자동실행 사용 안 함" 더블클릭
-> 사용
-> 자동 실행 사용 안함: 모든 드라이브
-> 확인
-> 화면 우측에 "자동실행 사용 안 함" 더블클릭
-> 사용
-> 자동 실행 사용 안함: 모든 드라이브
-> 확인
USB같은 경우에는 루트에 autorun.inf 폴더를 만들어놔서 자동실행파일이 만들어지는 것을 애초에 막아버릴 것을 권한다.
출처 : 뮤직트로트 - http://www.xtx.kr
Turn off auto run on external devices (USB DRIVE)
How to use Group Policy settings to disable all Autorun features in Windows Server 2008 or Windows Vista
Use either of the following methods:
Method 1
Method 1
- Click Start, type Gpedit.msc in the Start Search box, and then press ENTER.If you are prompted for an administrator password or for confirmation, type the password, or click Allow.
- Under Computer Configuration, expand Administrative Templates, expand Windows Components, and then clickAutoplay Policies.
- In the Details pane, double-click Turn off Autoplay.
- Click Enabled, and then select All drives in the Turn off Autoplay box to disable Autorun on all drives.
- Restart the computer.
Method 2
- Click Start, type Gpedit.msc in the Start Search box, and then press ENTER.If you are prompted for an administrator password or for confirmation, type the password, or click Allow.
- Under Computer Configuration, expand Administrative Templates, expand Windows Components, and then clickAutoplay Policies.
- In the Details pane, double-click Default Behavior for AutoRun.
- Click Enabled, and then select Do not execute any autorun commands in the Default Autorun behavior box to disable Autorun on all drives.
- Restart the computer.
How to use Group Policy settings to disable all Autorun features in Windows Server 2003, Windows XP Professional, and Windows 2000
- Click Start, click Run, type Gpedit.msc in the Open box, and then click OK.
- Under Computer Configuration, expand Administrative Templates, and then click System.
- In the Settings pane, right-click Turn off Autoplay, and then click Properties.
Note In Windows 2000, the policy setting is named Disable Autoplay. - Click Enabled, and then select All drives in the Turn off Autoplay box to disable Autorun on all drives.
- Click OK to close the Turn off Autoplay Properties dialog box.
- Restart the computer.
Source: Microsoft http://support.microsoft.com/kb/967715/en-us
Friday, April 15, 2011
D:\tmp\mysql-connector-odbc-noinstall-5.1.8-win32 modified Install.bat for Windows 7 / Vista 32-bit ODBC driver install
@ECHO OFF
REM #########################################################
REM
REM \brief Install myodbc.
REM
REM This exists for those working with the Windows source
REM distribution.
REM
REM Use this to copy the driver and supporting files
REM to the system directory and register the driver.
REM
REM \sa README.win
REM
REM #########################################################
SET installdir=none
IF EXIST %windir%\system\nul SET installdir=%windir%\system
IF EXIST %windir%\system32\nul SET installdir=%windir%\system32
IF EXIST %windir%\SysWOW64\nul SET installdir=%windir%\SysWOW64
IF %installdir%==none GOTO :doError5
IF EXIST %installdir%\myodbc-installer.exe GOTO :doError4
REM ****
REM * Find out the bin/lib directory, or use default
REM ****
SET libdir=lib
SET bindir=bin
IF EXIST lib\release\myodbc5.lib SET libdir=lib\release
IF EXIST lib\relwithdebinfo\myodbc5.lib SET libdir=lib\relwithdebinfo
IF EXIST bin\release\myodbc-installer.exe SET bindir=bin\release
IF EXIST bin\relwithdebinfo\myodbc-installer.exe SET bindir=bin\relwithdebinfo
REM ****
REM * Copying myodbc libraries and executables to install dir...
REM ****
ECHO Copying installation files
IF NOT EXIST %libdir%\myodbc5.lib GOTO :doError2
IF NOT EXIST %libdir%\myodbc5S.lib GOTO :doError2
IF NOT EXIST %bindir%\myodbc-installer.exe GOTO :doError2
copy %libdir%\myodbc5S.dll %installdir%
copy %libdir%\myodbc5S.lib %installdir%
copy %libdir%\myodbc5.dll %installdir%
copy %libdir%\myodbc5.lib %installdir%
copy %bindir%\myodbc-installer.exe %installdir%
REM ****
REM * Registering driver...
REM *
REM * We can do this with myodbc-installer.exe or the MS Windows ODBCConf.exe. It
REM * may be safer to use the ODBCConf.exe when we think about such things
REM * as 64bit windows.
REM ****
ECHO Registering driver
REM myodbc-installer -d -a -n "MySQL ODBC 5.1 Driver" -t "DRIVER=myodbc5.dll;SETUP=myodbc5S.dll"
%installdir%\odbcconf INSTALLDRIVER "MySQL ODBC 5.1 Driver|DRIVER=myodbc5.dll|SETUP=myodbc5S.dll"
ECHO "+-----------------------------------------------------+"
ECHO "| DONE |"
ECHO "+-----------------------------------------------------+"
ECHO "| |"
ECHO "| Hopefully things went well; the Connector/ODBC |"
ECHO "| files have been copied to the system directory |"
ECHO "| and the driver has been registered. |"
ECHO "| |"
ECHO "| Connector/ODBC is ready to use. |"
ECHO "| |"
ECHO "| The most common thing to do next is to go to the |"
ECHO "| Control Panel and find the ODBC Administrator - |"
ECHO "| then use it to create a Data Source Name (DSN) |"
ECHO "| so you (and your application) can connect to a |"
ECHO "| MySQL server. |"
ECHO "| |"
ECHO "+-----------------------------------------------------+"
EXIT /B 0
:doError2
ECHO "+-----------------------------------------------------+"
ECHO "| ERROR |"
ECHO "+-----------------------------------------------------+"
ECHO "| |"
ECHO "| Connector/ODBC not built. |"
ECHO "| |"
ECHO "+-----------------------------------------------------+"
PAUSE
EXIT /B 1
:doError4
ECHO "+-----------------------------------------------------+"
ECHO "| ERROR |"
ECHO "+-----------------------------------------------------+"
ECHO "| |"
ECHO "| Existing Connector/ODBC installed. Request ignored. |"
ECHO "| |"
ECHO "+-----------------------------------------------------+"
PAUSE
EXIT /B 1
:doError5
ECHO "+-----------------------------------------------------+"
ECHO "| ERROR |"
ECHO "+-----------------------------------------------------+"
ECHO "| |"
ECHO "| Can't find the Windows system directory |"
ECHO "| |"
ECHO "+-----------------------------------------------------+"
PAUSE
EXIT /B 1
Monday, August 23, 2010
Windows 98 Multi Menu
1. Edit MSDOS.sys
Attrib -h -r -s msdos.sys
edit msdos.sys
...
[Options]
Logo=0
BootMulti=0
BootGUI=0
...
Attrib +h +r +s msdos.sys
2. Edit CONFIG.sys
[MENU]
MENUITEM = LIN, Start RedHat Linux 6.1
MENUITEM = WIN, Start Windows 98
MENUITEM = DOS, Start MS-DOS 7.1
MENUDEFAULT=WIN,3
MENUCOLOR=7,0
[COMMON]
REM DEVICE=C:\WINDOWS\HIMEM.SYS
[LIN]
REM Now, This System is booting to Linux
[WIN]
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000
DEVICEHIGH C:\WINDOWS\BILING.SYS
[DOS]
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
files=60
buffers=30
DEVICEHIGH=C:\CTCM\CTCM.EXE
DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000
3. Edit Autoexec.bat
@ECHO OFF
REM LH C:\CDROM\MSCDEX.EXE /D:MSCD000
GOTO %CONFIG%
:LIN
c:\linux\loadlin.exe c:\linux\vmlinuz root=/dev/hda2 ro
GOTO END
:WIN
LOADHIGH C:\WINDOWS\COMMAND\NLSFUNC.EXE C:\WINDOWS\COUNTRY.SYS
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\MDIR;C:\UTIL;C:\UTIL\COMPRESS;
WIN
GOTO END
:DOS
PATH=C:\MDIR;C:\;C:\UTIL;C:\UTIL\COMPRESS;C:\VACCINE\V3neo;c:\vaccine\virobot;
LH V3RES
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET SOUND=C:\CTCM\SB16
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTCM=C:\CTCM
C:\CTCM\SB16\DIAGNOSE /S
C:\CTCM\SB16\AWEUTIL /S
C:\CTCM\SB16\MIXERSET /P /Q
LH C:\CDROM\MSCDEX.EXE /D:MSCD000
doskey
lh c:\mouse\mouse.exe
GOTO END
:END
Attrib -h -r -s msdos.sys
edit msdos.sys
...
[Options]
Logo=0
BootMulti=0
BootGUI=0
...
Attrib +h +r +s msdos.sys
2. Edit CONFIG.sys
[MENU]
MENUITEM = LIN, Start RedHat Linux 6.1
MENUITEM = WIN, Start Windows 98
MENUITEM = DOS, Start MS-DOS 7.1
MENUDEFAULT=WIN,3
MENUCOLOR=7,0
[COMMON]
REM DEVICE=C:\WINDOWS\HIMEM.SYS
[LIN]
REM Now, This System is booting to Linux
[WIN]
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000
DEVICEHIGH C:\WINDOWS\BILING.SYS
[DOS]
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
files=60
buffers=30
DEVICEHIGH=C:\CTCM\CTCM.EXE
DEVICEHIGH=C:\CDROM\GSCDROM.SYS /D:MSCD000
3. Edit Autoexec.bat
@ECHO OFF
REM LH C:\CDROM\MSCDEX.EXE /D:MSCD000
GOTO %CONFIG%
:LIN
c:\linux\loadlin.exe c:\linux\vmlinuz root=/dev/hda2 ro
GOTO END
:WIN
LOADHIGH C:\WINDOWS\COMMAND\NLSFUNC.EXE C:\WINDOWS\COUNTRY.SYS
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\MDIR;C:\UTIL;C:\UTIL\COMPRESS;
WIN
GOTO END
:DOS
PATH=C:\MDIR;C:\;C:\UTIL;C:\UTIL\COMPRESS;C:\VACCINE\V3neo;c:\vaccine\virobot;
LH V3RES
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET SOUND=C:\CTCM\SB16
SET MIDI=SYNTH:1 MAP:E MODE:0
SET CTCM=C:\CTCM
C:\CTCM\SB16\DIAGNOSE /S
C:\CTCM\SB16\AWEUTIL /S
C:\CTCM\SB16\MIXERSET /P /Q
LH C:\CDROM\MSCDEX.EXE /D:MSCD000
doskey
lh c:\mouse\mouse.exe
GOTO END
:END
Friday, July 30, 2010
Maximize Qt compile speed
unzip src package into somewhere (eg: c:\dev\qt\4.6.3src )
create target directory (eg: c:\dev\qt\4.6.3x64 )
copy mkspecs\ to target directory
C:\dev\Qt\4.6.3src>configure -prefix c:\dev\Qt\4.6.3x64 -opensource -native-gestures -nomake examples -nomake demos -no-qt3support -no-webkit -saveconfig testconfig
replace -nologo -Zm200 to -nologo -MP -Zm200 from Makefile.*
nmake sub-src
nmake sub-tools release
nmake install
create target directory (eg: c:\dev\qt\4.6.3x64 )
copy mkspecs\ to target directory
C:\dev\Qt\4.6.3src>configure -prefix c:\dev\Qt\4.6.3x64 -opensource -native-gestures -nomake examples -nomake demos -no-qt3support -no-webkit -saveconfig testconfig
replace -nologo -Zm200 to -nologo -MP -Zm200 from Makefile.*
nmake sub-src
nmake sub-tools release
nmake install
now it's ok to delete source directory
copy .qmake.cache to target directory
Saturday, November 07, 2009
MSVC and MinGW DLLs | MinGW
MSVC and MinGW DLLs | MinGW
Assume we have a testdll.h, testdll.c, and testmain.c. In the first case, we will compile testdll.c with MinGW, and let the MSVC-compiled testmain call it. You should use
gcc -shared -o testdll.dll testdll.c -Wl,--output-def,testdll.def,--out-implib,libtestdll.a
to produce the DLL and DEF files. MSVC cannot use the MinGW library, but since you have already the DEF file you may easily produce one by the Microsoft LIB tool:
lib /machine:i386 /def:testdll.def
Once you have testdll.lib, it is trivial to produce the executable with MSVC:
cl testmain.c testdll.lib
Now for MinGW programs calling an MSVC DLL. We have two methods. One way is to specify the LIB files directly on the command line after the main program. For example, after
cl /LD testdll.c
use
gcc -o testmain testmain.c testdll.lib
The other way is to produce the .a files for GCC. For __cdecl functions (in most cases), it is simple: you only need to apply the reimp tool from Anders Norlander (since his web site is no longer available, you may choose to download [this version|http://jrfonseca.dyndns.org/projects/gnu-win32/software/reimp/index.html] enhanced by Jose Fonseca):
reimp testdll.lib
gcc -o testmain testmain.c -L. -ltestdll
However, for __stdcall functions, the above method does not work. For MSVC will prefix an underscore to __stdcall functions while MinGW will not. The right way is to produce the DEF file using the pexports tool included in the mingw-utils package and filter off the first underscore by sed:
pexports testdll.dll | sed "s/^_//" > testdll.def
Then, when using dlltool to produce the import library, add `-U' to the command line:
dlltool -U -d testdll.def -l libtestdll.a
And now, you can proceed in the usual way:
gcc -o testmain testmain.c -L. -ltestdll
Hooray, we got it.
Assume we have a testdll.h, testdll.c, and testmain.c. In the first case, we will compile testdll.c with MinGW, and let the MSVC-compiled testmain call it. You should use
gcc -shared -o testdll.dll testdll.c -Wl,--output-def,testdll.def,--out-implib,libtestdll.a
to produce the DLL and DEF files. MSVC cannot use the MinGW library, but since you have already the DEF file you may easily produce one by the Microsoft LIB tool:
lib /machine:i386 /def:testdll.def
Once you have testdll.lib, it is trivial to produce the executable with MSVC:
cl testmain.c testdll.lib
Now for MinGW programs calling an MSVC DLL. We have two methods. One way is to specify the LIB files directly on the command line after the main program. For example, after
cl /LD testdll.c
use
gcc -o testmain testmain.c testdll.lib
The other way is to produce the .a files for GCC. For __cdecl functions (in most cases), it is simple: you only need to apply the reimp tool from Anders Norlander (since his web site is no longer available, you may choose to download [this version|http://jrfonseca.dyndns.org/projects/gnu-win32/software/reimp/index.html] enhanced by Jose Fonseca):
reimp testdll.lib
gcc -o testmain testmain.c -L. -ltestdll
However, for __stdcall functions, the above method does not work. For MSVC will prefix an underscore to __stdcall functions while MinGW will not. The right way is to produce the DEF file using the pexports tool included in the mingw-utils package and filter off the first underscore by sed:
pexports testdll.dll | sed "s/^_//" > testdll.def
Then, when using dlltool to produce the import library, add `-U' to the command line:
dlltool -U -d testdll.def -l libtestdll.a
And now, you can proceed in the usual way:
gcc -o testmain testmain.c -L. -ltestdll
Hooray, we got it.
Thursday, August 27, 2009
snoopy : 윈도우 7 홈 프리미엄 버전에 언어팩 설치하기
snoopy : 윈도우 7 홈 프리미엄 버전에 언어팩 설치하기: "dism /online /add-package /packagepath:d:\lp.cab"
제가 해보니까 언어팩 설치는 윈도우 상에서 가능한데 국가별 설정 변경은 윈도우 상에서 되지 않았습니다. 따라서 윈도우 7 DVD로 부팅을 해주셔야 합니다. 윈도우 7 DVD로 부팅하신 다음 처음 화면에서 Shift + F10 을 눌러서 명령 프롬프트를 띄웁니다. 그리고 다음과 같이 입력합니다.
dism /image:d: /set-skuintldefaults:ko-kr
다시 재부팅해서 윈도우에 진입을 해보면 키보드, 표시언어, 로케일을 포함한 모든 설정이 한글판으로 되어있을 것입니다. 따로 제어판에서 추가로 작업해주실 내용은 없습니다. 그런데 아마 부팅 화면 애니메이션은 그대로 영어로 남아있을 것입니다. 따라서 다시 명령 프롬프트를 관리자 권한으로 띄워주셔서 다음 2개의 명령어를 입력합니다.
bcdedit /set {bootmgr} locale ko-kr
bcdedit /set {current} locale ko-kr
그러면 이제 멀티부팅 화면이나 부팅 애니메이션이 한글판으로 잘 나올 것입니다.
제가 해보니까 언어팩 설치는 윈도우 상에서 가능한데 국가별 설정 변경은 윈도우 상에서 되지 않았습니다. 따라서 윈도우 7 DVD로 부팅을 해주셔야 합니다. 윈도우 7 DVD로 부팅하신 다음 처음 화면에서 Shift + F10 을 눌러서 명령 프롬프트를 띄웁니다. 그리고 다음과 같이 입력합니다.
dism /image:d: /set-skuintldefaults:ko-kr
다시 재부팅해서 윈도우에 진입을 해보면 키보드, 표시언어, 로케일을 포함한 모든 설정이 한글판으로 되어있을 것입니다. 따로 제어판에서 추가로 작업해주실 내용은 없습니다. 그런데 아마 부팅 화면 애니메이션은 그대로 영어로 남아있을 것입니다. 따라서 다시 명령 프롬프트를 관리자 권한으로 띄워주셔서 다음 2개의 명령어를 입력합니다.
bcdedit /set {bootmgr} locale ko-kr
bcdedit /set {current} locale ko-kr
그러면 이제 멀티부팅 화면이나 부팅 애니메이션이 한글판으로 잘 나올 것입니다.
Saturday, August 22, 2009
Silverglaze » Canon PowerShot S45 and Windows Vista
Silverglaze » Canon PowerShot S45 and Windows Vista
Canon PowerShot S45 and Windows Vista
Filed under: Useful Tech Tips — Jeffito @ 9:40 pm
250px-Canon_PowerShot_S45I discovered after I installed vista that Canon had not yet provided any vista drivers for the Canon PowerShot S45. I tried using a few other programs and nothing seemed to work to get my images off the camera. Luckily I have other laptops with XP and I have always just used these XP machines to get my images, but today I was stuck at home with just my vista laptop.
I was about to give up when I thought of something….. my iPod. I had bought an ipod camera connector to get my images off my camera when I am traveling. So I just hooked it up and transferred the pictures from the S45 to the iPod. I then plugged my iPod into my Windows Vista Laptop, opened windows explorer and then surfed to the DCIM folder on my iPod and the images were there for me to move to my hard drive… and eventually to Flickr.
Not a solution for everyone…. but it saved me from spending $40 on a USB flash card reader.
Canon PowerShot S45 and Windows Vista
Filed under: Useful Tech Tips — Jeffito @ 9:40 pm
250px-Canon_PowerShot_S45I discovered after I installed vista that Canon had not yet provided any vista drivers for the Canon PowerShot S45. I tried using a few other programs and nothing seemed to work to get my images off the camera. Luckily I have other laptops with XP and I have always just used these XP machines to get my images, but today I was stuck at home with just my vista laptop.
I was about to give up when I thought of something….. my iPod. I had bought an ipod camera connector to get my images off my camera when I am traveling. So I just hooked it up and transferred the pictures from the S45 to the iPod. I then plugged my iPod into my Windows Vista Laptop, opened windows explorer and then surfed to the DCIM folder on my iPod and the images were there for me to move to my hard drive… and eventually to Flickr.
Not a solution for everyone…. but it saved me from spending $40 on a USB flash card reader.
Tuesday, May 12, 2009
bv2.co.uk » Blog Archive » Visual Studio 2008 and CUDA
CUDA with Visual Studio 2008
bv2.co.uk » Blog Archive » Visual Studio 2008 and CUDA
Visual Studio 2008 and CUDA
As promised I received my Visual Studio 2008 on Friday from polyhedron and set about installing it on Saturday. This post will describe how to get VS 2008 to work with CUDA. I use CUDA 2.2 which is still under NDA so I wont be making any comments about its performance improvements today. Rather I will describe how to set up syntax highlighting, building and Intellisense.
Visual Studio is now distributed in DVD format which makes the installation process much easier due to not having to swop disks every few minutes. The installation went smoothly and quickly as I had the prerequisites (.net etc) installed already. I usually install software on my D drive and it didn’t have any complaints or issues with that either.
I already had the CUDA 2.2 SDK and toolkit installed along with the 185 drivers so I could move directly to configuring my Visual Studio to use CUDA:
Syntax highlighting: By default a .cu file is displayed all in black which makes editing rather tricky. NVidia supply a usertype.dat file which you will find under: “NVIDIA Corporation\NVIDIA CUDA SDK\doc\syntax_highlighting\visual_studio_8″ copy this file to: “\Program Files\Microsoft Visual Studio 9.0\Common7\IDE”. Now open up Visual Studio and navigate to: tools->options->text editor->file extension. In the extension box type “cu”, make sure you select “Microsoft Visual C++” in the drop down and not the default of “Microsoft Visual C#”. If you do select the C# one they syntax highlighting will still work but you wont see all the “__syncthreads()” etc highlighted.
Building: This is rather simple to configure, you can either specify the standard “nvcc ” command line for each .cu file in your project by right clicking ->properties->custom build. A better solution is to select a custom build rule for your project by selecting “project -> custom build rules -> find existing”. Again NVidia supply a rules file which you will find under the “\NVIDIA Corporation\NVIDIA CUDA SDK\common” directory. Select this build rule in your project properties and it makes it much easier to configure options for your building of CUDA projects.
Intellisense: Getting intellisense to work on .cu and .cuh files proved to be the most tricky step. I don’t actually use it very much as I try and keep my code fairly simple but its still nice to have when you can’t remember parameters etc. Logically I thought by adding .cu to the file extensions lists in the options wherever there was .c,.cpp etc listed and by the step used in enabling syntax highlighting it would just magically work. Sadly this was not the case. I did find a suggestion on the web mentioning a process that would enable it but it seemed rather clumsy to me. It involves writing your CUDA code in a .c file and then just as you hit compile a pre-build step copies the .c file to a .cu extension. To me it seemed odd that the Intellisense would work with .c,.cpp,.h etc and not with .cu where it is clearly just a different extension but essentially C code. As I ran out of option dialogs in Visual Studio I decided to look in the registry. After about 15 minutes I found what turned out to be the key. The “fix” is really simple: open the registry editor and navigate to “HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Languages\Language Services\C/C++” then go to the string entry “NCB Default C/C++ Extensions” and add “;.cu;.cuh” to the end of the list. Restart Visual Studio and Intellisense will work for your CUDA files. Keep in mind it doesnt know about CUDA specific extensions but will still help with all the normal C bits.
bv2.co.uk » Blog Archive » Visual Studio 2008 and CUDA
Visual Studio 2008 and CUDA
As promised I received my Visual Studio 2008 on Friday from polyhedron and set about installing it on Saturday. This post will describe how to get VS 2008 to work with CUDA. I use CUDA 2.2 which is still under NDA so I wont be making any comments about its performance improvements today. Rather I will describe how to set up syntax highlighting, building and Intellisense.
Visual Studio is now distributed in DVD format which makes the installation process much easier due to not having to swop disks every few minutes. The installation went smoothly and quickly as I had the prerequisites (.net etc) installed already. I usually install software on my D drive and it didn’t have any complaints or issues with that either.
I already had the CUDA 2.2 SDK and toolkit installed along with the 185 drivers so I could move directly to configuring my Visual Studio to use CUDA:
Syntax highlighting: By default a .cu file is displayed all in black which makes editing rather tricky. NVidia supply a usertype.dat file which you will find under: “NVIDIA Corporation\NVIDIA CUDA SDK\doc\syntax_highlighting\visual_studio_8″ copy this file to: “\Program Files\Microsoft Visual Studio 9.0\Common7\IDE”. Now open up Visual Studio and navigate to: tools->options->text editor->file extension. In the extension box type “cu”, make sure you select “Microsoft Visual C++” in the drop down and not the default of “Microsoft Visual C#”. If you do select the C# one they syntax highlighting will still work but you wont see all the “__syncthreads()” etc highlighted.
Building: This is rather simple to configure, you can either specify the standard “nvcc ” command line for each .cu file in your project by right clicking ->properties->custom build. A better solution is to select a custom build rule for your project by selecting “project -> custom build rules -> find existing”. Again NVidia supply a rules file which you will find under the “\NVIDIA Corporation\NVIDIA CUDA SDK\common” directory. Select this build rule in your project properties and it makes it much easier to configure options for your building of CUDA projects.
Intellisense: Getting intellisense to work on .cu and .cuh files proved to be the most tricky step. I don’t actually use it very much as I try and keep my code fairly simple but its still nice to have when you can’t remember parameters etc. Logically I thought by adding .cu to the file extensions lists in the options wherever there was .c,.cpp etc listed and by the step used in enabling syntax highlighting it would just magically work. Sadly this was not the case. I did find a suggestion on the web mentioning a process that would enable it but it seemed rather clumsy to me. It involves writing your CUDA code in a .c file and then just as you hit compile a pre-build step copies the .c file to a .cu extension. To me it seemed odd that the Intellisense would work with .c,.cpp,.h etc and not with .cu where it is clearly just a different extension but essentially C code. As I ran out of option dialogs in Visual Studio I decided to look in the registry. After about 15 minutes I found what turned out to be the key. The “fix” is really simple: open the registry editor and navigate to “HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Languages\Language Services\C/C++” then go to the string entry “NCB Default C/C++ Extensions” and add “;.cu;.cuh” to the end of the list. Restart Visual Studio and Intellisense will work for your CUDA files. Keep in mind it doesnt know about CUDA specific extensions but will still help with all the normal C bits.
Saturday, February 28, 2009
Sony PS3Eye Camera DirectShow Capture Source Filter *Update* v2.1.0.0130 « AlexP’s Weblog
Sony PS3Eye Camera DirectShow Capture Source Filter *Update* v2.1.0.0130 « AlexP’s Weblog: "Manual removal of PS3Eye.ax and PS3EyeLib.dll files:
- Close any program that are using PS3Eye camera.
- Press ‘WinKey’+R on your keyboard or alternatively go to Start->Run
- Type the following: regsvr32 /u “C:\Program Files\AlexP\PS3Eye.ax”
- You will see the following dialog box confirming successful un-registration of the PS3Eye.ax file."
- Close any program that are using PS3Eye camera.
- Press ‘WinKey’+R on your keyboard or alternatively go to Start->Run
- Type the following: regsvr32 /u “C:\Program Files\AlexP\PS3Eye.ax”
- You will see the following dialog box confirming successful un-registration of the PS3Eye.ax file."
Monday, November 24, 2008
웹초보의 Tech 2.1 :: 윈도우의 아쉬운 2%를 채워주는 프리웨어 Top 10
웹초보의 Tech 2.1 :: 윈도우의 아쉬운 2%를 채워주는 프리웨어 Top 10
윈도우를 사용하다 보면 "아.. 이런 기능이 있었으면 좋을텐데.." 하고 아쉬워 할 때가 있는데요. 그럴때 그 아쉬움을 채워주는 유틸리티를 만나게 되면 마치 보석을 캔 것 같은 뿌듯함과 함께 컴퓨터 사용이 한층 즐거워집니다.
그 런 의미에서 제가 나름대로 "아쉬운 2%를 채워주는 중독성 강한 유틸리티 10종"을 뽑아봤습니다. (순전히 제 사용 경험에서 나온 것이니까 더 좋은 유틸리티가 있으면 댓글로 추천해 주세요. 당연히 이 포스트에 적극적으로 반영하겠습니다. 그리고 소개하는 것들 중 더 자세한 사용법이 궁금하신 분들은 문의해 주시고요. 미흡하지만 요청한 건에 한하여 자세한 사용법을 올리도록 노력하겠습니다..^^)
윈도우를 사용하다 보면 "아.. 이런 기능이 있었으면 좋을텐데.." 하고 아쉬워 할 때가 있는데요. 그럴때 그 아쉬움을 채워주는 유틸리티를 만나게 되면 마치 보석을 캔 것 같은 뿌듯함과 함께 컴퓨터 사용이 한층 즐거워집니다.
그 런 의미에서 제가 나름대로 "아쉬운 2%를 채워주는 중독성 강한 유틸리티 10종"을 뽑아봤습니다. (순전히 제 사용 경험에서 나온 것이니까 더 좋은 유틸리티가 있으면 댓글로 추천해 주세요. 당연히 이 포스트에 적극적으로 반영하겠습니다. 그리고 소개하는 것들 중 더 자세한 사용법이 궁금하신 분들은 문의해 주시고요. 미흡하지만 요청한 건에 한하여 자세한 사용법을 올리도록 노력하겠습니다..^^)
엠파스 블로그 - 세상과 맞닿은 나의공간
엠파스 블로그 - 세상과 맞닿은 나의공간
관리자 계정 이름 바꾸기
관리자 계정(Administrator)은 지울 수 없다. 그러나 이 계정 이름을 바꿀 수는 있다.
해킹을 당할 수도 있기 때문에 관리자 계정 이름을 바꾸는 것이 좋다.
1. 관리자로 로그인한다.
2. 제어판 - 관리도구 - 컴퓨터 관리 - 로컬 사용자와 그룹 - 사용자 선택하고 왼쪽 화면에서 Administrator 에 오른쪽 마우스를 눌러 내 이름으로 바꾼다.
제어판 - 사용자 계정 - 내 이름 계정에서 암호를 만든다.
자동 로그인 끄기, 켜기
시작-실행(R) 창에 다음을 써넣고 확인을 누른다.
control userpasswords2
'사용자 이름과 암호를 입력해야 이 컴퓨터를 사용할 수 있음'에 v표시를 하면 암호를 묻고
v표시를 없애면 자동로그인 한다.
http://qaos.com/article.php?sid=86 이 글을 보고 썼다.
파코즈에서 펐다.
컴퓨터관리 > 로컬 사용자와 그룹 > 사용자
에서 고칠 수 있습니다.
그리고 administrator ID 변경은
gpedit.msc > 컴퓨터 구성 > 보안 설정 > 로컬 정책 > 보안 옵션
>계정 : administrator 계정 이름 바꾸기
다른 방법
시작 > 실행 > regedit > 확인하면
레지스터편집기가 나옵니다.
여기서
HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion으로 가시면
CurrentVersion 목록 중에
RegisteredOwner와 RegisteredOwner이란 게 있습니다.
RegisteredOrganization : 사용자 회사명
RegisteredOwner : 사용자 이름 입니다.
더블클릭하셔서 창이 하나 뜨면 거기서
값데이터를 사용하고 싶은 이름으로 바꾸시고 확인하시면 됩니다.
재부팅 하는 거 없구요..바로 바뀌고 사용가능합니다..
이상 허접팁이었습니다 ㅠ.ㅠ
관리자 계정 이름 바꾸기
관리자 계정(Administrator)은 지울 수 없다. 그러나 이 계정 이름을 바꿀 수는 있다.
해킹을 당할 수도 있기 때문에 관리자 계정 이름을 바꾸는 것이 좋다.
1. 관리자로 로그인한다.
2. 제어판 - 관리도구 - 컴퓨터 관리 - 로컬 사용자와 그룹 - 사용자 선택하고 왼쪽 화면에서 Administrator 에 오른쪽 마우스를 눌러 내 이름으로 바꾼다.
제어판 - 사용자 계정 - 내 이름 계정에서 암호를 만든다.
자동 로그인 끄기, 켜기
시작-실행(R) 창에 다음을 써넣고 확인을 누른다.
control userpasswords2
'사용자 이름과 암호를 입력해야 이 컴퓨터를 사용할 수 있음'에 v표시를 하면 암호를 묻고
v표시를 없애면 자동로그인 한다.
http://qaos.com/article.php?sid=86 이 글을 보고 썼다.
파코즈에서 펐다.
컴퓨터관리 > 로컬 사용자와 그룹 > 사용자
에서 고칠 수 있습니다.
그리고 administrator ID 변경은
gpedit.msc > 컴퓨터 구성 > 보안 설정 > 로컬 정책 > 보안 옵션
>계정 : administrator 계정 이름 바꾸기
다른 방법
시작 > 실행 > regedit > 확인하면
레지스터편집기가 나옵니다.
여기서
HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion으로 가시면
CurrentVersion 목록 중에
RegisteredOwner와 RegisteredOwner이란 게 있습니다.
RegisteredOrganization : 사용자 회사명
RegisteredOwner : 사용자 이름 입니다.
더블클릭하셔서 창이 하나 뜨면 거기서
값데이터를 사용하고 싶은 이름으로 바꾸시고 확인하시면 됩니다.
재부팅 하는 거 없구요..바로 바뀌고 사용가능합니다..
이상 허접팁이었습니다 ㅠ.ㅠ
Thursday, October 09, 2008
MS IT Academy Course
http://itastudentpass.microsoftelearning.com/
IT Academy Course: Database Developer
7698-SP2778-3898
IT Academy Course: Windows Developer
8515-SP5160-4914
IT Academy Course: Windows Server
8324-SP2274-5822
IT Academy Course: Web Developer
8291-SP2543-1195
IT Academy Course: Windows Client
6456-SP5347-9845
IT Academy Course: Database Developer
7698-SP2778-3898
IT Academy Course: Windows Developer
8515-SP5160-4914
IT Academy Course: Windows Server
8324-SP2274-5822
IT Academy Course: Web Developer
8291-SP2543-1195
IT Academy Course: Windows Client
6456-SP5347-9845
Thursday, June 26, 2008
Sunday, June 15, 2008
How to work with AHCI and RAID on GA-MA78GM-S2H for VISTA
First, it's true that its about twice faster to set two identical SATA disc as RAID 0, however limitation of AMD SB700 chipset, you can't enjoy RAID with Hot-Plug funcitionality.
1. Install AHCI mode by installation
- Change SATA mode to IDE
- After installation, follow below steps
| 1. | Exit all Windows-based programs. |
| 2. | Click Start, type regedit in the Start Search box, and then press ENTER. |
| 3. | If you receive the User Account Control dialog box, click Continue. |
| 4. | Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci |
| 5. | In the right pane, right-click Start in the Name column, and then click Modify. |
| 6. | In the Value data box, type 0, and then click OK. |
| 7. | On the File menu, click Exit to close Registry Editor. |
from http://support.microsoft.com/kb/922976
2. Install RAID mode by installation
- Change SATA mode to RAID
- Setup RAID set on POST
- Install driver from installation screen (Can use USB as well)
- Now, RAID drives are shown to installation path.
3. Uninstall RAID mode and bring system back to AHCI
- Now, you really want to use Hot-Plug feature on your system, you need to complete PC backup on your system disk first
- It's always good idea to keep system partition as small as possible and extend it only when is needed
- Use Windows Backup Centre to make back up of your system partiton to outside of RAID drives
- Change SATA mode to AHCI
- Boot from Windows Installation disc
- Choose Recovery Mode, the drives are already on the list, since it's not RAID
- Recover system
- Not finished yet, although it's capable of run the system, it's on existing RAID driver and not supporting Hot-Plug feature just yet
- Remove AMD RAID driver from Device Manager, also remove AMD IDE driver as well. Should choose option to delete files as well.
- Try to reboot, it wouldn't because it doesn't have any driver to running the drives, boot from Windows Installation Disc
- Choose Recovery Mode, Windows automatically detects there were problems, and try to install AHCI drivers from installation disc
- Boot to Safe mode for sure it installs all new IDE channels
- Now it's good to go, try to connect SATA device on SATA channel 4 and 5 to check Hot-Plug feature is working
4. Uninstall AHCI and bring system back to RAID
- Never tried yet, however it may possible to follow same step as above, because windows Recovery Mode should needs corect RAID dirver to see RAID drives
Subscribe to:
Posts (Atom)