Archived from groups: alt.cellular.verizon (More info?)

I have a Kyocera 2325 from Verizon and th eUSB cable from Kyocera.
 
I have the USB cable in Device Manager (Windows 98SE) as COM1.
 
No modem .inf file I've tried will work. The Modems control panel
diagnostics always says it's not responding.
 
I can use Hyperterminal to directly connect to COM1 then use
the ATDT command to dial and login to my ISP so I know the phone
will work as a modem. Of course that's useless except to demonstrate
it works because I don't have a shell or SLIP account.
 
So how do I convince the rest of Windows that the phone really is
there and will work as a modem?
 
Verizon "support" is no help at all. Absolutely NONE of their
suggestions have worked. Trying it with any of the "standard"
modem drivers does not work. The only Windows Kyocera modem drivers
available on the Kyocera site are for the 7135 and Qualcomm PalmOS
based phones. I've found software on driverguide.com for Kyocera
phones other than the 7135, doesn't work either. I've tried all
the port speed settings on the phone and matched them in Windows,
also tried them different.
 
When I got the phone at the Verizon store (an actual Verizon
storefront, not a place like RadioShack) I specifically asked
if it would work as a modem and they told me all I needed was
this USB cable.
 
The computer I'm trying to get it to work on is a Toshiba Tecra
8000 laptop. Pentium II, 300Mhz, 128meg RAM, Windows 98SE.
 
I have 21 years of experience with PC hardware and software, so
this _shouldn't_ be hard. My bet is Verizon has "fixed" something
in this phone to block Windows from detecting its modem capabilities.
 
Last week I took the phone back to see if there are any firmware
updates. The guy looked at it, said it's way old, told me the version
number on it and the new version number. Said it would be about 45
minutes. They were very busy. I come back 45 minutes later and finally
snag one of their people and ask if my phone is done. He goes in back
and comes out with my phone. I get home (75 miles away) and try it
again with the USB cable. Same non results. I go online and find how to
check the firmware version. THEY DIDN'T UPDATE IT! The guy just went and
picked it up without asking their tech people if they were through
with it.
 
***>-_-<*** (steam coming out my ears) Can you tell I am NOT HAPPY
with Verizon?

Archived from groups: alt.cellular.verizon (More info?)

GAlan wrote:
 
> So how do I convince the rest of Windows that the phone really is
> there and will work as a modem?
 
Try setting it up as a "Standard Modem". Worked for me.
 
> When I got the phone at the Verizon store (an actual Verizon
> storefront, not a place like RadioShack) I specifically asked
> if it would work as a modem and they told me all I needed was
> this USB cable.
 
That actually should be the case.
 
 
--  
JustThe.net Internet & New Media Services, http://JustThe.net/
Steven J. Sobol, Geek In Charge / 888.480.4NET (4638) / sjsobol@JustThe.net
PGP Key available from your friendly local key server (0xE3AE35ED)
Apple Valley, California     Nothing scares me anymore. I have three kids.

Archived from groups: alt.cellular.verizon (More info?)

"GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
news:Xns959D320345434gregg1valintnet@216.168.3.44...
>I have a Kyocera 2325 from Verizon and th eUSB cable from Kyocera.
>
> I have the USB cable in Device Manager (Windows 98SE) as COM1.
>
> No modem .inf file I've tried will work. The Modems control panel
> diagnostics always says it's not responding.
>
 
>
> So how do I convince the rest of Windows that the phone really is
> there and will work as a modem?
>
 
You could just do it the simple way. Go to Dial up networking and add it.  
Use a standard modem driver and whatever phone number you want. That will  
work fine for low speed (qwk2net circuit switched 14.4 etc). (use name: qnc  
password: qnc)
 
If you want to use it as high speed, that's a bit trickier. First it HAS to  
already be on your account as an active option (look at your bill and see if  
National Access is listed as an active additional service). The phone number  
must be #777 instead of a real number, setup strings to the phone are  
different and need to be added, max speed to connect must be changed, logon  
to vzw3g must be added etc...
 
For now, I'd go for the simple add it as low speed first.

Archived from groups: alt.cellular.verizon (More info?)

The driver that you need can be downloaded from Kyocera support:
 
http://www.kyocera-wireless.com/2300-phone/support.htm
 
There is no reason why you can't use the 2325 as a data phone once you get  
it installed properly....
 
Good luck!
 
PC
 
"GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
news:Xns959D320345434gregg1valintnet@216.168.3.44...
|I have a Kyocera 2325 from Verizon and th eUSB cable from Kyocera.
|
| I have the USB cable in Device Manager (Windows 98SE) as COM1.
|
| No modem .inf file I've tried will work. The Modems control panel
| diagnostics always says it's not responding.
|
| I can use Hyperterminal to directly connect to COM1 then use
| the ATDT command to dial and login to my ISP so I know the phone
| will work as a modem. Of course that's useless except to demonstrate
| it works because I don't have a shell or SLIP account.
|
| So how do I convince the rest of Windows that the phone really is
| there and will work as a modem?
|
| Verizon "support" is no help at all. Absolutely NONE of their
| suggestions have worked. Trying it with any of the "standard"
| modem drivers does not work. The only Windows Kyocera modem drivers
| available on the Kyocera site are for the 7135 and Qualcomm PalmOS
| based phones. I've found software on driverguide.com for Kyocera
| phones other than the 7135, doesn't work either. I've tried all
| the port speed settings on the phone and matched them in Windows,
| also tried them different.
|
| When I got the phone at the Verizon store (an actual Verizon
| storefront, not a place like RadioShack) I specifically asked
| if it would work as a modem and they told me all I needed was
| this USB cable.
|
| The computer I'm trying to get it to work on is a Toshiba Tecra
| 8000 laptop. Pentium II, 300Mhz, 128meg RAM, Windows 98SE.
|
| I have 21 years of experience with PC hardware and software, so
| this _shouldn't_ be hard. My bet is Verizon has "fixed" something
| in this phone to block Windows from detecting its modem capabilities.
|
| Last week I took the phone back to see if there are any firmware
| updates. The guy looked at it, said it's way old, told me the version
| number on it and the new version number. Said it would be about 45
| minutes. They were very busy. I come back 45 minutes later and finally
| snag one of their people and ask if my phone is done. He goes in back
| and comes out with my phone. I get home (75 miles away) and try it
| again with the USB cable. Same non results. I go online and find how to
| check the firmware version. THEY DIDN'T UPDATE IT! The guy just went and
| picked it up without asking their tech people if they were through
| with it.
|
| ***>-_-<*** (steam coming out my ears) Can you tell I am NOT HAPPY
| with Verizon?

Archived from groups: alt.cellular.verizon (More info?)

Steve Sobol <sjsobol@JustThe.net> wrote in news:cmtdak$37s$2
@ratbert.glorb.com:
 
> GAlan wrote:
>  
>> So how do I convince the rest of Windows that the phone really is
>> there and will work as a modem?
>  
> Try setting it up as a "Standard Modem". Worked for me.
 
Doesn't work. Modem does not respond to the diagnostic probe.
(I said this already in my previous post.)

Archived from groups: alt.cellular.verizon (More info?)

"Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
news:2vf1o1F2kvdlnU1@uni-berlin.de:  
 
>  
> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
> news:Xns959D320345434gregg1valintnet@216.168.3.44...
>>I have a Kyocera 2325 from Verizon and th eUSB cable from Kyocera.
>>
>> I have the USB cable in Device Manager (Windows 98SE) as COM1.
>>
>> No modem .inf file I've tried will work. The Modems control panel
>> diagnostics always says it's not responding.
>>
>  
>>
>> So how do I convince the rest of Windows that the phone really is
>> there and will work as a modem?
>>
>  
> You could just do it the simple way. Go to Dial up networking and add
> it. Use a standard modem driver and whatever phone number you want.
> That will work fine for low speed (qwk2net circuit switched 14.4 etc).
> (use name: qnc password: qnc)
 
Doesn't work. Modem does not respond to the diagnostic probe.
(I said this already in my previous post.)

Archived from groups: alt.cellular.verizon (More info?)

"Proconsul" <nospam@nospam.org> wrote in news:tdzkd.97494$kz3.31398
@fed1read02:
 
> http://www.kyocera-wireless.com/2300-phone/support.htm
 
The cable I have uses this download
 
http://www.kyocera-wireless.com/su [...] indows.zip
 
This ZIP file does not contain _modem_ driver files. It only contains
the drivers for the Prolific chip in the cable and a USB/COM port.
 
I'll have a look at
 
http://www.kyocera-wireless.com/su [...] indows.zip
 
and
 
http://www.kyocera-wireless.com/su [...] indows.zip
 
They're larger files, may contain more than just the bare-bones
cable drivers. I doubt they'll work.
 
What's odd is that Hyperterminal can access and use the phone without
the modem showing in Device Manager or the Modems control panel.
 
What's hiding it from Windows?

Archived from groups: alt.cellular.verizon (More info?)

"GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
news:Xns959E2766D751gregg1valintnet@216.168.3.44...
> Steve Sobol <sjsobol@JustThe.net> wrote in news:cmtdak$37s$2
> @ratbert.glorb.com:
>
>> GAlan wrote:
>>
>>> So how do I convince the rest of Windows that the phone really is
>>> there and will work as a modem?
>>
>> Try setting it up as a "Standard Modem". Worked for me.
>
> Doesn't work. Modem does not respond to the diagnostic probe.
> (I said this already in my previous post.)
 
I have and use his older phone as a standard modem, depending on your  
version of windows (win 98 didn't support USB), you may need one of the free  
utility programs from zdnet or download.com (memory resident about 300-400  
bytes) that convert USB to COM. If all you have is a serial cable, phones  
default to USB and you have to go into the communications setup menu (on the  
phone) and make it rs-232 instead of USB.

Archived from groups: alt.cellular.verizon (More info?)

"GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
news:Xns959E290E57Fgregg1valintnet@216.168.3.44...
> "Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
> news:2vf1o1F2kvdlnU1@uni-berlin.de:
>
>>
>> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message
>> news:Xns959D320345434gregg1valintnet@216.168.3.44...
>>>I have a Kyocera 2325 from Verizon and th eUSB cable from Kyocera.
>>>
>>> I have the USB cable in Device Manager (Windows 98SE) as COM1.
>>>
>>> No modem .inf file I've tried will work. The Modems control panel
>>> diagnostics always says it's not responding.
>>>
>>
>>>
>>> So how do I convince the rest of Windows that the phone really is
>>> there and will work as a modem?
>>>
>>
>> You could just do it the simple way. Go to Dial up networking and add
>> it. Use a standard modem driver and whatever phone number you want.
>> That will work fine for low speed (qwk2net circuit switched 14.4 etc).
>> (use name: qnc password: qnc)
>
> Doesn't work. Modem does not respond to the diagnostic probe.
> (I said this already in my previous post.)
 
As I said in other posts, go to www.zdnet.com or www.download.com and get  
one of the free memory resident utilities that convert USB to COM.

Archived from groups: alt.cellular.verizon (More info?)

"Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
news:2vgnhqF2kbburU1@uni-berlin.de:  
 
>  
> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
> news:Xns959E2766D751gregg1valintnet@216.168.3.44...
>> Steve Sobol <sjsobol@JustThe.net> wrote in news:cmtdak$37s$2
>> @ratbert.glorb.com:
>>
>>> GAlan wrote:
>>>
>>>> So how do I convince the rest of Windows that the phone really is
>>>> there and will work as a modem?
>>>
>>> Try setting it up as a "Standard Modem". Worked for me.
>>
>> Doesn't work. Modem does not respond to the diagnostic probe.
>> (I said this already in my previous post.)
>  
> I have and use his older phone as a standard modem, depending on your  
> version of windows (win 98 didn't support USB), you may need one of
> the free utility programs from zdnet or download.com (memory resident
> about 300-400 bytes) that convert USB to COM. If all you have is a
> serial cable, phones default to USB and you have to go into the
> communications setup menu (on the phone) and make it rs-232 instead of
> USB.  
 
I'm using Windows 98 SECOND EDITION, WHICH DOES SUPPORT USB.
 
How many times do I have to say THIS DOES NOT WORK ON MY PHONE?
 
The 2325 has a built in serial port, NOT USB. The _cable_ has a
chip in it, made by Prolific, that converts the USB port to a
serial port.
 
The CABLE DRIVER makes Windows see the Prolific chip as a
COM port attached to the USB.
 
HYPER TERMINAL _CAN_ send an ATDT command with the phone number
to "COM1". The phone dials and I get my ISP login prompt.
 
I can login, then get a screen full of gibberish since it's
_not_ a SHELL OR SLIP (Serial Line Internet Protocol) account.
 
 
The PROBLEM is that DIAL UP NETWORKING _CANNOT_ SEE THE MODEM!!!
 
I've tried several different Kyocera and the standard modem
drivers. NONE OF THEM WORK!
 
And I've already said I've tried all three port speeds available
with the phone, hasn't made a difference.
 
How many more times will people tell me to do what I've already
said I've tried, that does not work?!

Archived from groups: alt.cellular.verizon (More info?)

"GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message  
news:Xns959ECA51173CAgregg1valintnet@216.168.3.44...
> "Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
> news:2vgnhqF2kbburU1@uni-berlin.de:
>
>>
>> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message
>> news:Xns959E2766D751gregg1valintnet@216.168.3.44...
>>> Steve Sobol <sjsobol@JustThe.net> wrote in news:cmtdak$37s$2
>>> @ratbert.glorb.com:
>>>
>>>> GAlan wrote:
>>>>
>>>>> So how do I convince the rest of Windows that the phone really is
>>>>> there and will work as a modem?
>>>>
>>>> Try setting it up as a "Standard Modem". Worked for me.
>>>
>>> Doesn't work. Modem does not respond to the diagnostic probe.
>>> (I said this already in my previous post.)
>>
>> I have and use his older phone as a standard modem, depending on your
>> version of windows (win 98 didn't support USB), you may need one of
>> the free utility programs from zdnet or download.com (memory resident
>> about 300-400 bytes) that convert USB to COM. If all you have is a
>> serial cable, phones default to USB and you have to go into the
>> communications setup menu (on the phone) and make it rs-232 instead of
>> USB.
>
> I'm using Windows 98 SECOND EDITION, WHICH DOES SUPPORT USB.
>
> How many times do I have to say THIS DOES NOT WORK ON MY PHONE?
>
> The 2325 has a built in serial port, NOT USB. The _cable_ has a
> chip in it, made by Prolific, that converts the USB port to a
> serial port.
>
> The CABLE DRIVER makes Windows see the Prolific chip as a
> COM port attached to the USB.
>
> HYPER TERMINAL _CAN_ send an ATDT command with the phone number
> to "COM1". The phone dials and I get my ISP login prompt.
>
> I can login, then get a screen full of gibberish since it's
> _not_ a SHELL OR SLIP (Serial Line Internet Protocol) account.
>
>
> The PROBLEM is that DIAL UP NETWORKING _CANNOT_ SEE THE MODEM!!!
>
> I've tried several different Kyocera and the standard modem
> drivers. NONE OF THEM WORK!
>
> And I've already said I've tried all three port speeds available
> with the phone, hasn't made a difference.
>
> How many more times will people tell me to do what I've already
> said I've tried, that does not work?!
 
I would check that cable then. I have two that work just fine and NEITHER of  
them have any sort of chip thing in it, come to think of it, neither have  
drivers either.. who makes the cable you are using? Do they have a website?

Archived from groups: alt.cellular.verizon (More info?)

I'm going to try to help here...
 
GAlan wrote:
 
> The 2325 has a built in serial port, NOT USB. The _cable_ has a
> chip in it, made by Prolific, that converts the USB port to a
> serial port.
 
As the former owner of a 2325, can I point out that the typical cell phone has  
a connector that is neither a USB nor a serial connector? (Sorry... Nitpicking,  
I know.)
 
> The CABLE DRIVER makes Windows see the Prolific chip as a
> COM port attached to the USB.
 
> HYPER TERMINAL _CAN_ send an ATDT command with the phone number
> to "COM1". The phone dials and I get my ISP login prompt.
 
And which device are you using when you successfully connect this way? Standard  
14400 or 28800 modem? Something else? Hyperterminal uses the same modem drivers  
that DUN uses.
 
Are you trying to connect using Quick2Net (the old 14.4K service) or  
ExpressNetwork/NationalAccess? If the latter, I might be able to at least offer  
suggestions about what your problem is, if not a solution...
 
> I can login, then get a screen full of gibberish since it's
> _not_ a SHELL OR SLIP (Serial Line Internet Protocol) account.
 
At what speed are you connecting when you make the successful connection?
 
> How many more times will people tell me to do what I've already
> said I've tried, that does not work?!
 
I'm not telling you anything yet. Just collecting some data. Forget what I said  
earlier. I have used my 2325 succesfully before, but with a serial data cable  
and I think I may be able to identify the problems you're having, which I  
wouldn't have had.
 
Oh, also, just for the sake of completeness, perhaps you could list the drivers  
you've tried to use (both Kyo and Windows drivers)
 
Just bear with me and answer my questions and the chances are good that I'll be  
able to solve this mystery for you.
 
**SJS (been a long time since the last time I did ISP tech support!)
 
--  
JustThe.net Internet & New Media Services, http://JustThe.net/
Steven J. Sobol, Geek In Charge / 888.480.4NET (4638) / sjsobol@JustThe.net
PGP Key available from your friendly local key server (0xE3AE35ED)
Apple Valley, California     Nothing scares me anymore. I have three kids.

Archived from groups: alt.cellular.verizon (More info?)

> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message
> news:Xns959ECA51173CAgregg1valintnet@216.168.3.44...
>> "Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
>> news:2vgnhqF2kbburU1@uni-berlin.de:
>>
>>>
>>> "GAlan" <gregg1@NOCANNEDMEAT.valint.net> wrote in message
>>> news:Xns959E2766D751gregg1valintnet@216.168.3.44...
>>>> Steve Sobol <sjsobol@JustThe.net> wrote in news:cmtdak$37s$2
>>>> @ratbert.glorb.com:
>>>>
>>>>> GAlan wrote:
>>>>>
>>>>>> So how do I convince the rest of Windows that the phone really is
>>>>>> there and will work as a modem?
>>>>>
>>>>> Try setting it up as a "Standard Modem". Worked for me.
>>>>
>>>> Doesn't work. Modem does not respond to the diagnostic probe.
>>>> (I said this already in my previous post.)
>>>
>>> I have and use his older phone as a standard modem, depending on your
>>> version of windows (win 98 didn't support USB), you may need one of
>>> the free utility programs from zdnet or download.com (memory resident
>>> about 300-400 bytes) that convert USB to COM. If all you have is a
>>> serial cable, phones default to USB and you have to go into the
>>> communications setup menu (on the phone) and make it rs-232 instead of
>>> USB.
>>
>> I'm using Windows 98 SECOND EDITION, WHICH DOES SUPPORT USB.
>>
>> How many times do I have to say THIS DOES NOT WORK ON MY PHONE?
>>
>> The 2325 has a built in serial port, NOT USB. The _cable_ has a
>> chip in it, made by Prolific, that converts the USB port to a
>> serial port.
>>
>> The CABLE DRIVER makes Windows see the Prolific chip as a
>> COM port attached to the USB.
>>
>> HYPER TERMINAL _CAN_ send an ATDT command with the phone number
>> to "COM1". The phone dials and I get my ISP login prompt.
>>
>> I can login, then get a screen full of gibberish since it's
>> _not_ a SHELL OR SLIP (Serial Line Internet Protocol) account.
>>
>>
>> The PROBLEM is that DIAL UP NETWORKING _CANNOT_ SEE THE MODEM!!!
>>
>> I've tried several different Kyocera and the standard modem
>> drivers. NONE OF THEM WORK!
>>
>> And I've already said I've tried all three port speeds available
>> with the phone, hasn't made a difference.
>>
>> How many more times will people tell me to do what I've already
>> said I've tried, that does not work?!
>
 
Sorry you are having problems, but you are posting information in multiple  
posts/places, not in one post. If you expect someone to remember exactly  
what you said in another post at another time, when they are trying to offer  
you some free advice, then screw you pal.. I have lots of way way better  
things to do than remember every single thing you wrote at different times  
in different posts... I suggest you put all the details in one block of text  
and paste it into each message.
 
Here's a clue.. mine works just fine. On 5 computers and two different  
cables, with just the drivers in windows.  Thousands of people have that  
phone and it works just fine...None of us have a financial motive to  
remember YOUR stuff. I can't answer for anyone else here, but I didn't sell  
you the hardware, made absolutely nothing, **YOU** have the problem, not me,  
and **YOU** better learn some manners if you want free help. When I do  
computer and phone repair, I will **NOT** tolerate someone getting nasty...  
And if they start shouting, I have one firm and fast rule..NO ABUSE  
WHATSOEVER!.. pack the stuff up, put it in the persons hands, and point them  
to the door.

Archived from groups: alt.cellular.verizon (More info?)

Steve Sobol <sjsobol@JustThe.net> wrote in
news:cn1boe$16n$1@ratbert.glorb.com:  
 
 
> And which device are you using when you successfully connect this way?
> Standard 14400 or 28800 modem? Something else? Hyperterminal uses the
> same modem drivers that DUN uses.
 
I've done it without any driver installed. Just direct to COM1, Just
like can be done by connecting any external modem that's not host
based, without having to install a driver or inf file for DUN.
Windows 98SE allows direct port access. Hyperterminal communicates
directly with the modem, if it's not a Winmodem or other software
driven modem. The 2325 has to have an all hardware modem or the
"driver" would be more than an .inf file.
 
> Are you trying to connect using Quick2Net (the old 14.4K service) or  
> ExpressNetwork/NationalAccess? If the latter, I might be able to at
> least offer suggestions about what your problem is, if not a
> solution...  
 
None of the above. I have a normal ISP account.
 
>> I can login, then get a screen full of gibberish since it's
>> _not_ a SHELL OR SLIP (Serial Line Internet Protocol) account.
>  
> At what speed are you connecting when you make the successful
> connection?  
 
I never noticed that Hyperterminal reported a connect speed.
 
> I'm not telling you anything yet. Just collecting some data. Forget
> what I said earlier. I have used my 2325 succesfully before, but with
> a serial data cable and I think I may be able to identify the problems
> you're having, which I wouldn't have had.
>  
> Oh, also, just for the sake of completeness, perhaps you could list
> the drivers you've tried to use (both Kyo and Windows drivers)
 
I've tried every driver that Kyocera has for a USB to serial cable
with a Prolific chip, as well as Prolific drivers from the Prolific
site and other vendors who sell cabled with those chips. All of them
I've tried, it's been able to work with Hyperterminal.
 
I've tried every version of the Kyocera CDMA Modem and Kyocera High
Speed CDMA Modem .inf I could find. (And I've tried all three COM
port speed settings with each on both the phone and laptop.  
 
> Just bear with me and answer my questions and the chances are good
> that I'll be able to solve this mystery for you.
>  
> **SJS (been a long time since the last time I did ISP tech support!)
 
I used to work the "helldesk" too, got a twitch in my left eyelid that
took a month to go away after I was done dealing with customers that
literally did not know left, right, up and down. Ever spend an hour
just walking a person through inputting their DNS numbers?

Archived from groups: alt.cellular.verizon (More info?)

"Peter Pan" <Marcs1102NOSPAM@HotmailNOSPAM.com> wrote in
news:2vivepF2m3g4kU1@uni-berlin.de:  
 
 
> Sorry you are having problems, but you are posting information in
> multiple posts/places, not in one post. If you expect someone to
> remember exactly what you said in another post at another time, when
> they are trying to offer you some free advice, then screw you pal.. I
> have lots of way way better things to do than remember every single
> thing you wrote at different times in different posts... I suggest you
> put all the details in one block of text and paste it into each
> message.  
 
This thread right here has everything I've tried. I learned long ago
that it's considered "bad manners" to repeatedly post large chunks of
the same text into several messages in a thread. That's why messages are
threaded, so people can read "upstream" to see what's been said previously.
 
If people can't be bothered to read "up thread" to see what the original
poster has said/done/tried already, then why bother to reply at all
when it's quite likely all you'll be doing is telling them to try
what they've already said they've tried?
 
What's even worse is trying to get help on IRC. Post a problem,
get asked what's been tried, reply "X" and someone posts "Well,
try 'X' and see if that works."
 
So I'm not going to re-post the entire litany of everything on
this problem into every single post in this thread. It's a waste
of space, bandwidth and it makes it harder to follow the thread.
 
If you don't like that, then don't bother getting all bitchy
about it.
 
FYI, I have 21 years experience with PC hardware and software,
this @#%%#@%@# phone is one of the very few things to ever
"stump" me for this long.

Archived from groups: alt.cellular.verizon (More info?)

GAlan wrote:
 
> I've done it without any driver installed. Just direct to COM1, Just
> like can be done by connecting any external modem that's not host
> based, without having to install a driver or inf file for DUN.
> Windows 98SE allows direct port access. Hyperterminal communicates
> directly with the modem, if it's not a Winmodem or other software
> driven modem. The 2325 has to have an all hardware modem or the
> "driver" would be more than an .inf file.
 
It can be done that way with no problems with a serial cable. A USB cable will  
normally require drivers with WIN98 SE, although perhaps not with Win2K or XP  
as those operating systems have much better support for USB.
 
>>Are you trying to connect using Quick2Net (the old 14.4K service) or  
>>ExpressNetwork/NationalAccess? If the latter, I might be able to at
>>least offer suggestions about what your problem is, if not a
>>solution...  
>  
> None of the above. I have a normal ISP account.
 
You MUST be using either Quick2Net or NationalAcccess to dial into the ISP. If  
it's an ISP and you're dialing their number directly, you're probably using Q2N  
which is the slower service - I don't know that you can dial an ISP using  
NationalAccess (as far as I know that requires connecting directly through VZW).
 
> I've tried every version of the Kyocera CDMA Modem and Kyocera High
> Speed CDMA Modem .inf I could find. (And I've tried all three COM
> port speed settings with each on both the phone and laptop.  
 
Are you trying to connect at 14.4?
 
--  
JustThe.net Internet & New Media Services, http://JustThe.net/
Steven J. Sobol, Geek In Charge / 888.480.4NET (4638) / sjsobol@JustThe.net
PGP Key available from your friendly local key server (0xE3AE35ED)
Apple Valley, California     Nothing scares me anymore. I have three kids.