Hello, Maurice Kinal.
On 11/01/15 21.41 you wrote:

 MK> -={ dimanche, janvier 11 2015, 13:41:05 -0800 }=- Hey Alexey! Just 
 MK> to make sure it isn't a x86_64 issue I repeated the nasm/syslinux 
 MK> on the below processor; -={ output of 'lscpu' starts }=- 
 MK> Architecture:          i686 CPU op-mode(s):        32-bit Byte 
 MK> Order:            Little Endian CPU(s):                1 On-line 
 MK> CPU(s) list:   0 Thread(s) per core:    1 Core(s) per socket:    1 
 MK> Socket(s):             1 Vendor ID:             GenuineIntel CPU 
 MK> family:            6 Model:                 13 Model name:         
 MK> Intel(R) Celeron(R) M processor          900MHz Stepping:          
 MK> 6 CPU MHz:               630.104 BogoMIPS:              1260.20

damm near my quad p2 in bogomips lol :)
 
 MK> -={ output of 'lscpu' ends }=- Exactly the same problem as before 
 MK> using nasm-2.11.06 and syslinux-6.03 which are both the latest 
 MK> versions.  From what I've read and seen it looks to be an issue 
 MK> with Intel processors and nano-2.11.06 although syslinux-6.03 
 MK> could still have some bugs in it.  Mind you that doesn't 
 MK> completely jive with what I saw when using the latest nasm 
 MK> snapshot so there it is more likely that the fault lies with nasm. 
 MK> Aside:  Using vim to do Fidonet messaging is definetly kickass.  
 MK> :-)

some might patch vim to use smapi.lib ? :)

we could possible get first working fidonet READER FOR UNICODE then ?

 MK> Life is good, Maurice

he yep it just better with gentoo :)
 
 MK> ... Don't cry for me I have vi. --- GNU bash, version 
 MK> Society - Ladysmith BC, Canada (1:153/7001.0)

--
Best regards, Posted using Hotdoged on Android
--- Hotdoged/2.10/Android