Liferea
November 3, 2009
click the dropdown menu, and then select others
/usr/bin/liferea-add-feed
ref. http://joshh.co.uk/index.php/2009/06/15/adding-feeds-to-liferea-in-firefox/
내주 영역 포기를 통한 HDD 성능 향상시키기
October 30, 2009
Seagate HDD의 경우 Seagate tool을 통해 내주부분에 해당하는 부분의 사용을 제한할 수 있다.
HDD의 arm의 이동하는 범위를 줄여 access time 또한 단축 가능하다.
http://www.kbench.com/hardware/?no=76281&sc=3
Virtualbox tip
October 27, 2009
Users of Fedora/Mandriva might want to install the dkms package (not available on openSUSE) to ensure that the VirtualBox host kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are properly updated if the linux kernel version changes during the next kernel update.
# yum install dkms
한국의 100대 명반, rock 명반
October 20, 2009
Optimize Win 7
October 12, 2009
1. Disk Defragmentation
시작 → 프로그램 → 보조 프로그램 → 시스템 도구 → 디스크 조작 모음
: turn off the Defragmentation demon
2. Temp folder
move to 2nd physical drive or ramdrive(if you have enough ram)
My Computer(Right click) → properties → Advanced tab→Performance, Startup and Recovery, and Environment Variables.
IE and Firefox Temp(about:config →새로만들기 → 문자열→ browser.cache.disk.parent_directory → 경로 입력). folder, Antivirus, swap
ramdrive and page file
- SuperSpeed Ramdisk Plus
- C:\pagefile.sys ← create 0 byte pagefile.sys and then change its attribute as “read only”
3. Servies
My Computer(Right click) → Management → Advanced tab→Performance, Startup and Recovery, and Environment Variables.
- Distributed Link Tracking Client → manual
- IP Helper → manual
- Machine Debug Manager
- npkcmsvc 되나?
- Offline Files
- Windows Live ID Sign-in Assistant
- Windows Media Player Network Sharing Service
- Windows Search → disable
4. Advanced SystemCare Free
- download
5. Avira
- http://www.free-av.com/en/download/1/avira_antivir_personal__free_antivirus.html
- 제어판 → 관리 도구 → 로컬 보안옵션 → 소프트웨어 제한 정책 → 새 소프트웨어 제한 정책(시작→secpol.msc)
- drop down 에 “추가 규칙” 선택하고 오른쪽 남는공간에 “새 경로규칙”을 선택
- “c:\Program Files\Avira\Antivir Desktop\avnotify.exe” 등록
ref. http://windows.microsoft.com/en-US/windows7/Optimize-Windows-7-for-better-performance
http://www.blackviper.com/Windows_7/servicecfg.htm
http://middleage.tistory.com/478
Shared folder on Windows 7
October 12, 2009
Start → type cmd
net use h: \\vboxsvr\mysharedfolder
h: is the name of the guest OS drive I assigned, vboxsvr refers to the guest OS, and mysharedfolder is the name I provided when I set up the shared folder
ref. http://geekswithblogs.net/TakeNote/archive/2009/08/19/134188.aspx
ref.
October 5, 2009
properties of the rare earth metals and compounds
http://scripts.iucr.org/cgi-bin/paper?S056774088200288X
Cannot open pdf file into Firefox
September 30, 2009
- Symptom: Cannot open pdf file ino firefox with Plugin error message.
- Cause: Either Acrobat and Acrobat Reader or have installed a newer version of Reader without uninstalling the old version before.
- Solution: Find the firefox program folder, goto plugins and remove/rename the nppdf32.dll file.
ex) del “C:\Program Files\Mozilla Firefox\plugins\nppdf32.dll”
노트북 살때 고려해야할 점 090929
September 29, 2009
1. Processor
- Atom vs Penrin
Atom: 저전력 저성능, Penrin: 고성능, 전력소모가 큼
model name
- T : 초기 코어2듀오 센트리노 제품군. 6메가의 L2 캐쉬 메모리, 버스 스피드는 모델명 뒤에 숫자가 증가하면서 클럭속도가 더 빠름, 전력소모 35W. T7XXX제품들은 센트리노2, T9XXX 제품들부터는 펜린(45nm)
- P : 캐쉬 메모리가 3M, 버스 스피드가 1066, 전력소모율 25W(즉 45nm이 적용됨), P시리즈는 보급형이지만 T 시리즈에 비해 별 차이점이 없음.
- L (Low Voltage): 센트리노2 제품군(T7XXX) 까지만 적용(사장?)
- ULV or U(Ultra Low Voltage) : 더 적은 전력 소모. Core2Solo까지만 적용된듯(사장?), U7XXX 이상 나오지 않고 있음
- SL(Small Low Voltage) : CPU의 크기를 코어2듀오 프로세서의 60% 크기로 줄임. 더욱 저전력, SL7XXX 제품 이후로 잘 안나오는듯. 호환되는 메인보드가 적음, 성능 위주(X, 트랜지스터 집적도가 기본제품보다 적음) 장시간 사용을 기준.
- SU : Small에다가 U가 붙은 것입니다. SL보다도 더 전력 소모가 적은 제품이면서, CPU 다이 크기가 줄어든 것이겠죠?
- N270 or N280(N3oo: dual core) : 아톰의 CPU, 저성능, 전력소모가 워낙에 적음(single: 2.5~4, dual: 8W), 하이퍼 스레딩 적용, code name: Diamondville
- Z520 : N270 후속. MID, Ultra-Mobile용, 전력소모가 적음(w HT: 0.65~2, w/o HT: 2~2.4W), atom 계열 중 최하위 성능, code name: Silverthorne
2. 무게 및 화면 크기: 1~1.3kg 이내 보통 10~10.1인치 정도임(1024×800 이상의 해상도)
3. Battery: 병렬연결하는 cell의 증가는 사용 시간을 증가시켜줌.. 무게가.. (3cell ~9cell)
4. 무선랜: g는 최대 54Mbps, n은 100Mbps.. AP가 g까지 지원하면..
5. Graphics: 고성능의 ION flatform(전련소모 및 성능 면에서 Intel 계열 보다 우수하다고 알려짐)
N330+ION+IEEE 802.11 b/g/n+…
기타.
ref. http://kin.naver.com/detail/detail.php?d1id=1&dir_id=10405&docid=7831434&qb=7Y6c66awIHAgc3U=&enc=utf8&pid=fV44qloi5UhssvUAUiNsss–184163&sid=SsIIqubMwUoAADXiWHw
http://en.wikipedia.org/wiki/Intel_Atom
Theora 1.1 Thusnelda
September 28, 2009
Xiph.Org Foundation
- Vorbis (.ogg .oga): audio codec
free software / open source project that produces an audio format specification and software implementation (codec) for lossy audio compression
- Theora (.ogv): lossy video codec
royalty-free, open standard, lossy video compression technology
- Thusnelda (Codename of Theora 1.1)
: improved encoding, providing better video quality for a given file size, a faster decoder, bitrate controls to help with streaming, and two-pass encoding, CPU usage during encoding is much more consistent
1. Rate-distortion optimization, which leads to
a. Better mode decision
b. Better quantization decisions
Most coding decisions only use an approximation of the full RDO
process for speed reasons, but casting this in a proper RDO framework
eliminates vast swaths of heuristics and fragile thresholds from the 1.0
encoder.
2. Better motion search
The new motion search generates better results in less time, and
does not suffer from CPU spikes under heavy motion like the 1.0
encoder’s did.
3. Better fDCT
The 1.0 encoder’s forward transform was not well-matched to the
inverse DCT used in the decoder, and was as a result responsible for
substantial loss of detail and texture at high rates. It has been
replaced with a forward DCT that gives much smaller round-trip error.
The inverse DCT in the decoder remains unchanged, for compatibility.
4. Adaptive quantization
The bitstream specification has supported changing the quantizer on a
block-by-block basis since it was first published in 2004, however only
an unreleased proof-of-concept encoder made use of this facility. The
1.1 encoder now uses it to allocate bits more effectively within a
frame, giving improved quality at higher rates.
5. Better quantization matrices
The new matrices give much less ringing and mosquito noise at low
rates, substantially improving the appearance of high-contrast edges
(e.g., text).
6. A real rate-control module
As mentioned above, the new rate control actually meets its targets,
can enforce hard buffer constraints, and has a two-pass mode to allow it
to plan allocation decisions in advance.
7. Expanded rate-control API
It is now possible to change the target quality, bitrate, buffer
delay, and keyframe interval in the while encoding. This gives an
application using libtheora much more control over the final output.
8. Explicit variable frame rate support in the encoder
A new API allows an application to cheaply insert duplicate frames
to maintain A-V sync during live streaming or for hybrid 24/30 fps
content. The decoder still operates at a fixed frame rate, but can
report these duplicates to the application, allowing it to skip
expensive processing.
9. Support for 4:2:2 and 4:4:4 video
As with adaptive quantization, the specification has always
supported the less common 4:2:2 and 4:4:4 chroma subsamplings, useful
for high quality intermediate work in video production. The 1.0
decoder supported these subsamplings properly. However, the 1.0
encoder couldn’t produce streams in these formats. They are now
supported in the 1.1 encoder.
ref. http://hacks.mozilla.org/2009/09/theora-1-1-released/
http://news.slashdot.org/story/09/09/26/1611252/Theora-11-Thusnelda-Is-Released?from=rss
http://lists.xiph.org/pipermail/theora/2009-September/002807.html
1. Rate-distortion optimization, which leads to a. Better mode decision b. Better quantization decisions Most coding decisions only use an approximation of the full RDO process for speed reasons, but casting this in a proper RDO framework eliminates vast swaths of heuristics and fragile thresholds from the 1.0 encoder. 2. Better motion search The new motion search generates better results in less time, and does not suffer from CPU spikes under heavy motion like the 1.0 encoder's did. 3. Better fDCT The 1.0 encoder's forward transform was not well-matched to the inverse DCT used in the decoder, and was as a result responsible for substantial loss of detail and texture at high rates. It has been replaced with a forward DCT that gives much smaller round-trip error. The inverse DCT in the decoder remains unchanged, for compatibility. 4. Adaptive quantization The bitstream specification has supported changing the quantizer on a block-by-block basis since it was first published in 2004, however only an unreleased proof-of-concept encoder made use of this facility. The 1.1 encoder now uses it to allocate bits more effectively within a frame, giving improved quality at higher rates. 5. Better quantization matrices The new matrices give much less ringing and mosquito noise at low rates, substantially improving the appearance of high-contrast edges (e.g., text). 6. A real rate-control module As mentioned above, the new rate control actually meets its targets, can enforce hard buffer constraints, and has a two-pass mode to allow it to plan allocation decisions in advance. 7. Expanded rate-control API It is now possible to change the target quality, bitrate, buffer delay, and keyframe interval in the while encoding. This gives an application using libtheora much more control over the final output. 8. Explicit variable frame rate support in the encoder A new API allows an application to cheaply insert duplicate frames to maintain A-V sync during live streaming or for hybrid 24/30 fps content. The decoder still operates at a fixed frame rate, but can report these duplicates to the application, allowing it to skip expensive processing. 9. Support for 4:2:2 and 4:4:4 video As with adaptive quantization, the specification has always supported the less common 4:2:2 and 4:4:4 chroma subsamplings, useful for high quality intermediate work in video production. The 1.0 decoder supported these subsamplings properly. However, the 1.0 encoder couldn't produce streams in these formats. They are now supported in the 1.1 encoder.
ohwordpress