Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq:win [2010/02/23 19:38] – digitalman | faq:win [2015/08/14 01:33] – [SBBSEXEC.DLL] Mention the 16-bit application support control panel setting digital man | ||
---|---|---|---|
Line 3: | Line 3: | ||
Answers to Frequently Asked Questions regarding Synchronet and Microsoft Windows operating systems. | Answers to Frequently Asked Questions regarding Synchronet and Microsoft Windows operating systems. | ||
- | * [[# | + | * [[# |
- | * [[#64-bit|Why don't DOS programs | + | * [[#win64|Why don't DOS programs |
* [[# | * [[# | ||
stealing the keyboard/ | stealing the keyboard/ | ||
* [[# | * [[# | ||
+ | * [[# | ||
+ | * [[# | ||
===== SBBSEXEC.DLL ===== | ===== SBBSEXEC.DLL ===== | ||
- | **Question: | + | :?: **Question: |
- | Why don't DOS programs (e.g. editors, door games) run on my //Windows Vista// | + | Why don't DOS programs (e.g. editors, door games) run on my //Windows Vista//, //Windows 7//, //Windows 8// or //Windows 10// 32-bit |
- | **Answer: | + | :!: **Answer: |
- | There are 2 new requirements for 16-bit DOS programs to work under Synchronet-Win32 on //Windows Vista// | + | There are 2 new requirements for 16-bit DOS programs to work under Synchronet-Win32 on //Windows Vista+// 32-bit |
- You must have '' | - You must have '' | ||
- You must copy '' | - You must copy '' | ||
- | ===== 64-bit ===== | + | Beginning with Windows 8, Microsoft disables support for 16-bit (DOS) programs |
- | **Question: | + | |
- | Why won' | + | |
- | **Answer: | + | 64-bit (x64, amd64) editions of Windows cannot run 16-bit DOS programs from Synchronet. See the next FAQ item for the details. |
+ | |||
+ | ===== Win64 ===== | ||
+ | :?: **Question: | ||
+ | Why won't DOS programs run on my 64-bit computer running a 64-bit version of Windows? | ||
+ | |||
+ | {{: | ||
+ | |||
+ | :!: **Answer: | ||
Microsoft does not include Virtual DOS Machine (NTVDM) support in their | Microsoft does not include Virtual DOS Machine (NTVDM) support in their | ||
64-bit operating systems. Synchronet for Windows relies on NTVDM for | 64-bit operating systems. Synchronet for Windows relies on NTVDM for | ||
- | 16-bit DOS program support, so you need to either run a 32-bit Windows | + | 16-bit DOS program support, so you need to either run a 32-bit Windows |
(e.g. re-install, use dual-boot, or run in a Virtual Machine) or forgo | (e.g. re-install, use dual-boot, or run in a Virtual Machine) or forgo | ||
- | DOS programs on your BBS. | + | DOS programs on your BBS. Yes, you can run 32-bit Windows versions of Synchronet on a 64-bit (x64) system. |
- | | + | |
+ | As of March 12, 2014, you can disable DOS program support in a single instance of Synchronet with the '' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **Note**: The Synchronet [[server: | ||
+ | |||
+ | | ||
+ | ║ | ||
+ | ╠════════════════════════════╣ | ||
+ | ║ │cmd.exe | ||
+ | ║ │sh ║ | ||
+ | ║ │csh | ||
+ | ║ │bash | ||
+ | ║ │node | ||
+ | ║ │smbutil | ||
+ | ║ │zip | ||
+ | ║ │unzip | ||
+ | ║ │pkzip25 | ||
+ | ║ │mp3info | ||
+ | ║ │ ║ | ||
+ | ╚════════════════════════════╝ | ||
===== External Popup ===== | ===== External Popup ===== | ||
- | **Question: | + | :?: **Question: |
How do I keep external programs (doors) from popping up windows and | How do I keep external programs (doors) from popping up windows and | ||
stealing the keyboard/ | stealing the keyboard/ | ||
- | **Answer: | + | :!: **Answer: |
- | Check SBBSCTRL: | + | Check [[:monitor:SBBSCTRL]]: |
===== Socket I/O ===== | ===== Socket I/O ===== | ||
- | **Question: | + | :?: **Question: |
- | Why do external programs that use socket I/O (e.g. Synchronet Blackjack, Synchronet BBS List, DoorMUD, SEXYZ) not work on my BBS? | + | Why do external programs that use socket I/O (e.g. Synchronet Blackjack, Synchronet BBS List, DoorMUD, |
- | **Answer: | + | :!: **Answer: |
Some " | Some " | ||
+ | |||
+ | Another potential cause of this Windows problem is malware (viruses, trojans, etc.) which disable the Windows Firewall Service. Even if/when the malware is successfully removed, the damage done to Windows (and specifically the registry) remains. One recent sighting of this problem was rectified with the following steps (found [[http:// | ||
+ | |||
+ | - In Registry Editor, browse to the key '' | ||
+ | - Right-click // | ||
+ | - Click //Add//. | ||
+ | - In the “Enter the object names to select” field, type “NT SERVICE\mpssvc”. Then click //Check Names//. The name should change to '' | ||
+ | - Click //OK//. | ||
+ | - Check //Full Control// checkbox in the //Allow// column. | ||
+ | - Click //OK//. | ||
+ | |||
+ | ===== Dial-up ===== | ||
+ | :?: **Question: | ||
+ | How do I setup my BBS to support dial-up modems/ | ||
+ | |||
+ | :!: **Answer: | ||
+ | Use the [[util: | ||
+ | |||
+ | ===== ANSI.SYS ===== | ||
+ | :?: **Question: | ||
+ | Why is the console output of some 16-bit DOS programs not intercepted/ | ||
+ | |||
+ | :!: **Answer: | ||
+ | Check that your '' | ||
===== See Also ===== | ===== See Also ===== | ||
* [[:faq:|FAQ Index]] | * [[:faq:|FAQ Index]] | ||