VOGONS

Search

Common searches

DirectSerial patch

Topic actions

Reply 180 of 353, by Pan

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I assume by "directserial" though, you are referring to real serial connections rather than virtual ones? It seems you are referring to Linux serial/USB devices.

I went to try and compile with the nullmodem7 patch, but it seems to of disappeared. Can you re-post it? 😀 Thanks

Has there been any command changes for the emulated modem in nullmodem7? It seems not, but I just wanted to check to see if it was worth testing further as well as compiling.

Thanks

Reply 182 of 353, by Pan

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Sorry, I must of missed that when I was looking back.

I managed to compile the latest CVS with the nullmodem7 patch without any problems at all on Linux. After testing it, I can confirm that the modem and nullmodem code appear to be working in the same way as nullmodem6 😀

I think this patch has really added to the multiplayer options in Dosbox. It's a good candidate to be included in the official CVS for the long-term.

Great work Hal 😀

Reply 183 of 353, by wd

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

@hal: there should be a callback type that starts off with a STI,
so you don't need the callback idling, right?

+	// the first thing this handler does in real BIOS is STI
+	CALLBACK_Idle();

Please try to avoid (if possible of course) callback code that starts
a new core.

Reply 184 of 353, by h-a-l-9000

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

That code is older than my knowledge about callback types...
This has the same effect (the right side column of inttest):
callback[3].Install(&INT14_Handler,CB_IRET_STI,"Int 14 COM-port");

There are other parts where I have to burn time

while(!(LSR&0x20)) {
CALLBACK_Idle();
}
Is there a better way?

1+1=10

Reply 185 of 353, by wd

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

> Is there a better way?

It's quite hard to replace the idling as is, where it was possible in the
sources it is already done. Think when browsing through the ipx and
serial code it didn't look replacable, but in some cases i wasn't sure
why it was needed.
Don't bother with this too much 😉

Reply 186 of 353, by h-a-l-9000

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

8th "revision":

- fix the callback_idle
- add STDAUX support (empire com1)
- remove message "bios: port x does not exist"
- count and display the IFlag status on serial overrun errors

Maybe the nullmodem should be mentioned in the readme?

Attachments

  • Filename
    nullmodem8.diff
    File size
    166.52 KiB
    Downloads
    51 downloads
    File license
    Fair use/fair dealing exception

Reply 187 of 353, by MiniMax

Posted on 
User metadata
Rank Moderator
Rank
Moderator
h-a-l-9000 wrote:

Maybe the nullmodem should be mentioned in the readme?

I am sure that if you write a paragraph or two about it, it will find its way into the ReadMe in no time.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 188 of 353, by h-a-l-9000

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

Maybe like this (it has a few not related random ideas as well)

Index: README
===================================================================
RCS file: /cvsroot/dosbox/dosbox/README,v
retrieving revision 1.54
diff -u -r1.54 README
--- README	8 Oct 2006 19:26:04 -0000	1.54
+++ README	22 Dec 2006 01:58:57 -0000
@@ -27,12 +27,13 @@
 5. Special Keys
 6. Keymapper
 7. System Requirements
-8. To run resource-demanding games
-9. The config file
-10. The language file
-11. Building your own version of DOSBox
-12. Special thanks
-13. Contact
+8. Serial Multiplayer feature
+9. To run resource-demanding games
+10. The config file
+11. The language file
+12. Building your own version of DOSBox
+13. Special thanks
+14. Contact
 
 
 ==============
@@ -49,6 +50,7 @@
 Some Frequently Asked Questions:
 
 Q: I've got a Z instead of a C at the prompt.
+Q: I still have a Z instead of a C. How do I navigate in DOS?
 Q: My game crashes when using opengl/nb or is much slower.
 Q: My CD-ROM doesn't work.
 Q: The mouse doesn't work.
@@ -56,6 +58,8 @@
 Q: I can't type \ or : in DOSBox.
 Q: The game/application can't find its CD-ROM.
 Q: The game/application runs much too slow!
+Q: Can DOSBox harm my computer?
+Q: DOSBox cannot use more than 50% CPU no matter what cycles I set.
 Q: I would like to change the memory size/cpu speed/ems/soundblaster IRQ.
 Q: What sound hardware does DOSBox presently emulate?
 Q: DOSBox crashes on startup and I'm running arts
@@ -72,6 +76,20 @@
    In Linux, "mount c /home/username" will give you a C drive in DOSBox
    which points to /home/username in Linux.
 
+   
+Q: I still have a Z instead of a C. How do I navigate in DOS?
+A: To change to your new C drive, type "c:".
+   To open a folder, type "cd folder".
+   
+   "dir" lets you list the contents of the current folder.
+   "dir /p" lists the contents per screen.
+   
+   Executable files are FILENAME.EXE, FILENAME.COM, FILENAME.BAT.
+   Type "filename" to run it.
+   
+   Leave the folder with "cd..". "cd\" brings you back to the root of the
…Show last 181 lines
+   drive.
+
 
 Q: My game crashes when using opengl/nb or is much slower.
 A: Somehow our opengl code isn't entirely stable on some platforms. 
@@ -136,6 +154,18 @@
 A: Look at the section "To run resource-demanding games" for more information.
 
 
+Q: Can DOSBox harm my computer?
+A: DOSBox can not harm your computer more than any other ressource demanding
+   program. Increasing the cycles does not overclock your real CPU.
+   Setting the cycles too high has a negative performance effect on the 
+   software running inside DOSBox.
+
+
+Q: DOSBox cannot use more than 50% CPU no matter what cycles I set.
+A: Your processor has the hyperthreading or a similar feature. DOSBox is 
+   mostly singlethreaded and therefore cannot use more than 50%.
+
+
 Q: I would like to change the memory size/cpu speed/ems/soundblaster IRQ.
 A: This is possible! Just create a config file: config -writeconf configfile .
    Start your favourite editor and look at all the settings present. To
@@ -552,6 +582,10 @@
   For example, if your server is at bob.dosbox.com, 
   you would type "IPXNET CONNECT bob.dosbox.com" on every non-server system. 
   
+  To play games that need Netbios a file named NETBIOS.EXE from Novell is
+  needed. Establish the IPX connection as explained above, then run 
+  "netbios.exe". 
+  
   The following is an IPXNET command reference: 
 
   IPXNET CONNECT 
@@ -578,9 +612,16 @@
      session. By default, the server will accept connections on UDP port 
      213, though this can be changed. Once the server is started, DOSBox 
      will automatically start a client connection to the IPX tunnelling server.
-
+    
      The syntax for IPXNET STARTSERVER is:
      IPXNET STARTSERVER <port>
+     
+     If the server is behind a router, UDP port <port> needs to be forwarded
+     to that computer.
+     
+     On Linux/Unix-based systems port numbers smaller than 1023 can only be
+     used with root privileges. Use ports greater than 1023 on those systems.
+     
 
   IPXNET STOPSERVER
 
@@ -607,12 +648,10 @@
      IPX tunnelling network. For a list of all computers connected to the 
      network use the IPXNET PING command. 
 
-The syntax for IPXNET STATUS is: 
-IPXNET STATUS 
-
-For more information use the /? command line switch with the programs.

-
+     The syntax for IPXNET STATUS is: 
+     IPXNET STATUS 
 
+  For more information use the /? command line switch with the programs.
 
 
 ================
@@ -723,10 +762,52 @@
 them to run fast, though! Be sure to read the next section on how to speed
 it up somewhat.
 
+==============================
+8. Serial Multiplayer feature:
+==============================
+
+DOSBox can emulate a serial nullmodem cable over network and internet.
+This is controlled by the [serialports] section in the DOSBox configuration
+file and can as well be reconfigured during runtime.
+To make a nullmodem connection, one side needs to be the server and one 
+the client. 
 
+The server is being set up like this:
+   serial1=nullmodem
+
+The client:
+   serial1=nullmodem server:<IP or name of the server>
+   
+Now start your game and choose nullmodem / serial cable / already connected
+as multiplayer method on COM1. Set the same baudrate on both computers.
+
+Furthermore, additional parameters can be specified to control the behavior
+of the nullmodem connection. These are all parameters:
+
+ * port:         - TCP port number. Default: 23
+ * rxdelay:      - how long (milliseconds) to delay received data if the
+                   interface is not ready. Increase this value if you encounter
+                   overrun errors in the DOSBox Status Window. Default: 100
+ * txdelay:      - how long to gather data before sending a packet. Default: 12
+ 	               (reduces Network overhead)
+ * server:       - This nullmodem will be a client connecting to the specified 
+                   server. (No server argument: be a server.)
+ * transparent:1 - Only send the serial data, no RTS/DTR handshake. Use this
+                   when connecting to anyting other than a nullmodem.
+ * telnet:1      - Interpret Telnet data from the remote site. Automatically
+                   sets transparent.
+ * usedtr:1      - The connection will not be established until DTR is switched
+                   on by the DOS program. Useful for modem terminals.
+                   Automatically sets transparent.
+ * inhsocket:1   - Use a socket passed to DOSBox by command line. Automatically
+                   sets transparent. (Socket Inheritance: It is used for
+                   playing old DOS door games on new BBS software.)
+
+Example: Be a server listening on TCP port 5000.
+   serial1=nullmodem server:<IP or name of the server> port:5000 rxdelay:1000
 
 ===================================
-8. To run resource-demanding games: 
+9. To run resource-demanding games: 
 ===================================
 
 DOSBox emulates the CPU, the sound and graphic cards, and some other
@@ -757,7 +838,7 @@
 
 
 ===================
-9. The Config File:
+10. The Config File:
 ===================
 
 A config file can be generated by CONFIG.COM, which can be found on the 
@@ -765,6 +846,9 @@
 programs section of the readme for usage of CONFIG.COM.
 You can edit the generated configfile to customize DOSBox.
 
+On Windows, a pre-generated config file (dosbox.conf) can be opened from
+the DOSBox start menu entry.
+
 The file is divided into several sections (the names have [] around it). 
 Some sections have options you can set.
 # and % indicate comment-lines. 
@@ -780,7 +864,7 @@
 
 
 ======================
-10. The Language File:
+11. The Language File:
 ======================
 
 A language file can be generated by CONFIG.COM. 
@@ -792,7 +876,7 @@
 
 
 ========================================
-11. Building your own version of DOSBox:
+12. Building your own version of DOSBox:
 ========================================
 
 Download the source.
@@ -801,7 +885,7 @@
 
 
 ===================
-12. Special Thanks:
+13. Special Thanks:
 ===================
 
 Vlad R. of the VDMSound project for excellent SoundBlaster info.
@@ -815,7 +899,7 @@
 
 
 ============
-13. Contact:
+14. Contact:
 ============
 
 See the site:

Reply 189 of 353, by rome

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hi everyone,
I have communication problem with running old DOS based software for PLC (PSR,FUPLA if someone familiar to..) in DOSBOX. Original software works under WIN XP without any problems with communication even my laptop doesn't have real comport (I'm using PCMCI RS232 converter with attached ATEN RS232-485 converter) The reason why I've decided to use DOSBOX - original DOS was running under XP with restriction 0-exp.memory,so just no more two segments(windows) could be opened for debugging which is very bothering (you have to close current segment to open another one) etc. In DOSBOX 0.65 I can use my software fine - no memory restrictions a lot of segments could be opened at the same time , so I can use DOSBOX for tracing links between software modules, but I can't get communication with real hardware.In this case I'm trying to use(instead of PCMCI) COM port from laptop's docking station(IBM Thinkpad T41) with attached ATEN RS232-485 converter. Other note - there is another solution using Virtual PC and running real MS DOS under virtual machin which works fine with COM port from docking station.
When I've discovered DOSBOX I tried to avoid of using Virtual PC.
I went through all topics,tried all recomendations CVS,improved DOSBOX serial versions,dos conf modifications from great guys like h-a-l and ohers(thanks a lot to all..) but i can't succeed. I just didn't try to boot MS DOS inside DOSBOX (cause i really don't know how to do that).Will it help too much? And is the COM port from docking station could considered like real com port (or it's still dummy one)? Is there any possibilities to use PCMCI-RS232 converters with DOSBOX?
Any comments,advise will be appreciated.

Reply 191 of 353, by rome

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Thank you for quick respond,
I'm not just following you - pls take my excuse 😕 .
Did I understand you correctly -there is still possibility increase EMS (in my ThinkPad machine) by using some settings? All what I know is following - all attempts to get that full functional DOS application work in those machines are failed (IT team). 😢 This application has been modified to make it work under XP with restricted options (0 EMS which is the major case here). But there isn't communication problems even without using real COMport.The solutions known up to date:
1.Kill all USB ports - and in this way release EMS memory resourses
2.Use Virtual PC and run real MS DOS (with hard drive partition etc)
So, in this case this DOS application works fine.
3. Use this DOS based software in Windows (0 EMS, 1 software segment working at the time) - no communication problems either by using docking station COMport or PCMCI-RS232 converter plus attached RS232-RS485

That is why I was trying to use DOSBOX to avoid all these complications. Everybody impressed! No problem with Editor and Debbuger functions enumerous segments could be opened at the same time and edited. But it seems to me COMport from ThinkPad Docking station couldn't be used in DOSBOX like realcomport (under Virtual PC the same COM port with the same DOS application works fine). Also,looks like I can't use PCMCI type RS232 converter. it seems to get DOSBOX work the only way to buy laptop with built in DB9 RS232 (smth. from Dell,Toshiba, buisness family laptops) 🤣
Please advise,
Thanks again

Reply 194 of 353, by Pan

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I already did, that's what I can't understand. This is the second time this has happened, so it can't just be an accident. That patch did not show up on Hal's post when I looked earlier. I specifically looked there.

I have a suspicion attachments only show up if you are logged in, let me check....

Go to top of page Go to top of page
Back to DOSBox Patches
Close window
Close window