-=> JEAN PARROT wrote to WAYNE CHIRNSIDE <=-

 JP>       Hello, Wayne, it is a great day here.

 WC> Nope, the problem I'm certain is in the limited NVRAM
 WC> Rockwell KFLEX modem protocols in the modem.

 JP>  OK now. You seemed to me that you were balming Verizon and I mentioned
 JP>  that I connect at 50,666 ( not 50,333 ) all the time. I only wnanted
 JP> to
 JP>  have you think this out and see if there was another reason, not
 JP>  Verizon.

I AM unhappy with Verizon, no problems when they were GTE.
The problem is Verizon did not update their negotoation
protocols in such a way as to support some existing modems

 WC> This is NOT the first modem rendered usless by Verizon's protocol
 WC> changes the first being a hardware 14,400 modem.

 JP>  What could they have done to your modem? I never knew that they or any
 JP>  ISP, network could "burn" the hardware in a modem. New to me !

Well this was not  the case in either case, it's the negotiations
protocols they implemented that doesn't support some older modems
previously perfectly good 56k units.

My 56k modem will NOT negotate unless throttled back to V34.

There IS a case of one ISP I can think of which _did_
reassign modem COM ports and IRQ's and that's AOL.

My sister was pursuing her doctorate and had several expensive
computer troubleshooters in to _fix_ her computer.
It got expensive so one day she asked me to fix it.
I was sitting there when her kids logged onto AOL when up comes
a screen saying "updating system software."
I looked and sure enough AOL had swapped the modems IRQ and port
around again disabling her ability to use her communications
program to stay in touch with her university and associates.

I immediately asked her to get me her modem setup software so
I could use the same ports in her COMM package as those AOL
insisted on using however having misplaced the disks
this didn't work out. Wendy wound up buying another modem on
my recomendation as well.
 
--- MultiMail/MS-DOS v0.45