Talk:DOS/GA1

GA Review

I'll be reviewing this article. I'll add comments in a day or two, after I've read through the article and done a little reading around. -- Philcha (talk) 18:07, 7 September 2008 (UTC)[reply]

Gaps in coverage

It's a big subject, and I can see you've put in a lot of work! Unfortunately I think there are some significant gaps in coverage:

.BAT files
Differences between MS-DOS and PC-DOS:
- Some command language differences, for example PC-DOS did not support the CHOICE command, and its absence made writing menus via .BAT files harder.
- What's the difference between MS-DOS and PC-DOS? says IBM tied PC-DOS to their hardware - I know blogs are not usually considered WP:RS but Osterman is a long-term MS designer, so I'd defend it quite happily.
The article mentions Terminate and Stay Resident programs, but does not convey a picture to a reader who wasn't there. I suggest you mention SideKick, which was very big in the 1980s.
Graphical Environment Manager (DR GEM). In fact I'd be inclined to break out a new section on "ease of use". I remember that around the time DOS-based system became common in offices (1984 in UK) Apple introduced their "test drive a Mac" campaign to re-launch their GUI systems after the Apple Lisa was criticised for being expensive and slow. Usability for office staff and home users was a big issue at the time, see History of the graphical user interface. The Real History of the GUI may give you some points to check out, e.g. Amiga. Usability "features" on DOS machines included:
- GUI: DR GEM.
- Non-GUI: DOS Shell, DESQview (yes, I know it's mentioned later), GEOS (16-bit operating system) (also mentioned later).
- Not exactly add-ons but some serious MS-DOS apps provided their own GUIs, e.g. early CASE tools.
- I'd be tempted to include SideKick in this category.
- And .BAT fles, especially the use of .BAT for menus.
- Commercial significance of all this, e.g., Quarterdeck Office Systems went into decline after Win 3 and was swallowed, but Borland is still going (fairly) strong.
The fundamental reason for all these limitations and work-rounds - Moore's Law, which, if you run it backwards, implies that early 1980s PCs were pathetic. Job_Control_Language #Complexity has some stats, with sources.
I also remember an ex-IBM guy saying IBM didn't want the PC to become a threat to its larger ranges, and was quite happy for PC software to have severe limitations. You might like to see of you can find sources for this.
There was a DOS version of MS Word (I used it) before Win 3 was released - same menu structure and ALT shortcuts.

General approach

While commenting on gaps in coverage, I've realised that we look at the subject quite differently - the article is technical / internals oriented, while I see the subject in user-oriented terms. I think for the "general reader" it would be best to explain how primitive / limited it was first, and then explain the technical causes of the limitations. I don't know what the consensus is at Wikiproject Computing about whether the dominant point of view should be technical or user-oriented, and would be happy to discuss this at Talk:DOS.

A sourcing issue

IBM's unhappiness about the licensing issue over CP/M is important, but I'm unhappy about the use of a video as the main source for this point: the sound is sometimes poor; the preamble is too long. Is there a text / HTML source that covers the same ground?

I'll produce more section-by-section comments after we've had a chance to discuss the ones above. -- Philcha (talk) 22:07, 7 September 2008 (UTC)[reply]

GA discussion

I just added a stub on batch files; of course, I hatnoted it as the main topic has some good detail. I'm not sure about implementing the MS/PC differences, as that would necessitate diferences between, for example, DR-DOS and MS-DOS, of which there are many (mostly because DR-DOS had the feature first). For example, while PC-DOS may not have the "choice" command, DR-DOS had a similar command earlier than MS-DOS, which was the "switch" command. "Doskey" in MS-DOS (and probably PC-DOS) was predated by the DR-DOS "history" command in config.sys. Basically, I worry about such a section getting way to large. Actually, I think an MS-PC comparison would be great to add to IBM PC-DOS, which is rather short.

You convinced me about not going into the MS/PC differences. OTOH I think the comparison stuff might be best in its own article, if ever. Thinking about it, there is a comparison article whose name I forget, but it's just a list of releases.

OTOH I'd regard .BAT files as an "ease of use" feature - especially as .BAT files were commonly used for menus in offices - so it's another UI improvement. To show how important menus were, this book (1991) has a section on .BAT menus. -- Philcha (talk) 23:37, 10 September 2008 (UTC)[reply]

Comparison of x86 DOS operating systems. A command difference section could definitely be put there. JeremyMcCracken (talk) (contribs) 00:36, 11 September 2008 (UTC)[reply]

An ease of use section is a great idea. I'm think two subsections: multitasking, where I'll put Sidekick. Later versions of DR-DOS had multitasking as well. (AFAIK MS and PC never had it, but not completely sure). Obviously, single-task was a big limitation from the user end. The second subsection will be the interface. I'll put some in about the CLI and later GUIs/TUIs that aimed to give users a more friendly experience: Geos, Desqview, Norton Commander, etc. I'll go ahead and pull the GUIs out of the software section and put them in the new section.

I agree about the 2 main sections of "ease of use section" being "multitasking" and "UI".

IIRC MS-DOS and PC-DOS never had multi-tasking. A purported MS doc form an anti-trust case backs this up, but may not be WP:RS. OTOH I think this SAMS book on Win XP is good enough. BTW remember to add page number(s) in the citation. -- Philcha (talk) 23:37, 10 September 2008 (UTC)[reply]

As for the source, I'll look. I would definitely like to use the interview for that citation. The peer reviewer was concerned with primary sources, but the whole IBM/DR thing has become almost folklorish in the way it's described, so a source so close to the event is a really good find. JeremyMcCracken (talk) (contribs) 21:26, 10 September 2008 (UTC)[reply]

Just Say No to Microsoft (book) looks good: non-disclosure issue; licensing issue; poss origin of "Kildall out flying" urban myth. BTW remember to add page number(s) in the citation. -- Philcha (talk) 23:37, 10 September 2008 (UTC)[reply]

I took the liberty of moving your response inside the review line. -- Philcha (talk) 23:37, 10 September 2008 (UTC)[reply]

Thanks; wasn't sure where the proper place for it was. JeremyMcCracken (talk) (contribs) 00:36, 11 September 2008 (UTC)[reply]

Ease of use section and book cite for the Rolander interview added. JeremyMcCracken (talk) (contribs) 22:21, 12 September 2008 (UTC)[reply]

Make this "main article" for MS-DOS and PC-DOS

Not strictly a part of the GA review, but it would be a good idea to avoid duplication of content and research. Since DOS describes the common features, it should do the heavy lifting.

Article structure

I keep having 2nd, 3rd, 4th etc. thoughts about this, because there several dimensions: historical development of MS-DOS and PC-DOS as stand-alone OSs; gradual absorption of MS-DOS into Win, which progressed at different rates in the home / client and business / server lineages of Win; add-ons to make stand-alone DOS more usable (1980s & 1990s); competitors (1980s & 1990s); continuing use of DOS-like environments (subtle wording of title to include e.g DosBOX, freeware desk-top DOS variants, embedded variants); internals. The current structure looks fragmented to me, but producing a better alternative isn't easy.

Here are my latest thoughts. Feel free to comment, criticise, object, tell me I'm missing things, etc.

Built-in facilities (currently "Operating system structure")
Hardware supported - with example of how pathetic it was by modern standards (only floppies; the IBM PC spec cited at Job Control Language#Complexity). Basic DOS kernel facilities. Files & sub-directories. CLI, preferably with horrendous example of file names including 2 levels of sub-dir. Batch files, including menus (they really were important in the 1980s and early 1990s).
Link to Comparison of x86 DOS operating systems if you like, but I don't think that article lives up to its name and is just a list of versions.
Origins (currently "History", but you've provided content to show that DOS's history is not over).
Major applications that run on DOS.
comment on increasing attempts by apps to provide easier UI (including but not limited to GUIs) and some multi-tasking in pre-Win apps.
- Business applications
- Games (PC games were huge before consoles got really good, see History of video games
- Development tools
- OS extenders / enhancers
- etc.
DOS and Microsoft Windows
Continuing use of DOS-like environments
- Emulators
- Free and commercial desk-top look-alikes.
  Can you explain why HP & Dell provide FreeDOS? Why does anyone wan to run DOS these days, apart from gamers who think some mid-1990s games are still the greatest (includes me to a degree)?
- Embedded
Technical summary (currently "Operations")
But move scripting / .BAT up to "Built-in facilities"

-- Philcha (talk) 14:28, 13 September 2008 (UTC)[reply]

I just did a massive rearrange and added a bit. As for FreeDOS being included as an OEM system, I couldn't honestly tell you why they would do that. JeremyMcCracken (talk) (contribs) 13:45, 26 September 2008 (UTC)[reply]

Hi, JeremyMcCracken, welcome back. Are you planning to do any more re-arranging? I ask because at present we seem to have very different ideas about the structure. I've written enough about my thoughts. Perhaps it would help if you could explain why you handle things in the sequence you prefer, and how each part connects to / supports later ones in that sequence. -- Philcha (talk) 16:08, 26 September 2008 (UTC)[reply]

- - - - - - - End of review - - - - - -