----------------------------------------------------------------------------------
@MSGID:
<2911ec76-3a10-43ca-8f9f-5c45dec89ff2n@googlegroups.com> 3529cf41
@REPLYADDR muta...@gmail.com
<mutazilah@gmail.com>
@REPLYTO 2:5075/128 muta...@gmail.com
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<2911ec76-3a10-43ca-8f9f-5c45dec89ff2n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
Note that the photo of the CPU in the laptop I have
ordered shows an NEC V20. Assuming I actually
get one of those, I will be in a position to run 8080
code.
(on a new computer)
I can still run 8086 code on new computers - although
new computers without a BIOS would require me to
switch to LM64 to do UEFI calls - but this is the first
time I have ever had the opportunity to run 8080 code.
I have programmed an 8-bit computer before (Commodore 64,
6502/6510), but never an 8080.
I`ve never even personally run CP/M - any flavor - real or
emulated.
I also have an interest in "BDS C" for CP/M-80, which is
a public domain C compiler.
So there are two things I may do.
1. Add the same functionality as 22Nice to PDOS/86 so
that it is a small clone of CP/M-80.
2. Replace the CP/M BIOS layer with callbacks to 8086
code to be handled by PDOS/86 and run real CP/M-80.
Although I think I am more likely to prioritize something
else on my plate - a custom version of msvcrt.dll that
opens a graphics window and writes 80 * 25 text to it
so that my win32 console mode programs run under
Windows 3.11 and commercially-supported ArcaOS
(ie OS/2).
One other thing of interest to me is making sure that
PDOS/386 can be built with commercially-supported
Digital Mars.
BFN. Paul.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441