1. Forum
  2. FIDO
  3. MYSTIC

  • Cannot get Usurper Door to run

    From Jeff Earle@1:229/700 to All on Wed Mar 31 13:42:23 2021
    Having some issues with this door.

    1st off, I can run it in local mode. Open cmd, change to the Usurper dir and run usurper32.exe.

    2nd, I can run it by opening file explorer to the Usurper dir and double click on usurper32.exe. Starts but get USURP.CTL Missing and Can't find DOOR32.SYS (this one I get, I didn't tell Usurper where it is kept).

    3rd, I can run editor32.exe either way, cmd or double click and use all of
    the commands in it (reset, edit player, etc).

    Mystic refuses to run it. I have it setup with command D3. I can see that the DOOR32.SYS file is created (along with the rest of the drop files).

    I have tried running directly from the command with %# as the node # and
    temp# directory. c:\mystic\doors\usurper\usurper32.exe /N%#
    /Pc:\mystic\temp%# is the command.

    I have even tried running it from a batch file in the command. No joy.

    I also tried using the DD door comand (I know it doesn't create the
    DOOR32.SYS) just to see if I could get anything. Again no joy.

    Any help would be apprecited. Oh yes, its version Usurper v0.24. I also have NTVMx64 installed.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
    * Origin: Mystic Realms (1:229/700)
  • From g00r00@1:129/215 to Jeff Earle on Fri Apr 2 23:56:56 2021
    Having some issues with this door.

    1st off, I can run it in local mode. Open cmd, change to the Usurper dir and run usurper32.exe.

    I'll try to get some time to test with it. I do seem to remember people saying the 32-bit version was broken in general but I could be mistaken. They were recommending people use the DOS version.

    --- Mystic BBS v1.12 A47 2021/04/01 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jeff Earle@1:229/700 to g00r00 on Sat Apr 3 05:04:49 2021
    1st off, I can run it in local mode. Open cmd, change to the Usurper and run usurper32.exe.

    I'll try to get some time to test with it. I do seem to remember people saying the 32-bit version was broken in general but I could be mistaken. They were recommending people use the DOS version.

    I did not know that there were reports of issues. I will do some research.
    I dont have a problem with running non-win32 versions, I have dosbox working very well with many older doors. I would prefer to the 32bit version as its faster to load. I am still trying to figure out what the problem is. No log makes it difficult to diagnose.

    Thanks

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
    * Origin: Mystic Realms (1:229/700)
  • From g00r00@1:129/215 to Jeff Earle on Sat Apr 3 12:19:57 2021
    I did not know that there were reports of issues. I will do some
    research. I dont have a problem with running non-win32 versions, I have dosbox working very well with many older doors. I would prefer to the 32bit version as its faster to load. I am still trying to figure out
    what the problem is. No log makes it difficult to diagnose.

    Mystic is just executing a command line, which is logged - so there isn't really anything else to log on the Mystic side.

    --- Mystic BBS v1.12 A47 2021/04/01 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)