Phone Scoop

printed September 30, 2014
See this page online at:
http://www.phonescoop.com/phones/p_forum.php?fm=m&ff=508&fi=376262

Home  ›  Phones  ›  Sanyo  ›

Sanyo PM-8200 / SCP-8200

 

Info Photos Reviews  85 News Forum  

Back to message list

BitPim 0.7.34 does not detect Qwest Sanyo SCP-8200 in Win2K

by NellieNobody    Sep 3, 2005, 12:23 PM

I am using the Sanyo USB cable.

I have downloaded and installed the drivers using the .ini files from the following location:

http://www.sanyo.com/consumer/communications/usb_dri ... »

The Windows Phone and Modem Options dialog box shows the phone on COM4 and is able to communicate with it.

BitPim is able communicate with the phone enough to display information about it on the Protocol Log tab. It also retrieves and displays the directory structure, backs it up to my hard drive, and reboots the phone.

BUT!!! BitPim cannot detect the phone as a phone or get data from the phone. I've tried using the PM-8200, SCP-8100, and the Other CDMA phone settings.

According to postings on various cell phone message boards, Sprint users are able to use BitPim with the same model of phone. I'm wondering if Qwest disabled something to force users to use PCS Vision. >8-P I wouldn't put that past Qwest--I have had many struggles with those evil ones.

Here's the Protocol Log entry when BitPim attempts to detect the phone:

18:48:10.742 coms:[{'available': True, 'driverdate': (1999, 11, 14),
'description': 'Communications Port (COM1)', 'driverprovider': 'Microsoft',
'driverversion': '5.0.2183.1', 'hardwareinstance': 'ACPI\\PNP0501\\1',
'driverdescription': 'Communications Port', 'active': True, 'class':
'serial', 'name': 'COM1'}, {'available': True, 'driverdate': (1999, 11, 14),
'description': 'Communications Port (COM2)', 'driverprovider': 'Microsoft',
'driverversion': '5.0.2183.1', 'hardwareinstance': 'ACPI\\PNP0501\\2',
'driverdescription': 'Communications Port', 'active': True, 'class':
'serial', 'name': 'COM2'}, {'available': True, 'driverdate': (1999, 1, 22),
'description': '3Com Windows Modem PCI ADI', 'driverprovider': '3Com',
'driverversion': '5.0.2167.1', 'hardwareinstance':
'PCI\\VEN_12B9&DEV_1006&SUBSYS_008112B9&REV_0 0\\3&18D45AA6&0&70',
'driverdescription': '3Com Windows Modem PCI ADI', 'active': True, 'class':
'modem', 'name': 'COM3'}, {'available': True, 'description': 'SANYO USB
Phone', 'driverprovider': 'Microsoft', 'driverversion': '5.0.2167.1',
'hardwareinstance': 'USB\\VID_0474&PID_0701\\SERIAL_NUMBER',
'driverdescription': 'SANYO USB Phone', 'active': True, 'class': 'modem',
'name': 'COM4'}]
18:48:10.772 Available ports: ['COM1', 'COM2', 'COM3', 'COM4']
18:48:10.772 Available modem ports: ['COM3', 'COM4']
18:48:11.812 Gathering data on port: COM3
18:48:11.822 COM3: Opening port COM3, 115200 baud, timeout 1.000000,
hardwareflow 0, softwareflow 0
18:48:11.822 COM3: Open of comm port suceeded
18:48:11.822 COM3: Writing Data - 8 bytes
00000000 41 54 45 30 56 31 0d 0a ATE0V1..

18:48:11.832 Gathering data on port: COM4
18:48:11.832 COM4: Opening port COM4, 115200 baud, timeout 1.000000,
hardwareflow 0, softwareflow 0
18:48:11.832 COM3: Reading remaining data Data - 4 bytes
00000000 4f 4b 0d 0a OK..

18:48:11.832 COM3: Writing Data - 8 bytes
00000000 41 54 2b 47 4d 49 0d 0a AT+GMI..

18:48:11.832 COM4: Open of comm port suceeded
18:48:11.832 COM4: Writing Data - 8 bytes
00000000 41 54 45 30 56 31 0d 0a ATE0V1..

18:48:11.832 COM3: Reading remaining data Data - 7 bytes
00000000 45 52 52 4f 52 0d 0a ERROR..

18:48:11.842 COM3: Writing Data - 8 bytes
00000000 41 54 2b 47 4d 4d 0d 0a AT+GMM..

18:48:11.842 COM3: Reading remaining data Data - 7 bytes
00000000 45 52 52 4f 52 0d 0a ERROR..

18:48:11.842 COM3: Writing Data - 8 bytes
00000000 41 54 2b 47 4d 52 0d 0a AT+GMR..

18:48:11.842 COM3: Reading remaining data Data - 7 bytes
00000000 45 52 52 4f 52 0d 0a ERROR..

18:48:11.852 COM3: Writing Data - 8 bytes
00000000 41 54 2b 47 53 4e 0d 0a AT+GSN..

18:48:11.852 COM3: Reading remaining data Data - 7 bytes
00000000 45 52 52 4f 52 0d 0a ERROR..

18:48:11.933 Done on port: COM3
18:48:11.933 Done on port: COM4
18:48:11.933 Checking for model: LG-TM520
18:48:11.983 Checking for model: LG-VX10
18:48:11.993 Checking for model: LG-VX3200
18:48:12.094 Checking for model: LG-VX4400
18:48:12.114 Checking for model: LG-VX4500
18:48:12.174 Checking for model: LG-VX4600 (Telus Mobility)
18:48:12.483 Checking for model: LG-VX6000
18:48:12.513 Checking for model: LG-VX6100
18:48:12.553 Checking for model: LG-VX7000
18:48:12.604 Checking for model: LG-VX8000 (Verizon Wireless)
18:48:12.624 Checking for model: MM-7400
18:48:13.005 Checking for model: Other CDMA phone
18:48:13.015 Checking for model: PM-8200
18:48:13.025 Checking for model: RL-4920
18:48:13.045 Checking for model: SCH-A310
18:48:13.125 Likely ports:[]
18:48:13.134 Checking for model: SCH-A650
18:48:13.184 Likely ports:[]
18:48:13.194 Checking for model: SCH-A670
18:48:13.224 Likely ports:[]
18:48:13.234 Checking for model: SCP-4900
18:48:13.255 Checking for model: SCP-5300
18:48:13.285 Checking for model: SCP-5400
18:48:13.295 Checking for model: SCP-5500
18:48:13.315 Checking for model: SCP-7200
18:48:13.335 Checking for model: SCP-7300
18:48:13.345 Checking for model: SCP-8100
18:48:13.385 Checking for model: SCP-8100 (Bell Mobility)
18:48:13.415 Checking for model: SK6100 (Pelephone)
18:48:13.456 Checking for model: SPH-A460
18:48:13.555 Checking for model: SPH-A620 (VGA1000)

Report to moderator

Replies

No replies to this message


Reply You must log in to reply.

Back to message list

Subscribe to Phone Scoop News with RSS Follow @phonescoop on Twitter Phone Scoop on Facebook Phone Scoop on Google+ Subscribe to Phone Scoop on YouTube Follow on Instagram

 

All content Copyright 2001-2014 Phone Factor, LLC. All Rights Reserved.
Content on this site may not be copied or republished without formal permission.
2