delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
X-Received: | by 10.224.42.141 with SMTP id s13mr14239364qae.3.1369619231938; |
Sun, 26 May 2013 18:47:11 -0700 (PDT) | |
X-Received: | by 10.49.87.70 with SMTP id v6mr1659684qez.25.1369619231884; Sun, |
26 May 2013 18:47:11 -0700 (PDT) | |
Newsgroups: | comp.os.msdos.djgpp |
Date: | Sun, 26 May 2013 18:47:11 -0700 (PDT) |
In-Reply-To: | <90dceebd-8d81-4433-8932-9bce42bddb97@googlegroups.com> |
Complaints-To: | groups-abuse AT google DOT com |
Injection-Info: | glegroupsg2000goo.googlegroups.com; posting-host=78.45.215.137; |
posting-account=Q0wMHAoAAADjYrghh94FTf6YnbpTqZgp | |
NNTP-Posting-Host: | 78.45.215.137 |
References: | <1137560452 DOT 398133 DOT 301490 AT g14g2000cwa DOT googlegroups DOT com> |
<0ed77a97-aec8-4fde-8124-707ca9cffad1 AT googlegroups DOT com> <28c2ff16-6cef-46c3-8f52-f67b320b5c04 AT googlegroups DOT com> | |
<de2dnU5WsKrWXQPMnZ2dnUVZ_jydnZ2d AT earthlink DOT com> <68c3dec5-8fd4-4eb0-888d-3949d879a33c AT googlegroups DOT com> | |
<90dceebd-8d81-4433-8932-9bce42bddb97 AT googlegroups DOT com> | |
User-Agent: | G2/1.0 |
MIME-Version: | 1.0 |
Message-ID: | <95489b27-4b13-43e8-bf37-2b05561151d0@googlegroups.com> |
Subject: | Re: Adding 64-bit file support to DJGPP |
From: | RayeR <glaux AT centrum DOT cz> |
Injection-Date: | Mon, 27 May 2013 01:47:11 +0000 |
Bytes: | 2218 |
Lines: | 6 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> The 64bit hardware does no longer support V86 mode. This mode was intended to allow 32 bit operating systems to run 16 bit applications, i.e. DOS applications. I know. But I'm not sure if UEFI run under 32b PM or 64b long mode on modern boards. If it would run 32b (switch to 64b later when starting OS) there would be chance to setup v86 mode and still use UEFI API (insted writting all from the scratch). > Writing a Hypervisor that uses VT-X is really a lot of development since you have to virtualise just about anything. I evaluated an alternative Hypervisor just to see how much is left to implement to make it usable. I don't know much about VT-X abilities but you mean it allows to run 16b programs with something like RM? What alternative hypervisors you found?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |