(adsbygoogle = window.adsbygoogle || []).push({}); O_o :: 'Computer' 카테고리의 글 목록

'Computer'에 해당되는 글 39건

  1. 2009.03.17 원격 데스크탑 해상도를 마음대로 설정하기
  2. 2009.03.17 바이러스가 의심되는 프로세스가 있을때.
  3. 2009.03.12 Creating a Self-Signed SSL Certificate without a mess of makecert.exe (using SSL Diagnostics Tool)
  4. 2008.12.14 vmware에 Mac 설치시 네트워크 드라이버
  5. 2008.12.14 iPhone Toolchain 1
  6. 2008.11.17 IIS 4G보다 큰 파일 다운로드 안될때
  7. 2008.11.16 Installing on telos-family mote (telosa, telosb)
  8. 2008.11.16 TinyOS RPM 인스톨시.
  9. 2008.11.10 TinyOS 2.x 설치 (msp430 기준) 2
  10. 2008.11.05 Remote Access VPN Connections

원격 데스크탑 해상도를 마음대로 설정하기

|

 

원격 데스크탑은 몇 가지 기본 해상도를 제공하고 있으나, 다른 해상도가 필요할 때도 있다.

 

1. 우선 원격 데스크톱 연결 메뉴를 통하여 원격 컴퓨터 정보를 입력하여 접속이 될 수 있도록 설정한다.

2. 다른 이름으로 저장을 눌러 연결 설정을 저장한다.

image

 

3. UNICODE 편집이 가능한 편집기를 이용하여 저장된 *.rdp 화일을 연다. (없으면 MS-WORD를 이용한다)

4. 해상도 부분을 마음대로 수정 후 저장..

desktopwidth:i:1200
desktopheight:i:480

image

5. 해당 연결 설정 아이콘을 누르면 설정한 해상도로 표시된다.

 image

[1200x480 해상도 설정화면]

And

바이러스가 의심되는 프로세스가 있을때.

|

 

우선 Ctrl+F 로 아래 해당하는 화일인지 검색해 본다.

해당하는 경우 http://www.liutilities.com/products/wintaskspro/processlibrary 사이트에서 더 자세한 내용을 확인해 볼 수 있으나, 아닌 경우는 한번 의심해 보길.

 

accwiz.exe
act.exe
activation.exe
actmovie.exe
ad-aware.exe
adobe gamma loader.exe
adsl autoconnect.exe
advchk.exe
ad-watch.exe
aexnsagent.exe
agentsvr.exe
airplus.exe
alaunch.exe
alcfdrtm.exe
alcrmv.exe
alcupd.exe
alcxmntr.exe
alerter
alg.exe
almon.exe
alunotify.exe
am32.exe
amd_dc_opt.exe
amgrsrvc.exe
amvo.exe
anbmserv.exe
aoldial.exe
aolspscheduler.exe
apcsystray.exe
apntex.exe
appmgr.exe
appsvc32.exe
arservice.exe
ashdisp.exe
ashmaisv.exe
ashwebsv.exe
aspnet_state.exe
aspnet_wp.exe
asusprob.exe
aswupdsv.exe
atkkbservice.exe
audiosrv.dll
autochk.exe
autodown.exe
autoruns.exe
autoupdate.exe
avengine.exe
avgamsvr.exe
avgas.exe
avgcc.exe
avgemc.exe
avginet.exe
avgupsvc.exe
avgw.exe
avp.exe
avpm.exe
avsynmgr.exe
awc.exe
awrem32.exe
backitup.exe
bacstray.exe
bdmcon.exe
bdoesrv.exe
bdss.exe
bdswitch.exe
benetns.exe
bengine.exe
beremote.exe
bkupexec.exe
blackd.exe
blastcln.exe
bmmlref.exe
bootcfg.exe
brctrcen.exe
brmfrsmg.exe
brss01a.exe
brsvc01a.exe
bsclip.exe
cabarc.exe
cacls.exe
ca.exe
capfasem.exe
carpserv.exe
cavasm.exe
cavrid.exe
cavtray.exe
cbinterface.exe
ccap.exe
ccapp.exe
ccevtmgr.exe
cclaw.exe
ccleaner.exe
ccmexec.exe
ccpwdsvc.exe
ccregvfy.exe
ccsvchst.exe
ceepwrsvc.exe
center.exe
cepmtray.exe
cfgwiz.exe
cfsvcs.exe
cfxfer.exe
charmap.exe
chdaudpropshortcut.exe
checker.exe
cidaemon.exe
cisvc.exe
cleanmgr.exe
cli.exe
clipsrv.exe
clisvcl.exe
cmain.exe
cmd.exe
cmdl32.exe
cmdow.exe
cmicnfg.cpl
cnxdsltb.exe
cocimanager.exe
comhost.exe
command.exe
comp.exe
comres.dll
conime.exe
control.exe
convert.exe
cpd.exe
cpf.exe
cpqeadm.exe
csrss.exe
cssauth.exe
ctcms.exe
ctcmsgo.exe
ctdetect.exe
ctfmon.exe
cthelper.exe
ctrlvol.exe
ctsvolfe.exe
cygrunsrv.exe
dadapp.exe
dadtray.exe
damon.exe
davcdata.exe
ddhelp.exe
defrag.exe
delay.exe
dfrgfat.exe
dfrgntfs.exe
dfssvc.exe
dialer.exe
diskpart.exe
diskperf.exe
dla.exe
dlbkbmgr.exe
dlbkbmon.exe
dllhost.exe
dmadmin.exe
dmremote.exe
dnscst.exe
dns.exe
dos4gw.exe
doscan.exe
doskey.exe
dotnetfx.exe
dragdiag.exe
drmupgds.exe
drwtsn32.exe
dsagent
dsagnt.exe
dsentry.exe
dslagent.exe
dslstat.exe
dsncservice.exe
dtsrvc.exe
dumeter.exe
dummy.exe
dumprep.exe
dvdlauncher.exe
dwm.exe
dwtrig20.exe
dwwin.exe
eabservr.exe
edonkey.exe
ehmsas.exe
ehrec.exe
ehshell.exe
ekrn.exe
elbycheck.exe
em_exec.exe
esb.exe
evteng.exe
exmgmt.exe
explorer.exe
extrac32.exe
extract.exe
ezejmnap.exe
fameh32.exe
fast.exe
fch32.exe
find.exe
finger.exe
fingerprint compiler.exe
fixmapi.exe
fldrclnr.dll
floater.exe
fmctrl.exe
fnrb32.exe
fpassist.exe
frameworkservice.exe
frameworkservic.exe
freeram xp pro.exe
fsav32.exe
fsbwsys.exe
fsdfwd.exe
fsgk32.exe
fsgk32st.exe
fsm32.exe
fsma32.exe
fsmb32.exe
fspex.exe
fsqh.exe
fsquirt.exe
fsrremos.exe
fssm32.exe
ftp.exe
fuj02e3.exe
fwcagent.exe
fwcmgmt.exe
fwsrv.exe
g2mstart.exe
gbpoll.exe
gcasdtserv.exe
gcasserv.exe
gcastdtserv.exe
gdi.exe
getflash.exe
ghostexp.exe
ghosts~2.exe
ghoststartservice.exe
gpresult.exe
gpupdate.exe
grpconv.exe
gsicon.exe
guard.exe
hamachi.exe
hdashcut.exe
hdaudprop.dll
hdaudpropshortcut.exe
hddhealth.exe
helpctr.exe
helper.exe
helphost.exe
hidfind.exe
hidserv.exe
hkcmd.exe
hotkey.exe
hotkeyscmds.exe
hpadvisor.exe
hpbootop.exe
hpobnz08.exe
hpqwmi.exe
hpsysdrv.exe
hpztsb04.exe
hpztsb05.exe
hpztsb06.exe
hpztsb07.exe
hpztsb08.exe
hpztsb09.exe
hpztsb10.exe
hpztsb11.exe
hwapi.exe
hwinfo.exe
hypertrm.exe
i8kfangui.exe
iaanotif.exe
iao.exe
ibmprc.exe
icwconn1.exe
idriver.exe
idrivert.exe
ie4uinit.exe
ie5setup.exe
ie6setup.exe
ieuser.exe
iexplore.exe
igfxext.exe
igfxsrvc.dll
ikernel.exe
imagedrive.exe
imapi.exe
imekrmig.exe
imjpmig8.1
imonnt.exe
incdsrv.exe
incmail.exe
inetinfo.exe
inetwiz.exe
inicio.exe
inorpc.exe
inort.exe
inotask.exe
instmsiw.exe
intelmem.exe
internat.exe
iolodmvsvc.exe
ipccheck.exe
iptray.exe
ireike.exe
isafe.exe
isbmgr.exe
isignup.exe
ismserv.exe
issch.exe
isstart.exe
issvc.exe
isuninst.exe
j2gdllcmd.exe
jusched.exe
jushed.exe
jv16pt.exe
kav.exe
kavmm.exe
kavsvc.exe
kb891711.exe
kem.exe
kernel32.dll
kernelfaultcheck
keyboardsurrogate.exe
khooker.exe
klswd.exe
kpf4gui.exe
label.exe
launch32.exe
lcdmon.exe
lcfd.exe
lights.exe
linksysagent.exe
livesrv.exe
livesystem.exe
lmiguardian.exe
localcooling.exe
locator.exe
logitechdesktopmessenger.exe
logonui.exe
lsass.exe
lsm.exe
luall.exe
lucoms~1.exe
lucomserver.exe
lucoms.exe
lxcrmon.exe
lxrjd31s.exe
mace.exe
mad.exe
magickbd.exe
mainserv.exe
managementagentnt.exe
mantispm.exe
mapisp32.exe
maxbackserviceint.exe
maximizer_startup.exe
mbm5.exe
mcafeedatabackup.exe
mcagent.exe
mcappins.exe
mcdetect.exe
mcinfo.exe
mcmnhdlr.exe
mcmscsvc.exe
mcnasvc.exe
mcods.exe
mcproxy.exe
mcrdsvc.exe
mcscript_inuse.exe
mctskshd.exe
mcuimgr.exe
mcupdmgr.exe
mcvsescn.exe
mcw.exe
mdm.exe
mghtml.exe
migwiz.exe
mmc.exe
mmkeybd.exe
mnmsrvc.exe
monitor.exe
monsvcnt.exe
mouse32a.exe
moviemk.exe
mozilla.exe
mpapi3s.exe
mpbtn.exe
mpcmdrun.exe
mpfagent.exe
mpfservice.exe
mprexe.exe
mpssvc.exe
mqrt.dll
mqtgsvc.exe
mrt.exe
msacui.exe
msascui.exe
msconfig.exe
mscorsvw.exe
msd.exe
msdtc.exe
msg.exe
msgsrv32.exe
mshta.exe
msiexec.exe
msinfo32.exe
mskagent.exe
msksrver.exe
msmpeng.exe
msnmsgr.exe
msoobe.exe
mspy2002
mssearch.exe
msswchx.exe
mstask.exe
mstinit.exe
mstsc.exe
mtx.exe
mwaser.exe
mxoaldr.exe
mxtask.exe
naprdmgr.exe
narrator.exe
navapsvc.exe
navw32.exe
nbj.exe
nddeagnt.exe
ndisuio.sys
neotrace.exe
net1.exe
netdde.exe
net.exe
netstat.exe
netsvcs
ngctw32.exe
ngserver.exe
nip.exe
nisum.exe
njeeves.exe
nmain.exe
nod32.exe
nod32krn.exe
nod32kui.exe
notify.exe
npfmntor.exe
nprotect.exe
nscsrvce.exe
nslookup.exe
nsmdtr.exe
ntfrs.exe
ntkrpamp.exe
ntoskrnl.exe
ntrayfw.exe
ntrtscan.exe
ntsd.exe
ntvdm.exe
nutsrv4.exe
nvcoas.exe
nvstartup
nwereboot
oasclnt.exe
ochealthmon.exe
ofcdog.exe
ofcpfwsvc.exe
omniserv.exe
onetouch.exe
oodag.exe
opera.exe
opscan.exe
osa9.exe
oscheck.exe
osk.exe
packager.exe
padexe.exe
patch.exe
pavfnsvr.exe
pavprsrv.exe
pavsrv51.exe
pccguide.exe
pcclient.exe
pccnt.exe
pccntmon.exe
pccntupd.exe
pcctlcom.exe
pcdsmartmonitor.exe
pcfmgr.exe
pchschd.exe
pcs_agnt.exe
pcscan.exe
pcscnsrv.exe
pdsched.exe
pg_ctl.exe
phime2002a
ping.exe
pop3trap.exe
postgres.exe
powerdvd.exe
ppped.exe
pqibrowser.exe
pqv2isvc.exe
presentationfontcache.exe
prfldsvc.exe
print.exe
prismsta.exe
prismsvr.exe
processquicklink2admin.exe
processquicklink2.exe
processquicklink.exe
processscanner.exe
procexp.exe
progman.exe
psimsvc.exe
pskmssvc.exe
pstat.exe
pstores.exe
pthosttr.exe
pview.exe
pvlsvr.exe
qaccess.exe
qconsole.exe
qoeloader.exe
quickcam10.exe
quickpar.exe
qwinsta.exe
raid_tool.exe
rapapp.exe
rar.exe
rasautou.exe
rasman.exe
ravmon.exe
razerhid.exe
rdpclip.exe
rdshost.exe
regedit.exe
reg.exe
regini.exe
registrybooster.exe
regshave.exe
regsvc.exe
regsvr32.exe
restart.exe
retrorun.exe
routernt.exe
rpcss.exe
rps.exe
rrpcsb.exe
rsm.exe
rsmui.exe
rstrui.exe
rsvp.exe
rthdcpl.exe
rundll32.exe
rundll.exe
runonce.exe
runservice.exe
s3hotkey.exe
sapisvr.exe
savadminservice.exe
savedump.exe
savroam.exe
savscan.exe
savservice.exe
scan32.exe
scandisk.exe
scanningprocess.exe
scanpst.exe
scanregw.exe
scardsvr.exe
sccertprop
sched.exe
schedhlp.exe
schedul2.exe
scm.exe
service.exe
services.exe
sessmgr.exe
seticon.exe
setup50.exe
sgbhp.exe
sgmain.exe
shadow.exe
shotkey.exe
shutdown.exe
shwiconem.exe
sigverif.exe
siteadv.exe
skeys.exe
skytel.exe
slrundll.exe
slsvc.exe
smagent.exe
smax4.exe
smlogsvc.exe
smss.exe
sndmon.exe
sndsrvc.exe
sndvol32.exe
snmp.exe
snmptrap.exe
soundtrax.exe
spamsub.exe
spamsubtract.exe
spcustom.dll
spdwnwxp.exe
spmgr.exe
spool32.exe
spoolss.exe
spoolsv.exe
sprestrt.exe
sp_rsser.exe
sptip.dll
spuninst.exe
spupdsvc.exe
spyeraser.exe
spysub.exe
spysweeper.exe
sqlmaint.exe
sqlmangr.exe
srvany.exe
srvload.exe
ssdpsrv.exe
sshd.exe
ssonsvr.exe
stacmon.exe
starwindservice.exe
statemgr.exe
stillimagemonitor
stimon.exe
stinger.exe
stmgr.exe
support.exe
swagent.exe
swdoctor.exe
sweepsrv.sys
switcher.exe
swupdtmr.exe
sxgtkbar.exe
symsport.exe
symwsc.exe
syntpenh.exe
sysfader.exe
sysmon.exe
sysocmgr.exe
system
system idle process
systray.exe
tabbtnu.exe
tablet.exe
tabtip.exe
tapisrv.exe
taskeng.exe
taskkill.exe
tasklist.exe
taskman.exe
taskmgr.exe
taskmonitor
taskswitch.exe
tbmon.exe
tcpsvcs.exe
tcsd_win32.exe
tcserver.exe
termsrv.exe
tgcmd.exe
timezone.exe
tintsetp.exe
tiservicemonitor.exe
tlntsvr.exe
tmlisten.exe
tmpfw.exe
tmproxy.exe
tnbutil.exe
toshkcw.exe
tpkmapap.exe
tpkmapmn.exe
tponscr.exe
tpscrex.exe
tray.exe
trueimagemonitor.exe
trustedinstaller.exe
tsc.exe
tscon.exe
tsshutdn.exe
type32.exe
typeperf.exe
uaservice7.exe
ucstartup.exe
ulcdrsvr.exe
unins000.exe
uninst.exe
unlockerassistant.exe
unsecapp.exe
updspapi.dll
uphclean.exe
ups.exe
urllstck.exe
userinit.exe
usrprmpt.exe
usrshuta.exe
utilman.exe
uwdf.exe
uzqkst.exe
vaderetro_oe.exe
vbc.exe
vcsw.exe
verclsid.exe
verifier.exe
vetmsg.exe
viewmgr.exe
vm305_sti.exe
vmware-ufad.exe
vpc32.exe
vsnpstd.exe
vssadmin.exe
vsserv.exe
vssvc.exe
vstskmgr.exe
vttimer.exe
vttrayp.exe
vxtaskbarmgr.exe
vzfw.exe
watchdog.exe
waveedit.exe
wbload.exe
wdbtnmgr.exe
wdsvc.exe
webproxy.exe
webreg.exe
webscanx.exe
wercon.exe
wgatray.exe
winaw32.exe
windowsxp-kb905474-enu-x86.exe
wininit.exe
winload.exe
winlog.exe
winlogon.exe
winmgmt.exe
winoldap.exe
winpatrol.exe
winrar.exe
wins.exe
winss.exe
winssnotify.exe
winsync.exe
winzip32.exe
wisptis.exe
wjview.exe
wkdetect.exe
wlancfg5.exe
wlballoon
wltray.exe
wmdc.exe
wmiadap.exe
wmiapsrv.exe
wmiexe.exe
wmiprvse.exe
wmipvse.exe
wowdeb.exe
wowexec.exe
wpabaln.exe
wpctrl.exe
wros.exe
wrsssdk.exe
wscntfy.exe
wtsrv.exe
wuaclt.exe
wuauclt1.exe
wuauclt.exe
wuaudt.exe
wucrtupd.exe
wupdmgr.exe
x10nets.exe
x1exec.exe
xpsp2res.dll
zanda.exe
zcast.exe
zlclient.exe
zonealarm.exe
00thotkey.exe
1xconfig.exe
3dm2.exe
3dxsrv.exe
[system process]

And

Creating a Self-Signed SSL Certificate without a mess of makecert.exe (using SSL Diagnostics Tool)

|
Creating a Self-Signed SSL Certificate without a mess of makecert.exe (using SSL Diagnostics Tool)

Introduction:
So you have a server and you need to implement SSL to allow secure (https) communication. What choices do you have? You can buy a certificate from certification authority or you can issue a Self-Signed certificate to yourself. The difference is that your browser "knows" it can trust the certificates from the authorities (it has it installed). But when the browser encounters the https connection with a server with the self-signed certificate, the user is presented with a message like this:

Thus, self-signed certificates are OK for test and development web sites, but generally not OK for public websites.
This article will show you the simplest ways to create a Self-Signed SSL Certificate.

Here are your options. (Or just go to the Best Solution )

Solution 1 (quite long, but recommended by Microsoft)
Setting Up SSL Using IIS and Certificate Server

MS recommends that you get the certificate from the certificate server. This means that you have to have an access to Window 2000 or Windows 2003 server with "Certification Services" installed. You use IIS MMC to generate request to this server. Then using browser you submit this request to the server. Then, when somebody at that server approves the request, you will get back a certificate.
See details at http://support.microsoft.com/default.aspx?kbid=299525

Solution 2 (fast, but sometimes could be tricky)
Creating Self-Signed SSL Certificates using makecert.exe It is a quite simple solution. The only problem is that sometimes it just doesn't work, and it's hard to determine what is wrong. The makecert.exe comes with VS.NET. It you don't have .NET Framework 1.1 installed, the makecert might be outdated. You can download a newer version from http://download.microsoft.com/download/platformsdk/Update/5.131.3617.0/NT45XP/EN-US/makecert.exe
Just replace yourservername with the computer name of your PC and run:
makecert -r -pe -n "CN=yourservername" -b 01/01/2000 -e 01/01/2050 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12

Then go to the IIS "Web Site Properties", "Directory Security", "Server Certificate...", "Assign an existing certificate" and select the new certificate from the list.
It works? Fine! No? Go to the Best Solution

Solution 3 (OK for not-technical users)
Download a test certificate from certification authorities The certificate companies like VeriSign and Thawte issue test certificates, but they expire after 90 days or so, and the process of getting it could be quite tedious.

Solution 4 (The Best and Recommended)
Create a Self-Signed Certificate using SSL Diagnostics Tool

Avoid all this pain with a nice tool from Microsoft: SSL Diagnostics . Download setup.exe (2112 KB) from here: http://www.microsoft.com/downloads/details.aspx?familyid=CABEA1D0-5A10-41BC-83D4-06C814265282&displaylang=en

Install it and run. In the main window of SSL Diagnostics, right-click the Web site level (shown by [W3SVC/<site number>]), and then click Create New Certificate.


That is it. You are done. Don't forget to explore other capabilities of this nice tool.

And

vmware에 Mac 설치시 네트워크 드라이버

|

vmware에 Mac 설치시 네트워크 드라이버
분류:
Link#1: http://video.paulooi.com/Maxxuss-AMDPCNET-v1.0_1043.zip
Link#2: http://wiki.osx86project.org/wiki/index.php/Vmware_how_to

And

iPhone Toolchain

|

 

Build iPhone Toolchain on Mac OS X Tiger

This is a brief description about how to install iPhone toolchain on Mac OS X Tiger.

Needed Packages

1. llvm source
2. iphone-dev source
3. iphone-filesystem

Put all the packages in your $HOME folder.

How To Build

Make sure you’re running Mac OS X 10.4, and have installed Xcode development environment.

1. Extract packages
$ cd ~
$ tar xjvf llvm-svn.tar.bz2
$ tar xjvf iphone-dev.tar.bz2
$ cd /usr/local
$ sudo tar xjvf ~/iphone-filesystem.tar.bz2
$ sudo mkdir -p /usr/local/arm-apple-darwin
$ LLVMOBJDIR=~/llvm-svn
$ HEAVENLY=/usr/local/iphone-filesystem
2. Build LLVM
$ cd ~/llvm-svn
$ ./configure --enable-optimized
$ make ENABLE_OPTIMIZED=1
$ sudo make install
3. Build odcctools
$ mkdir -p ~/iphone-dev/build/odcctools
$ cd ~/iphone-dev/build/odcctools
$ ../../odcctools/configure --target=arm-apple-darwin --disable-ld64
$ make
$ sudo make install
4. Install headers
$ cd ~/iphone-dev/include
$ ./configure --with-macosx-sdk=/Developer/SDKs/MacOSX10.4u.sdk
$ sudo bash install-headers.sh
5. Install csu (binary)
$ mkdir -p ~/iphone-dev/build/csu
$ cd ~/iphone-dev/build/csu
$ ../../csu/configure --host=arm-apple-darwin
$ sudo make install
6. Build LLVM-GCC
$ mkdir -p ~/iphone-dev/build/llvm-gcc-4.0-iphone
$ cd ~/iphone-dev/build/llvm-gcc-4.0-iphone
$ ../../llvm-gcc-4.0-iphone/configure --enable-llvm=`llvm-config --objc-root` \
--enable-languages=c,c++,objc,obj-c++ --target=arm-apple-darwin --enable-sjlj-exceptions \
--with-heavenly=$HEAVENLY --with-as=/usr/local/bin/arm-apple-darwin-as \
--with-ld=/usr/local/bin/arm-apple-darwin-ld
$ make LLVM_VERSION_INFO=2.0-svn-iphone-dev-0.3-svn
$ sudo make install

Done.

Build iPhone Toolchain on Mac OS X Leopard

HOWTO build the toolchain for 1.1.1 on Leopard by drudge with pure ownage by lupinglade

Ensure that you have a copy of bison and flex installed on your system. All major systems should have these tools installed or available in package management systems.

$ bison --version
GNU Bison version 1.28
$ flex --version
flex version 2.5.4

Check out a copy of LLVM SVN, and build a release build (as opposed to a debug one). Currently, due to Issue 70, we are limited to revision 42498.

$ svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm-svn -r 42498
$ pushd llvm-svn
$ ./configure --enable-optimized
$ make ENABLE_OPTIMIZED=1
$ sudo make install
$ LLVMOBJDIR=`pwd`
$ popd

Check out a copy of the iphone-dev SVN repository.

$ svn checkout http://iphone-dev.googlecode.com/svn/trunk/ iphone-dev
pushd iphone-dev

Make a directory to hold the toolchain.

$ sudo mkdir /usr/local/arm-apple-darwin

Build odcctools.

$ mkdir -p build/odcctools
$ pushd build/odcctools
../../odcctools/configure --target=arm-apple-darwin --disable-ld64
export INCPRIVEXT="-isysroot /Developer/SDKs/MacOSX10.4u.sdk"
$ make
$ sudo make install
$ popd

Get a copy of the iPhone root filesystem. This is usually obtained by decrypting and extracting the iPhone restore software using these tools, but there are many other methods to obtain this, including simply using scp to download all the files from the iPhone over Wi-Fi. I would use the method describled here: http://www.touchdev.net/wiki/Jailbreak_Guide to get the dmg.

To unpack the root filesystem, mount the dmg, open terminal and run

$ sudo mkdir /usr/local/share/iphone-filesystem
$ sudo cp -Rp /Volumes/Snowbird3A110a.N45Bundle/* /usr/local/share/iphone-filesystem/

Now, set the environment variable $HEAVENLY to its path:

$ HEAVENLY=/usr/local/share/iphone-filesystem

Patch the system headers

$ pushd include
$ ./configure --with-macosx-sdk=/Developer/SDKs/MacOSX10.4u.sdk
$ sudo bash install-headers.sh
$ popd

Install csu, which includes crt1.o, dylib1.o, and bundle1.o. Don’t rebuild them from source, as this requires a working cross-GCC, which you don’t have yet (and the build-from-source process for csu is broken right now anyway). Binaries are provided for this reason.

$ mkdir -p build/csu
$ pushd build/csu
$ ../../csu/configure --host=arm-apple-darwin
$ sudo make install
$ popd

Configure and make LLVM-GCC. Make sure that $LLVMOBJDIR and $HEAVENLY are set per the instructions above.

$ mv llvm-gcc-4.0-iphone/configure llvm-gcc-4.0-iphone/configure.old
$ sed 's/^FLAGS_FOR_TARGET=$/FLAGS_FOR_TARGET=${FLAGS_FOR_TARGET-}/g' \
 llvm-gcc-4.0-iphone/configure.old > llvm-gcc-4.0-iphone/configure
$ sudo ln -s /usr/local/arm-apple-darwin/lib/crt1.o \
 /usr/local/arm-apple-darwin/lib/crt1.10.5.o
$ mkdir -p build/llvm-gcc-4.0-iphone
$ pushd build/llvm-gcc-4.0-iphone
$ export FLAGS_FOR_TARGET="-mmacosx-version-min=10.1"
 ../../llvm-gcc-4.0-iphone/configure --enable-llvm=`llvm-config --obj-root` \
 --enable-languages=c,c++,objc,obj-c++ --target=arm-apple-darwin --enable-sjlj-exceptions \
 --with-heavenly=$HEAVENLY --with-as=/usr/local/bin/arm-apple-darwin-as \
 --with-ld=/usr/local/bin/arm-apple-darwin-ld
$ make LLVM_VERSION_INFO=2.0-svn-iphone-dev-0.3-svn
$ sudo make install
$ popd
$ popd

You’re done. Have fun!

Build iPhone Toolchain on Windows XP

This guide and binary installation server is provided by David Supuran .
If you have any questions, comments, or suggestions please visit irc.osx86.hu #iphone or email me at Darken@iPhoneGameover.com

Requirements

/Developer/SDKs/MacOSX10.4u.sdk

To obtain this directory it is recommended that you download Xcode 2.5 Developer Tools (Disk Image) (902.9 MB as of 30 Oct 2007).

Once you have downloaded the disk image, you will need additional software to open and extract it such as PowerISO, then extract the following file:

\Packages\Packages\MacOSX10.4.Universal.pkg\Contents\Archive.pax.gz

Note: It has been reported that UltraISO and MacDrive do not work for extracting this package.
This archive provides the necessary header files which will later be installed for the compiler to use.

Note: Due to Apple’s strict redistribution license the files required from this archive could not be included in the installer, so you are required to agree to the terms and licenses under your ADC account and download the full disk image.

iPhone/iTouch root filesystem

The easiest way to obtain the root filesystem is to have a wireless network and OpenSSH installed. If you have this please skip this part as the post-installation will walk you through obtaining the files automatically. You may alternatively decrypt a firmware ipsw manually and place the extracted filesystem in /usr/local/arm-apple-darwin/filesystem after Cygwin is installed.

Installation

Download and run the Cygwin Setup. It is recommended you use the default settings and click Next until you get to the following window:
Cygwin Setup Step 6
Type in the User URL: http://www.iphonegameover.com/cygwin, then click Add.

Once you see the URL added and highlighted in the Available Download Sites list click Next.
Cygwin Setup Step 7
All the software is selected for you; it is recommended you use the default settings and click Next, then follow the on-screen instructions to finish the setup.
Cygwin Setup Step 8
Click the Start button and select All Programs -> Cygwin -> Cygwin Bash Shell and you will see the following window:
Cygwin Setup Step 9
Place the Archive.pax.gz file in your Cygwin home directory that you obtained earlier from the Xcode 2.5 Developer Tools (Disk Image). Example home directory: C:\cygwin\home\Administrator

When asked ‘Do you wish to connect to your device and download the required files?‘ Press y for Yes.

Type in the IP address of your iPhone / iTouch device on the next prompt that says ‘Please enter the remote IP address of your device:‘.

*Note: If you do not know the IP address of your device go to Settings -> Wi-Fi and Click the blue arrow to the right of your wireless network you are currently connected to which is marked with a check on the left.

If SSH asks you ‘Are you sure you want to continue connecting (yes/no)?‘ Type yes.
Cygwin Setup Step 10
NOTE: SSH will now create an archive of your root file system once you type in your password which takes approximately 5 minutes, so please be patient.

If you are asked ‘Do you wish to install the XCode header files now?‘ Press y for Yes.
If you have been following the instructions so far, you will see the following:

Found Archive.pax.gz in current directory.
Extracting /home/David/Archive.pax.gz…

If everything goes well you will see:

Your toolchain installation is now complete!

Now go out there and make some iPhone/iTouch programs!

And

IIS 4G보다 큰 파일 다운로드 안될때

|

증상

  • Web 상에서 4G 이상의 화일을 다운로드 할때 3.99G 까지만 다운되다가 더이상 안받아짐.
  • dvd의 iso 들 4G 넘는 용량인경우 발생

원인

  • ms의 internet explorer의 모든 버전은 원래 4G이상은 다운로드가 안된다

     

해결

  • firefox를 사용한다.

     

And

Installing on telos-family mote (telosa, telosb)

|

 

Installing on telos-family mote (telosa, telosb)

Telos motes are USB devices, and can be plugged into any USB port:

Telos mote Telos mote plugged into a USB port

Because Telos motes are USB devices, they register with your OS when you plug them in. Typing motelist will display which nodes are currently plugged in:

 $ motelist
 Reference  CommPort   Description
 ---------- ---------- ----------------------------------------
 UCC89MXV   COM4       Telos (Rev B 2004-09-27)
 

motelist tells you which ports have motes attached. Under Windows, it displays the mote's COM port (in this case 4), under Linux it displays just the USB serial port number (e.g., 2). Confusingly, the Windows version of the code installer (tos-bsl) takes the COM port number - 1 as it's argument (in this case 3); under Linux it takes the USB device name (e.g., /dev/ttyUSB2 or /dev/tts/usb/2 if motelist reports that the mote is device 2). On Linux, as with the mica programmers, you will typically need to make the USB serial port world writeable. As superuser, execute the following command:

chmod 666 usb-device-name

Now you can install the application using one of:

  make telosb reinstall bsl,3            # Windows example
  make telosb reinstall bsl,/dev/ttyUSB2 # Linux example

This would compile an image suitable for the telosb platform and install it with a mote ID of 2 on a mote connected to COM4 on Windows or /dev/ttyUSB2 on Linux. If you have a single mote installed, you can skip the bsl and device name/number arguments. Again, see the Getting Started Guide for your chosen platform for the exact make parameters.

You should see something like this scroll by:

    installing telosb binary using bsl
tos-bsl --telosb -c 16 -r -e -I -p build/telosb/main.ihex.out
MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass Erase...
Transmit default password ...
Invoking BSL...
Transmit default password ...
Current bootstrap loader version: 1.61 (Device ID: f16c)
Changing baudrate to 38400 ...
Program ...
2782 bytes programmed.
Reset device ...
rm -f build/telosb/main.exe.out-2 build/telosb/main.ihex.out
And

TinyOS RPM 인스톨시.

|

 

$ rpm -Uvhi --nodeps avrdude-tinyos-5.6cvs-1.cygwin.i386.rpm
Preparing...                ########################################### [100%]
   1:avrdude-tinyos         ########################################### [100%]
/usr/bin /
Copying the driver to the windows directory
target file: G:\WINDOWS\giveio.sys
        1개 파일이 복사되었습니다.
Remove a running service if needed...
Installing Windows NT/2k/XP driver: giveio
installing giveio from G:\WINDOWS\giveio.sys... ok.
starting giveio... ok.
set start type of giveio to auto... ok.
Success

And

TinyOS 2.x 설치 (msp430 기준)

|
bsp;

기본 문서는 다음을 참조한다.

LINK : TinyOS_2.1#Manual_installation_on_your_host_OS_with_RPMs">http://docs.tinyos.net/index.php/Installing_TinyOS_2.1#Manual_installation_on_your_host_OS_with_RPMs

 

Step 1: Install Java 1.6 JDK

 Download and install Sun's 1.6 JDK from http://java.sun.com.

Step 2: Install Cygwin

Download cygwin-files.zip 및 설치

Step 3: Install native compilers

Atmel AVR Tools

 

Tool Windows/Cygwin Linux
avr-binutils rpm" href="http://www.tinyos.net/dist-2.1.0/tools/windows/avr-binutils-2.17tinyos-3.cygwin.i386.rpm" rel="nofollow">avr-binutils-2.17tinyos-3.cygwin.i386.rpm avr-binutils-2.17tinyos-3.i386.rpm
avr-gcc avr-gcc-4.1.2-1.cygwin.i386.rpm avr-gcc-4.1.2-1.i386.rpm
avr-libc avr-libc-1.4.7-1.cygwin.i386.rpm avr-libc-1.4.7-1.i386.rpm
avarice avarice-2.4-1.cygwin.i386.rpm avarice-2.4-1.i386.rpm
insight (avr-gdb) avr-insight-6.3-1.cygwin.i386.rpm avr-insight-6.3-1.i386.rpm
avrdude avrdude-tinyos-5.6cvs-1.cygwin.i386.rpm avrdude-tinyos-5.6cvs-1.i386.rpm

If you receive an rpm error that indicates that you have a newer version already installed, try rpm -Uvh --force

rpm 옵션은 -ivh --ignoreso 로 자잘한 에러는 pass

TI MSP430">MSP430 Tools

Tool Windows/Cygwin Linux
base msp430tools-base-0.1-20050607.cygwin.i386.rpm msp430tools-base-0.1-20050607.i386.rpm
python tools msp430tools-python-tools-1.0-1.cygwin.noarch.rpm msp430tools-python-tools-1.0-1.noarch.rpm
binutils msp430tools-binutils-2.16-20050607.cygwin.i386.rpm msp430tools-binutils-2.16-20050607.i386.rpm
gcc msp430tools-gcc-3.2.3-20050607.cygwin.i386.rpm msp430tools-gcc-3.2.3-20050607.i386.rpm
libc msp430tools-libc-20080808-1.cygwin.i386.rpm msp430tools-libc-20080808-1.i386.rpm

rpm 옵션은 -ivh --ignoreso 로 자잘한 에러는 pass

 

Step 4: Install TinyOS toolchain

TinyOS-specific Tools

 

Tool Windows/Cygwin Linux Command
NesC nesc-1.3.0a-1.cygwin.i386.rpm nesc-1.3.0-1.fc9.i386.rpm rpm -Uvh
rpm -Uvh --ignoreos (if Cygwin complains)
Tool Windows/Cygwin Linux Command
Deputy tinyos-deputy-1.1-1.cygwin.i386.rpm tinyos-deputy-1.1-1.fc9.i386.rpm rpm -i
rpm -i --ignoreos (if Cygwin complains)
Tool Windows/Cygwin Linux Command
tinyos-tools tinyos-tools-1.3.0-1.cygwin.i386.rpm tinyos-tools-1.3.0-1.i386.rpm rpm -ivh --force (1.x tree)
rpm -Uvh (no 1.x tree)

뒤에 Command 를 참조하여 패키지 설치

Step 5: Install the TinyOS 2.x">2.x source tree

TinyOS 2.x

 

  Windows/Cygwin Linux
TinyOS tinyos-2.1.0-1.cygwin.noarch.rpm tinyos-2.1.0-1.fc9.noarch.rpm

rpm -ivh --ignoreos rpmname 으로 설치

Configure your environment

 

TinyOS 2.x

 

Environment Variable Windows Linux
TOSROOT /opt/tinyos-2.x same as in Cygwin  
TOSDIR $TOSROOT/tos same as in Cygwin  
CLASSPATH C:\tinyos\cygwin\opt\tinyos-2.x\support\sdk\java\tinyos.jar;. $TOSROOT/support/sdk/java/tinyos.jar:.  
MAKERULES $TOSROOT/support/make/Makerules same as in Cygwin  
PATH /opt/msp430/bin:/opt/jflashmm:$PATH same as in Cygwin

다음 테이블 내용은 계정에 쉘 스크립트에 넣는다.


export TOSROOT="/opt/tinyos-2.x"
export TOSDIR="$TOSROOT/tos"
export CLASSPATH="G:\CYGWIN\opt\tinyos-2.x\support\sdk\java\tinyos.jar;."
export MAKERULES="$TOSROOT/support/make/Makerules"
export PATH="opt/msp430/bin:/opt/jflashmm:$PATH"

 

Step 6: Installing Graphviz

download page  에서 받아서 설치

 

다음은 잘 깔렸는지 확인차 컴파일을 해보자`~

LINK : http://docs.tinyos.net/index.php/Getting_Started_with_TinyOS#Making_sure_you.27re_invoking_the_right_version_of_the_nesC_compiler

cd  /opt/tinnyos-2.x /apps/Blink

make telos install

완료~!! 

And

Remote Access VPN Connections

|

Remote AccessVPN Connections

For remote access VPN connections, a computer creates a remote access connection to a VPN server. During the connection process the VPN server assigns an IP address for the remote access VPN client and changes the default route on the remote client so that default route traffic is sent over the virtual interface.

IPAddresses and the Dial-Up VPN Client

For dial-up VPN clients who connect to the Internet before creating a VPN connection with a VPN server on the Internet, two IP addresses are allocated:

?

When creating the PPP connection, IPCP negotiation with the ISP NAS assigns a public IP address.

?

When creating the VPN connection, IPCP negotiation with the VPN server assigns an intranet IP address. The IP address allocated by the VPN server can be a public IP address or private IP address, depending on whether your organization is implementing public or private addressing on its intranet.

In either case, the IP address allocated to the VPN client must be reachable by hosts on the intranet and vice versa. The VPN server must have appropriate entries in its routing table to reach all the hosts on the intranet and the routers of the intranet must have the appropriate entries in their routing tables to reach the VPN clients.

The tunneled data sent through the VPN is addressed from the VPN client's VPN server-allocated address to an intranet address. The outer IP header is addressed between the ISP-allocated IP address of the VPN client and the public address of the VPN server. Because the routers on the Internet only process the outer IP header, the Internet routers forward the tunneled data to the VPN server's public IP address.

An example of dial-up client addressing is shown in Figure 9.14 where the organization uses private addresses on the intranet, and the tunneled data is an IP datagram.

Figure 9.14 Public and Private Addresses in PPTP Tunneled Data

DefaultRoutes and Dial-Up Clients

When a typical dial-up client dials the ISP, it receives a public IP address from the ISP NAS. A default gateway address is not allocated as part of the IPCP negotiation process. Therefore, in order to reach all Internet addresses, the dial-up client adds a default route to its routing table using the dial-up interface connected to the ISP. As a result, the client can forward the IP datagrams to the ISP NAS from where they are routed to its Internet location.

For dial-up clients with no other TCP/IP interfaces, this is the wanted behavior. However, this behavior can cause confusion for dial-up clients that have an existing LAN-based connection to an intranet. In this scenario, a default route already exists pointing to the local intranet router. When the dial-up client creates a connection with their ISP, the original default route remains in the routing table but is changed to have a higher metric. A new default route is added with a lower metric using the ISP connection.

As a result, the intranet locations that are not on the dial-up client's directly attached network are not reachable for the duration of the connection to the ISP. If the new default route is not created, all intranet locations are reachable, but Internet locations are not.

A Windows 2000?based dial-up client creates the default route by default.

To prevent the default route from being created

?

In the properties of the TCP/IP protocol of the dial-up connection object, in the Advanced TCP/IP Settings dialog box, click the General tab, and then clear the Use default gateway on remote network check box.

To achieve connectivity to both intranet and Internet locations while the ISP connection is active, leave the Use default gateway on remote network option selected and add the routes of the intranet to the routing table of the dial-up client. The intranet routes can be added through static persistent routes using the route utility, or, if Routing Information Protocol (RIP) version 1 is being used as the intranet routing protocol, you can use the Route Listening Service to listen to RIP version 1 routing protocol traffic and dynamically add intranet routes. When connected to the ISP, all intranet locations are reachable using the intranet routes and all Internet locations are reachable using the default route.

Default Routes and VPNs over the Internet

When the dial-up client calls the ISP, it adds a default route using the connection to the ISP as shown in Figure 9.15. At this point, it can reach all Internet addresses through the router at the ISP NAS.

Figure 9.15 Default Route Created When Dialing an ISP

When the VPN client creates the VPN connection, another default route and a host route to the IP address of the tunnel server are added, as illustrated in Figure 9.16. The previous default route is saved but now has a higher metric. Adding the new default route means that all Internet locations except the IP address of the tunnel server are not reachable for the duration of the VPN connection.

Figure 9.16 Default Route Created When Initiating the VPN

Just as in the case of a dial-up client connecting to the Internet, when a dial-up VPN client using voluntary tunneling creates a VPN connection to a private intranet across the Internet, one of the following occurs:

?

Internet locations are reachable and intranet locations are not reachable when the VPN connection is not active.

?

Intranet locations are reachable and Internet locations are not reachable when the VPN connection is active.

For most Internet-connected VPN clients, this behavior does not represent a problem because they are typically engaged in either intranet or Internet communication, not both.

For VPN clients who want concurrent access to intranet and Internet resources when the VPN is connected, the solution depends on the nature of the IP addressing in the intranet. In all cases, configure the VPN connection object so that it does not add a default gateway. When the VPN connection is created, the default route remains pointed to the ISP NAS, allowing access to all Internet addresses.

Based on the type of intranet addressing you use, enable concurrent access to intranet and Internet resources as follows:

Public Addresses    Add static persistent routes for the public network IDs of the intranet using the IP address of the VPN server's virtual interface as the gateway IP address.

Private Addresses    Add static persistent routes for the private network IDs of the intranet using the IP address of the VPN server's virtual interface as the gateway IP address.

Overlapping or Illegal Addresses    If the intranet is using overlapping or illegal addresses (IP network IDs that are not private and have not been registered by Internet Network Information Center [InterNIC] or obtained from an ISP), those IP addresses might be duplicated by public addresses on the Internet. If static persistent routes are added on the VPN client for the overlapping network IDs of the intranet, the locations on the Internet for the overlapping addresses are not reachable.

In each of these cases, static persistent routes for the network IDs of the intranet need to be added to the VPN client. When the persistent routes are added, they are saved in the registry. With Windows NT 4.0 Service Pack 3 and later and with Windows 2000, the persistent routes are not actually added to the IP routing table (and are not visible with the route print command at the Windows 2000 command prompt) until the IP address of the gateway is reachable. The IP address of the gateway becomes reachable when the VPN connection is made.

For each route, type the following route utility syntax at a Windows 2000 command prompt:

ROUTE ADD <Intranet Network ID> MASK <NetMask> <IP address of VPN server's virtual interface> -p

The gateway IP address in the route commands for each intranet route is the IP address assigned to the VPN server's virtual interface, not the IP address of the VPN server's Internet interface.

You can determine the IP address of the VPN server's virtual interface from the IP address of the Internal interface under IP Routing - General in the Routing and Remote Access snap-in. If you use DHCP to obtain IP addresses for dial-up networking and VPN clients, the IP address of the VPN server's virtual interface is the first IP address obtained when requesting DHCP addresses. If you have configured a static IP address pool, the IP address of the VPN server's virtual interface is the first IP address in the static IP address pool. You can also determine the IP address of the VPN server's virtual interface by double-clicking the virtual private networking connection object when the VPN connection is active. In the resulting Status dialog box, click the Details tab.

caution-icon

Caution

For all of these cases, you must add the routes very carefully to ensure that the private traffic to the intranet is forwarded using the VPN connection and not the PPP connection to the ISP. If the wrong routes are added, the traffic that you intend to forward across the VPN in an encrypted form is instead sent unencrypted across the Internet. For example, if your intranet is using the public network ID 207.46.130.0/24 (subnet mask 255.255.255.0), and you mistakenly add a persistent static route for 207.46.131.0/24, all traffic to the intranet network 207.46.130.0/24 is forwarded across the Internet in plaintext, rather than being encrypted and sent across the VPN connection.

Source : MS TechNet

And
prev | 1 | 2 | 3 | 4 | next