----------------------------------------------------------------------------------
@MSGID:
<742b149b-a9a1-4876-b4ba-40446d814a0bn@googlegroups.com> 4b5eb84f
@REPLY:
<23171eb9-3e45-4811-8798-262be319a98fn@googlegroups.com> 9ef9d1c3
@REPLYADDR muta...@gmail.com
<mutazilah@gmail.com>
@REPLYTO 2:5075/128 muta...@gmail.com
@CHRS: CP866 2
@RFC: 1 0
@RFC-References: 1@reader2.panix.com>
<2aqaM.646077$5S78.232737@fx48.iad> 1@reader2.panix.com> ZhSc.294901@fx38.iad>
<2abf76b3-8032-4be7-b78d-5776c1916079n@googlegroups.com> <23171eb9-3e45-4811-8798-262be319a98fn@googlegroups.com>
@RFC-Message-ID:
<742b149b-a9a1-4876-b4ba-40446d814a0bn@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Tuesday, May 23, 2023 at 11:11:51 PM UTC+8,
muta...@gmail.com wrote:
> So now PDOS can be built with professional Microsoft tools
> instead of having to take your chances with jackasses on
> the internet.
That was in reference to the 32-bit portion of PDOS/386,
which is almost everything.
And just now the 16-bit bootloader can be built with
Visual C++ 1.52, which I think can be obtained via
the MSDN (I instead got mine from ebay a few weeks ago),
and runs under modern Windows (although you get an out
of memory error if you don`t specify "-f"). But I needed to develop
my own crude exe2bin since that was only ever supplied as
a DOS executable (Watcom has one too, but the version I
tried crashed, and I don`t want to be dependent on copyrighted
freeware anyway).
The bootsector was already able to be built with masm.
BFN. Paul.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5005/49 5015/255 5019/40 5020/715 848 1042
4441 12000 5030/49 1081
SEEN-BY: 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441