I'm now using Calmira II -very nice!
Now finally having TCP/IP working, I began wondering if I could establish remote control of DOS and Windows 3.1 on my hot-rodded 5610 from another machine (e.g. from a Win 95 system) (I know, always pushing the limits). I wanted to be able to remotely control both DOS and Win3.1 from a remote, more current system.
Update on the disabled keyword issue...some interesting clues - I don't think it was a keyboard driver issue or a Win 3.11 issue per se, I think it is 386enh mode with an InBoard/PC and the way it hooks (or doesn't) do the right IRQ.
So I grabbed a copy of PCAnywhere 2.0 for DOS and Windows 3.1.x and Win95 (Version 1 didn't support TCP/IP). I almost got it fully working. PCAnywhere remote control worked, but its Host function didn't because it wanted to load a 32bit driver. So I tried starting up Windows 3.1 in enhanced mode and PCAnywhere Host mode loaded fine. Actually, I was surprised Win 3.1 started in enhanced mode at all using the InBoard/386 PC (now a 486 with the Cyrix Cx2 CPU upgrade) - and it runs snappy, but I ended up with only one critical thing not working again as in Win 3.11 earlier - the keyboard. I had thought (see earlier posts) that the issue was a 3.11 keyboard driver related problem, but it must have something to do with the way the InBoard hooks the keyboard interrupt and I've run out of ideas to solve; it might be that it can't be worked around.
The issue at hand isn't remote control - that was just playing around, but the dead keyboard issue still nags me in enhanced more because everything else works fine running Win 3.1 in enhanced mode other than the keyboard. I can run apps, use the mouse...just can't type :-(
PS Another clue, when I return to DOS from a Win 3.1 enhanced session after the keyboard gets disabled, the keyboard remains disabled when I return to DOS (it was working under DOS before starting up Win 3.1 in enhanced mode, e.g. Win /3) . Win 3.1 in protected mode must somehow be stealing the keyboard IRQ, not getting it right, and not returning it going back to DOS.
UPDATE: I am thinking I might be able to solve the problem by upgrading from Windows 3.1 to WFW 3.1 (''Sparta'' 3.10.014e B2) I think its becoming clear to me that the furthest the InBoard/PC can go is running Windows in Standard mode. If I want NetBios/IPX support I have to add full Windows networking support, but MS killed being able to run in standard mode starting with WFW 3.11. The interesting detail is there was a release of WFW 3.1 called Sparta which looks like it adds all of the networking support, including NetBios/IPX, and also runs in standard mode. That also likely means I ought to be able to add the regular TCP/IP stack for Windows rather than use the shim to bridge between DOS and Windows. After that I ought to be able to remotely control other computers over NetBios and allow this system to be controlled remotely (bot Win and DOS using PCAnywhere V2) from other systems running different versions of Windows. It is only a guess - might be worth a shot.
Regards,
Mike