Minggu, 09 Agustus 2009

The internal components of a typical keydrive

Usbkey internals.jpg

The internal components of a typical keydrive

This photograph shows both sides of the printed circuit board inside a typical keydrive (Seitec USB-BAR USB 1.1circa 2004), in this case an inexpensive 64 Mbyte USB2.0 device. The plastic clamshell case has been removed.

In practice the keydrive consists of only two significant components. The first is the flash memory part (item 4 in the diagram), a generic device that might as easily be found in a digital camera's memory card. The second (item 2 in the diagram) is a device which implements the USB networking and mass-storage interface, and which knows how to make a chunk of generic flash memory appear like a normal disk drive. The high degree of integration in this latter part makes small, inexpensive keydrives possible.

The parts of the device are as follows:

  1. A male type-A USB connector.
  2. An Ours Technology Inc. OTi-2168 USB 2.0 mass storage controller. This implements the USB 2.0 host controller, and provides a seamless linear interface to block-oriented serial flash devices, while hiding the complexities of block-orientation, block erasure, and wear balancing. It contains a small RISC microprocessor and a small amount of ROM and RAM. This communicates with the Hynix device over an 8-line unified address/data bus. This version is a 7x7mm 48-pin LQFP (Low Profile Quad Flat Pack) surface-mount device (info).
  3. JP1 and JP2: two unpopulated 10-pin connectors, used for testing during the keydrive's manufacture.
  4. A Hynix Semiconductor HY27USxx121M series NAND Flash memory device, featuring 4096 independently erasable blocks each providing 16 Kbytes of storage, yielding a total of 64 Mbytes of usable storage. The version used in this keydrive is a 20x12mm 48-pin TSOP1 (Thin Small Outline Package) surface-mount package (info) (datasheet).
  5. An SKC Shin Chang Electronics 12.000 MHz crystal oscillator (XTAL). The OTi device runs the output of this through a phase-locked loop to produce its main 12 MHz clock signal.
  6. A single yellow light-emitting diode (run from a pin on the OTi device) which flashes to indicate activity.
  7. A simple two-position switch, used to indicate whether the device should be in "write-protect" mode. It is shown here in the make position, indicating write-protect is off.
  8. An unpopulated space for a second TSOP1 memory package. The OTi device is capable of driving up to eight such devices. Having this second space allows the manufacturer to choose (generally on a cost basis) whether to use one or two TSOP flash parts.

Surrounding these main components are a number of tiny surface-mount resistors (many of them serving as pull-ups) and capacitors.

For a closeup of an area of this keydrive, see this image.

USB Flash Drive in Windows

Microsoft's operating system mengimplementasikan USB flash drive's Windows as USB Mass Storage Device, wield device driver usbstor.sys. Since really Windows have auto mounting's feature, and USB Flash Drive constitutes one plug and play's peripheral, Windows will try to carry on its one can maybe momentary that peripheral is plugged into USB'S socket. Windows xp and later one even have Autoplay's feature, one that concedes flash drive that was accessed as a whole to determine what content from USB Flash Drive that.

Latterly, there are many local computer virus as well as Brontok / RontokBro, PendekarBlank, and another local virus utilizes USB Flash Drive as media of virus transmission of one host goes to another host, replacing diskette. Viruses that largely walks Windows above that will get quick circulating while really Windows accesses drive teserbut to utilize proprietary autoplay feature by Windows. Hence, there is it is better to deactivate autoplay's feature, even it less just after helps to prevent broadcast virus.

USB flash drive

USB flash drive is data stored tool flash's memory NAND'S type that have integrated USB interface. Flash drive this usually gets pocket edition, demulcent, and can be read and ditulisi easily. Per November 2006, reserve for capacity USB Flash Drive there is of 128 megabyte until 64 gigabyte.

USB flash drive has a lot of excess than another data storage tool, notably diskette or solid the disk. This tool is faster, little, with greater capacity, and more gets to be relied (since have no a part one moves) than diskette.

winbox

General Information

Summary

The MikroTik RouterOS can be configured remotely, using Telnet, SSH, WinBox Console or Webbox. In this manual we will discuss how to use the interactive WinBox console.

Description

The Winbox console is used for accessing the MikroTik Router configuration and management features, using graphical user interface (GUI).

All Winbox interface functions are as close as possible to Cons

ole fun

ctions: all Winbox functions are exactly in the same hierarchy in Terminal Console and vice versa (except functions that are not implemented in Winbox). That is w

hy there are no Winbox sec

tions in the manual.

The Winbox Console plugin loader, the winbox.exe program, can

be retrieved from the MikroTik router, the URL is http

://router_address/winbox/winbox.exe Use any web browser on Windows 95/98/ME/NT4.0/2000/XP or Linux to retrieve the winbox.exe executa

ble file from Router. If your rout

er is not specifically configured, you can also type in the web-browser just http://router_address

The Winbox plugins are cached on the local disk for each Mikr

oTik RouterOS version. The plugins are not downloaded, if they

are in the cache, and the ro

uter has not been upgraded since the last time it has been accessed.

Starting the Winbox Console

When connecting to the MikroTik router via http (TCP port 80 by default), the router's Welcome Page is displayed in the web browser:


By clicking on the Winbox link you can start the winbox.exe down

load. Choose Open to start the Winbox loader program (you can

also save this program to your local d

isk, and run it from there)

The winbox.exe program opens the Winbox login window.

where:

discovers and shows MNDP (MikroTik Neighbor Discovery Protocol) or CDP (Cisco Discovery Protocol) devices.

  • logs on to the router by specified IP address (and the port number if you have changed it from the default value of 80) or MAC Address (if the router is in the same subnet), user name, and password.

  • saves the current sessions to the list (to run them, just double-click on an item).

  • removes selected item from the list.

  • removes all items from the list, clears cache on the local disk, imports addresses from wbx file or exports them to wbx file.


  • Secure Mode

    provides privacy and data integrity between WinBox and RouterOS by means of TLS (Transport Layer Security) protocol.

  • Keep Password

    Saves password as a plain text on a local hard drive. Warning

    : storing passwords in plain text allows anybody with access to your files to read the password from there.

The Winbox Console of the router:


The Winbox Console uses TCP port 8291. After logging onto the router you can work with the MikroTik router's configuration through the Winbox console and perform the same tasks as using the regular console.

Overview of Common Functions

You can use the menu bar to navigate through the router's configuration menus, open configuration windows. By double clicking on some list items in the windows you can open configuration windows for the specific items, and so on.

There are some hints for using the Winbox Console:

  • To open the required window, simply click on the corresponding menu item
  • Add a new entry

  • Remove an existing entry

  • Enable an item

  • Disable an item

  • Make or edit a comment

  • Refresh a window

  • Undo an action

  • Redo an action

  • Logout from the Winbox Console


Sabtu, 08 Agustus 2009

antara benci dan bahagia

Dunia ini semakin sempit
Itu dan aku semakin ingin pergi
Tak ada satupun cahaya dalam hening
Hati membeku dan menjadi batu
Akankah semua itu tepati janji?
Ruang maaf di hati ini sudah tak muat di
Isi dengan omong kosong mereka
Zopfan pun semakin jauh
Kalau gembira datang memang aku butuh
Yang yakin pada kabar itu
Semakin jauh itu semakin aku
Iri pada mereka yang telah
Lama menjadi bahagia dengan segudang
Virus kebencian pada diriku
Andaikan nanti aku bisa melihat mimpi
Nyata pada rasa kebahagiaan dan
Yakin akan hari esok yang bahagia.

Jumat, 07 Agustus 2009

Welcome to Deep Zoom Composer


Welcome to Deep Zoom Composer
[This topic is pre-release documentation and is subject to change in a future release. Blank topics are included as placeholders.]

With Deep Zoom Composer, you can take a collection of images of various resolutions (including large, high-resolution images) and arrange them into a composition. You can then export or publish the composition as either a single high-resolution image or a set of individual images with different resolutions. Once you export or publish your composition, you can use a standard broadband connection to quickly display and navigate a large, detailed image or a panorama of images that might otherwise be extremely slow to view.

What is Deep Zoom Composer used for?

There are many things you can do with Deep Zoom Composer, from artistic applications, such as complex photo mosaics, to business applications, such as photo galleries for real estate sites. Here are just a few potential uses:

· Mapping

· Photo galleries

· Online banner ads

· High-resolution photos

· Visual catalogs

· 3D photography

You can also use Deep Zoom Composer to share photo albums online by using the PhotoZoom service.

For more Deep Zoom e How does the Deep Zoom technology work?

Deep Zoom Composer uses the Deep Zoom technology found in Microsoft Silverlight 2 and Seadragon Ajax. When you view an image created in Deep Zoom Composer in a browser, the browser downloads only the portion of the image that you are actually viewing on your screen at that time, and at a resolution appropriate to the scale of the image. Downloading only part of the image data at a time decreases the time it takes to load the image and optimizes the viewing experience.

For more information about Silverlight 2 and Seadragon Ajax, see Exporting a composition.

xamples online, see Seadragon Ajax on Microsoft Live Labs.

Blurry-to-crisp loading

When you first view a Deep Zoom image, your browser displays a scaled-up version of a low-resolution version of the image, and then blends in higher-resolution images as they are downloaded. This is the reason for the blurry-to-crisp experience when you view an image created in Deep Zoom Composer. It is also the reason that the Deep Zoom images open quickly regardless of the file size of the image. The blurry-to-crisp behavior that you see during loading also occurs when you interact with the Deep Zoom image (for example, zooming or panning the image), and it enables you to smoothly pan and zoom a Deep Zoom image the way you would an online map, such as Microsoft Live Earth.

Blurry-to-crisp loading







Image pyramids and tiles

Each image in a Deep Zoom Composer composition is partitioned (or sliced up) into tiles. During the tiling process, Deep Zoom Composer creates an image pyramid of various resolutions. An image pyramid has the highest-resolution image, composed of multiple tiles, at the base of the pyramid, and the lowest-resolution image at the top of the pyramid, as a single tile. In Deep Zoom Composer, each tile at each level in the pyramid is 256x256 pixels. This tiling process happens at design time as part of the Deep Zoom Composer exporting process.

At run time (when you are viewing the image in a browser), one of the lower-resolution image tiles loads first to decrease wait time and download size so you can see the image as quickly as possible, instead of waiting for the entire image to load. As you pan and zoom the image, other pieces of image data are loaded as needed. For example, if you zoom in to see only the highlighted middle part of the image, your browser loads only the highlighted tiles, rather than the higher-resolution tiles of the entire image.

Image pyramid


Getting Started with the Map Control

Getting Started with the Map Control

The Bing Maps™ map control is a JavaScript control that contains the objects, methods, and events that you need to display maps powered by Bing Maps on your Web site.

Using the Bing Map Control

The topics in this section provide a walkthrough to help you start using the map control.

Version Changelist

Version Changelist

This topic describes the changes to the Bing Map Control SDK for the 6.2 release.

New Map Control Elements

The following objects, properties, and methods are either new or have been updated in the 6.2 version of the map control.

Name

Description

VEClusteringOptions Class

Contains the options for customizing a pushpin cluster display.

VEClusteringType Enumeration

An enumeration of pushpin clustering algorithms.

VEClusterSpecification Class

Contains the shape objects and location of a pushpin cluster.

VEImageryMetadata Class

Contains information about the specified imagery.

VEImageryMetadataOptions Class

Contains the options that represent the imagery.

VEMap.AddCustomLayer Method

Adds a custom layer to the map.

VEMap.GetImageryMetadata Method

Returns information about the requested imagery, including imagery date stamps and vendor attribution.

VEMap.HideScalebar Method

Hides the scale bar from the map.

VEMap.Import3DModel Method

Imports a model data file and displays a 3D model on the map.

VEMap.RemoveCustomLayer Method

Removes a custom layer from the map.

VEMap.ShowScalebar Method

Displays the scale bar on the map.

VEMapOptions.BirdseyeOrientation Property

A VEOrientation Enumeration value indicating the orientation of the bird's eye map.

VEMapOptions.LoadBaseTiles Property

A Boolean value indicating whether or not to load the base map tiles.

VEModelFormat Enumeration

An enumeration of 3D model formats.

VEModelOrientation Class

Represents the orientation of a 3D model on the map.

VEModelScale Class

Represents the scale of a 3D model with respect to the map.

VEModelScaleUnit Enumeration

An enumeration of scale units.

VEModelSourceSpecification Class

Contains the specification for importing a 3D model onto the map.

VEModelStatusCode Enumeration

An enumeration of status codes returned in the callback of the VEMap.Import3DModel Method.

VERouteHint Class

Specifies a route itinerary item hint.

VERouteHintType Enumeration

An enumeration specifying route itinerary item hint types.

VERouteItineraryItem.Hints Property

An array of VERouteHint Class items that correspond to the itinerary item.

VEShapeLayer.GetClusteredShapes Method

Returns an array of VEClusterSpecification Class objects representing the pushpin clusters of the shape layer.

VEShapeLayer.SetClusteringConfiguration Method

Sets the method for determining which pushpins are clustered as well as how the cluster is displayed.

VEShapeSourceSpecification.MaxImportedShapes Property

Specifies the maximum number of items that can be imported from an XML file. The default value is 200.