Subj : Release of v3.4?
To   : Roy Witt
From : Kees van Eeten
Date : Fri May 24 2013 13:20:36

Hello Roy!

22 May 13 15:19, you wrote to me:

 RW> Kees van Eeten wrote to Roy Witt:

 RW>>> My RC, Marc Lewis can't use MNL on his OS/2 system and has reverted
 RW>>> back to using NLMake. Some of the new keywords produce errors when
 RW>>> MNL encounters a PVT listing with a 000.0.0.0.0 number in the phone
 RW>>> field of an ION node. We've been waiting for months on this issue,
 RW>>> which Andrew Leary has been aware that it exists and has stated that
 RW>>> the MNL team is working on it.

 KvE>>  Someone must have missed something in the specs.

 RW> That could be. My MNL compiled netseg crashed the RC19's OS/2 system and
 RW> so did a few other netsegs in R19...meanwhile, I've blocked the keywords
 RW> that crashed his system...


 RW> ; control file for Net 387 using
 RW> ; MakeNL v3.3.1 -- Windows 32 Bit Version
 RW> ; nodelist control file.
 RW> ;ALLOWUNPUB 1
 RW> ;MINphone 1

 RW>   ________ Roy snipped text here!________O/___________________
 RW>                                          O\

 I have looked at your remarks again. It seems to me that you talk of two
 distinct problems.

 The first is where you get error messages is a specific case, the seconds
 where your RC has a program crash on a OS/2 system.

 In your case a line with  Pvt,......,000.0.0.0.0,........
 produces an error message.

 Your current segment does not list a dotted number in te telephone field.
 And the logic in the programs is that a line starting with Pvt, has the
 word "Unpublished" in the telephonenumber field.

 The flag "ALLOWUNPUB 1" allows the word "Unpublished" to be used in lines
 starting with other tags than "Pvt"

 The flag "MINPHONE 1" counts the number of "-" separated groups in a
 telephone number. For a value other than "Unpublished" it should be set
 to "1" if there are no dashes in the phone number field.

 What is not clear what causes makenl to crash on OS/2. If it is something
 not in line with the specs, it should produce an error message, so
 it is something more serious.

 If those who have this problem are not in a position to hunt for the
 problem themselves, someone else has to be found, who can reproduce and
 analyse the same problem.

 Lets hope that we can entice Ulrich to have a go, or whoever compiled the
 executables for OS/2.

 As a last thought, there should not be a problem in using NLMAKE, if it can
 handle the envisioned changes to the nodelist.

Kees

--- FPD v2.9.040207  GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that I know nothing. (2:280/5003.4)

.