* Reply to a message in ENET.SYSOP.

 > Ward wanted to solve this problem with specifying the
 > baudrate in the nodelist.

 MvdV> Breaking my nodelist compiler in the process.. :-(

As I see it, the original use of this field in the days when modems usually
did not have speed buffering was to adjust the DCE-DTE speed to the
expected DCE-DCE speed. 

If you expected a 300 bps connection you set your serial port to 300 bps.
If you expected a 1,200 bps connection you set your serial port to 1,200
bps. If you expected a 2,400 bps connection you set your serial port to
2,400 bps.

With data compression functionality built into modems and other DCE's, it became
practically impossible to predict the required serial port speed and speed
buffering functionality was built into the modems.

That meant that you could lock your serial port at a high speed and the
modem speed buffering mechanism took care of the differences between the
actual DCE-DTE and the DCE-DCE speeds.


I've looked into a number of nodelist compilers and mailers and they all seem to
have some mechanism to limit the maximum serial port speed to be used for
an outgoing call. If you've got a V.22bis modem without data compression
you just set the maximum speed to 2,400 bps and the mailer will never set
the serial port
to any higher speed. Even if the nodelist says 33,600 bps for the system
you're calling.

Are there any problems with speeds in the nodelist above 9,600 bps in this
regard? Are there any nodelist compiler/mailer combinations which lack this
speed limitation functionality and will attempt to set the serial port to
33,600 bps if the nodelist says so? Are there any modems capable of 14,400
bps or more which require floating DCE-DTE speed? 


Are there any nodelist processing programmes (besides the InterMail
nodelist compiler and old versions of the FrontDoor nodelist compiler)
which will refuse to process a nodelist with speeds above 9,600 bps or act
up in other ways?

---