Fair use rationale for Image:Drinc.gif
Image:Drinc.gif is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to ensure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
Digital Research Forth
DR did a Forth for one or more of their OSes? Really? I remember (and probably still have somewhere, the Basics, Pascal etc, but I cannot find any mention of them doing a Forth. Citation please. Lovingboth (talk) 17:18, 13 May 2010 (UTC)
XVCPI support in Concurrent DOS 386
Does someone have any information (announcements, documentation, or other bits) in regard to XVCPI (Extended Virtual Control Program Interface) support in Concurrent DOS 386 since ca. 1989? This was apparently a parallel effort to DPMI to enable the full memory management and multitasking capabilities of the 386 in which Intel, Digital Research, Interactive Systems and other parties seem to have played a role. Very little is known about this, so if you know anything about it, your comments or contributions to the VCPI article or talk page would be highly welcome. Thanks. --Matthiaspaul (talk) 12:03, 28 May 2013 (UTC)
No mention of CP/M-68 and little mention of GEM
This article is missing of a significant aspect of DRI's output - the Atari ST running GEM and underlying supporting OS called GEMDOS, which was basically CP/M-68K hacked about to support the MS-DOS hooks that were needed to run GEM (established as running on MS-DOS as its primary OS by then). GEM was built on top of the GEM VDI system, which I think was a virtual device system built on top of GSX. The AES (Application Environment Services) handled the higher level stuff. The system call parameters were incompatible between the two (for example, rectangles in VDI were TLBR whereas in AES they were TLWH). Atari called this entire system TOS, and as developers, we didn't disagree.
I believe Atari sold upwards of two million STs; in the heyday of the bog-standard Z-80 64K CP/M machine, sales couldn't have been much more than 100K units a year. In terms of revenue, I doubt Uncle Jack was paying very much per machine, but in terms of installed base this has to be the most common DRI product.
Do I have references for any of this? Probably not, unless you count the paper listings of GEMDOS I think I probably still have in the attic. However, most of the people who were there at the time are still alive. (And most seem to be working for Microsoft, apart from me). And as for anecdotes about Gary Kildall... well they're just anecdotes.
Someone needs to fill in the gaps. If I have time, I might.