Be careful using "AT" functions.. you need to keep track of where the cursor is, and should generally start with a clear screen. I tend to avoid it in login scripts..
My earlier example is untested - You'll need to take that as a coarse example and look at the manual to insure the syntax. I'm an instructor by trade, and expect my students to get their hands dirty after a good shove in the right direction. 
The use of external files for MOTD is much more flexible - you don't want to mess with the login script once its written. That's why our commercial script is tokenized and uses an external config file to define disk, printer, message, and command resources.
Since login scripts need to be fast and unobtrusive, I generally avoid MessageBox in favor of short delays when important messages are displayed. Without any message delays, our script can process over 40 resource decisions, then mapp 10-12 drives and 2-3 printers in under 4 seconds on a LAN, and under 12 seconds on a 256Kbps WAN link. This leaves plenty of time to display MOTD type messages.
Glenn
_________________________
Actually I
am a Rocket Scientist!
