| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Dos doors under OS/2 |
ES> It looks like Max isn't passing the right comm handle info to door.sys ES> though. My modem is on com2 and it writes it's connected to com3 which ES> is unavailable and causes errors??? Same here. Max is doing right, its passing the com port handle that OS/2 uses to the door which is bad for DOS doors. Here is a fix that I did overhere that works great! What it does is set the com port on a per task basis. I modified the DOORSYS.MEC file to look like: === [delete]node%K\Door.Sys [open]node%K\Door.Sys [iftask]1 [write]COM2: [iftask]2 [write]COM3: [iftask]3 [write]COM4: [iftask]4 [write]COM5: [iftask]5 [write]COM6: [write]%b[comment Baud rate] [write]8[comment Stop bits] [write]%k[comment Node number] [write]N[comment DTE locked? -- Set to baud rate if running a locked port!!!] === These are the first few lines of the DOORSYS.MEC but I modified the part that writes the comport to check the task and write the com port that I use for that task. I also modified the location of where I write the door.sys file so be aware of that, in my case it would be written to \max\node01\door.sys if the node was 1 and 02 if the node is 2. Someone might have a better way, but this was what I use and I've never had a problem with it. matt --- Blue Wave/DOS v2.30 [NR]* Origin: The PostOffice - telnet: bbs.cisvcs.net (1:106/1) SEEN-BY: 396/1 632/0 371 633/260 262 267 270 284 371 634/397 635/444 506 725 SEEN-BY: 635/728 639/252 670/218 @PATH: 106/1 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.