Zugg Software :: View topic

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

http://forums.zuggsoft.com/forums/viewtopic.php?t=31179

The log file is locked by CMUD and I can open it in read only mode.

Nothing is written to the file. Hard disk space is fine, permission are fine.

If I shutdown CMUD the file is unlocked but nothing is written to it.

#LOG test.txt
creates a file

#LOG
Log is off
#LOG
Log is on: C:\KEEP\CMUD\test.txt

I can't get it to do:
Appending to log: C:\KEEP\CMUD\pComm.txt

Any ideas where to troubleshoot next? It affects a normal session window.

Beginner Joined: 05 Aug 2002 Posts: 25

What OS are you running? If it's Vista, try running CMUD as administrator (right click and run as) and see if that makes any difference.

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

XP and I'm logged as the sole account admininistrator.

It has worked before but now it doesn't work.
Further testing has some of my child windows that are blank settings have the same issue.

Tempted to format and reinstall :P

Beginner Joined: 05 Aug 2002 Posts: 25

Latest beta version of CMUD? Fresh install of CMUD?

Format and reinstall seems a little drastic.

Posted: Mon Jun 01, 2009 6:40 pm

Try rebooting your computer. I am not able to reproduce any problem with this on either XP or Vista. So maybe the file just got locked by Windows somehow and needs to be rebooted. Otherwise I'm not sure what else to suggest...it certainly sounds like an OS file access issue, which XP shouldn't really have.

Posted: Mon Jun 01, 2009 9:43 pm

Do have another process that logs or opens that file. Any other file handles to that file via #WRITE or something like that? Did you check to make sure you only have one instance of CMUD running?

What about closing CMUD, unchecking the read-only property and trying again.

[Edit] Yeah... what Zugg said.

Posted: Wed Jun 24, 2009 1:16 pm

I have a simular issue. It will create the Log file, but won't append to it. Rebooting is a null fix.

CMUD version 3.08 Beta 22-May-2009

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc.
System Model Dell DM051
System Type X86-based PC
Processor x86 Family 15 Model 4 Stepping 7 GenuineIntel ~2660 Mhz
Processor x86 Family 15 Model 4 Stepping 7 GenuineIntel ~2660 Mhz
BIOS Version/Date Dell Inc. A07, 1/8/2007
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
Total Physical Memory 3,584.00 MB
Available Physical Memory 2.71 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 5.34 GB
Page File C:\pagefile.sys

Posted: Wed Jun 24, 2009 1:42 pm

On the same note. Once the log has been created on one file, it won't create another log file...

For Example...

When I start my log > #LOG AuctionLog.txt
I get ... Log is on: C:\Documents and Settings\Buddy\My Documents\My Games\CMUD\AuctionLog.txt

This creates a 1kb file which has the windows information captured in the text file, but won't append any further information.

If I then enter > #LOG AuctionLog2.txt
I get ... Log is on: C:\Documents and Settings\Buddy\My Documents\My Games\CMUD\AuctionLog2.txt
This creates a 0kb file which is blank.

If this helps any.

Posted: Wed Jun 24, 2009 2:58 pm

I think I am figuring out what is going on. Will post results shortly.

Posted: Wed Jun 24, 2009 4:35 pm

Ok, after further review, it was the method of my use of the command. I did get this working.
To others that have this issue...
The Help is some help, but leaves out some important notes.

- What you can't do is send multiple log commands (Only 1 #Log filename.txt to the session) then leave it alone. Don't trigger this without turning the log off at the end of what needs to be logged.

For example using Triggers:
#TRIGGER {condition} {#LOG logfile.txt }
Starts the logging of all input from session window.
#TRIGGER{other condition} {#LOG}
Toggles the logging flag to Off, but if top trigger goes off again before this trigger stops the logging, all logging fails. If this trigger goes off a second time, then logging starts again.

The best way to avoid this is to Start the logging with an alias such as
#ALIAS {STARTLOG} {#LOG logfile.txt}
Then use the #LOG in each trigger to start and stop the logging as such…
#TRIGGER {start condition} {#LOG}
#TRIGGER {end condition} {#LOG}

Regards,
Sogom