| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | V34 |
PE> Which section would that be in? Presumably not the bit that says: PE> 29:30 Trellis encoder select bits: PE> 0 = 16 state, 1 = 32 state, 2 = 64 state, 3 = reserved for ITU PE> Receiver REQUIRES remote-end transmitter PE> to use selected trellis encoder. RS> Again, you are reading to much into the specific wording RS> there on the question of all three being mandated. PE> NOTE - Source modem does not use bits 29-32, and should set these bits to 0 PE> So Rod, just where does the transmitter get to select PE> maximum supported trellis-encoding, when it is SPECIFICALLY PE> REQUIRED to zero out the bits that deal with trellis coding? PE> So try explaining how the calling modem says that it supports a maximum PE> of 16S trellis coding, when it has to zero-out all the bits. Have fun. No need to, clearly it manages to do that somehow when the rockwell datapump doesnt support 64S. The most likely explanation for how it achieves that is that you have focused on just one bit of the V34 protocol involved in that negotiation and missed the other bit that is used to achieve that outcome. Wouldnt be the first time, they aint easy to read, particularly the hardware ones. RS> Now try explaining how the rockwell chipsets which RS> dont have 64S actually manage to work Paul. Have fun. PE> What evidence do you have that the Rockwell does PE> not acknowledge the called USR's request for 64S? 64S isnt used dorko. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.