I found a work-around until I get this resolved. I have a script to remove the two .. before the packet name and sbbsecho is able to process it even if it's more than 8 characters. That is for inbound. Outbound works fine.
Re: Alternative...
By: Storm Tracker to All on Sun Aug 05 2018 01:57 am
I found a work-around until I get this resolved. I have a script to remove the two .. before the packet name and sbbsecho is able to process it even if it's more than 8 characters. That is for inbound. Outbound works fine.
I've been following what you have been saying about all this and sorry
to say I have no idea or comment what might be happening.
Looks like a linux path beggining with .., that shouldn't happen. Is
the tosser you are receiveing these files from running on linux or windows?
I wonder if it would make a difference if you made sure the path
settings there used "/" as a path specifier on linux, or "\" on
windows.
I wonder if it would make a difference if you made sure the path settings there used "/" as a path specifier on linux, or "\" on windows.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495937:19:35 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,956 |