Monthly Archives: August 2008

TomTom Navigator 7 on Telesystem TS8.5 PND

by

Prepare Telesystem registry according to Adivor.it discussion:
  • Download and Install Registry Workshop to edit the PDA registry from the PC
  • Remove SD card from the PDA
  • Perform a Reset
  • Insert the SD card –> It should be shown as “\SDMMC”
  • Edit the following registry keys:
    • HKLM/SYSTEM/EXPLORER/SHELL FOLDERS/My Documents –> “\SDMMC”
    • HKLM/System/StorageManager/FATFS/CacheSize –> “1000”
  • Copy all TomTom files inside the \SDMMC\MobileNavigator folder
  • Copy all files of the required map inside the \SDMMC\Map_Name folder
  • Rename the program “TomTom Navigator.exe” in “MobileNavigator.exe” inside “\SDMMC\MobileNavigator\” folder

If you would like to have a different home screen, install NicolMenu as indicated on Adivor forum:

  • Copy the “MENU” folder in \ResidentFlash\
  • Edit the registry key:
    HKLM/init/Launch 50 –> “\ResidentFlash\MENU\Menu3button.exe”
  • Replace the file “NicolConfig.xml” with “NicolConfig.xml.ok”
  • Edit the file “NicolConfig.xml” to point to the “TomTom Navigator.exe” file correctly

If you receive the error “Unable to start. Not enough memory is available.”, you should change the “Memory allocation” in Control Panel –> System –> Memory and slide the cursor to left.

Please note that you must not start Explorer.exe after the change of the “My Documents” folder because this will show the SD Card as “\SDMMC2”

Samsung SGH-i780 with Windows Mobile 6

by



Brand: Samsung
Manufacturer: Samsung Electronics
Model ID: i780GSMH
Codename: Mirage
Release Date: Febrary 2008

Physical Attributes
Dimensions(width x height x depth): 61.3 x 115.9 x 12.9 mm
Bounding Volume: 91.7 cubecentimetres
Mass: 120 grams (battery included)

Software Environment
Embedded Operating System: Microsoft Windows Mobile 6 Professional
Operating System Kernel: Windows CE 5.2.1929 Build 18579.0.7.0

Microprocessor, Chipset
CPU: Marvell PXA310
Width of Machine Word: 32 bit
CPU Clock: 624 MHz
CPU Core: Intel XScale
Instruction Set: ARM

Memory, Storage capacity
ROM type: Flash EEPROM
ROM capacity: 256 Mb, including 146.36Mb user-accessible non-volatile storage
RAM type: SDRAM
RAM capacity: 128 Mb, 108.24Mb accessible

Graphical subsystem
Display Type: Color transflective TFT display
Display Color Depth: 18 bit/pixel (262144 scales)
Display Diagonal: 2.5″ (64.7 millimetres)
Display Resolution: 320 x 320 (102400 pixels)
Viewable Display Area: 1.8″ x 1.8″ (45.75 x 45.75 millimetres)
Dot Pitch: 0.143 millimetre/pixel

Audio Subsystem
Audio Channel(s): stereo sound
Analog/Digital Converter(Recording): 16 bit nominal quantization 44100 Hz sampling frequency
Digital/Analog Converter(Playing): 16 bit resolution44100 Hz holding frequency
Microphone(s): mono sound
Loadspeaker(s): mono sound
Audio Output: Proprietary plug

Cellular Phone
Cellular Networks: GSM900, GSM1800, GSM1900, UMTS2100
Cellular Data Links: CSD, GPRS, EDGE, UMTS, HSDPA
Cellular Antenna: Internal antenna
Call Alert: 64 -chord melody (polyphonic)
Vibrating Alert: Supported
Speakerphone: Supported
Phone Controller: Qualcomm MSM6260
SAR: 0.514 W/kg

Control Peripherals
Positioning Device: Touchscreen & TouchPad
Primary Keyboard: Built-in QWERTY-type keyboard, 37 keys
Directional Pad: Four-way (without action button)
Scroll Wheel: Not supported

Interfaces
Expansion Interfaces: microSD, microSDHC, TransFlash, SDIO Supports High Capacity (SD 2.0/HC) memory cards with capacity of up to 32GB
USB: USB 2.0 client, Full-Speed (12Mbit/s)Proprietary connector
Bluetooth (802.15): Bluetooth 2.0, Internal antenna
Wireless LAN/Wi-Fi (802.11): IEEE 802.11b, IEEE 802.11g, 54 Mbit/sInternal antenna
Infrared Gate: Not supported

Multimedia Telecommunication
Analog Radio: Not supported
Digital Media Broadcast: Not supported

Satellite Navigation
Built-in GPS module: Supported
GPS Protocol: NMEA 0183
GPS Antenna: Internal antenna
Complementary GPS Services: Assisted GPS
Navigation Chip(set): Qualcomm MSM6260 gpsOne

Built-in Digital Camera
Sensor Type: CMOS sensor
Resolution: 1600 x1200 pixels (1.92MP)
Autofocus (AF): Not supported
Optical Zoom: 1 x
Macro Mode: Not supported
Built-in Flash: Not supported
Camcorder: 320×240 pixels
Recordable Image Formats: JPG, BMP
Recordable Video Formats: 3GPP, MPEG4

Built-in Secondary Digital Camera
Sensor Type: CMOS sensor
Resolution: 640 x480 pixels (0.31MP)
Camcorder: 320x240pixel
Recordable Image Formats: JPG, BMP
Recordable Video Formats: 3GPP

Power Supply
Battery Technology: Lithium-ion battery
Battery Build: removable
Estimated Battery Life: 7 hours
Battery Capacity: 1000 mAh
Estimated Average Current: 143 mA

Additional Details
GPRS Class 10
Samsung Finger Mouse touchpad/D-Pad combined positioning device voice command
Bluetooth stereo audio profile (A2DP)
Spare battery in the packet

More information at Samsung Mobile and a full review at GSM Arena

TomTom Navigator 7 on Samsung i780

by
TomTom 7 was released on a HTC Diamond Mobile Phone.
So there will be a new version that should works fine on Windows Mobile devices.
Configure Samsung i780 internal GPS settings:
  • Start Menu –> Settings –> System tab –> External GPS
  • Program Tab = COM8
  • Hardware Tab = COM9 & 4800

Install and Configure GPS Proxy:

  • Menu –> Extensions –> Delete “Garmin Protocol Output” as extensions
  • Select “NMEA Input” in the GPS Provider –> Configure button
  • Set “GPS COM Port” = COM8
  • Enable “Mirror GPS To Output Port”
  • Set “Output COM Port” = COM1
  • Menu –> “Virtual COM Ports”
  • Set “Virtual COM Port” = COM1 by press Add button
  • Menu –> Settings
  • Enable “Run External App after Proxy Startup”
  • Set “External Application” = “TomTom Navigator.exe”

Install TomTom 7:

  • Following the XDA Developers instruction
  • Configure GPS settings to “Other GPS NMEA”
  • GPS Transmission Rate = “4800 Baud”
  • GPS Port = “GPSProxy Virtual COM Port on COM1:”

Quick summary of the serial port communication between GPS and TomTom:

NMEA GPS 4800 Samsung i780 GPS Proxy TomTom 7

Windows 7 & Windows Server 2008 R2 & Windows NT 7.0

by

“Okay, I don’t know how someone on our side could have miscommunicated this or if you are purposely reporting this incorrectly, but let’s be clear on this: Windows 7 Server is and has always been Windows Server 2008 R2.
“Furthermore, Windows 7, despite it’s rather pretentious sounding code name (a result of Sinofsky’s like of big round numbers) is NOT Windows NT 7, but rather 6.1(current builds are numbered 67xx as a direct continuation of the longhorn codebase). Put simply, it is not a big jump as a codebase revision and the new changes, on both the client and server, will be focused on user features, not core OS components. The big core OS changes are WDDM 2 and a kernel scheduler update to remove the simple bitmask enumeration of processors so that the OS can schedule more than 64 concurrent threads.
“Finally, and I can’t be more clear on this, ‘Windows 7′ client and Windows Server 2008 R2 will RTM simultaneously (and just so you are 100% clear on this) and are based on exactly the same codebase (just as Vista SP1 and Server 2008 are based on an identical core OS codebase).
“As for the next major release (meaning a full revision of the NT codebase) that will not occur until well after the current Win7 wave.”

More info at ZDNet

99942 Apophis (2004 MN4) – Earth Impact Risk Summary

by

Researchers at NASA/JPL, Caltech, and Arecibo Observatory have released the results of radar observations of the potentially hazardous asteroid 99942 Apophis, along with an in-depth analysis of its motion. The research will affect how and when scientists measure, predict, or consider modifying the asteroid’s motion. The paper has been accepted for publication in the science journal “Icarus” and was presented at the AAS/DPS conference in Orlando, Florida in October of 2007. The Apophis study was led by Jon Giorgini, a senior analyst in JPL’s Solar System Dynamics group and member of the radar team that observed Apophis. The analysis of Apophis previews situations likely to be encountered with NEAs yet to be discovered: a close approach that is not dangerous (like Apophis in 2029) nonetheless close enough to obscure the proximity and the danger of a later approach (like Apophis in 2036) by amplifying trajectory prediction uncertainties caused by difficult-to-observe physical characteristics interacting with solar radiation as well as other factors.