I'm running MakeNL 3.5.0 for OS/2. With the FORsesubmit 1 verb, it
seems to have a limit on how old the segment files can be to be
included in the submission. Does anyone know the actual age
limitation on the stored segment files?
does anyone know the actual age limitation on the stored segment
files?
By default MakeNL goes back 7 weeks from the next publish day when searching for a segment in the masters directory. If your segments
are older than that, copy the most recent one to your mailer
inbound. MakeNL will detect the segment in the inbound directory
and consider it a new update.
Does anyone know the actual age limitation on the stored segment files?
Does anyone know the actual age limitation on the stored segment files?
The solution which I have been using for over 2 decades is to have only 1 region-segment per region, no old stuff, in the directory and use a wildcard ...
For exampple ...
Region 20 region20.* 2:20/0
Region 24 region24.* 2:24/0
Region 25 region25.* 2:25/0
Region 28 region28.* 2:28/0
region 29 region29.* 2:29/0
... etc ...
I'm running MakeNL 3.5.0 for OS/2.Wich one do you use?
With the FORsesubmit 1 verb, itDepends on the version of makenl and depends on the configuration.
seems to have a limit on how old the segment files can be to be
included in the submission.
Does anyone know the actual age limitation on the stored segment
files?
Or am I missing some other verb?Don't know. My crystal ball is on vacation. ;-)
Best regards,Bye/2 Torsten
Marc
Region 20 region20.* 2:20/0
Region 24 region24.* 2:24/0
Region 25 region25.* 2:25/0
Region 28 region28.* 2:28/0
region 29 region29.* 2:29/0
... etc ...
That will only work on systems, where only one dot is accepted in the filename.
I'm running MakeNL 3.5.0 for OS/2.
Wich one do you use?
:-)))I'm running MakeNL 3.5.0 for OS/2.
Wich one do you use?OS/2 32bit
Best regards,Bye/2 Torsten
Marc
Region 20 region20.* 2:20/0
Region 24 region24.* 2:24/0
Region 25 region25.* 2:25/0
Region 28 region28.* 2:28/0
region 29 region29.* 2:29/0
... etc ...
That will only work on systems, where only one dot is accepted in the
filename.
You make it sound as if that's the exception while in fact it's the rule.
So indeed, from my point of view, your option only works if makenl runs in DOS or or a DOSbox. If DOS and DOSbox are the norm in Fidonet, then my view is indeed an exeption.
So indeed, from my point of view, your option only works if makenl runs
in DOS or or a DOSbox. If DOS and DOSbox are the norm in Fidonet, then
my view is indeed an exeption.
MakeNL/DOS has ran flawlessly here and I have no intention on moving off DOS.
16.12.2019 21:27, Marc Lewis schrieb an Torsten Bamberg:
I'm running MakeNL 3.5.0 for OS/2.
Wich one do you use?OS/2 32bit
:-)))
Okay, I ask again, which version exactly? Looks like this if you do
a 'makenl.exe >> version.txt'
Looks like this:
=##= Anfang "mknlversion.txt" =##=
MakeNL 3.5.0 (OS/2 32-bit) compiled with EMX on Dec 17 2019
12:06:17 =##= Ende "mknlversion.txt" =##=
MakeNL/DOS has ran flawlessly here and I have no intention on moving o DOS.
Why should you?
MakeNL/DOS has ran flawlessly here and I have no intention on moving o >> NA> DOS.
Why should you?
No particular reason, other than I deal with a lot of Linux fans.
Hello All.
I'm running MakeNL 3.5.0 for OS/2. With the FORsesubmit 1 verb, it
Best regards,
Marc
(1:396/45)
Sunday December 15 2019 19:21, you wrote to All:
Hello All.
I'm running MakeNL 3.5.0 for OS/2. With the FORsesubmit 1 verb, it
^--- Typo ?
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 01:01:06 |
Calls: | 635 |
Calls today: | 2 |
Files: | 7,638 |
Messages: | 292,270 |