It has been a few versions now that DBRIDGE on WIN10 32bit crashes with the following error:
ERROR: Non-standard error #204 @ 1d7e:0370 MEM=53737 MAX=53737
@MSGID: 1:229/426 DA44350C
@REPLY: 2:410/9 0d3e4b17
@TZUTC: -0500
On 17 Sep 21 09:53:58, Petros Argyrakis said the following to All:
It has been a few versions now that DBRIDGE on WIN10 32bit crasheswith the
following error:
ERROR: Non-standard error #204 @ 1d7e:0370 MEM=53737 MAX=53737
We have traded emails on this so I'm not sure why its being posted here;
it
seems to work perfectly fine on Windows 10.
I have tested with Windows 10 Enterprise LTSC builds 1607 and 1809.
The problems you are having with Error 204 and "Unable to write" are very
likely to do with something else related to Windows and most likely
either a
corrupt NTVDM subsystem or anti-virus software or something wrong with
the
file system.
It has been a few versions now that DBRIDGE on WIN10 32bit crashesI also run D'Bridge in VM Virtualbox Windows 10 32 bits system.
with the following error:
ERROR: Non-standard error #204 @ 1d7e:0370 MEM=53737 MAX=53737
ANy idea how to fix this?
17 Sep 21 09:53, you wrote to all:
It has been a few versions now that DBRIDGE on WIN10 32bit crashes LB>PA> with the following error:
ERROR: Non-standard error #204 @ 1d7e:0370 MEM=53737 MAX=53737
ANy idea how to fix this?I also run D'Bridge in VM Virtualbox Windows 10 32 bits system.
The first D'Bridge installation went well until I tried to start DB lots
of errors.
After that I started DB as administrator and since then I have no more problems with D'Bridge.
It's running like a charm here now.
Well I found the solution to the problem. Or I think I found it.
mode 80,25 before running DB
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 00:59:25 |
Calls: | 635 |
Calls today: | 2 |
Files: | 7,638 |
Messages: | 292,269 |