The big question (and it might have already been answered somewhere) is has anyone tried running DB on different Windows Server verions? 2008R2, or ma even 2016. Not sure my other utilities will work and will see if I can do some testing first.
Please look into the NTVDM64 project as per the BBS_CARNIVAL echo.
D'Bridge works on Server 2016/2019 just fine with this approach.
At this point I need to decide if I want to move the BBS network share to a existing Windows 2016 server or leave it on the tossing VM (and upgrade it from Windows 7 32-bit to 2016 server).
I would clone it first if possible, for testing, or fire up a new 2016 instance.
It seems to root of the problem is Windows non-server only allows a
total of 20 connections for a share. For some unknown reason, Samba
on eCS and ArcaOS use 4 connections for each BBS node.
On the event that I hit the 20 connection limit, JFS crashes and
the eCS VM dumps.
this makes sense if there's four shares in use...
this sounds like an improperly handled exception with the connection is refused...
this makes sense if there's four shares in use...
In this case it is a single share, but (4) BBS nodes waiting
for caller. This uses a total of (16) connections to my
Windows VM.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,035 |
Nodes: | 15 (0 / 15) |
Uptime: | 179:48:11 |
Calls: | 710 |
Calls today: | 3 |
Files: | 95,166 |
U/L today: |
3 files (545K bytes) |
D/L today: |
142 files (170M bytes) |
Messages: | 298,130 |
Posted today: | 1 |