- Released 2009, May
110g, 14.4mm thickness
Feature phone
50MB storage, microSDHC slot - N/A135,457 hits
- 2.2'240x320 pixels
- 3MP
- 1150mAh
Network | Technology | GSM / HSPA |
---|---|---|
2G bands | GSM 900 / 1800 / 1900 | |
3G bands | HSDPA 2100 | |
Speed | HSPA 3.6/0.384 Mbps |
INQ1 Modem INQ1 PCSync Intel Matrix Storage Manager IntelĀ® PROSet/Wireless Software. Synaptics Pointing Device Driver Texas Instruments PCIxx21/x515/xx12 drivers. TIPCI TOSHIBA Assist. INQ1 PCSYNC Device INQ1 USB Modem JAF FLASHER INTERFACE. (COM15) RIM Virtual Serial Port v2 (COM30). V171-USB-Device-Driver VK Vodafone-710. Drivers for laptop IBM ThinkPad R52 (18469CG): the following page shows a menu of 24 devices compatible with the laptop model ThinkPad R52 (18469CG), manufactured by 'IBM'. To download the necessary driver, select a device from the menu below that you need a driver for and follow the link to download.
Launch | Announced | 2009, February. Released 2009, May |
---|---|---|
Status | Discontinued |
Body | Dimensions | 97 x 47.6 x 14.4 mm (3.82 x 1.87 x 0.57 in) |
---|---|---|
Weight | 110 g (3.88 oz) | |
SIM | Mini-SIM |
Display | Type | TFT, 256K colors |
---|---|---|
Size | 2.2 inches, 15.0 cm2 (~32.5% screen-to-body ratio) | |
Resolution | 240 x 320 pixels, 4:3 ratio (~182 ppi density) |
Inq1 Pc Sync Device (com15) Driver Updater
Memory | Card slot | microSDHC (dedicated slot) |
---|---|---|
Phonebook | 1000 entries, Photocall | |
Call records | 30 received, dialed and missed calls | |
Internal | 50MB |
Main Camera | Single | 3.15 MP |
---|---|---|
Video | Yes |
Selfie camera | No |
---|
Sound | Loudspeaker | Yes |
---|---|---|
3.5mm jack | No |
Comms | WLAN | No |
---|---|---|
Bluetooth | 2.0, A2DP | |
GPS | No | |
Radio | No | |
USB | miniUSB 2.0 |
Features | Sensors |
---|---|
Messaging | SMS, MMS, Email, IM |
Browser | WAP2.0 / xHTML |
Games | Yes |
Java | Yes, MIDP 2.0 |
Facebook, Skype, Twitter applications and integration MP3/WAV/eAAC+ player MP4/H.264 player Organizer Voice memo Predictive text input |
Battery | Type | Removable Li-Ion 1150 mAh battery |
---|---|---|
Stand-by | Up to 330 h | |
Talk time | Up to 5 h 20 min |
Misc | Colors | Gray |
---|
Disclaimer. We can not guarantee that the information on this page is 100% correct. Read more
iNQ iNQ1 - user opinions and reviews
- Anonymous
- myk
hi i read your comment and i was not able to retrieve my photos
- bJ8
This phone is obviously not a feature phone because you can use Skype and Facebook ....... but is it a smartphone ?? It lacks everything that makes a smartphone such as multi touch touchscreen ...... web browser etc etc Kinda in the similar catalo...
- vaf
Inq1 Pc Sync Device (com15) Driver Windows 10
Well I think you should sell the phone on eBay while you still can...... not sure if anyone will buy it though as the phone is virtually useless with no apps and not support by any type of phone cards
Some operations on a peripheral component interconnect (PCI) device are reserved for the device's function driver. Such operations include, for example, accessing the device-specific configuration space of a bus and programming a direct memory access (DMA) controller. Microsoft provides system support for accessing the configuration space of PCI devices by two methods:
The BUS_INTERFACE_STANDARD bus interface
The configuration I/O request packets (IRPs), IRP_MN_READ_CONFIG and IRP_MN_WRITE_CONFIG
Note
Starting with Windows 10, 2004, if a device has a Secure Devices (SDEV) ACPI table and Virtualization-based security enabled, restrictions are placed on unsupported methods for accessing PCI device configuration space. If a driver or process attempts to read or manipulate PCI device configuration space using a method that is not listed above, the access will be blocked and will result in a system bug check.
The Windows XP and Windows Server 2003 and later operating systems have exclusive control over the configuration space header, as defined by the PCI Local Bus specification, as well as all of the capabilities in the capabilities linked list. Drivers must not attempt to modify these registers.
However, drivers can write to the configuration space that does not belong to the header or the capabilities list that is vendor-defined, using the IRP_MN_WRITE_CONFIG request or the SetBusData method of BUS_INTERFACE_STANDARD. Drivers can also read a device's capabilities, using the IRP_MN_READ_CONFIG request or the GetBusData method of BUS_INTERFACE_STANDARD. To use IRP_MN_READ_CONFIG or IRP_MN_WRITE_CONFIG, drivers must be running at PASSIVE_LEVEL. For a list of capabilities and the corresponding structures that drivers can query for, see the PCI Structures section.
Drivers can read from the extended PCI device configuration space (that is, more than 256 bytes of configuration data) using the IRP_MN_READ_CONFIG request or the GetBusData method of BUS_INTERFACE_STANDARD. Likewise, drivers can write to the extended PCI device configuration space using the IRP_MN_WRITE_CONFIG request or the SetBusData method of BUS_INTERFACE_STANDARD. If a device does not have an extended configuration space or the platform does not define a path for an extended configuration space on a device, the read requests will return 0xFFFF and the write requests will have no effect. To determine if the operation succeeded, drivers can examine the number of bytes read or written.
PCI Express and PCI-X mode 2 support an extended PCI device configuration space of greater than 256 bytes. Drivers can read and write to this configuration space, but only with the appropriate hardware and BIOS support. Within the ACPI BIOS, the root bus must have a PNP ID of either PNP0A08 or PNP0A03. For root buses with PNP ID of PNP0A03, the _DSM method with function 4 should indicate that the current mode is PCI-X mode 2. All the bridges and devices should either be PCI express or operate in PCI-X mode 2.
In addition, the system should support memory-mapped configuration space accesses. This is by defining an MCFG table in the system BIOS/firmware. Windows Vista and Windows Server 2008 and later operating systems automatically support memory-mapped configuration space accesses.
The following code example shows how to query for the power management capability data of a device: