Satechi® Smart Converter USB Port Cigarette Adapter for iPhone 5S, 5C, 5, 4S, iPad Air, Mini Retina, Samsung Galaxy S5, S4, Note 3, 2, HTC One, Nexus 5, LG Optimus, BlackBerry Playbook, HTC One and more (2.4 AMP) (Single USB Port)

Satechi® Smart Converter USB Port Cigarette Adapter for iPhone 5S, 5C, 5, 4S, iPad Air, Mini Retina, Samsung Galaxy S5, S4, Note 3, 2, HTC One, Nexus 5, LG Optimus, BlackBerry Playbook, HTC One and more (2.4 AMP) (Single USB Port)
Features:

  • Space-saving design with 2100mA power can support most USB powered devices
  • Use your existing USB charging cables to charge iPad, iPhone, iPod, Android Phones & Tablets, MP3 Players, Digital Cameras, PDAs, etc.
  • Blue LED indicator confirms whether USB charger is properly connected
  • Self recover safety function with Current Limit & Thermal Shutdown Protection
  • Smart-converter is designed to enhance charging compatibility for smartphones which are powered through Micro USB connector and enables quick charge for your device. It may also be used with PC or USB wall charger.

Description:
Keep your USB devices powered while on the move. Use this product in your car to charge or power any device that needs USB for power. With small size but 2100mA power, it can support most USB powered devices such as iPad, iPhone, iPod, Android Phones & Tablets, MP3 Players, Digital Cameras, PDAs, etc. Blue LED indicator confirms whether USB charger is properly connected. Included Smart-converter enhances capability with devices that cannot be charged through data cable.

Compatible with:

iPad: 2, 3, Mini, Air

iPhone: 5S, 5C, 5, 4S

Samsung Galaxy: S5, S4, S3, S2, Note 3, 2

HTC: One, SV, Flyer

Blackberry: Playbook

Droid

and more

iXCC ® Quad USB 20W 4 port Black High Capacity FAST AC Travel Charger for iPhone, iPad, Samsung and Android Smart Phone and Tablet

iXCC ® Quad USB 20W 4 port Black High Capacity FAST AC Travel Charger for iPhone, iPad, Samsung and Android Smart Phone and Tablet
Features:

  • 4 USB charging ports, high speed charging Apple, Samsung, and Android together
  • 20W Charger provides plenty power to charge 4 devices at the same time.
  • Brand: iXCC. Included with this listing: Wall Charger, user book.
  • One year warranty offer.

Description:
This 4 USB Port 20w Travel Wall Charger is a versatile powerful and reliable charger. It is convenient, powerful, safe, easy to use, and designed to have enough power to charge 4 Devices Simultaneously.Manufacture Limited Warranty This iXCC ® product is offered with limited manufacture warranty. The limited warranty period for the Product extends for ONE (1) YEAR from the date of purchase.

Aukey Wireless Charger Charging Pad Station Qi-Enabled for Google Nexus 4 / 5 / 7(2013);Nokia Lumia 920, 928, 1020; LG Optimus Vu2, D1L, LTE2, G2; HTC 8X, Droid DNA; MOTO Droid Maxx/Droid Mini; Blackberry Z30; iPhone; Samsung and other Other Qi-Enabled Phones – Powered by AC Adapter or USB Port (AC adapter is not included)

Aukey Wireless Charger Charging Pad Station Qi-Enabled for Google Nexus 4 / 5 / 7(2013);Nokia Lumia 920, 928, 1020; LG Optimus Vu2, D1L, LTE2, G2; HTC 8X, Droid DNA; MOTO Droid Maxx/Droid Mini; Blackberry Z30; iPhone; Samsung and other Other Qi-Enabled Phones - Powered by AC Adapter or USB Port (AC adapter is not included)
Features:

  • Compatible with any Qi-enabled device or a device equipped with a Qi-compatible cover or Qi standard receiver.
  • Charge your Smartphone without cables and USB interface, a product that really keeps you away from tangle of wires.
  • DC 5V 1.5A Input and 1A output to fast charge your QI-Enabled devices.LEDs display charging status; designed with an energy efficient idle mode.
  • Green anti-slip rubber rings keep the charging pad secure on any flat smooth surface and protect your phone sliding from the charging pad.
  • Featuring coffee cup coaster size (2.7 x 2.7 x 0.4in / 70 × 70 × 10.5mm), this charger fits perfectly on a desk or nightstand without drawing unneeded attention.

Description:
Aukey T20 Qi-Enabled Wireless Charger Charging Pad

Tired of the tangle of wires? Seeking a way to get rid of plug and plug when charging your phone? Now with the cutting-edge Qi inductive charging technology, this innovation continues the quest for wireless freedom by eliminating yet another wire, and achieves the first step for wireless charging.

Compatible Models
Direct Charging Models (No additional QI Receiver needed):
-Nokia Lumia 1020/920/928
-Google Nexus4,Nexus5,Nexus 7(2013)
-Moto Droid Maxx, Droid Mini
-LG D1L, LG LTE2, LG G2
-Pentax WG-III camera
-Blackberry Z30
-HTC 8X (UK version does not support QI wireless charging),HTC Droid DNA,HTC Rzound,HTC Incredible 4G LTE

Qi-Compatible Wireless Charging Receiver Required
-Samsung Galaxy Note 3/S5/S4/S3/Note 2
-Nokia 925,Nokia 720,

External QI Compatible Receiver Models
-iPhone 5C/5S/5/4/4S
– Nokia 820
– LG G3

For Optional Use
1

INTERNET ERROR CODES | ERROR CODE LIST IN RAS (REMOTE ACCESS SERVER)

INTERNET ERROR CODES | ERROR CODE LIST IN RAS (REMOTE ACCESS SERVER)
Sometimes when you try to visit a Web site, instead of seeing what you expected, you see an error code. Some of these codes may be familiar, but there are a lot that you may have never seen. To give you a greater understanding of these errors, here is a list of the most popular codes. As a rule of thumb, the first thing you should if you get an error is make sure that you have typed in the URL or page address correctly.
Bad request 400
The request could not be understood by the server due to bad syntax. You should not repeat the request without modifications.
Unauthorized 401
The creators of a Web page may want only certain people have access to that page. You should only retry the request if you know that you have authorization.
PaymentRequired 402
This message gives a specification of charging schemes which are acceptable. You may retry the request with a suitable ChargeTo header.
Forbidden 403
The request is for something forbidden. Authorization will not help. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable. (The file needs to be set with “read permissions” for all users.)
Not found 404
The server has not found anything matching what you requested. Make sure that the Web address (URL) that you typed in exactly matches the address you were given. Check that the capitalization matches, spelling, and punctuation, like dots (.) and slashes (/), are correctly placed. Be sure you are using the forward slash (/) and not the backward slash ().
405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the request. The response must include an Allow header containing a list of valid methods for the requested resource.
406 Not Acceptable
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that you must first authenticate yourself with the proxy. The proxy must return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. You may repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in section 11.
408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. You may repeat the request without modifications at any later time.
409 Conflict
The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request.
410 Gone
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners want remote links to that resource be removed.
411 Length Required
The server refuses to accept the request without a defined Content- Length. The client may repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
412 Precondition Failed
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
413 Request Entity Too Large
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.
414 Request-URI Too Long
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Internal Error 500
The server encountered an unexpected condition which prevented it from fulfilling the request. Your request could not be processed due to an internal server error.
Not implemented 501
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, you should handle the response as it would for a 500 response.
504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server it accessed in attempting to complete the request.
505 HTTP Version Not Supported
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The response should contain an entity describing why that version is not supported and what other protocols are supported by that server
ERROR CODE LIST IN RAS (REMOTE ACCESS SERVER)
600   An operation is pending.
601   The port handle is invalid.
602   The port is already open.
603   Caller’s buffer is too small.
604   Wrong information specified.
605   Cannot set port information.
606   The port is not connected.
607   The event is invalid.
608   The device does not exist.
609   The device type does not exist.
610   The buffer is invalid.
611   The route is not available.
612   The route is not allocated.
613   Invalid compression specified.
614   Out of buffers.
615   The port was not found.
616   An asynchronous request is pending.
617   The port or device is already disconnecting.
618   The port is not open.
619   The port is disconnected.
620   There are no endpoints.
621   Cannot open the phone book file.
622   Cannot load the phone book file.
623   Cannot find the phone book entry.
624   Cannot write the phone book file.
625   Invalid information found in the phone book.
626   Cannot load a string.
627   Cannot find key.
628   The port was disconnected.
629   The port was disconnected by the remote machine.
630   The port was disconnected due to hardware failure.
631   The port was disconnected by the user.
632   The structure size is incorrect.
633   The port is already in use or is not configured for Remote Access dialout.
634   Cannot register your computer on the remote network.
635   Unknown error.
636   The wrong device is attached to the port.
637   The string could not be converted.
638   The request has timed out.
639   No asynchronous net available.
640   A NetBIOS error has occurred.
641   The server cannot allocate NetBIOS resources needed to support the client.
642   One of your NetBIOS names is already registered on the remote network.
643   A network adapter at the server failed.
644   You will not receive network message popups.
645   Internal authentication error.
646   The account is not permitted to log on at this time of day.
647   The account is disabled.
648   The password has expired.
649   The account does not have Remote Access permission.
650   The Remote Access server is not responding.
651   Your modem (or other connecting device) has reported an error.
652   Unrecognized response from the device.
653   A macro required by the device was not found in the device .INF file section.
654   A command or response in the device .INF file section refers to an undefined macro
655   The  macro was not found in the device .INF file section.
656   The  macro in the device .INF file section contains an undefined macro
657   The device .INF file could not be opened.
658   The device name in the device .INF or media .INI file is too long.
659   The media .INI file refers to an unknown device name.
660   The device .INF file contains no responses for the command.
661   The device .INF file is missing a command.
662   Attempted to set a macro not listed in device .INF file section.
663   The media .INI file refers to an unknown device type.
664   Cannot allocate memory.
665   The port is not configured for Remote Access.
666   Your modem (or other connecting device) is not functioning.
667   Cannot read the media .INI file.
668   The connection dropped.
669   The usage parameter in the media .INI file is invalid.
670   Cannot read the section name from the media .INI file.
671   Cannot read the device type from the media .INI file.
672   Cannot read the device name from the media .INI file.
673   Cannot read the usage from the media .INI file.
674   Cannot read the maximum connection BPS rate from the media .INI file.
675   Cannot read the maximum carrier BPS rate from the media .INI file.
676   The line is busy.
677   A person answered instead of a modem.
678   There is no answer.
679   Cannot detect carrier.
680   There is no dial tone.
681   General error reported by device.
682   ERROR WRITING SECTIONNAME
683   ERROR WRITING DEVICETYPE
684   ERROR WRITING DEVICENAME
685   ERROR WRITING MAXCONNECTBPS
686   ERROR WRITING MAXCARRIERBPS
687   ERROR WRITING USAGE
688   ERROR WRITING DEFAULTOFF
689   ERROR READING DEFAULTOFF
690   ERROR EMPTY INI FILE
691   Access denied because username and/or password is invalid on the domain.
692   Hardware failure in port or attached device.
693   ERROR NOT BINARY MACRO
694   ERROR DCB NOT FOUND
695   ERROR STATE MACHINES NOT STARTED
696   ERROR STATE MACHINES ALREADY STARTED
697   ERROR PARTIAL RESPONSE LOOPING
698   A response keyname in the device .INF file is not in the expected format.
699   The device response caused buffer overflow.
700   The expanded command in the device .INF file is too long.
701   The device moved to a BPS rate not supported by the COM driver.
702   Device response received when none expected.
703   ERROR INTERACTIVE MODE
704   ERROR BAD CALLBACK NUMBER
705   ERROR INVALID AUTH STATE
706   ERROR WRITING INITBPS
707   X.25 diagnostic indication.
708   The account has expired.
709   Error changing password on domain.
710   Serial overrun errors were detected while communicating with your modem.
711   RasMan initialization failure. Check the event log.
712   Biplex port is initializing. Wait a few seconds and redial.
713   No active ISDN lines are available.
714   Not enough ISDN channels are available to make the call.
715   Too many errors occurred because of poor phone line quality.
716   The Remote Access IP configuration is unusable.
717   No IP addresses are available in the static pool of Remote Access IP addresses.
718   PPP timeout.
719   PPP terminated by remote machine.
720   No PPP control protocols configured.
721   Remote PPP peer is not responding.
722   The PPP packet is invalid.
723   The phone number, including prefix and suffix, is too long.
724   The IPX protocol cannot dial-out on the port because the computer is an IPX router.
725   The IPX protocol cannot dial-in on the port because the IPX router is not installed.
726   The IPX protocol cannot be used for dial-out on more than one port at a time.
727   Cannot access TCPCFG.DLL.
728   Cannot find an IP adapter bound to Remote Access.
729   SLIP cannot be used unless the IP protocol is installed.
730   Computer registration is not complete.
731   The protocol is not configured.
732   The PPP negotiation is not converging.
733   The PPP control protocol for this network protocol is not available on the server.
734   The PPP link control protocol terminated.
735   The requested address was rejected by the server.
736   The remote computer terminated the control protocol.
737   Loopback detected.
738   The server did not assign an address.
739   The remote server cannot use the Windows NT encrypted password.
740   The TAPI devices configured for Remote Access failed to initialize or were not installed correctly.
741   The local computer does not support encryption.
742   The remote server does not support encryption.
743   The remote server requires encryption.
744   Cannot use the IPX net number assigned by the remote server. Check the event log.
752   A syntax error was encountered while processing a script