Been starting to think this is a mystic issue and not a Usurper game issue. I am posting here to see if anyone has any suggestions if they
have this working under Linux with the Linux version.
I know this topic has been semi ignored by most as most are probably running win32 or the MS-DOS version under win32. But if there is anyone out there with some ideas to clear this up please do let the rest of us know!
On 12/20/16, Pequito said the following...
Been starting to think this is a mystic issue and not a Usurper game issue. I am posting here to see if anyone has any suggestions if they have this working under Linux with the Linux version.
So it's the duplex issue of doubling all characters right? To have any idea we'd need to know the environment it's being run in and what Mystic command are you using to start it. It's the environment setup that is
the issue, same as Linux games under Mystic. Most require curses environment setup, but it would need to be started under Mystic to work (curses that is). As a wild guess add the line:
stty -echo
that turns off the normal echo in Linux shells.
stty echo
turns it back on and 'stty sane' tries to fix a 'crazy' terminal setup.
I am running debian and here is the script:
#!/bin/ksh
NODE=${1}
cd /mystic/game/usrl
cp /mystic/temp${NODE}/door32.sys /mystic/game/usrl/DOOR32.SYS
#./USURPER /N${NODE} 2>&1 >/dev/null
./USURPER /N${NODE}
rm DOOR32.SYS
in mystic its run as a D3 for door32.sys.
Command in mystic: /mystic/game/usrl/usurper.ksh %3
I tried adding the stty -echo before calling of the game and stty echo after and did nothing for it. The command above thats nulled out seems
to work but the input is slightly messed up so avoid using it.
On 12/21/16, Pequito said the following...
I am running debian and here is the script:
#!/bin/ksh
NODE=${1}
cd /mystic/game/usrl
cp /mystic/temp${NODE}/door32.sys /mystic/game/usrl/DOOR32.SYS
#./USURPER /N${NODE} 2>&1 >/dev/null
./USURPER /N${NODE}
rm DOOR32.SYS
in mystic its run as a D3 for door32.sys.
Command in mystic: /mystic/game/usrl/usurper.ksh %3
I tried adding the stty -echo before calling of the game and stty ech after and did nothing for it. The command above thats nulled out see to work but the input is slightly messed up so avoid using it.
Interesting, it's been about 20 years since I last used ksh, been using bash. I used to use ksh or tcsh for about 10 years before that, and csh for a few years before that. Since stty just 'messed things up' I'm guessing that has no real part in the problem. I doubt it's the shell, none of them is that different when it comes to such things. My guess is something in the win32 part of it. Right now I'm typing under bash on Ubuntu 14.04 LTS on an x86 64Bit AMD based system, so much like what
your running. I've run a number of things under wine and dosbox, this problem appears to be with what's doing the win32 part of things. It's
odd that it's any different under Linux than windows in this case,
though all windows from 3.1 up have used win32 including Windows10
(which this system dual boots with). I know how dos works but have never dug in to win32 in that detail as yet - first time for everything huh? I suspect it uses the same interrupts as DOS with different higher level interrupts for services. I'll look at the door32.sys and see if I can figure that driver out as it's possible it's in there. Hmm, nope, it's
not a driver, at least on my system, just a setup list: 00000000 32 0A 37 0A 33 38 34 30 30 0A 4D 79 73 74 69 63 2.7.38400.Mystic 00000010 20 31 2E 31 32 20 41 32 37 0A 32 33 38 0A 42 72 1.12 A27.238.Br 00000020 69 61 6E 20 57 61 6C 6C 61 63 65 0A 62 63 77 31 ian Wallace.bcw1
00000030 34 32 0A 31 30 0A 31 34 34 30 0A 31 0A 32 0A 42.10.1440.1.2. Gets broken up by echomail, but you can see there's no code there. Just baud rate (38400) versions and such, 1440 guessing
that's a floppy size, not sure about that 1 or 2 at the end. DOOR.SYS is much the same with more data. DORINFO1.DEF is more like that door32.sys. DORINFO1.DEF at least shows COM1 as 38400 BAUD,N,8,1,0 so no duplex mode there. I guess systems like ours use the interrupts directly as does windows which is why ARM doesn't really do it. It's relying on the DOS/Windows interrupts of the x86 base. So why a difference? It should
be using the same exact code for Linux & Windows.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 2 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 72:30:46 |
| Calls: | 2,119 |
| Files: | 11,149 |
| D/L today: |
45 files (9,960K bytes) |
| Messages: | 950,581 |