ANSI escapes for input (Developers)
> > I am already using that - for OUTPUT. And as you noted, I need to go to
> > NTVDM. But I still want to run 32-bit software. Win32 executables. And
> > hence - HX.
>
> Well, to me it sounds like all this could be done much simpler. Like,
> running it in pure DOS
If I just wanted to run this one Win32 executable,
I could indeed use pure DOS.
But what if I want to run Visual Studio 2005 Professional
to produce Win32 and Win64 Hercules/380 executables?
The development machine I have chosen is Windows 2000.
The last version that didn't require activation.
I run that under Virtualbox under Windows 10 currently.
On a Chinese-made computer with a Zhaoxin processor.
> or even DOSEmu on Linux should do the work in much
> simpler way (and it's likely to have a builtin debugger).
I have tested that I can run my Virtualbox + Windows
2000 under Linux if necessary, but for now I am happy
to run under Windows 10.
> > I am interested in 16-bit software too (as you apparently are too if you
> > are still running MSDOS). So OS/2 1.x is an important part of that.
>
> You want to implement 16-bit OS/2 runtime on PDOS/386?
No. Currently PDOS/86 uses the MSDOS API. I am
tentatively planning to switch to the OS/2 1.x
API for both RM16 and PM16.
Note that MSDOS 4.0 (which I have never used) was
able to load NE executables. But I assume that
executed DOS interrupts. I would instead (pretend
to) be loading an OS/2 1.x DLL (I need to find out
what Microsoft C 6.0 produces for its DLL - similar
to MSVCRT.DLL but with no standardized name) -
including on RM16.
> Well, if that's what your goal is, take a look at the following projects:
> https://github.com/icculus/2ine
> https://github.com/osfree-project
Both of those are copyright, so not what I'm after.
> Or you just want to have ability to run 16-bit OS/2 apps on your
> development machine?
I want that TOO. And that's ALL I want currently. I
haven't started the switch from MSDOS to OS/2 1.x.
I have other priorities at the moment (gccx64).
BFN. Paul.
Complete thread:
- ANSI escapes for input - kerravon, 18.07.2023, 02:08 (Developers)
- ANSI escapes for input - mbbrutman, 24.07.2023, 03:01
- ANSI escapes for input - kerravon, 24.07.2023, 15:18
- ANSI escapes for input - DosWorld, 08.02.2024, 23:03
- ANSI escapes for input - kerravon, 09.02.2024, 13:17
- ANSI escapes for input - DosWorld, 08.02.2024, 23:03
- ANSI escapes for input - ecm, 24.07.2023, 17:01
- ANSI escapes for input - mbbrutman, 25.07.2023, 03:35
- ANSI escapes for input - kerravon, 25.07.2023, 12:34
- ANSI escapes for input - KormaX, 25.07.2023, 12:57
- ANSI escapes for input - kerravon, 27.07.2023, 07:15
- ANSI escapes for input - kerravon, 30.07.2023, 09:08
- ANSI escapes for input - kerravon, 31.07.2023, 15:21
- ANSI escapes for input - kerravon, 07.02.2024, 08:23
- ANSI escapes for input - bocke, 07.02.2024, 08:45
- ANSI escapes for input - kerravon, 09.02.2024, 10:00
- ANSI escapes for input - bocke, 09.02.2024, 20:10
- ANSI escapes for input - kerravon, 09.02.2024, 22:07
- ANSI escapes for input - bocke, 09.02.2024, 20:10
- ANSI escapes for input - kerravon, 09.02.2024, 10:00
- ANSI escapes for input - bocke, 07.02.2024, 08:45
- ANSI escapes for input - kerravon, 30.07.2023, 09:08
- ANSI escapes for input - kerravon, 27.07.2023, 07:15
- ANSI escapes for input - mbbrutman, 27.07.2023, 04:51
- ANSI escapes for input - kerravon, 27.07.2023, 07:25
- ANSI escapes for input - KormaX, 25.07.2023, 12:57
- ANSI escapes for input - kerravon, 25.07.2023, 12:34
- ANSI escapes for input - mbbrutman, 25.07.2023, 03:35
- ANSI escapes for input - kerravon, 24.07.2023, 15:18
- ANSI escapes for input - mbbrutman, 24.07.2023, 03:01