1. Forum
  2. FidoNet
  3. DBRIDGE

  • D'Bridge on 64-bit Windows

    From Nick Andre@1:229/426 to All on Wed Jul 17 22:11:41 2019
    Its possible:

    http://www.columbia.edu/~em36/ntvdmx64.html

    I have D'Bridge running on a 64-bit Windows 7 Lenovo laptop. I strongly suspect other 16-bit Fido/BBS software can work with this; however I have yet to test dialup-modem or Telnet.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Petros Argyrakis@2:410/9 to Nick Andre on Tue Oct 29 01:45:53 2019

    @MSGID: 1:229/426 2394E16D
    Its possible:

    http://www.columbia.edu/~em36/ntvdmx64.html

    I have D'Bridge running on a 64-bit Windows 7 Lenovo laptop. I strongly suspect other 16-bit Fido/BBS software can work with this; however I have yet
    to test dialup-modem or Telnet.

    No complain, just letting you know about my experience.

    Currently I am running DB on a Windows 7 32bit HyperV VM and since I moved to a
    new apartment my "server" is in the living room so I try to reduce the number of VMs running to keep the CPU cool and the fan silent.
    So... 2 DCs, 1 IIS server, a couple of other VMs removed....still no joy

    Why? Because of the NTVDM process on the fido VM..... More that 50% of the virtual cpu for DB.
    So I tried Windows 10 and vDOS.... Running fine but...50% CPU load again...
    and I went back to Win 7 32bit...

    Did you check the ntvdmx64 cpu consumption by any chance?

    --- D'Bridge 3.99
    * Origin: VM/SP (2:410/9)
  • From Nick Andre@1:229/426 to Petros Argyrakis on Mon Oct 28 21:15:33 2019
    On 29 Oct 19 01:45:53, Petros Argyrakis said the following to Nick Andre:

    Why? Because of the NTVDM process on the fido VM..... More that 50% of the virtual cpu for DB.
    So I tried Windows 10 and vDOS.... Running fine but...50% CPU load again... and I went back to Win 7 32bit...

    Did you check the ntvdmx64 cpu consumption by any chance?

    I have not, I would assume the CPU usage would be the same since NTVDM64 is a direct port of the NTVDM system?

    Did you try adjusting the time-slice settings in DB under Config-Basic?

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Petros Argyrakis@2:410/9 to Nick Andre on Tue Oct 29 10:49:19 2019

    @MSGID: 1:229/426 B8E85E28
    On 29 Oct 19 01:45:53, Petros Argyrakis said the following to Nick
    Andre:

    Why? Because of the NTVDM process on the fido VM..... More that 50%
    of the
    virtual cpu for DB.
    So I tried Windows 10 and vDOS.... Running fine but...50% CPU load
    again...
    and I went back to Win 7 32bit...

    Did you check the ntvdmx64 cpu consumption by any chance?

    I have not, I would assume the CPU usage would be the same since NTVDM64
    is a
    direct port of the NTVDM system?

    Did you try adjusting the time-slice settings in DB under Config-Basic?


    On vDOS under 64bit yes and there was no change in CPU. Stuck at 50%.
    Under 32bit huge difference.

    Strange thing... When I am in the DBeditor going through messages the 32bit CPU
    goes to 100% with ntvdm at 97%. Under vDOS on the 64bit goes down to nothing.

    p@rgy

    --- D'Bridge 3.99
    * Origin: VM/SP (2:410/9)