Modified much of the original content
Modified much of the original content, added too much information about stuff that's now irrelevent. Hopefully appropriate and up to Wikipedia's standards, this is my first major contribution. --X3J11 20:57, 27 June 2006 (UTC)
I've been trying to improve the first few paragraphs of this article, because they sound rather clumsy. They must have been writen by someone who doesn't natively speak English. Anyway, I removed the sentence "Most XP users know nothing about them, but are occasionally happy to have DOS based partitioning, recovery or similar products, partially faking the "Win" look, and based on DOS extenders of course." because I can't understand it at all, and I was therefore unable to improve it. If anyone can figure out this cryptic gibberish, please improve it and put it back in the article. Nick Warren 17:00, 24 September 2006 (UTC)
- Someone seems to have been kind enough to put it back in for you. :/ There's a lot in this article that (I think) should be changed/removed, but I'm afraid to do it since other folks have done it to what I wrote (which is kinda disheartening). But there's lots of extraneous junk that's been added. X3J11 21:23, 24 December 2006 (UTC)
Cleaning It Up Some
I've taken the liberty of trimming a lot of the extra "junk" from this article. Specifically, the chunk:
...and many older extenders had limitations of 16, 32 or 64 MB (even Windows 3.0, which used a DOS extender, were limited to 16 MB memory, and relied on the Windows 3.0 version of himem.sys to enforce this limitation in standard mode. Windows 3.1 increased the limit to 256 MB memory and that limitation were because of the limited number of descripter table entries, which allowed Windows 95, because of it's flat address space, to increase the limitations to 480 MB, then a limitation of the VMM were hit for which increasing allowed Windows to support more memory, but increased the memory required to initialize the VMM, so obviously it became a tradeoff. Windows 98 required more memory anyway, so Microsoft decided in increase the limitation, allowing it to support 1 GB of memory as long as VCACHE's address space were limited to 512 MB by adding this setting to the [vcache] section: maxfilecache=524288. See  for details.) New extenders however, have higher or no limits (all 4 GB supported). Some DOS extenders do not provide access to virtual memory, limiting the application to memory installed in the machine, some of them do.
The article is about DOS extenders in general, not about a particular version of the drivers, or about specific features of particular versions of Windows. The above quoted paragraph is also too dense and difficult to decipher. Also removed several entries from the "Notable" section... the very idea of a notable program is that it left some mark on the PC application/gaming scene. The section should not be used for a dumping ground of DOS extended applications, although defining what is and is not a notable application is somewhat difficult to do while remaining neutral. X3J11 00:50, 25 March 2007 (UTC)
- Well, even though I didn't initiate the idea, I did think adding at least one example for most every DOS extender was a good idea of showing who used it for their apps. If Wikipedia doesn't mention the existence of every DOS extenders, who will? They need to be chronicled somewhere, especially because some have bugs (Zurenava -> FreeDOS) or can be easily replaced (DOS4GW -> DOS/32A) or are still being updated (HX) or are abandoned but stable (PMODE/W or WDOS/X) or have their own quirks, advantages, and disadvantages regarding DPMI compatibility, virtual memory, DLLs, .EXE types supported, etc. Granted, a lot of that kind of info wouldn't necessarily belong in this particular article, but it should go somewhere (I hope).
Armslurp 04:56, 25 March 2007 (UTC)
- I still don't think this is the place to dump every extended application known to man (figuratively speaking of course). By definition, the word "notable" means prominent, important, or distinguished. Applications that drove the business world, such as Lotus Notes and AutoCad are notable. Games that made a major impact such as DOOM and Warcraft are notable. Small programming languages and assemblers (Sphinx C-- and Lazy Assembler) are hardly notable, for example.
- I also feel that the section on extender operation has once again been made too dense. While the information is applicable to the topic, it contains a lot of extraneous "junk" that is not essential and could be removed or moved to a more relevant article (the information on the limitations of Windows, for example, could be in the Windows article if it's not already).
- However, I don't want to play an Undo wargame with the other people contributing to this article, and it's a bit disheartening to see my attempts at clarifying this end up for naught as someone comes along and reinserts all the stuff that I think shouldn't be there. :) X3J11 16:32, 22 September 2007 (UTC)
As far as the facts:
Wasn't Quake I compiled using DJGPP, usind CWSDMI as the DPMI host?
Did DOS/32A actually provide a Win32 emulation? I thought it was a DOS4G/W replacement? WDOSX did, though. I should know, because in a past life I did this WDOSX thing mentioned in the article. ;-) —Preceding unsigned comment added by 22.214.171.124 (talk) 22:35, 8 September 2007 (UTC)
- Yes, Quake 1 was originally built with DJGPP using CWSDPMI. As for WDOSX, it was one of the best extenders I ever used, and if I were still trying to write DOS software, I'd probably still be using it. (So I guess that makes you Michael T, huh? =) X3J11 16:02, 22 September 2007 (UTC)
Does anybody know how feasible it would be to make an extender to run 64 bit windows programs on 32 bit windows? Of course I could just buy Vista x64, but I don't want to deal with any unsupported drivers.
The main issues I'm thinking of are:
1. Still need separate 64 bit shared libraries
2. Registers not preserved on context switch (not a problem for DOS extender)
3. Need to switch to 32 bit mode before system calls (like switching to real mode in DOS extender)
Borland C++ and Pascal
Since Pascal 7.0 Borland passed 3 IDE builds: turbo.exe - real-mode IDE, very slow because of exnesive Overlays used, bpw.exe - IDE for Windows 3.x, and DOS-extender based BP.exe
Later they did the same for Borland C++ package.