Open AviatingPenguin opened 2 years ago
Ok, I figured it out, it took me the better part of the day but I have it working and showing on the client. first I had to delete usurp.ctl if I had it on it wouldn't work at all, then I have these settings in scfg Command line: usurper /p%n /n%1 I/O: socket Native exe: yes Use shell: yes Modify user data: no Exe on event: no Pause after exe: no BBS drop file type: Mystic door32.sys
Which version of the binaries are you running? I have only been able to get the DOS ones to work correctly. The 32-bit version starts, and displays on the client screen, but client input is ignored so you're just locked up on the title screen. I don't mind running the DOS version, but I would prefer the speed of the 32-bit one if I can ever get it to work correctly.
I'm running the 64 bit binaries with the above settings in scfg of synchronet and it's running flawlessly right now
Okay, thanks. That was what I was afraid of. :) My BBS VM is 32-bit Win10, so I can't use the 64-bit binaries. I'll just stick with what I've got working until another build is compiled and see if I can get that one to work. I appreciate the response.
Install a copy into a new directory and have it so only the sysop can access it then you can play around and see if you can figure out the 32 bit version and get it to work that's the only thing I can think of. Try with the settings I use and see if it works for you if you do and let me know because now I'm curious!
Turns out, the issue was my Door server. It doesn't seem to like windows native doors. When I moved it to Rick Parrish's GameSrv door server, it works fine. (Deleting USURP.CTL was still necessary.)
I'm running The Major BBS, so getting doors to work is quite a bit more complicated than with Synchronet. But, now I've got the 32-bit version running fine. That makes me happy. :)
So if I install up to Version 0.24 the game will load (but it takes at least 5 minutes for it to load) and if I upgrade to 0.25 the game loads instantly but it doesn't show on the client screen only server side and I'm not sure what the problem is (I'm running synchronet on Windows 10)