Is anyone else getting a bad filename error when mutil tries to toss the recent 'MyGUI v1.0.2.26.zip' file inbound for 'FSXNet MysticBBS Utils'?
Is anyone else getting a bad filename error when mutil tries to toss the recent 'MyGUI v1.0.2.26.zip' file inbound for 'FSXNet MysticBBS Utils'?
After tossing, a file (ominously named "MyGUI") is left lurking within
the echomail 'in' directory; it appears that mutil is able to move the accompanying .tic, but not the zip file itself, into the 'badfile' directory. I'm guessing this 'MyGUI' file is a remanent of 'MyGUI v1.0.2.26.zip' after the failed move operation.
If I leave the 'MyGUI' file situated within the echomail 'in' directory, fidopoll subsequently times out after 'skipping' said file; if I delete the file, it simply gets delivered again and the cycle begins once more. As fidopoll leaves its semaphore in tact when it stalls, all further
fido traffic is halted until I intervene to remove it.
Any advice would be greatly appreciated.
Is anyone else getting a bad filename error when mutil tries to toss recent 'MyGUI v1.0.2.26.zip' file inbound for 'FSXNet MysticBBS Utils
I noticed the same problem late last night. I brought it to Avon's attention, thinking it was related to the 21:4/100 HUB. Clearly, it's affecting more than just me, though. You're on 21:3/100 HUB, correct?
I've had to clear a couple semaphores as well, but only once, when I interrupted the fidopoll process too early. Don't do that. Let it time
out on its own, and you shouldn't have that particular problem.
For now, I'm doing manual fidopolls. The automatic BinkP is working, but not perfectly, because my HUB keeps trying to send that same file, often first, and then it's timing out.
I'm sure more experienced minds than mine are already working on this!
I've just read your post to Avon, so I'm happy to see I'm not alone. I don't really understand the intricacies of echomail/FTN - I follow
Avon's tutorials and it just works - so I'm always weary of calling
foul. It looks like you're on the ball with this, so I'll relax and have
a cup of tea.
Please, continue providing any information you can about the MyGUI problem. The more information we provide, the faster a solution can be found.
Funny you should mention that as I've just noticed I'm getting a ton of duplicates from fsxNET at the moment. I have a feeling someone's pushing buttons somewhere ^^
Meanwhile, Avon has been made aware of this thread, and (I'm assuming) he's looking into it.
Sorry folks, yes the issue is a file has been hatched by me to fsx_mutl but it contains a space in the file name. This does not (I now know)
play nicely with some mailer software and causes things to bork when the file is trying to be sent/recieved.
Fun times.
Meanwhile, Avon has been made aware of this thread, and (I'm assuming he's looking into it.
Sorry folks, yes the issue is a file has been hatched by me to fsx_mutl but it contains a space in the file name. This does not (I now know)
play nicely with some mailer software and causes things to bork when the file is trying to be sent/recieved.
Sorry folks, yes the issue is a file has been hatched by me to fsx_mutl but it contains a space in the file name. This does not (I now know)
play nicely with some mailer software and causes things to bork when the file is trying to be sent/recieved.
See? Even a genius can make mistakes! Especially on the command line! Never think of yourself as lesser than the rest of us!
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 01:39:52 |
Calls: | 4,624 |
Files: | 8,491 |
Messages: | 348,757 |