Winpopup Lan Messenger 5.5.9 Serial Number
Floriana Monterroza
WinMessenger is available for immediate download. Once you have purchased the product by filling in the online order form, a license will be sent to you via email to unlock the software for use. You may download the trial software before or after you complete the purchase process.
If you do not receive your product license within a reasonable amount of time (usually two business days for credit card payments or two weeks for other payments), please notify us via e-mail sa...@winmessenger.com! We apologize for any inconvenience caused by such delays.
This is the fastest and easiest way to order WinMessenger. Your credit card information is sent directly to the credit card processor in a highly secure manner (). We protect you by ensuring that nobody but you and the automated credit card processor will see your credit card information. You can go directly to the order page:
Companies with purchasing departments that do not use credit cards usually use Purchase Orders. We accept orders on account only from established companies that have faxed us signed Purchase Orders on their company letterhead. We have given the customer a payment deadline of 30 days from purchase (Terms: Net30). Please notify us via e-mail sa...@winmessenger.com after you sent (or faxed) the Purchase Order.
Please use company letterhead to submit the purchase order. Include your company's mailing address as well as billing address. Purchase orders need to be signed by a purchasing agent of your company. Please give name for the point of contact. Include all pertinent telephone numbers, both voice and fax. Most Importantly please include the email address of the person you would like to have the license information emailed to. Please include the Product ID number as well as the cost of the program. The vendor needs to be made out to ShareIt! and not VyPRESS Research, LLC. ShareIt! addresses are here. You can call to ShareIt if you have any purchase-related questions (see phone numbers above).
Eligible Academic and Educational Institutions and the Students, Faculty and Staff of accredited Colleges, Universities and other institutions are able to purchase VyPRESS software at up to 50% discounted pricing. For more information on eligibility, click here. If you wish to purchase Academic versions of VyPRESS software, you should e-mail sa...@winmessenger.com for pricing and purchase arrangements.
This chapter wraps up our coverage of thesmb.conf configuration file with somemiscellaneous options that can perform a variety of tasks. We talkbriefly about options for time synchronization, internationalization,messages, and common Windows bugs. For the most part, you will usethese options only in isolated circumstances.
In a network of computers, the systems on the network must agree onthe current time and also on what time files have been modified. Oneexample of the importance of synchronization is theroaming profiles we covered inChapter 4. It is vital for all clients accessing aroaming profile to agree on what time it is and which client lastmodified the user's profile.
If you set these options, Samba shares will provide compatibility offile-modification times that Visual C++, nmake,and other Microsoft programming tools require. Otherwise, PCmake programs might think that all the files ina directory need to be recompiled every time. Obviously, this is notthe behavior you want.
In Chapter 4, we showed you how to create a logonscript that used the nettime command to synchronizeclients' clocks automatically when they log on tothe domain. If your network is configured as a workgroup rather thana domain, you can still make use of net time byplacing the command:
Assuming that domain users log on to the domain at least once per dayand workgroup clients reboot frequently, the nettime command can keep client systems'clocks fairly well synchronized. However, sometimes domain users staylogged on for longer periods, and workgroup clients can run for daysbetween reboots. In the meantime, the systems'hardware clocks can wander enough to become a problem. It might bepossible to work around this, depending on the version of Windows theclient system is running. On Windows 98/Me, you can use the TaskScheduler to run the net time command at regularintervals. Likewise, on Windows 2000/XP you can use the MS-DOSat command. However, a better way to deal withthis issue is to use Network Time Protocol, which we will discussshortly.
Proper time synchronization is also important when operating in anActive Directory domain because Active Directory usesKerberos authentication.When a Kerberos domain controller creates an authentication ticketfor a client, the time is encoded into the challenge-and-responseexchanges between the client and domain controller. If theclient's clock disagrees with theserver's clock, authentication can fail.
To provide proper time synchronization in Active Directory domains, Microsoft hasadopted Network Time Protocol (NTP), using thename Windows Time Service for its implementation. For furtherinformation, the Microsoft white paper entitled TheWindows Time Service can be downloaded from
The nice thing about this is that NTP is the standard method forsynchronizing Unix hosts on a network, so you can synchronize allyour Unix systems (including the Samba server) and Windows systemswith the following method:
For other Windows clients, you might have to download an update fromMicrosoft to add Windows Time Service client support oruse a third-party application such as the freeanalogX Atomic TimeSync ( ). Or you can use thenet time command to update theclient's clock periodically, as discussedpreviously.
Samba always operates as an SMB time server, matching the behavior ofWindows systems. However, Samba's default is not toadvertise itself as a time server to the network. When this option isset to yes, Samba advertises itself as an SMB timeserver:
To deal with clients that don't properly processdaylight savings time, Samba provides the timeoffset option. If set, it adds the specifiednumber of minutes to the current time. This is handy ifyou're in Newfoundland and Windowsdoesn't know about the 30-minute time differencethere:
Traditionally, only the root user and the owner of a file can changeits last-modified date on a Unix system. The share-leveldos filetimes option allows theSamba server to mimic the characteristics of a DOS or Windows system:any user can change the last-modified date on a file in that share ifshe has write permission to it. To do this, Samba uses its rootprivileges to modify the timestamp on the file.
By default, this option is disabled. Setting this option toyes is often necessary to allow PCmake programs to work properly. Without it, theycannot change the last-modified date themselves. This often resultsin the program thinking all files needrecompiling when they really don't.
The dosfiletime resolution parameteris a share-level option. If set to yes, Sambarounds file times to the closest 2-second boundary. This optionexists primarily to satisfy a quirk in Windows that prevents VisualC++ from correctly recognizing that a file has not changed. You canenable it as follows:
The fakedirectory createtimes option exists to keep PCmake programs sane. VFAT and NTFS filesystemsrecord the creation date of a specific directory, while Unix doesnot. Without this option, Samba takes the earliest recorded date ithas for the directory (often the last-modified date of a file) andreturns it to the client. If this is not sufficient, set thefollowing option under a share definition:
If set, Samba will adjust the directory create time it reports to thehardcoded value January 1, 1980. This is primarily used to convincethe Visual C++ nmake program that any objectfiles in its build directories are indeed younger than the creationdate of the directory itself and need to be recompiled.
Magic scripts are a method of running programson Unix and redirecting the output back to the SMB client. These areessentially an experimental hack. However, some users and theirprograms still rely on these two options for their programs tofunction correctly. Magic scripts are not widely trusted, and theiruse is highly discouraged by the Samba Team.
If the magicscript option is set to a filename and the clientcreates a file by that name in that share, Samba will run the file assoon as the user has opened and closed it. For example,let's assume that the following option was createdin the share [accounting]:
Samba continually monitors the files in that share. If one by thename of tally.sh is closed (after being opened)by a user, Samba will execute the contents of that file locally. Thefile will be passed to the shell to execute; it must therefore be alegal Unix shell script. This means that it must have newlinecharacters as line endings instead of Windows CRLFs. In addition, youneed to use the #! directive at the beginning ofthe file to indicate under which shell or interpreter the scriptshould run, unless the script is for the default shell on yoursystem.
The character sets on Windows platforms hark back to the originalconcept of a code page. These code pages are used by DOS andWindows clients to determine rules for mapping lowercase letters touppercase letters. Samba can be instructed to use a variety of codepages through the use of the globalclient codepage option to match the corresponding code pagein use on the client. This option loads a code page definition fileand can take the values specified in Table 11-4.
The default value of this option is 850, for MS-DOS Latin 1. You canuse the make_smbcodepage tool that comes withSamba (by default in /usr/local/samba/bin ) tocreate your own SMB code pages, in the event that those listedearlier are not sufficient.
The global characterset option can be used to convert filenamesoffered through a DOS code page (see the previous section, Section 11.3.1.1) to equivalents that can berepresented by Unix character sets other than those in the UnitedStates. For example, if you want to convert the Western EuropeanMS-DOS character set on the client to a Western European Unixcharacter set on the server, you can use the following in yourconfiguration file:
b1e95dc632