옴니아2009. 2. 24. 09:52
Posted by krsuncom
링크2008. 2. 4. 14:22

이래저래 알아두면 좋은 소프트웨어 모음이다.

담에 시간되면 리뷰라도 써야겠다.


출처 :  Voip Business Solution: voips (87 сообщений)

Office

OpenOffice - office suite
PC Suite 602 - office suite
AbiWord - text editor
Atlantis Nova - text editor
Microsoft PowerPoint Viewer - power point files viewer
Adobe Reader - pdf reader
Foxit PDF Reader - pdf reader
PDFCreator - create pdf documents
Doc Convertor - document convertor
Convert - unit convertor
Converber - unit convertor
Sunbird - calendar/organizer
EssentialPIM Free - calendar/organizer
PhraseExpress - speed up your writing
ATnotes - create notes on the desktop

Archive managers

7-Zip - compression program
IZArc - compression program
TugZIP - compression program
CabPack - compression program
Universal Extractor - extract files from any type of archive

Internet

Firefox - web browser
Internet Explorer- web browser
Maxthon - web browser
Opera - web browser
Avant Browser - web browser
Thunderbird - email client
PopTray - check for emails
Free Download Manager - download manager
FlashGet - download manager
WellGet - download manager
Download Master - download manager
WGET - commandline download manager
HTTrack - offline browser
WebReaper - offline browser
Yeah Reader - RSS reader
GreatNews - RSS reader
RSSOwl - RSS reader

P2P  this is sharing files on your computer with someone else.

?Torrent - torrent client
Azureus - torrent client
BitComet - torrent client
ABC - torrent client
BitTornado - torrent client
eMule - p2p client
SoulSeek - p2p client
Shareaza - p2p client
DC++ - Direct Connect network client
PeerGuardian - IP blocker

Chat

Miranda - chat client
MSN Messenger - chat client
Yahoo Messenger - chat client
QIP - chat client
Gaim - chat client
JAJC - chat client
HydraIRC - IRC client
Talkative IRC - IRC client
IceChat - IRC client
Skype - VOIP client
Google Talk - VOIP client
VoipStunt - VOIP client
Gizmo - VOIP client
Wengo - VOIP client

Security

AVG Free - antivirus
Avast Home Free - antivirus
AntiVir PersonalEdition - antivirus
BitDefender Free - antivirus
ClamWin - antivirus
CyberDifender - Internet Security Suite
Ad-aware - anti-spyware
Spybot: Search & Destroy - anti-spyware
Windows Defender - anti-spyware
SpywareBlaster - anti-spyware
Spyware Terminator - anti-spyware
Tootkit Reveaker  - rootkit detection utility
Winpooch - system protection
HiJack Free - system protection
HighJackThis - hijackers detector and remover
Kerio Personal Firewall - firewall
Sygate Personal Firewall - firewall
ZoneAlarm - firewall
AxCrypt - file encryption
Simple File Shredder - securely delete files
PuTTy - SSH client
KeePass - password manager
LockNote - password manager
nPassword - password manager
Microsoft Baseline Security Analyzer - identify security misconfigurations

Network

Hamachi - VPN client
RealVNC - remote control
UltraVNC - remote control
Ethereal - local area network administration
The Dude - network administration
Wireshark - network administration
Angry IP Scanner - IP scanner
IP-Tools - IP scanner
Free Port Scanner - IP scanner
NetMeter - network bandwidth monitoring

Servers

FileZilla - FTP client
FileZilla Server - FTP server
EFTP - FTP client/server
XAMPP - integrated server package of Apache, mySQL, PHP and Perl
WAMP - Apache, PHP5 and MySQL server

Audio

Foobar2000 - audio player
WinAmp - audio player
1by1 - audio player
JetAudio - audio player
XMPlay - audio player
Xion - audio player
Apollo - audio player
MediaMonkey - music organizer
The GodFather - music organizer
dBpowerAMP - audio converter
Audacity - audio converter
WavePad - audio converter
Kristal Audio Engine - audio editor
Exact Audio Copy - CD ripper
Audiograbber - CD ripper
CDex - CD ripper
Mp3 Tag Tools - tag editor
Mp3tag - tag editor
Taggin? MP3 - tag editor
Monkey?s Audio - APE compressor/decompressor
mpTrim - mp3 editor
WavTrim - wave editor
EncSpot Basic - analyse mp3 files

Video

Windows Media Player - audio/video player
VLC - video player
Media Player Classic - video player
MV2Player - video player
CrystalPlayer 1.95 - video player
Zoom Player - video player
GOM Player - video player
viPlay - video player
DSPlayer - video player
VirtualDub - video editor
CamStudio - video screen recording
AviSplit - Avi splitter
Video mp3 Extractor - rip audio from video files
Free iPod Converter - convert all popular video formats to iPod video
MediaPortal - turning your PCinto a Media Center
The FilmMachine

Image

Gimp - image editor
PhotoFiltre - image editor
Paint.net - image editor
ArtRage - image editor
Artweaver - image editor
IrfanView - image viewer
Picasa - image viewer
XnView - image viewer
FastStone Image Viewer - image viewer
FuturixImager - image viewer
Easy Thumbnails - create thumbnails from images
JoJoThumb - create thumbnails from images
iWebAlbum - create web photo albums
JAlbum - create web photo albums
3D Box Shot Maker - design quality box shot
FastStone Capture - screen capture
WinSnap - screen capture

3D

Blender3D - 3D renderer
3Delight Free - 3D renderer
SketchUp - 3D modeling
Maya Learning Edition - 3D modeling

Developers

AutoIt - task automation
SciTE4AutoIt3 - text editor for AutoIt
AutoHotkey - task automation
PHP Designer - PHP editor
Notepad++ - text editor
ConTEXT Editor - text editor
PSPad - text editor
FoxEditor - text editor
Crimson Editor - source code editor
Elfima Notepad - text editor
Notepad2 - text editor
Nvu - HTML editor
Alleycode - HTML editor
BlockNote - web page editor
Weaverslave - web page editor

CD/DVD

DeepBurner - CD/DVD burner
CDBurner XP Pro - CD/DVD burner
BurnAtOnce - CD/DVD burner
Express Burn - CD/DVD burner
Zilla CD-DVD Rip?n?Burn - CD/DVD burner
ImgBurn - ISO, BIN burner
Daemon tools - virtual CD/DVD
DVD Decrypter - DVD ripper
DVD Shrink - DVD ripper
Nero CD-DVD Speed - CD/DVD info and quality test

Codecs

GSpot - codec information
AC3Filter - audio codec
Xvid - video codec
QuickTime Alternative - video codec
Real Alternative - video codec
K-Lite Codec Pack - all codecs

System Ulilities

CCleaner - system cleaner
xp-AntiSpy - OS setup
jv16 Powertools - system utilities
XP SysPad - system monitoring utility
What?s Running - process guard
Registrar Lite - registry editor
WinIPConfig - replacement for ?ipconfig.exe? and ?route.exe?
Unlocker - file eraser
Eraser - secure file eraser
Undelete Plus - file recovery
freeCommander - file manager
ExplorerXP - file manager
Duplicate File Finder - find all duplicate files
Ant Renamer - file renaming
ReNamer - file renaming
Icons From File - icos extractor
Chaos MD5 - MD5 generator
HashTab - MD5, SHA1 and CRC-32 file hashes
Rainlendar Lite - desktop calendar
Weather Watcher - weather firecast
Subtitle Workshop - subtitles editor
Ant Movie Catalog - movie organizer
Disclib - CD organizer
Dexpot - virtual desktops
DriveImage XML - create partition images
MozBackup - backup and restore bookmarks, etc.
SyncBack - system backup
Atomic Cock Sync - syncronize your clock
Citrus Alarm Clock - alarm clock
TaskSwitchXP - Alt-Tab replacement
Launchy - application launcher
allSnap - make all windows snap
Sysinternals Tools - various system tools
StrokeIt - mouse gestures
Net Profiles - create profiles of your network settings
ResourceHacker - view, modify, rename, add, delete
Java Runtime Environment - java for Windows

UI Enhancements

RocketDock - application launcher
AveDesk - desktop enhancer
IconPhile - customize windows?s system icons
CursorXP Free - change mouse cursors
MacSound - volume control
LClock - Windows Longhorn clock
Y?z Dock - application launcher
Y?z Shadow - shadow effect to the windows
Y?z Toolbar - change the toolbar icons in Explorer and Internet Explorer
Taskbar Shuffle - rearrange the programs on the taskbar by dragging
Visual Task Tips - thumbnail preview image for each task in the taskbar
Badges  - put badges on any folder or file
Folderico - change icons of the folders
Folder Marker - mark your folders
Folder2MyPC - add favourite locations to My Computer
Microsoft TweakUI - system settings
BricoPacks - shell packs
ShellPacks - shell packs
Tango Shell Patcher - shell patcher
XPize - GUI enhancer
Vista Transformation Pack  - complete visual style
Vista Sound Scheme - Windows Vista sound scheme
Royale Theme - visual style

Hardware monitoring/Benchmarking

CPU-Z - cpu information
CrystalCPUID - cpu information
Central Brain Identifier - cpu information
Everest - system information
SiSoft Sandra - system information
SpeedFan - hardware monitor
Memtest86 - memory test
PowerMax - HDD test
3Dmark 06 - 3D game performance benchmark
Aquamark - performance benchmark
rthdribl - 3D benchmark
Fraps - 3D benchmark, fps viewer and screen recorder
Prime 95 - cpu benchmarking
SuperPI - cpu benchmarking
CPU Rightmark - cpu overclock
Core Temp - cpu temperature
ATiTool - video overclock
ATI Tray Tools - Radeon tweaker
aTuner - GeForce and Radeontweaker
RivaTuner - video overclock
Nokia Monitor Test - monitor adjustmets
UDPixel - fix dead pixels

Games

123 Free Solitaire - solitaire games collection
Arcade Pack - classic arcade games
Live For Speed - online racing simulator
Enigma - puzzle game
Freeciv - multiplayer strategy game
Tux Racer - race down steep, snow-covered mount?ins

Education

SpeQ Mathematics  - mathematics program
Dia - diagram creation program
Google Earth - explore the world
NASA World Wind - 3D virtual globe
Celestia - explore the space
Stellarium - planetarium

Miscellaneous

nLite - Build your own custom Windows disk.
VirtualPC - create virtual machines
grabMotion - webcam capture
iDailyDiary - simple page-for-a-day diary
Pivot Stickfigure Animator - create stick-figure animations
Wink - create presentations
Scribus - professional page layout
FreeMind - mind mapping software
Windows Live Writer - WYSIWYG blog authoring

Wallpapers

Michael Swanson - 1920 x 1200; 1600 x 1200; amazing wallpapers
Mikhail Arkhipov - 1920 x 1200; 1600 x 1200; amazing wallpapers

 

Voip Business Solution: voips (87 сообщений)

Posted by krsuncom
IT 이야기2007. 11. 2. 17:13

참 정리도 잘해놓은 사이트다

블로그를 하다보면 꼭 알아야 하는 사이트 들인데.. 많기도 하다

올블로그/이올린/미디어몹/오픈블로그/e버즈/커리어블로그/블로그플러스 기타등등.....

후~ 많기도 하다.

링크는 아래:

IT Gadget 임프레션(T) :: 블로그들의 공간 메타사이트 총정리

Posted by krsuncom
블랙잭이야기2007. 10. 19. 12:43

 

멋지다~

Posted by krsuncom
개발이야기2007. 10. 10. 09:57

원문이라네 : 요기

Tweaks and Hacks

Post registry and software hacks to make your TyTN do even more here.
(Obviously none of these will be supported by either HTC or your local phone service provider. Use these at your own risk.)
Registry Editors:
Mobile Registry Editor
Works with Mobile 5 though developed for older

Change Bluetooth Name Without Changing Owner Name
Normally the name of your device which is displayed when using bluetooth is the owner name.
To change this use a registry editor and browse to
\HCKU\Software\Microsoft\Bluetooth\Settings\Local Name
And change the value of the local name key to what ever you want.
THIS HAS ONLY BEEN TESTED ON MY DEVICE: IMATE JASJAM RUNNING WINDOWS MOBILE 5.0 (build 14955.2.3.0) AKU 2.3
Internet Explorer Navigation
The default behaviour for your device's four-way direction button in Pocket Internet Explorer (PIE) is to jump between hyperlinks/form fields on a web page. To change this behaviour so that the button scrolls the page left, right, up and down, use the following tweak:
\HKLM\Software\Microsoft\Internet Explorer\Navigation\4-Way Nav = 0 (DWORD decimal)
And to re-enable hyperlink/form field navigation:
\HKLM\Software\Microsoft\Internet Explorer\Navigation\4-Way Nav = 1 (DWORD decimal)
NB: You may still jump between links using Tab and Shift-Tab if your device has a built-in hardware keyboard.
WM5: Increase Performance and Speed

Boost Windows Mobile 5 performance by makeing the following changes in the registry...
[HKLM\System\StorageManager\FATFS] CacheSize = 4096 EnableCache = 1
[HKLM\System\StorageManager\Filters\fsreplxfilt] ReplStoreCacheSize = 4096
Default values for all keys are 0. Soft reset for changes to take effect.
Disable Menu Animation

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\GWE\Menu, then change the value of "AniType" from 6 (default) to 0.
This disables the menu animation which helps in speeding up your PocketPC.
Change the Tap and Hold Dots Colours

1) Go to the HKLM\SOFTWARE\Microsoft\Color\ key.
2) Add a Binary value called "40" if it does not already exist.
3) Set the value to "rr gg bb 00" (RGB hex values 00 to FF so "FF 00 000 00" is Red)
SMS Settings

SMS Notification Always On
[HKEY_CURRENT_USER\Software\Microsoft\Inbox\Settings]
"SMSDeliveryNotify"=dword:00000001 ->0 to disable, 1 to enable.
Disable SMS Sent Notification
[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Settings]
"SMSNoSentMsg"=dword:00000001 ->0 to enable, 1 to disable.
Bottom tray icons

Remove the Battery Icon:
[HKEY_LOCAL_MACHINE\Services\Power]
"ShowIcon"=dword:00000000
Remove the Wireless Manager Icon:
[HKEY_LOCAL_MACHINE\Services\WirelessMgr]
"Keep"=dword:00000000
Restore local language support for sliding keyboard after upgrade to a different language ROM

This has been reported not to work, see below for another hack
You need to create Registry value of name "Locale" and type of "String" and data of "Localization ID" within [HKEY_CURRENT_USER\ControlPanel\Keybd]
Localization IDs:
French = 040c
German = 0407
Italian = 0410
Japanese = 0411
Kazakh = 043f
Russian = 0419
Other IDs can be found here: Tweaks and Hacks - htcwikihttp://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx.
Some versions of the OS seem to be case sensitive on this value, and if it does not work, try upper case letters. Registry example for say russian kbd:
[HKEY_CURRENT_USER\ControlPanel\Keybd]
"Locale"="0419"
Modification to keyboard hack. The above solution does not work for the Hermes the following new settings are required.

Goto the following registry entry
[HKEY_LOCAL_MACHINE\Software\Oem\Qwerty]
There is a key called 'Layout' and it is in Decimal.
The default value of English ROM is 20409, and Chinese ROM is 20404 (both are in hexadecimal).
The suitable value for German Hermes keyboard is 20407 (132103 in decimal).
Probably Hermes use 20+country ID (409=WWE, 407=German, 404=Trad. Chinese, etc...) format for keyboard layout value.

The above settings does not work with the latest Hermes firmware, the following is required.

[HKEY_CURRENT_USER\keyboard layout\Preload]
"Default"="e0010414"
[HKEY_CURRENT_USER\keyboard layout\Preload\1]
"Default"="e0010414"
[HKEY_LOCAL_MACHINE\Software\Oem\Qwerty]
"Layout"="132116"
The last setting is the same as in the above solution
These settings are for Norwegian keyboard, country code : 0414
Tested on fw. 1.31.502.1
Improve BT A2DP sound quality

[HKLM/Software/Microsoft/Bluetooth/A2DP/Settings]
Add new dword, Value name=BitPool; Value data=48 (Decimal)
Modify, Value name=UseJointStereo; Value data=0 (Decimal, Originally 1)
For BitPool:
Microsoft suggests the following bitpool values for optimal buffer sizes.
30 - Low audio quality
40 - Medium audio quality
48 - High audio quality
58 - Excellent audio quality
Chose one you like. I think 48 is good enough.
For UseJointStereo: use 0 instead of 1, then you got the real stereo.
Show Network Operator Name in today screen

Restoring Today Item: WiFi, BT and Phone Connection Status
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Today\Items] Create "Wireless" use Key "Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
  • Enable clicking on the today plugin above open Comm Manager
[HKEY_LOCAL_MACHINE\ControlPanel\WrlsMgr] Create key "Redirect" "Redirect"= "\Windows\CommManager.exe"
Restore clock on top bar

[HKLM\Software\Microsoft\Shell\]
"ShowTitleBarClock"=1 (enable)
"ShowTitleBarClock"=0 (disable)
PocketIE Cache in storage card

Create these folders:
\Storage Card\Pocket IE\Temporary Internet Files
\Storage Card\Pocket IE\Cookies
\Storage Card\Pocket IE\History
Add the following registry keys, string data type:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\Storage Card\Pocket IE\Temporary Internet Files"
"Cookies"="\Storage Card\Pocket IE\Cookies"
"History"="\Storage Card\Pocket IE\History"
Disable flashing service LEDs

[HKLM\Drivers\BuiltIn\AllLEDMgr]
"Index"=0 Note! Disables vibrating.
Adding disconnect GPRS/UMTS button

To add Disconnect button and a timer display showing how long GRPS is in use for the session: HKLM\ControlPanel\Phone\Flags2 = 16 (DWORD decimal) To have only Disconnect button: HKLM\ControlPanel\Phone\Flags2 = 8 (DWORD decimal) To disable both the Disconnect button and the timer: HKLM\ControlPanel\Phone\Flags2 = 0 (DWORD decimal)
Disable annoying beeps when changing in-call volume

There are actually 3 different sounds in play here: the one at the bottom end of the slider (quietest), the one in the middle posisitions (standard), and the one at the top end of the slider (loudest). These are handled by 3 registry keys: HKCU\ControlPanel\Sounds\LoudestInCallVolume
HKCU\ControlPanel\Sounds\QuietestInCallVolume
HKCU\ControlPanel\Sounds\StandardInCallVolume Within each of these keys the default 'Script' value is 'p' for 'play', change the 'Script' value to blank (erase the 'p').
Change ringtone/vibrate/LED flash characteristics

If you would like more control over how your device rings/vibrates/flashes its LEDs on events, you can can change the Script values of these events.
For example, for an incoming call performing 'activate device, play ringtone, wait 3 seconds, repeat':
HKCU\ControlPanel\Sounds\RingTone0\Script = "apw3r" (REG_SZ string, no quotes)
For performing 'active device, set volume to 33%, play ringtone, set volume to 67%, play ringtone, set volume to 100%, play ringtone (no repeat)':
HKCU\ControlPanel\Sounds\RingTone0\Script = "ac33pc67pc100p" (REG_SZ string, no quotes)
The following are the full codes available to you.
Please note that all the codes are executed simultaneously except after a ringtone play / wait code. E.g. 'v1p' will vibrate and play at the same time, while vibrating for 1 second. But 'pv1' will play the ringtone through all the way first, then start vibrating for 1 second. a = activate device
cN = set volume to N in percentage max volume
fN = flash notification LED for N seconds
p = play ringtone. Note that this will play the ringtone all the way through before continuing with the next code.
r = repeat. Note that this should be the last code in your Script string, if used at all. The repeat will be from the most recent a. So: v3apr will vibrate once then repeat the ring signal.
vN = vibrate for N seconds
wN = wait for N seconds. Note that the device will wait this long before continuing with the next code.

Tweaks and Hacks - htc

Posted by krsuncom
링크2007. 8. 18. 10:31

원본 : 요기

네스팟 스윙 : http://pda.nespot.com/240/
드림위즈 PDA : http://p.dreamwiz.com/
TODAYSPPC Mobile : http://m.todaysppc.com/
ProPOZ 모바일사이트 : http://m.propoz.co.kr/
ZDNet Korea : http://zdnet.co.kr/pda
Mobile PDA 튜닝폰 : http://mpda.pe.kr/pda/
서울 버스 종합 관리 시스템 : http://mobile.bus.go.kr/pda/
서울지방경찰청 종합교통정보센터(CCTV) : http://210.100.168.33/ticker/pda/web/pda_main.asp
인천국제공항정보 PDA서비스 : http://www.airport.or.kr/pda/Kor/ipaq/index.jsp
PDANOTES 클리핑 : http://pdanotes.net/clip/
국가지식정보 통합검색 : http://pda.knowledge.go.kr/index.jsp
네이버 PDA : http://pda.naver.com/
네이버 카페iN : http://cafe.pda.naver.com/PdaMyClubList.nhn
다나와 - 쇼핑의 시작 : http://pda.danawa.com/
디지털바다낚시 : http://pda.dinak.co.kr/nespot/index.php
모바일 페이지 검색 엔진 Mohoo : http://mohoo.com/
무선 초고속 인터넷 NESPOT-service : http://www.nespot.com/pda/240/
여권, 전세계 비자정보 : http://visa-passport.com/m/
인크루트 PDA : http://pda.incruit.com/
일반웹을 pda용으로 변환 보여줌 Skweezer Home : http://www.skweezer.net/
파코즈하드웨어 PARKOZ HARDWARE : http://pda.parkoz.com/
bakion's clip : http://clip.bakion.com/
CINELINe films online : http://www.cineline.co.kr/mobile/default.asp
e-Station main : http://m.e-station.com:7202/login.jsp
Gmail에 오신 것을 환영합니다. : https://www.google.com/
Google-Enter a URL(PDA용으로 웹페이지 변환) : http://www.google.com/gwt/n
Google-Mobile : http://www.google.com/xhtml
Google-pda검색 : http://www.google.co.kr/pda
http--pda.daum.net : http://pda.daum.net/
http--pdamon.com-news- : http://pdamon.com/news/
http--www.kpug.net-pda : http://www.kpug.net/pda/
ibrary - 여러분들의 온라인 도서관! : http://www.ibrary.co.kr/
jumsim.com_PDA : http://www.jumsim.com/pda/index.htm
PDA용 CableTV 방송편성표 : http://ssrnet.snu.ac.kr/~gypark/offview/catv/
조흥은행-PDA화면 : http://www.chb.co.kr/kor/pda/main.html
PDANOTES.NET : http://w.pdanotes.net/
자동차보험의 모든것 : http://www.insuworld.co.kr/isw/mobile/index.htm
Welcome to korea.internet.com : http://korea.internet.com/pda/
싸이월드 : http://swing.cyworld.nate.com

투데이스피피시

Posted by krsuncom
개발이야기2007. 8. 14. 11:02

 

How to develop and test device drivers in Windows CE 5.0

by Mike Hall (Oct. 25, 2005)
Foreword: This article by Mike Hall, a technical product manager on Microsoft's Windows CE team, provides an introduction to developing and testing a Windows CE 5.0 device driver. It provides step-by-step instructions for creating a stream driver, creating a custom Windows CE Test Kit (CETK) test, and writing an application to test the driver. It will take approximately 60 minutes to complete.
Note: before beginning, download Windows CE 5.0 Embedded Development Labs.msi from the Microsoft Download Center.


Part 1: Setting Up a Device Driver



In this exercise, you will use Platform Builder to add a project that will act as a device driver.
Before you begin the process of writing drivers, you should understand the purpose of a device driver. Drivers abstract the underlying hardware from the operating system, and better still from an application developer. An application developer shouldn't need to know the specifics of your display hardware or your serial hardware -- for example, whether a serial device is implemented in a Universal Asynchronous Receiver/Transmitter (UART) or a field-programmable gate array (FPGA). For the most part, it makes no sense for an application developer to need to know how the hardware is implemented.

Microsoft Windows exposes application programming interfaces (APIs) for a developer to call into the hardware without needing to know what the physical hardware is. For example, to write to a serial port, an application developer simply calls CreateFile( ) on COMx (where x donates the serial port number you want to open, for example COM1 for serial port 1), calls WriteFile( ) to write some bytes of data to the serial port, and then calls CloseHandle( ) to close the serial port. The same sequence of APIs works no matter what the underlying serial hardware is (or which Windows operating system you are running).
The same is also true of other APIs: If you want to write to a line to the display surface, you would simply call PolyLine( ), MoveToEx( ), or LineTo( ). As an application developer, for the most part, you don't need to know what the display hardware is. There are APIs to call that will return the dimensions of the display surface, the color depth, and so on.
The good news is that developers have a consistent, well-known set of APIs to call. These APIs abstract their application from the underlying hardware. This is crucial because an application developer has no way of knowing whether the application will run on a laptop, Tablet PC, or desktop computer. Whether the computer is running at 1024x768 or 1600x1200, the application developer can query the screen resolution and color depth at run time and therefore doesn't need to build the application to run only on specific hardware.
A driver is simply a dynamic-link library (DLL). DLLs are loaded into a parent process address space; the parent process can then call any of the interfaces exposed from the DLL. The driver is typically loaded by its parent process through a call to LoadLibrary( ) or LoadDriver( ). LoadDriver not only loads the DLL into the parent process address space, but also makes sure the DLL isn't paged out.
How does a calling process know which APIs or functions are exposed from your DLL or driver? The parent process calls GetProcAddress( ), which takes the name of a function and the hInstance of the loaded DLL. The call returns a pointer to the function, if it exists, or NULL if the function is not exposed from the DLL.
Stream drivers expose a well-known set of functions. For a stream driver, you want to be able to write a stream of bytes to the device, or read a stream of bytes from the device. Therefore, in the serial port example used earlier, you would expect the following set of functions to be exposed from your driver: Open, Close, Read, and Write. Stream drivers expose some additional functions: PowerUp, PowerDown, IOControl, Init, and DeInit.
You can use an existing operating system image for the emulator platform (the Basic Lab MyPlatform platform is ideal). You can then add your DLL/driver project to the platform.
After the platform is built and downloaded (this shows that the operating system starts and runs well), you need to create your skeleton driver. You can use Platform Builder New Project or File command on the File menu to create a Microsoft Windows CE DLL. There is no difference between creating a DLL to expose functions or resources and creating a DLL to be used as a driver; the only difference is which functions the DLL exposes, and how the DLL is registered or used on the platform.
As an aside, one way to create internationalized applications is to create a base application that contains one set of core language strings, dialog boxes, and resources, and then create a number of external DLLs, each of which contains the dialog boxes, strings, and resources for a specific locale. The application can then load the appropriate language resources on the fly. You can add languages to the application by simply adding DLL files. This and other interesting topics are described in the book Developing International Software available on the Microsoft Press Web site.
To add a project that will act as the device driver

  1. Use Platform Builder to open the existing MyPlatform workspace.
  2. On the File menu, click New Project or File.
  3. Select WCE Dynamic-Link Library, give it an appropriate name (for example, StreamDrv), and then click OK, as shown in the following illustration.

  4. On the page shown in the following illustration, fill in as much or as little information as you want, and then click Next.

  5. Click A simple Windows CE DLL project, as shown in the following illustration.

  6. Click Finish to complete the wizard.
    At this point, the DLL contains only an empty DllMain function. You can expose functions to be called by an application, expose resources (perhaps to make this part of a language/culture-aware application), or make this into a device driver. In this article, you'll use the Windows CE Stream Driver Wizard to create your skeleton stream driver.
    In Windows CE, stream drivers are opened just like files, and are opened by means of a unique three-letter prefix (for example, COM).
  7. Choose a unique three-letter identifier for your driver. In the Location box, type the full path for the stream driver that you created previously. Or, use the browse button to browse to the PBWorkspaces directory in your Platform Builder installation, find the platform that you created previously, and then find the name of the stream driver (in the earlier example, this was PBWorkspaces\TuxPlat\StreamDrv).
  8. In the Driver Filename box, type a name for the driver. As shown in the following illustration, use the same name that you used earlier (StreamDrv) to ensure that the original file created in Platform Builder is overwritten.

  9. Press Go, and the stream driver source will be generated.

Part 2: Testing the Stream Driver Test Code



You have now written the basic code for a custom stream driver for Windows CE. At the moment, the driver isn't connected to any hardware.
After the driver is written, you need to provide a way for developers to test it. Windows CE ships with a Windows CE Test Kit (CETK), which provides driver tests for a range of driver types, including networking, Bluetooth, serial, and display. The driver that you wrote is a custom stream driver that doesn't expose the same functionality as existing driver tests, so you need to write a custom test for the driver. Although you could just write an application to exercise the driver, it's perhaps better to provide a CETK module that can be used during development and shipped to customers to test the driver on shipping hardware.
In this part of the exercise, you will perform the following procedures:
  • Create a skeleton Tux module
  • Add test code for a custom driver to the Tux DLL
  • Rebuild an operating system
  • Set a breakpoint
To create a skeleton Tux module
  1. In Platform Builder, on the File menu, click New Project or File.
  2. Select WCE TUX Dynamic-Link Library, type TuxTest as the project name, enter a location, click Workspace Project, and then click OK, as shown in the following illustration. (In practice, you can choose either project type; for this article, click Workspace Project).

  3. On the page shown in the following illustration, fill in as much or as little information as you want, and then click Next.

  4. Read the information on the screen shown in the following illustration, and then click Next.

  5. On the final page, you can optionally select CETK under Release Type, as shown in the following illustration. This option turns off optimizations for retail binaries to increase debugging productivity. Click Finish.

  6. Click View | File View, and then expand the Projects tree to show the tux source, as shown in the following illustration.

    The important files to note in the preceding illustration are:

    • ft.h -- This file contains the function table used by the tux DLL.
    • test.cpp -- This file contains the test procedures called from the function table.
    • TuxStreamTest.cpp -- This file contains DLLMain and ShellProc, the latter of which is called from Tux.exe.

To add the custom driver test code to the Tux DLL
  1. Open the source Test.cpp.
  2. Use CodeClip to get the Tux_Custom_Test | TuxCode source.
  3. Replace the contents of the function TestProc with the code from CodeClip.
    You will notice that the code in Test.cpp loads a driver called Demo.dll. For this article, you created a driver called StreamDrv. You will need to modify the source to load your StreamDrv.dll driver.
  4. Locate the source in Test.cpp that calls LoadLibrary, and then modify the name of the driver being loaded from Demo.dll to StreamDrv.dll.
  5. In the Platform Builder File View, right-click the TuxTest project, and then click Build Current Project.
    You also need to add the Windows CE Test Kit component from the catalog.
  6. Under Device Drivers, locate the Windows CE Test Kit component in the catalog, and then select Add the Windows CE Test Kit to add the component to your platform.
Note Adding the component to your platform doesn't add any files to the final operating system image; it adds the Clientside files to the build release folder. From Platform Builder, you can download the Clientside application and run the application on your target device.
To rebuild your operating system
  • In Platform Builder, select Build OS | Sysgen.
    The build process will take approximately five minutes to complete.
It would be useful to set a breakpoint in the entry point of the stream driver to see when the driver is loaded.
To set a breakpoint
  1. Click File View, open the StreamDrv project, and then open Source files.
  2. Locate and open StreamDrv.cpp.
  3. Locate DllMain, and then locate and click the switch statement.
  4. Set a breakpoint by pressing F9.
  5. Download the operating system to the emulation environment by clicking Target | Attach.
    You will see the following debug output, and the breakpoint will fire. Note that this happens long before the user interface (UI) of the operating system has loaded.
    4294780036 PID:23f767b6 TID:23f767e6 0x83fa6800: >>> 
    Loading module streamdrv.dll at address 0x01ED0000-0x01ED5000
    Loaded symbols for
    'C:\WINCE500\PBWORKSPACES\DRVDEMO\RELDIR\EMULATOR_X86_DEBUG\
    STREAMDRV.DLL'
  6. Disable the breakpoint by clicking the switch statement, and then pressing F9.
  7. Allow the operating system to continue loading by pressing F5.
You've now built a Windows CE 5.0 operating system that contains a custom stream driver, and you've seen the driver load during the boot sequence of the operating system.

Part 3: Examining the Driver



In this exercise, you will perform the following procedures:
  • Use a command-line tool to look at the exposed functions from the driver
  • Use the Remote System Information tool to examine the driver
  • Determine that the driver is loaded
The first way to examine the device driver that you created is to look at the exposed functions from the driver. There is a command-line tool that ships with Windows CE called Dumpbin, which you can use to examine the imports to an application or module, or to examine the exports from a DLL (or driver).
To use the command-line tool to look at the exposed functions from the driver
  1. In Platform Builder, click Build OS | Open Release Directory. This action opens a Command Prompt window in the build release folder for your current workspace.
  2. Type dumpbin 뻛xports StreamDrv.dll
    The following illustration shows how the output looks. You can see that all of the expected stream driver functions are exposed from the driver; functions are exposed from a DLL through the project's .def file.

  3. Close the Command Prompt window by typing Exit
    The contents of the StreamDrv.def file are as follows.
    LIBRARY DemoDriver
    EXPORTS
    DEM_Init
    DEM_Deinit
    DEM_Open
    DEM_Close
    DEM_IOControl
    DEM_PowerUp
    DEM_PowerDown
    DEM_Read
    DEM_Write
    DEM_Seek
    CustomFunction
    CustomFunctionEx
The second way that you can examine the driver is through the Remote System Information tool.
To examine the driver through the Remote System Information tool
  1. In Platform Builder, click Tools | Remote System Information.
  2. Select Windows CE Default Platform | Default Device, and then click OK, as shown in the following illustration.

    This procedure connects the Remote System Information application to the current active platform being used by Platform Builder. The following illustration shows the result.

You can also use the list of loaded modules to determine that your driver is loaded.
To determine that the driver is loaded

  • In Platform Builder, use the Target Control window (gi mod), or View | Debug Windows | Modules and Symbols.
    The following illustration shows the result of this procedure.


Part 4: Using the Windows CE Test Kit



The Windows CE Test Kit contains a device-side component and a desktop component. The device side component is called Clientside.exe, which you added to your workspace by adding the CETK component from the catalog. Note that adding the Clientside.exe application to the workspace doesn't add any files to the final operating system image, but it does copy the application to the build release folder.
Before running the CETK on the desktop computer, you need to start the Clientside.exe application on the device. The reason the tools are not linked (like a remote tool) is that the CETK will also operate on shipping (retail) devices, such as the Pocket PC.
In this part of the exercise, you will perform the following procedures:
  • Examine the Windows CE Test Kit user interface
  • Run one of the standard tests
To examine the Windows CE Test Kit user interface
  1. In Platform Builder, on the Tools menu, click Windows CE Test Kit.
    This step starts the Windows CE Test Kit application, as shown in the following illustration. Note that this is not a standard remote tool. Most of the remote tools that ship with Windows CE use the Kernel Independent Transport Layer (KITL), a transport that abstracts the tools from the underlying communication hardware so that the tools will run over Ethernet, serial, 1394, USB, or other transports.
    The Windows CE Test Kit typically connects over sockets, although for Windows CE 5.0, the tools have been updated to also support KITL.

  2. In the Windows CE Test Kit, click Connection | Start Client.
    This step displays the Device Connection dialog box, where you can choose whether to connect over sockets or KITL.
  3. Make sure that the Use Windows Sockets for the client/server communication check box is cleared, as shown in the following illustration.

  4. Click Connect.
    In the standard user interface for remote tools (KITL), select Windows CE Default Platform | Default Device, and then click OK, as shown in the following illustration.

    This procedure starts Clientside.exe on the target device and makes a connection to the target. After the connection is made, the CETK enumerates the supported devices on the target platform, and nonsupported devices are disabled in the CETK.
    After the CETK has connected to the target and enumerated devices, the UI looks similar to the following illustration. Notice that certain hardware categories, such as Bluetooth, IR Port, and Modem, are disabled.

Before adding a custom test to the CETK, you can run one of the standard tests to see how the test behaves.
To run a standard test

  1. In the CETK, expand Windows CE (x86).
  2. Locate and expand Serial Port.
  3. Right-click Serial Port Driver Test, and then click Quick Start.
This step runs just this one test without also running the other selected tests. The UI indicates that the test is in progress, as shown in the following illustration.

The CETK provides updates on the progress of the test and the outcome of the test. You can also examine the debug output in Platform Builder to see the progress of the test, as shown in the following example.

405910 PID:83d4ee4a TID:83ea5a8a *** Test Name:      
Set event mask and wait for thread to close comm port handle
405920 PID:83d4ee4a TID:83ea5a8a *** Test ID: 1007
405920 PID:83d4ee4a TID:83ea5a8a *** Library Path: \serdrvbvt.dll
405920 PID:83d4ee4a TID:83ea5a8a *** Command Line:
405920 PID:83d4ee4a TID:83ea5a8a *** Result: Passed
405920 PID:83d4ee4a TID:83ea5a8a *** Random Seed: 15595
405930 PID:83d4ee4a TID:83ea5a8a *** Thread Count: 1
405930 PID:83d4ee4a TID:83ea5a8a *** Execution Time: 0:00:05.110
405930 PID:83d4ee4a TID:83ea5a8a ***
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If the CETK UI indicates that the serial port test has failed on the emulator (as shown in the following illustration), the failure may not be due to a complete failure of every test. It may indicate that only a portion of the overall test suite has failed, which may actually be expected behavior.

  1. Right-click Serial Port Driver Test [Failed], and then click View Results.
    A window like that shown in the following illustration appears.

    Looking at the results shown in the preceding illustration, you can see that 10 individual tests have been run. All of these tests have passed except for Set and verify receive timeout.
    To get more information, you can click the individual test.


Part 5: Creating a Custom CETK Test



By using the Platform Builder User-Defined Test Wizard, you can create a custom CETK test. This test will verify the exported functions from a custom stream driver (which you've also added to the platform).
In this part of the exercise, you will perform the following procedures:
  • List the custom stream driver test in the CETK
  • Run the custom stream driver test
To list the custom stream driver test in the CETK
  1. In the CETK, click Tests | User Defined.
    This step starts the User-Defined Test Wizard. The first page of the wizard is for information only.
  2. Click Next, as shown in the following illustration.

  3. Click Add a New Test, and then click Next, as shown in the following illustration.

  4. Enter the following information, and then click Next:
    • In the Name of Test box, type Custom Stream Driver Test
    • In the Tux Module (DLL) box, browse to
      C:\Wince500\PBWorkspaces\MyPlatform\RelDir\Emulator_x86_Debug,
      and then select either test.dll or TuxTest.dll (this depends on the name of the Tux test you used in Platform Builder).
    • In the Command Line box, leave the default setting for the current test.
    • In the Processor box, type x86
    The following illustration shows how the information appears on the current wizard page.

  5. Click Copy the files to the directory for user-defined tests, and then click Next, as shown in the following illustration.
You want to copy the custom driver test (your DLL) to the folder for user-defined tests. If you were to delete your existing workspace, the custom driver test would still be intact.

  1. Click Next, as shown in the following illustration.

  2. Click Finish, as shown in the following illustration.
    The CETK application doesn't automatically refresh with the new tests. You need to resynchronize the desktop application to view the newly added test.

  3. Right-click Windows CE (x86), and then click Redetect Peripherals.
    This procedure adds a new driver category called User Tests. You've added only one test, so when you expand this item, you will see only Custom Stream Driver Test.
    Note The DLL for the custom stream driver test has been copied to the following location: C:\Program Files\Windows CE Platform Builder\5.00\CEPB\wcetk\user\x86.
To run the custom stream driver test
  1. In the list of available tests, expand User Tests.
  2. Right-click Custom Stream Driver Test, and then click Quick Start.
    Make a note of the following debug information being displayed in Platform Builder.
    1162630 PID:3c92032 TID:3efe3ea *** TEST STARTING
    1162630 PID:3c92032 TID:3efe3ea ***
    1162630 PID:3c92032 TID:3efe3ea *** Test Name: Sample test
    1162630 PID:3c92032 TID:3efe3ea *** Test ID: 1
    1162640 PID:3c92032 TID:3efe3ea *** Library Path: \test.dll
    1162650 PID:3c92032 TID:3efe3ea *** Command Line:
    1162650 PID:3c92032 TID:3efe3ea *** Random Seed: 26648
    1162650 PID:3c92032 TID:3efe3ea *** Thread Count: 0
    1162650 PID:3c92032 TID:3efe3ea ***
    vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    1162660 PID:3c92032 TID:3efe3ea test:
    ShellProc(SPM_BEGIN_TEST, ...) called
    1162660 PID:3c92032 TID:3efe3ea BEGIN TEST:
    "Sample test", Threads=0, Seed=26648
    1162690 PID:3c92032 TID:3efe3ea
    Custom Stream Driver Test Starting
    1162690 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Loading Demo.DLL
    1162710 PID:3c92032 TID:3efe3ea 0x83d3dc28: >>>
    Loading module streamdrv.dll at address 0x01ED0000-0x01ED5000
    1162720 PID:3c92032 TID:3efe3ea StreamDrv - DLL_PROCESS_ATTACH
    1162720 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Loaded Demo.DLL OK
    1162740 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking Interfaces...
    1162740 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Open
    1162740 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Open OK
    1162740 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Close
    1162750 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Close OK
    1162750 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Read
    1162750 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Read OK
    1162770 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Write
    1162790 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Write OK
    1162790 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Init
    1162790 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Init OK
    1162790 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Deinit
    1162800 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Deinit OK
    1162800 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_PowerUp
    1162800 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_PowerUp OK
    1162800 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_PowerDown
    1162810 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_PowerDown OK
    1162810 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_IOControl
    1162810 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_IOControl OK
    1162810 PID:3c92032 TID:3efe3ea
    Custom Driver Test - Checking DEM_Seek
    1162820 PID:3c92032 TID:3efe3ea
    Custom Driver Test - DEM_Seek OK
    1162830 PID:3c92032 TID:3efe3ea StreamDrv - DLL_PROCESS_DETACH
    1162840 PID:3c92032 TID:3efe3ea 0x83d3dc28:
    <<< Unloading module streamdrv.dll at address 0x01ED0000-0x01ED5000
    1162870 PID:3c92032 TID:3efe3ea test:
    ShellProc(SPM_END_TEST, ...) called
    1162870 PID:3c92032 TID:3efe3ea END TEST:
    "Sample test", PASSED, Time=0.180
    1162870 PID:3c92032 TID:3efe3ea ***
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    1162870 PID:3c92032 TID:3efe3ea *** TEST COMPLETED
    1162880 PID:3c92032 TID:3efe3ea ***
    1162880 PID:3c92032 TID:3efe3ea *** Test Name: Sample test
    1162880 PID:3c92032 TID:3efe3ea *** Test ID: 1
    1162890 PID:3c92032 TID:3efe3ea *** Library Path: \test.dll
    1162890 PID:3c92032 TID:3efe3ea *** Command Line:
    1162890 PID:3c92032 TID:3efe3ea *** Result: Passed
    1162900 PID:3c92032 TID:3efe3ea *** Random Seed: 26648
    1162910 PID:3c92032 TID:3efe3ea *** Thread Count: 1
    1162910 PID:3c92032 TID:3efe3ea *** Execution Time: 0:00:00.180
    The test completed without any warnings or errors. You can also examine the test results in the client.

Part 6: Determining Who Owns the Stream Driver



So far, you've seen the custom stream driver load through Platform Builder debug messages, through a breakpoint in the driver source, and through a custom CETK test.
In this part of the exercise, you will perform the following procedures:
  • Use the Remote Process Viewer to determine which process is loading the driver
  • Display information
To use the Remote Process Viewer to determine which process is loading the driver
  1. In Platform Builder, click Tool | Remote Process Viewer.
    The Process Viewer application displays a list of all the currently running processes, in addition to the DLLs or modules loaded into each process address space.
  2. Locate and select device.exe.
The following illustration shows the list of DLLs loaded into the Device.exe process address space. Device.exe is the device driver manager for Windows CE.

To display information
By using Platform Builder, write a Microsoft Win32 application that writes data to the custom stream driver and reads back and displays the information. You can use the MessageBox API to do this.
The APIs that you need for this task are:

  • CreateFile
  • WriteFile
  • ReadFile
  • CloseHandle
  • MessageBox

Summary


  • Drivers are simply DLLs.
  • Drivers are mapped into the Device.exe process address space.
  • Drivers expose a known set of interfaces.
  • It's relatively easy to add a device driver to a Windows CE operating system image.
  • The Windows CE Test Kit is available to assist with the development and debugging of a platform.
  • Writing custom CETK tests is fairly easy.


Copyright ?2005 Microsoft Corp. All rights reserved. This article was initially published on Microsoft's MSDN website. Reproduced by WindowsForDevices.com with permission.

Related stories:

How to develop and test device drivers in Windows CE 5.0

Posted by krsuncom
링크2007. 8. 8. 20:50

 

투데이PPC

http://www.todayppc.co.kr
국내 최대 Pocket PC 사용자 커뮤니티

네스팟 스윙

http://www.nespot.com/web/swing
/swing_01.htm

네스팟 스윙 서비스 홈페이지

마이미츠


http://www.mymits.net
삼성전자 Mits 사용자 모임

프로포즈


http://www.propoz.co.kr
싸이버뱅크 POZ 사용자 모임 커뮤니티

네이트PDA


http://pda.nate.com
다양한 PDA 정보 공유 커뮤니티

넥사모

http://www.nexamo.net
삼성전자 넥시오 사용자 커뮤니티

세티즌


http://www.cetizen.com
휴대폰 및 모바일 단말기 커뮤니티

MissPDA


http://www.misspda.com
모바일 사용자 커뮤니티

PDA Bench


http://www.pdabench.com
모바일 및 디지털 장비 커뮤니티


HandandGo

PocketPC.com


PocketGear.com

MobiPocket


Pocket PC Magazine

Pen Computing


Gadgeteer

Unwired-I.Net


MedicalPocketPC.com

InfoSync


PDASquare

Windows Mobile – 커뮤니티

Posted by krsuncom
링크2007. 8. 8. 20:48

 

Windows Mobile 기반 Smartphone 관련 링크

관심 분야 여행

Windows Mobile 기반 Smartphone 사용자에게 멋진 다운로드에서부터 즉각적인 정보 액세스, 단말기 소프트웨어 및 업데이트에 이르는 모든 것을 제공하는 다양한 사이트에 방문해 보십시오. 아래 나열된 사이트는 Microsoft Corporation의 제휴 업체가 아닙니다.

사이트 항목

비즈니스 뉴스/금융

비즈니스 동향 및 월 스트리트와 연결하십시오.

엔터테인먼트

최신 엔터테인먼트 뉴스에서 동영상 게임 및 TV 시간표까지 모든 것을 찾아 보십시오.

게임

첨단 게임 사이트에 연결해 Windows Mobile(tm) 기반 Smartphone을 위한 새로운 게임을 확인하십시오.

정보 사이트: 디렉터리 서비스/날씨/여행

Windows Mobile(tm) 기반 Smartphone과 함께하면 날씨 확인, 차량 렌트, 식당 찾기 등과 같은 필요한 모든 작업을 이동 중에도 손쉽게 할 수 있습니다.

국제 Windows Mobile 커뮤니티 사이트

전세계 모든 Windows Mobile 사이트입니다.

모바일 상거래

비즈니스 및 상거래용 Windows Mobile(tm) 기반 Smartphone 응용 프로그램에 대해 자세히 배워 보십시오.

뉴스

전세계 권위 있는 발행물 및 서비스의 온라인 뉴스를 살펴 보십시오.

벨소리

다운로드할 수 있는 멋진 벨소리가 있는 사이트에 방문해 보십시오.

설치 및 개인 설정

Smartphone의 설치 및 개인 설정을 도와 줍니다.

소프트웨어

다음 사이트를 방문하여 Smartphone용 소프트웨어 및 업데이트를 다운로드하십시오.

Smartphone 애호가

Windows Mobile(tm) 기반 Smartphone 사용자들의 다양한 관심 항목을 다루고 있는 사이트를 확인하십시오.

Smartphone Thoughts for Windows Mobile
많은 사랑을 받고 있는 Windows Mobile용 Pocket PC Thoughts 사이트를 제작한 신뢰할 수 있는 소스에서 뉴스, 의견 및 포럼을 즐기십시오.
Modaco
가장 활동적인 영어 버전 Windows Mobile 기반 Smartphone 포럼에 가입하고 수많은 초기 화면과 벨소리도 다운로드하십시오.
Cool Smartphone for Windows Mobile
Windows Mobile 기반 Smartphone 뉴스가 가장 먼저 시작되는 유럽에서 최신 뉴스를 받아 보십시오.
PPCW.Net
Windows Mobile(tm) 기반 Smartphone 및 Pocket PC와 관련된 유용한 정보로 가득한 최신 사이트도 방문하십시오.
Smartphone Themes for Windows Mobile
멋진 소프트웨어를 다운로드하고 다른 사이트 리뷰에도 연결하십시오.
Mobway.com
소프트웨어, 벨소리 및 기타 다운로드 링크가 마련된 Windows Mobile(tm) 기반 Smartphone 애호가 사이트입니다.
기타 Windows Mobile 기반 Smartphone 애호가 사이트

Windows Mobile - Smartphone 커뮤니티: 관련 링크

Posted by krsuncom
블랙잭이야기2007. 8. 7. 16:44
Posted by krsuncom
개발이야기2007. 8. 6. 19:08

원문: 요기

HKLM/Software/Microsoft/Bluetooth/A2DP/Settings
Add new dword, Value name=BitPool; Value data=48 (Decimal)
Modify, Value name=UseJointStereo; Value data=0 (Decimal, Originally 1)
For BitPool:
Microsoft suggests the following bitpool values for optimal buffer sizes.
30 - Low audio quality
40 - Medium audio quality
48 - High audio quality
58 - Excellent audio quality
Chose one you like. I think 48 is good enough.
For UseJointStereo: use 0 instead of 1, then you got the real stereo.......
BTW, if you lost your modification after soft reset, you might try to "totally" close the reg editor you use before soft reset.
And chosing an "appropriate" A2DP headset is quite important. Some just don't work well with this device

HowardForums: Your Mobile Phone Community & Resource - Bluetooth Stereo (A2DP) on Qtek 8500

Posted by krsuncom