1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • I'm missing something.

    From bcw142@21:1/145 to All on Sunday, October 07, 2018 10:56:18
    My 32 bit Linux test BBS doesn't work as of a month ago. It just yields: bcw@livingroom2:/mystic$ ./nodespy
    An unhandled exception occurred at $B73A454A:
    EAccessViolation: Access violation
    $B73A454A <- the first address it jumps to starting nodespy
    -rwxrwxrwx 1 bcw bcw 210180 May 18 09:57 nodespy*

    It does that for all mystic executables. I made a new 'nmystic' from the installer and it does the same thing! Everything else works and I am the
    owner of that area, so it should work without any 'Access violation'. Only
    the 32 bit has changed, 64 bit is normal as are the Pi's. It's like something major changed in Ubuntu 16.04.5 LTS over 16.04.3 LTS which I knew worked.

    Does anyone know a reason the built executables wouldn't work when the installer does?
    -rwxr-xr-x 1 bcw bcw 74476 Apr 21 20:18 install*
    -rw-r--r-- 1 bcw bcw 3321786 Apr 21 20:18 install_data.mys
    They'd both be built by fpc 3.0, so if one works the other should.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Avon@21:1/101 to bcw142 on Monday, October 08, 2018 20:06:51
    On 10/07/18, bcw142 pondered and said...

    My 32 bit Linux test BBS doesn't work as of a month ago. It just yields: bcw@livingroom2:/mystic$ ./nodespy
    An unhandled exception occurred at $B73A454A:
    EAccessViolation: Access violation
    $B73A454A <- the first address it jumps to starting nodespy
    -rwxrwxrwx 1 bcw bcw 210180 May 18 09:57 nodespy*

    Could it be a data file if you are only updating the exe? Or are you doing a fresh install and hitting this error?

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From bcw142@21:1/145.3 to Avon on Tuesday, October 09, 2018 13:17:48
    On 10/08/18, Avon said the following...

    On 10/07/18, bcw142 pondered and said...

    My 32 bit Linux test BBS doesn't work as of a month ago. It just yiel bcw@livingroom2:/mystic$ ./nodespy
    An unhandled exception occurred at $B73A454A:
    EAccessViolation: Access violation
    $B73A454A <- the first address it jumps to starting nodespy -rwxrwxrwx 1 bcw bcw 210180 May 18 09:57 nodespy*

    Could it be a data file if you are only updating the exe? Or are you
    doing a fresh install and hitting this error?


    Nope the nmystic is a full new install so it makes it's own data files (more
    or less empty to start), but they should run. ./mystic -cfg should run, it doesn't it yields the same type of error above! It's very odd, only the 32
    Bit linux does that, everything else works fine.

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, October 10, 2018 12:24:08
    On 10/07/18, bcw142 said the following...

    My 32 bit Linux test BBS doesn't work as of a month ago. It just yields: bcw@livingroom2:/mystic$ ./nodespy
    An unhandled exception occurred at $B73A454A:
    EAccessViolation: Access violation
    $B73A454A <- the first address it jumps to starting nodespy
    -rwxrwxrwx 1 bcw bcw 210180 May 18 09:57 nodespy*

    It does that for all mystic executables. I made a new 'nmystic' from the installer and it does the same thing! Everything else works and I am the owner of that area, so it should work without any 'Access violation'.
    Only the 32 bit has changed, 64 bit is normal as are the Pi's. It's like something major changed in Ubuntu 16.04.5 LTS over 16.04.3 LTS which I knew worked.

    Does anyone know a reason the built executables wouldn't work when the installer does?
    -rwxr-xr-x 1 bcw bcw 74476 Apr 21 20:18 install*
    -rw-r--r-- 1 bcw bcw 3321786 Apr 21 20:18 install_data.mys
    They'd both be built by fpc 3.0, so if one works the other should.

    Are you running 64bit mystic in 32bit world?

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Cyberia BBS | cyberiabbs.zapto.org | San Jose, CA (21:1/120)
  • From bcw142@21:1/145 to Gryphon on Thursday, October 11, 2018 18:15:57
    On 10/10/18, Gryphon said the following...

    On 10/07/18, bcw142 said the following...

    My 32 bit Linux test BBS doesn't work as of a month ago. It just yiel bcw@livingroom2:/mystic$ ./nodespy
    An unhandled exception occurred at $B73A454A:
    EAccessViolation: Access violation
    $B73A454A <- the first address it jumps to starting nodespy -rwxrwxrwx 1 bcw bcw 210180 May 18 09:57 nodespy*

    It does that for all mystic executables. I made a new 'nmystic' from installer and it does the same thing! Everything else works and I am owner of that area, so it should work without any 'Access violation'. Only the 32 bit has changed, 64 bit is normal as are the Pi's. It's l something major changed in Ubuntu 16.04.5 LTS over 16.04.3 LTS which knew worked.

    Does anyone know a reason the built executables wouldn't work when th installer does?
    -rwxr-xr-x 1 bcw bcw 74476 Apr 21 20:18 install*
    -rw-r--r-- 1 bcw bcw 3321786 Apr 21 20:18 install_data.mys
    They'd both be built by fpc 3.0, so if one works the other should.

    Are you running 64bit mystic in 32bit world?

    Nope, using mys112a39_l32.rar and the install runs fine. That's the thing that really confuses me. It as to be the right setup (32 bit) to run the install correctly which it does! It's very odd.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)