Hi,
The problem you describe seems to indicate an issue with how Windows handles it's file manager and not a problem with LMS per se.
You may benefit from using an application such as http://tailforwin32.sourceforge.net/
Here are some notes on syslog location:
1. Stop the syslog daemon in Control Panel-->Administrative Tools-->Services (CWCS/CMF Syslog Service)
2. Stop the Syslog Collector via the command line on DOS: cd C:\progra~1\CSCOpx\binpdterm SyslogCollector
3. Create the new syslog.log file (say d:\ciscoworks\syslog.log), ensure that casuser has full access to this file.
4. Open the Registry (Regedit) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Crmlog\Parameters Right mouse on this "LogFile" line-->Modify Note: If you want to change the default Syslog Message Sourcelocation, you must first set the new location in the Windows Registry and only then change the Message Source location in the RME-->Administration-->SyslogAnalyzer-->Change Storage Options dialog box.
5. Use an editor and modify the entry for: SYSLOG_FILES= in $NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Collector.properties
6. Start the Syslog daemon in Services (see step 1).
7. Start SyslogCollector Process via CLI on DOS:pdexec SyslogCollector
8. Update the location of the syslog.log file in the logstat.conf file. (The logstat.conffile is located at CSCOpx/conf.) This ensures that the new syslog.log file isreferenced when you generate a Log File Status report (Common Services --> Server -->Reports --> Log File Status).