New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running 16-bit app installed on x64 through Telnet? (Error) #49
Comments
Ok, that's because the loader currently isn't injecting into Services (like the Telnet server), for saftey reasons, to not crash them, and for practical reasons as it is propagating via GUI applications and the injection into non-GUI applications (like services) isn't very easy and may be a bit unstable. Btw., I had good results for running DOS applications on terminals by using dosemu on linux, it works very stable and also offers you SSH capabilities for using the remotely over the Internet. Just saying... |
Thanks for your answer, I hope you'll find a solution, that would be great, especially for a production environment. I already tried to run DOS applications on terminal using dosemu on Linux, or Dosbox, the problem is not about running the DOS application, but for example I made a test of performance for Foxpro. The aim is to make researches in database quickly :
I'm testing every possibilities |
Just out of interest: Did you also test ntvdmx64 performance-wise (without telnet, just as a plain user)? I wonder that DOSEMU is slow, because there was this kernel hack that even allows Linux to run v86 mode on x64 systems: http://v86-64.sourceforge.net/ |
I haven't tried it, but http://www.bttr-software.de/products/jhoffmann/#rmenu may be a good starting point to get telnet support into VDos, in case that it performs OK. |
That's exactly what I did with DOSEMU. I installed it on Fedora 30, FreeBSD, Debian, and it took too much time. (More than 600 seconds). I did not test with telnet, only opening Dosemu locally and testing my operations... I'll give you the results when I'll test on vDOS. |
Aha, it just sounded very suspicious to me that DOSEMU has the same bad performance as DOSBOX. One explanation might be, that you didnt set Did you check the ~/.dosemu/boot.log ?
then there is somthing wrong with the setup and it only uses useless CPU emulation. |
Maybe try dosemu2 (https://github.com/stsp/dosemu2) which supports kvm. |
Thanks for your answer Leecher, indeed, it is not available in my kernel. I did as you said : Still, the boot.log displays this warning. DOSEMU-1.4.0.8-180-g35054ba7 is coming up on Linux version 5.1.19-300.fc30.x86_64 #1 SMP Mon Jul 22 16:32:45 UTC 2019 x86_64 So as you said, I have to build my own kernel (I've never done that before, that will be a rewarding experience). Thank you very much for guiding me, I would never know that by my own ! @cracyc |
If you just want to test, you may also use an older Debian Version, i.e. Debian 7 32bit still has VM86 support enabled: root@debian:/# cat /boot/config-3.2.0-4-686-pae | grep VM86 |
Well, I'm struggling with that Debian 7 since Friday, because it's obsolete so I had difficulties to install it (All ftp servers weren't working, but I found solution) So I do have CONFIG_VM86=y and Debian version 7.11, but I meet a lot of problems installing Dosemu, do you have any idea of where to download the right dosemu package? Because I can't find it on the net I'm going to try on Debian Jessie (8) |
Why not use the precompiled binaries from http://www.dosemu.org/stable/ ? |
Ok, I've tested my program and this time it took 45 seconds (rather than 600 seconds)... 👍 Still, Windows Server 2008 is faster 🥇 . I'm gonna try the recompilation of kernel in Fedora for my own experience. Thank you very much for the help, I think I can close this issue now ! |
Yeah, just keep Windows Server 2008, original NTVDM still is the best! ;-) |
Dear leecher,
I've installed your program on my Windows Server 2012 64bits. Worked well.
I'm trying to run this app through a telnet client. So I connected my telnet server (Windows 2012) and my telnet client (Windows 10), both of them are 64bits.
When I tried to run the app, it shows me same message as running a 16 bit app in 64 bits system.
"This version of Foxpro is not compatible with the version of Windows"
Do you know if there is a way to avoid this?
The text was updated successfully, but these errors were encountered: