Slashdot Mirror


MS DOS: A Eulogy

roadhog95 writes: "Love it or hate it, I'm sure everyone's got a love story or traumatic memory of the infamous MS-DOS. Byte magazine reports on the passing away of DOS in light of the recent Windows XP launch. Even Regis Philben stopped by to pay tribute: 'Bill... Is that your final command prompt?'"

794 comments

  1. bye bye by Anonymous Coward · · Score: 0

    DOS we hardly knew yee.

  2. Sad to see DOS go by MrBlack · · Score: 4, Funny

    While it was around I could always use this joke..."I know DOS backwards...it's SOD". I guess I'll need to find/think up/steal some more material.

    1. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      ..."I know DOS backwards...it's SOD".

      Uhh... and this is funny how? Sod is a section of grass-covered surface soil held together by matted roots. Where's the humor?

    2. Re:Sad to see DOS go by Alrocket · · Score: 3, Funny

      Please insert sense of humour into drive a:
      (L)augh, (R)etry, (F)ail.

    3. Re:Sad to see DOS go by KingAdrock · · Score: 0, Offtopic

      F

      ...

    4. Re:Sad to see DOS go by theHook · · Score: 0, Offtopic

      Well, SOD is also a term of endearment, as in

      She was only the undertakers daughter,
      but she'd lie under any old sod.

      Or "you stupid sod" !

    5. Re:Sad to see DOS go by theHook · · Score: 0, Flamebait

      which is very appropriate for many readers here !

    6. Re:Sad to see DOS go by billybob2001 · · Score: 2
      If I'd known this event was due to happen, I would have got in first and typed

      doskey exit=@for %a in (%windir%\*) do start "DOS LIVES!"$Texit

    7. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      And DOS B(ackwards) backwards is BSOD.

      Hmm...

    8. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      I just had to see this in action so I did it. Pretty funny. :) I thought I seriously screwed something up for a minute :)

    9. Re:Sad to see DOS go by rppp01 · · Score: 2, Offtopic

      C:\
      C:\dos
      C:\dos\run

      C:\dos\run linload.exe

      --
      They stuck me in an institution, said it was the only solution, to...protect me from the enemy, myself
    10. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      'Core Dumped' backwards is: 'The system is alive, all user data deleted.'

      Wonderful, just wonderful.

    11. Re:Sad to see DOS go by pa-guy · · Score: 0

      Only the shit-eaters (That's what we used to call the Brits when I was in the army. If you ever ate at a squaddy messhall you would understand it. Deep-fried everything.) would think that calling someone a sodomizer is a term of endearment.

    12. Re:Sad to see DOS go by afdsfsdafsdaf · · Score: 1

      *sigh*.. nibbles is gone forever in its original qbasic form... oh well life goes on... what??? you say gorillas is gone too?!?!? DAMN THEM DAMN THEM DAMN THEM DAMN THEM.. im writing bill a letter.

      The logical dos drive you are trying to create cannot exist on your illogical non-existant DOS... (A)bort (R)etry (F)ail

    13. Re:Sad to see DOS go by jbarnett · · Score: 2


      Techinally, it should be

      C:\dos\run\linload.exe

      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    14. Re:Sad to see DOS go by manaway · · Score: 1

      DOS is, quite possibly, the worst text-adventure game ever. (stolen from a usenet sig)

    15. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      I don't think the Dennis Miller ratio applies to /.

    16. Re:Sad to see DOS go by The+Pi-Guy · · Score: 1

      Boy do I love that "Close Group feature of WinXP. *rightclicks on "98: DOS LIVES!" and hits close group.*

      :=j0shua

    17. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      OK, that was cool!

    18. Re:Sad to see DOS go by The+Pi-Guy · · Score: 1

      Not necessarily. Perhaps if you installed a program called c:\dos\run.exe, or c:\dos\run.bat which loaded it in high memory or loaded it over the interpreter, to free up RAM? Hmm.... --joshua

    19. Re:Sad to see DOS go by Anonymous Coward · · Score: 0

      Win 2000 (and possibly older versions) allow multiple selection in Task Manager. Then you just End Task on the lot of them. Easy.

  3. Passed away My furry little hiney by the_Bionic_lemming · · Score: 2, Insightful

    Just because xp doesn't use it, doesn't mean I am not going to use dos.

    Yet another reason NOT to go to Microsoft for new software.

    --
    _ _ _ Go for the eyes Boo! GO FOR THE EYES!
    1. Re:Passed away My furry little hiney by Anonymous Coward · · Score: 0

      Hear Here! (or whatever)

      I /just/ installed DoS 6 last night on a PII-200 with 64Mb ram (had to take 8 out because dos wouldn't recognize it) for a friend. With Win3.1 running on top, this is going to make one deadly minesweeper station.

      JK. Actually, it will be running wordperfect, have a cannon bj10 printer, and, all around, be an awesome system for this guy. No internet, but that's okay!

      Take that XP!

    2. Re:Passed away My furry little hiney by Anonymous Coward · · Score: 0

      DOS is still in XP.

      Just not at the core.

      Almost all DOS apps (except some games) work in XP.

      That isn't going to change soon.

    3. Re:Passed away My furry little hiney by Anonymous Coward · · Score: 0

      Actually I don't what they are talking about. DOS may not be inside but there IS a command prompt in WindowsXP at least the pre-formal-launch version that shipped on a Vaio notebook I support.

      There are many other, more valid reasons to run away from XP screaming. For one: absolutely shitty network configuration utilities that ought to be ripped out and shoved up Steve Balmers asshole til his eyes bug out. Whoever thought that crap up and Ok'ed it for release should die a death of 1000 cuts. I'll bring the brine!

    4. Re:Passed away My furry little hiney by FrankHaynes · · Score: 1

      Agreed.

      There are those who *can not* stop using DOS, such as radio shops that must reprogram Motorola radios built in an earlier time. The contractor that wrote the Radio Service Software for the Big-M tied the timing of the program to the clock used in the radio and the prevailing computer technology of the time.

      It's bad enough trying to find a cpu that will run the r.s.s. successfully, but you can almost always forget about running it inside a DOS emulation window. You must boot to real-mode DOS, so keep those DOS floppies around, boyz and grrrlz!

      Maybe I should start selling DOS 6.2 boot floppies at hamfests? Hmmmmmm....

      ---

      --
      slashdot: A failed experiment.
  4. FreeDOS / DOSEmu by CmdrPaco · · Score: 2, Insightful

    Hopefully FreeDOS and the DOSEmu will live on!

    --
    I bet this is not "First Post."
  5. Linux Version? by Anonymous Coward · · Score: 0

    So my company uses a legacy version of a proprietary program run on MS-DOS...

    Currently running on 95 and other old versions of windows - since it won't be supported in new versions of windows anyone got good pointers of an open source system that I can reccommend to management when they replace boxes?

    -- Ender, Duke_of_URL

    1. Re:Linux Version? by bero-rh · · Score: 2

      Sure - try DOSEMU with FreeDOS ripcord.

      If it doesn't work, try dosemu with DR-DOS - not open source, but at least $0.

      --
      This message is provided under the terms outlined at http://www.bero.org/terms.html
    2. Re:Linux Version? by Mondrames · · Score: 1

      Windows 2K comes with a compatibility feature with SP2:

      COMPATIBILITY MODE: Service Pack 2 (SP2) includes a compatibility mode that lets programs run as if they were on a Windows NT 4.0 SP5 or Windows 95 machine. To enable this interface, perform the following steps:
      Start a Run box (Start, Run).
      Enter the following command: "regsvr32 %systemroot%\apppatch\slayerui.dll"
      Click OK.
      Click OK to the confirmation.
      Now if you right-click a shortcut and select Properties, you'll see a Compatibility tab that lets you select whether the program target should run under an NT 4.0 SP5 or Win95 compatibility layer.

  6. autoexec.bat and config.sys by Forager · · Score: 2

    If I never have to rename my autoexec.bat and config.sys files to play Wolfenstein again, I could die a happy man. You know, there's a reason they called it the dosHELL.exe =)

    ~Aaron.

    --
    student of animation and the fine arts
    1. Re:autoexec.bat and config.sys by Ivan+Raikov · · Score: 1

      I hope you are aware of the fact that ever since MS-DOS 6.0, you could have multiple configurations in your config.sys, and select one of them at boot time.

      Before 6.0, there was a shareware tool, whose name I'm forgetting, which let you that same thing, and a myriad of ways to have multiple AUTOEXEC.BAT configurations.

    2. Re:autoexec.bat and config.sys by Forager · · Score: 2

      Keep in mind that when I was renaming my autoexec.bat and config.sys files I was probably wearing my Ninja-Turtles pajamas and drinking from tupperware cups with plastic spill-guards on them =) Also, at this point I had not even heard of the internet (that would happen a few years later, around the time Doom II was released). I did things the only way I knew how: DOS shell to rename autoexec.bat and config.sys so I could play Wolfenstein. When I was done, redo the changes so dad can use his mouse in Windows (one of the reasons why I was encouraged to learn to use a CLI before I was old enough to cross the street by myself). Ah, memories ...

      ~Aaron.

      --
      student of animation and the fine arts
    3. Re:autoexec.bat and config.sys by Anonymous Coward · · Score: 0

      LACE. I used to use it before DOS 6 was released.

    4. Re:autoexec.bat and config.sys by mblumber · · Score: 1

      Wow. I thought I was the only one who used to wear those pajamas.

      Do you remember the first time you REALLY messed up your computer, and you had to explain to your father that he had to spend $50 for someone to get it working again. That was no fun at all...

      --
      Anyone who posts about bad moderation are themselves off-topic and should be moderated accordingly.
    5. Re:autoexec.bat and config.sys by Anonymous Coward · · Score: 0

      Yep, I accidentally deleted the entire root directory. When I told my father, he wasn't pissed, he just said "Well, it looks like you're going to have to figure out how to fix it.". And that I did...undelete became my best friend (along with a friend of mine who I was on the phone with so that he could provide me with the correct filenames from his PC).

    6. Re:autoexec.bat and config.sys by Anonymous Coward · · Score: 0

      nope, sorry, never happened to me.

  7. Never say Die! by snatchitup · · Score: 1

    I'm still Redneck Rampaging with MS DOS running.

    Leonard, Here I am! Leonard? Come on Leonard!

    1. Re:Never say Die! by Anonymous Coward · · Score: 0

      The scary thing about that game is that I know someone who looks _exactly_ like Leonard.

  8. Re:A funny tribute to DOS by CmdrPaco · · Score: 0, Offtopic

    WARNING - Goatse.cx link redirect above... Yes, it got me, unfortunately... Ugh

    --
    I bet this is not "First Post."
  9. In lieu of flowers... by Root+Down · · Score: 2

    In lieu of flowers, we respectfully request that you make contributions to the charity of your choice.

    Good plan! Let's donate to open source projects in honor of the death of DOS.

    Mmmm... irony. Good stuff.

    1. Re:In lieu of flowers... by Anonymous Coward · · Score: 0

      Taco, are you posting under your alias again? We really can't have this. What if someone finds out you're actually gay?

      Michael

  10. Fond .bat memories by Kasmiur · · Score: 1, Informative

    I remember when I was younger I used a .bat file to create a simple menu system for my brothers to be able to play the games they wanted to play. It even had simple graphics from the wonderful echo command.

    --
    -THIS SPACE FOR RENT!
    1. Re:Fond .bat memories by guusbosman · · Score: 2, Funny

      Oh yes -- those could old times :) I was first called a 'hacker' when I found out how to break into somebody's password protected filemanager (simple hitting Ctrl-C inside the menu-shell was enough) :))

    2. Re:Fond .bat memories by terrymah · · Score: 2, Interesting

      True that. I remember spending hours learning the various ansi escape sequences (ansi.sys? anyone remember?) to have a fancy command prompt and colors on my little batch file menu system.

    3. Re:Fond .bat memories by spockman · · Score: 1

      Oh I remember those .bat files days well. Does anyone remember Edlin, the vi clone? Users used to be amazed when you would drop into Edlin and create this 'magical' batch file that would let them easily start their Lotus 123 or DBase with just pressing a number. You were the hero! Did a lot of things with just DOS. So has anyone checked to see if DOS still lives in XP? Seem to remember seeing a DOS command prompt window, did they upgrade it to 32 bit?

    4. Re:Fond .bat memories by fyonn · · Score: 1

      edlin was never a vi clone. edlin wishe dit had the intuitiveness and user friendlyness that vi did.

      Windows XP: form the people that brought you edlin.

      dave

    5. Re:Fond .bat memories by spockman · · Score: 1

      Never said it had the same capabilities, just the fact that you had to 'know' the special keys to use it amazed users!

    6. Re:Fond .bat memories by david+duncan+scott · · Score: 5, Funny

      Edlin wished it had the intuitiveness and user friendliness of writing in your own blood using the stump of your foot for a pen.

      --

      This next song is very sad. Please clap along. -- Robin Zander

    7. Re:Fond .bat memories by CaseyB · · Score: 2

      Mods. Funny. Now.

    8. Re:Fond .bat memories by CaseyB · · Score: 3, Insightful
      Does anyone remember Edlin, the vi clone?

      Edlin is more accurately a clone of ed, the line editor upon which vi is based. I'd bet that edlin predates vi.

    9. Re:Fond .bat memories by BRTB · · Score: 1

      Edlin? Try "copy con: autoexec.bat"... just hope you never have to go back a line, and remember to hit F6 (or Ctrl-Z) to put in your own EoF!

    10. Re:Fond .bat memories by operagost · · Score: 1
      It's been said that real DOS programmers type:

      copy con program.exe

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    11. Re:Fond .bat memories by spockman · · Score: 1

      Oh yeah, copy con, forgot about that. It was another one that amazed users. You are right tho, don't mistype, but then we 'old-timers' had to learn to type it right the first time!

    12. Re:Fond .bat memories by Anonymous Coward · · Score: 0

      IBM, not Microsoft, created edlin.

    13. Re:Fond .bat memories by Anonymous Coward · · Score: 0

      Edlin came with PC-DOS pretty much from the beginning.

      vi is older. It was originally written by Bill Joy, the man who founded the famous PC Clone company called 'Joy Systems' which produced fairly nice PC Clones in the era of the 286 and 386 processor. I remember buying a Joy Systems box at a swapmeet about four years ago and discovering it had Coherent (an early clone of an ancient time sharing operating system) installed on the hard drive.

      Bill Joy also did some other stuff, with an obscure near-failed company that produces systems dependent on proprietary hardware/software ('sparc' something or other). Not completely propietary, of course, because they run NetBSD (so does the Mac).

    14. Re:Fond .bat memories by gorilla · · Score: 2

      It's not really a clone of ed either. ed has many quite sophisticated features, such as regex based search & replace, reading & writing of possibly partial files into the buffer and doesn't have any command editing. edlin is based upon command editing, especially for it's rather primative subsitution.

    15. Re:Fond .bat memories by Wolfier · · Score: 2

      I'm not sure if you can still do...

      append backspace characters to your filenames, so no others can access it from the shell?

    16. Re:Fond .bat memories by Anonymous Coward · · Score: 0

      [quote]You were the hero! Did a lot of things with just DOS. So has anyone checked to see if DOS still lives in XP? Seem to remember seeing a DOS command prompt window, did they upgrade it to 32 bit? [/quote]

      There's the command prompt (not the MS-DOS command prompt), and there's a DOS-compatibility mode that can be set for individual programs (run the program in a virtual machine). Which do you want? Both have been there throughout NT's 32-bit days.

    17. Re:Fond .bat memories by CaseyB · · Score: 2
      vi is older

      By a solid 5 years, as it turns out. At least, vi was written in 1976, while edlin was released with PC-DOS 1.0 in 1981. So unless edlin had been enjoying quiet success as a private utility for a long time, it is newer.

    18. Re:Fond .bat memories by drsquare · · Score: 1

      Wildcards.

    19. Re:Fond .bat memories by Wolfier · · Score: 2

      do not work well if I have

      filename---

      and

      filena-

      and you just want to access one of them

    20. Re:Fond .bat memories by Wolfier · · Score: 1

      "-" denotes a backspace.

      {Lameness filter bypass}

    21. Re:Fond .bat memories by loraksus · · Score: 2

      But is it vi you are using on your linux box.
      Or vim?

      --
      1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
    22. Re:Fond .bat memories by shyster · · Score: 2

      I still use echo foobar > foobar.txt on a regular basis....

    23. Re:Fond .bat memories by clovis · · Score: 1

      How come Edlin is still in NT, 2000, and XP? It's the only editor that works in a MS telnet session for when you've really screwed up something.
      Edit and Notepad require Fn keys or try pop up a GUI window.

    24. Re:Fond .bat memories by dr_db · · Score: 1

      My favorite batch file had one line in it:\

      Win

      I called it lose.bat

    25. Re:Fond .bat memories by alizard · · Score: 1

      You mean you actually used EDLIN? MS worked that up as an intentional joke, like Easter Eggs and that sort of thing. There are a shitload of good DOS text / programmer's editors. I still use Q-Edit once in a long while.

    26. Re:Fond .bat memories by xQx · · Score: 0

      copy con c:\autoexec.bat

      All the editor you'll ever need.

      And for those extra commands:

      echo del c:\windows\win.com >> autoexec.bat

  11. Links my Man, Linkz... by Anonymous Coward · · Score: 0

    So where are these, and what do they run on?

    -- Ender, Duke_of_URL

    1. Re:Links my Man, Linkz... by CmdrPaco · · Score: 2, Informative

      They are both at their respective .org
      FreeDOS
      DOSEmu
      There is a lot of info on the net too, just google it.

      --
      I bet this is not "First Post."
    2. Re:Links my Man, Linkz... by Anonymous Coward · · Score: 0

      Don't forget that innovative project
      GoatDOS
      There is lots of info on slashdot, just troll for it.

    3. Re:Links my Man, Linkz... by Anonymous Coward · · Score: 0

      Don't forget about Dr-Dos, now known as Open DOS. Always was a better DOS.

    4. Re:Links my Man, Linkz... by Sj0 · · Score: 1

      the name changed back to DR-DOS for 7.2. I was using it around that time, and it's at that point where I couldn't find it on calderas site anymore.

      --
      It's been a long time.
    5. Re:Links my Man, Linkz... by Anonymous Coward · · Score: 0

      Umm...No... FreeDOS was at one time Free-DOS, then became FreeDOS....

      You are referring to OpenDos, which is now DR-DOS, and hasn't progressed since 1994. FreeDOS is a completely different animal.

      Check out: http://seal.dosos.com/

    6. Re:Links my Man, Linkz... by Sj0 · · Score: 1

      oops, my mistake. The OS was updated pst 1994 though, I downloaded the brand spanking new version of DR-Dos in 1997, and it was good(came with novel netware, not a bad deal, the price(zip) was right) :)

      I thought freedos started as C dos though...

      --
      It's been a long time.
  12. GONE? by Anonymous Coward · · Score: 1, Informative

    I still use it for some things, like when im doing some chip programing. No i'm note an old fart that sticks only with dos, I run several osen
    linux windowze beos they all have something good about them.

    1. Re:GONE? by Anonymous Coward · · Score: 0, Funny

      if you ever post the word osen again, you'll be sorry!

    2. Re:GONE? by gazbo · · Score: 2, Interesting

      And I'm sure you'll find lots of bios update utilities kindly requesting you boot into dos - and Amishly shunning such technologies as emm386.

      Besides, I rather liked dos. I never installed windows until 98 was released (sure it restricted my games, but Win3.11? Come on. And by the time I'd been convinced by 95, 98 had been released.)

      And at least the command prompt is still here, and getting more and more powerful; in Win2k there's a proper grep utility, and even a poor man's version of awk. It isn't a full programming language, but it allows you to parse a stream token by token - type 'help for' to see what I mean.

      Still, I'm glad to be mostly rid of 8/16bit code.

    3. Re:GONE? by Anonymous Coward · · Score: 0
      The proper plural forms are the following:
      1. Virus - Viruses
      2. Lego block - Lego blocks
      3. beeotchii - beeotchae


      thank you.
    4. Re:GONE? by Kruemelmo · · Score: 1
      Also, whereever OS/2 is still in use, there will be 16 bit windows; and whereever 16 bit windows is, will be DOS. And there is still a lot of OS/2 - at least I can say this for the German financial world. They still use MS Access 2.0 (the 16 bit version) because of that, too.

      I do not think it is gone just because there is no new OS containing it.

      What about making settings to older non-PnP ISA cards? 3COM network adapters? And so on...

    5. Re:GONE? by nosferatu1001 · · Score: 1

      And i have a perfectly serviceable mylex scsi raid card that likes to be set under dos....

    6. Re:GONE? by Anonymous Coward · · Score: 0

      Ya know, if anyone had written a _real_ users
      manual, that is for _users_ rather than geeks,
      it might have been a lot more popular. I wrote
      one for my aged father;

      Dir (with arguments b, l, w, etc.)
      (and with wild card *.exe)
      CD (up and down)
      run foo.exe

      AND THAT IS IT!! THE ENTIRE MANUAL!!
      All those 1 foot thick books were _administrator_
      manuals not _USER_ manuals. Computers still have
      not been marketed as a comsumer product.

      Nils

    7. Re:GONE? by canadian+troll · · Score: 0

      dude... in being the grammar nazi(which you are a poor replacement for the original) you yourself fucked up! 1 Virus - Virii

  13. True.. open source is charity by Macaw2000 · · Score: 0

    Irony indeed!

  14. Re:Ave Maria??? by Root+Down · · Score: 1, Offtopic

    What kind of crack-rock shit is that?

    Apparently you've not been keeping up with Sting over the last 10-15 years. Par for the course, really. ;)

  15. It's funny... by Anonymous Coward · · Score: 1, Redundant

    how Macs now finally have a command prompt (in OS X), but XP has lost it now?

    Mac users users used to be the object of derision for their lack of command prompt. Now XP users will be.
    There's some cosmic karma in there somewhere.

    1. Re:It's funny... by Ed+Avis · · Score: 1

      Doesn't Windows XP still have the cmd.exe command prompt?

      --
      -- Ed Avis ed@membled.com
    2. Re:It's funny... by Foxman98 · · Score: 3, Informative

      Ummmmm?

      Start->Programs->Accesories->Command Prompt

      Or

      Start->Run->cmd.exe

      Seems like it's there to me. But who knows. It might all be a figment of of my imagination.

      --
      S.t.e.v.e.
    3. Re:It's funny... by Anonymous Coward · · Score: 0

      there is a command prompt:
      cmd.exe

      actually there is two, the recovery console to boot without the gui.

      Now Mac users will only be the object of derision for the amount of money they spent for a commodity, but hey it's made of titanium and doesn't run Windows so more power to them

    4. Re:It's funny... by Anonymous Coward · · Score: 0

      Well crap..

      Kids - that's what happens when you try to comment on an operating system which you have never used before.

      Let this be a lesson - and don't let me catch you drinking from the toilet again.

    5. Re:It's funny... by Anonymous Coward · · Score: 0

      how Macs now finally have a command prompt (in OS X), but XP has lost it now?

      Start -> Run -> "command" ... and up pops a DOS Window.

    6. Re:It's funny... by Anonymous Coward · · Score: 0

      There is cygwin- which has a real shell.

    7. Re:It's funny... by Anonymous Coward · · Score: 0

      Incorrect. XP has a command prompt, and you have the option of formatting a boot disk that will start you directly into DOS, just like you could with every version of Windows. Please don't spread lies.

    8. Re:It's funny... by Teferi · · Score: 2

      Even better, start->run->cmd.
      Better shell with tabcomp and the like.

      --
      -- Veni, vidi, dormivi
    9. Re:It's funny... by Surak · · Score: 2

      cmd.exe is NOT DOS. Let's not even get into the fact that even command.com isn't DOS either. cmd.exe, if you examine the header, you will find it to have the letters 'PE' in the header, signifying that it is a Win32 console application, rather than a DOS application.

      cmd.exe is a Win32 console application that is designed to somewhat emulate DOS. But it is no more DOS than Wine is Windows.

      And as for command.com, command.com is no more DOS than bash is Linux. command.com is a DOS application that gives you a shell to work in, much like bash, when compiled on Linux, is a Linux application that gives you a shell to work in. Sorry, I lied, we did get into it. :)

    10. Re:It's funny... by Anonymous Coward · · Score: 0

      True, but the discussion was not "XP still has DOS" it was "XP stil has a command prompt". So while you are right, you're way off topic :)

      OT -1

    11. Re:It's funny... by Teratogen · · Score: 1

      I wonder if most "DOS" applications,
      (including qbasic) will run under WINE?

      --
      --- even the safest course is fraught with peril
    12. Re:It's funny... by micromoog · · Score: 2
      cmd.exe is NOT DOS.

      Duh. Nobody ever said it was. It's the command-line/batch interpreter for Win32.

      And it's not designed to emulate DOS . . . it's designed to emulate COMMAND.COM in 32 bits. The DOS emulator is called NTVDM.EXE (that's NT Virtual DOS Machine), and also runs as a 32-bit application.

      Furthermore, Win32 still has COMMAND.COM. It is a 16-bit application (and therefore runs under NTVDM.EXE). And I'm sure it's basically legacy code recompiled with new version information.

      So, in closing, you're a dumbass, your OS sucks, and, uh, my granny can code better than you.

    13. Re:It's funny... by cookd · · Score: 2, Interesting

      Umm, actually, cmd.exe is starting to approach usability. I actually like it. I am interested to know Bill's response to Regis' question "is that your last command prompt?" If Bill were honest, he would say no, because some little birdies have told me that MS development uses a whole lot of command line utilities.

      Well, actually, I suppose Bill doesn't do all that much development any more, so maybe not.

      --
      Time flies like an arrow. Fruit flies like a banana.
    14. Re:It's funny... by smallpaul · · Score: 1, Offtopic

      Why is it that this guy writes a message with a blatantly incorrect premise (that Windows XP won't have a command prompt) is corrected by several people and yet his score is much higher than those of the corrections? Slashdot isn't just a place where misunderstandings are created and perpetuated. They are even rewarded!

    15. Re:It's funny... by yatest5 · · Score: 1, Flamebait

      Because it's an anti-MS statement, and slashdot is mostly inhabited by sad, bitter, linux-shagging fuckers? Duh!

      Oh oh, there goes my karma, what a shame...

      --
      • Mod parent up! [a] by Anonymous Coward (Score:5) Thurs, June 31, @13:37
    16. Re:It's funny... by Anonymous Coward · · Score: 0

      ::sings halleluahs::

      i 3 you and your post

    17. Re:It's funny... by Anonymous Coward · · Score: 0

      surprise? thats why i became a troll :) when slashdot started to be filled with idiots.

    18. Re:It's funny... by Anonymous Coward · · Score: 0

      He's probably modding himself up with six or seven spare accounts.

    19. Re:It's funny... by Anonymous Coward · · Score: 0

      IMO I'd rather have cmd.exe in Win2000/XP than command.com :)

      I hate (HATE!) hitting tab and having a tab inserted into there instead of filename completion, or hitting up and nothing happened. I loathe it.

      I do have a question though. Why the hell is command.com so lagged in Win2000/XP?

    20. Re:It's funny... by yatest5 · · Score: 1

      >> Moderation Totals: Flamebait=2, Insightful=1, Total=3.

      Insightful - ha! Bloody hell, someone with a sense of humour!

      Flamebait=2 - ha! Two 30 year old virgins better go downstairs, your mum has your tea ready...

      --
      • Mod parent up! [a] by Anonymous Coward (Score:5) Thurs, June 31, @13:37
    21. Re:It's funny... by Anonymous Coward · · Score: 0

      No, XP (and NT and 2000) still have a command line, it is just run by the better cmd.exe. There is still a command.com, but it really just routes everything through cmd.exe, and doesn't nearly as many limits/lack of shell programming features that the real DOS command.com has.

      NT/2000/XP still support config.sys and autoexec.bat files, but that does not mean you can actually *put* real-mode drivers in config.sys, etc.

      If you still want to hack cmd/bat files in NT/2000/XP, get this book:

      "Windows NT Shell Scripting", by Tim Hill, MacMillan Tech Publishing.

      Or, get Cygwin or U/Win for a "real" CLI.

    22. Re:It's funny... by Chris+Mattern · · Score: 2

      > I wonder if most "DOS" applications,
      > (including qbasic) will run under WINE?

      As a guess, I'd say not. But you can
      always use dosemu, which is much more
      mature and stable anyways.

      Chris Mattern

    23. Re:It's funny... by donutello · · Score: 2

      I prefer: -R -> cmd

      --
      Mmmm.. Donuts
    24. Re:It's funny... by shyster · · Score: 2
      cmd.exe is NOT DOS. Let's not even get into the fact that even command.com isn't DOS either. cmd.exe, if you examine the header, you will find it to have the letters 'PE' in the header, signifying that it is a Win32 console application, rather than a DOS application. cmd.exe is a Win32 console application that is designed to somewhat emulate DOS. But it is no more DOS than Wine is Windows. And as for command.com, command.com is no more DOS than bash is Linux. command.com is a DOS application that gives you a shell to work in, much like bash, when compiled on Linux, is a Linux application that gives you a shell to work in. Sorry, I lied, we did get into it. :)

      True, neither cmd.exe nor command.com are MS-DOS. Of course, neither is MS-DOS dead, since Win98 and WinMe are still alive (ie., supported by MS) and both are essentially running on DOS.

      And I think the original point of both cmd.exe and command.com being available is that most /.'ers seem to be moaning the death of the CLI, not the OS. The CLI is alive and well, and actually seems to be getting more useful with the new MS OS's.

      For what it's worth, I'll be glad to see DOS the OS go. It was a great fun in its time, but it's out lived its usefulness and is causing us many more problems than it is solving them. Keep either it or Linux on a boot disk for emergencies, but if I never have to explain to a customer the difference between EMS and XMS memory, and the 640k limit, I'll be a happy man. That, and the Win9x resource issues (a main problem in the stability of those systems) will be a distant memory are enough to wish DOS farewell.

  16. Little content, little meaning... by Thomas+M+Hughes · · Score: 4, Interesting

    This just sounds like a Microsoft publicity stunt more than anything. A sort of "We have evolved beyond needing prompts, and are now fully graphically inspired."

    Still, I'd be willing to argue that the removal of legacy DOS functionality isn't always a good thing. You break functionality with code that used to run on previous MS Operating systems. Furthermore, I'd imagine everyone who's been working in computers for awhile has watched the Windows GUI break, and then need the command prompt to fix it.

    Now on the other hand, this may be a plus. Microsoft might actually believe that Windows is stable enough that you don't need the DOS prompt anymore. Stability is always good. But even on the most stable platform in the world, I'd still rather not have something crippled from my operating system just because MS doesn't think I need it anymore.

    But back to this little tid bit of a story...just a marketing ploy, not really news.

    1. Re:Little content, little meaning... by hashinclude · · Score: 0

      Well, I'd like to share a few thoughts on the demise of DOS...

      First of all, I always used to use dos batch files to do fancy little things (like renaming 100s of JPG or GIF files into a neat little order), and get stuff to work. CDROM drivers, sound drivers, you name it. Loaded through DOS.

      Second, when I wanted to remove all traces of WinNT from my machine, and install Win2k (at work), and I didnt have a boot disk! What could one do except delete everything manually (through the safe mode command prompt option), no deltree, no help from linux either (C: is NTFS). And doing a recursive ATTRIB -R -S -H -A * in all directories one at a time... couldnt have done it without DOS

      Sad to see you go.... DOS always rox (esp. on the 8086 I learned using a PC on.... )

      Refresh

      --
      US is now divided as the "Red" and "blue" states. Red States = communist countries. Coincidence? I think not
    2. Re:Little content, little meaning... by tswinzig · · Score: 3, Insightful

      Furthermore, I'd imagine everyone who's been working in computers for awhile has watched the Windows GUI break, and then need the command prompt to fix it.

      Well I haven't seen the GUI "break," but I do still use the commandline, and it's still in Windows XP. It's just not DOS any more... Big whoop.

      --

      "And like that ... he's gone."
    3. Re:Little content, little meaning... by zsazsa · · Score: 2

      Now on the other hand, this may be a plus. Microsoft might actually believe that Windows is stable enough that you don't need the DOS prompt anymore.

      Microsoft has believed that since 1993, when Windows NT 3.1 came out.

      Anyway, this isn't about "not needing a command prompt" as NT (and 2000 and XP) have always had one. It's about finally having a Windows operating system for the home that isn't kludged on top of ye olde DOS. (Instead, ye olde DOS is kludged on top of Windows NT. :)

      Ian

    4. Re:Little content, little meaning... by t14m4t · · Score: 3, Interesting
      I'd like to comment on all of your points.

      (1) this article is a marketing ploy
      (2) removing MS-DOS from XP breaks backward compatibility
      (3) command line necessary restore to working order
      (4) stable enough withouit CLI

      But i'll handle them out of order.

      (2) Removing MS-DOS from XP breaks backward compatibility
      If you're interested in backward compatibility of DOS-based progranms, then you shouldn't upgrade to XP in the fist place. Successive versions of Windows from 95 on have successively had less DOS-compatuibility then it's predecessor. By now, if I need DOS functionality, I wouldn't upgrade to XP even if it had a CLI. (Actually, if I needed MS-DOS compatibility, I FOR SURE would not have gone past 98, if even that far.)

      (3) Command line necessary restore to working order
      Yeah, I'll agree. Or, you could alternately do what most people do: ctl-alt-del, then reset button if that doesn't work (and then for me, there was one time I had to pull the power cord because even the reset button was frozen). Admitedly, if it's important enough that I don't want to reboot, then a CLI is very necessary. But when I'm in Windows, and it crashes, then I normally won't be able to bring up a CLI anyway, nor would I even be able to fix it should that be possible.

      (4) Stable enough withouit CLI
      From (3): "When I'm in Windows, and it crashes, then I won't be able to bring up a CLI anyway." At this point, the only thing I ever use a Windows CLI for is to use ping to see if my network problems are on my end or my ISP's. (it's usually my ISP's: RoadRunner SUCKS! but that's a different thread....) I LOVE my Linux CLI. It's more than a mere "Command Line Interface," but actually a small, on-the-fly, resizeable interpreter with a scrollable history. But the Windows CLI is so limited that it's not really all that useful for me.

      (1) This article is merely a marketing ploy
      Maybe. The conference and celebrity collection probably was a marketing ploy, but it's hard to say whether the article was or not. Either way, this is interesting, and it's hard to deny that (a) MS-DOS is dead (has been "effectively dead" for a while), and (b) it was very important in its day.

      weylin

      --
      67.5% Slashdot Pure I guess I need to work on that.... :)
    5. Re:Little content, little meaning... by bribecka · · Score: 2

      Microsoft has believed that since 1993, when Windows NT 3.1 came out.

      I thought that the first NT was actually version 3.51, or am I wrong. Either way, MS did think it was stable since then :)

      --

      Where are we going and why am I in this handbasket?

    6. Re:Little content, little meaning... by the_rev_matt · · Score: 1

      >Microsoft might actually believe that Windows is stable enough that you don't need the DOS prompt anymore

      Microsoft also believes that their products are secure and reliable. Just because a fanatic believes something, doesn't make it so. I'd trust real world examples of this stability long before I'd believe the Kool-Aid drinkers in Redmond.

      --
      this is getting old and so are you

      blog

    7. Re:Little content, little meaning... by operagost · · Score: 1

      You're wrong. 3.1 and 3.5 were pretty useless, being rushed out the door in full bugginess in a vain attempt to beat OS/2.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    8. Re:Little content, little meaning... by Doctor_D · · Score: 2

      Furthermore, I'd imagine everyone who's been working in computers for awhile has watched the Windows GUI break, and then need the command prompt to fix it.

      This was true with Windows 3.1. With newer versions of Windows, the standard response is 1) reboot, 2) re-install app, 3) re-install everything. So unfortunatley in that broken OS, there is little need for a command line. Besides re-installing windows seems to be the best fix. Personally I prefer the upgrade pack called Linux, or *BSD...

      --
      "If you insist on using Windoze you're on your own."
    9. Re:Little content, little meaning... by Zspdude · · Score: 1

      I definately find it very hard to believe that Microsoft, or anyone else, for that matter, will ever be able to replace the command prompt and replace it with a completely graphical system(no matter how graphically inspired they are). The simple fact of the matter is, that most number of buttons on a mouse I've ever seen is three, and there are 26 letters on a keyboard, not counting symbols, numbers, or capitals.... Try as you may, it is impossible to graphically provide the same versatility provided by a command prompt. Stability matters aside, there are always(and there will always be) tasks for which Windows fails to provide the opportunity to directly issue a command. For tasks where I know precisely what I want to do, and which could be done with a single instruction at a command prompt, the inadequacy of Windows makes it hard for me to ever take their graphical inspiration seriously.

      --
      What's in a Sig?
    10. Re:Little content, little meaning... by Already.there · · Score: 1

      I'd like to clarify something here: It took this many cycles of the NT OS for MS to figure out the benefits to doing something from the command line, but they've finally caught on. In XP you see their first real push to provide a command-line equivalent for everything that you can do inside of it's management consoles. Virtually any management task that you would perform using the GUI can be scripted and run remotely from the command line.

      While they're pushing more gunk into the GUI they're not saying they no-longer need command prompts -- cmd.exe is a usefull tool & it gets more functionality with each release.

      Take a look at the advances made in win2k & xp: partitioning from the command line, scriptable running in alternate credentials, recovery consoles to securely access your NTFS data in the event of a system crash, etc...

    11. Re:Little content, little meaning... by Anonymous Coward · · Score: 0

      I have quite a few batch files on my XP box, they work perfectly fine as long as the commands being used are supported in cmd.exe (there's a list in the XP help file of commands that are no longer supported as well as new commands, or you can just look up the full command list). Of course, you shouldn't be messing with drivers in the command line when you're running XP...

      Umm... not sure why you were using the command line to slick your system for 2k from NT, when you could've just started it with Windows running, and had the 2k setup format the drive. Also, booting to the command line on an NT box doesn't put you in DOS, either, unless you were on a dual-boot system (besides the fact that you can't access NTFS with DOS).

    12. Re:Little content, little meaning... by Mike+McTernan · · Score: 1

      Still, I'd be willing to argue that the removal of legacy DOS functionality isn't always a good thing. You break functionality with code that used to run on previous MS Operating systems

      I'd have to disagree. It is legacy that makes Wintel boxes as bad as they are. In the case of windows, parts of the API's are broken and have to be that way to remain compatible with older programs (a problem for WINE as they have to implement the bugs!). Leaving these bugs in is bad for developers and also leaves the API's a mess. In the case of chip makers, a lot of them would probably love to ditch compatability with older chips to make something fast and lean...

      --
      -- Mike
    13. Re:Little content, little meaning... by thehamster · · Score: 1

      Err, Apple Macintosh System / MacOS used a completly graphical system. MacOS X is the first time a MacOS has had a command line.

      --
      -- This is not a sig. But I'm a liar.
    14. Re:Little content, little meaning... by NutscrapeSucks · · Score: 2

      (2) Removing MS-DOS from XP breaks backward compatibility

      The semi-compatible "Virtual DOS Machine" was pretty much unchanged through MS-OS/2 1.3 to Windows NT 3.1 to Windows 2000. It's good enough to run most DOS business applications, but not good enough to run most games or anything that requires funky drivers.

      DOS compatibility was actually the "killer feature" back in the late 80s -- as in the lack thereof killed OS/2 1.x as a viable desktop OS. IBM significantly improved it for OS/2 2.x, but Microsoft (probably because they were still making a gazillion dollars off of MS-DOS) never really took fixing the NT emulation very seriously.

      I understand that with XP, it now emulates a SoundBlaster and VESA. This is pretty amazing considering that absolutely no work has been done on the thing in 10+ years. Anyway, OS/2 shipped in 1987 and it's not like people haven't been warned for more than a decade that DOS is going away and would be replaced by some virtual emulator.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    15. Re:Little content, little meaning... by noda132 · · Score: 1

      Furthermore, I'd imagine everyone who's been working in computers for awhile has watched the Windows GUI break, and then need the command prompt to fix it.

      Yes, it's truly lovely. Ever had win2k die on you? The only solution I've found (since safe mode doesn't work about 7 times out of 10) is to boot to the CD (which most of the time involves changing your BIOS to do that); wait for the entire setup to load; get through the rather annoying setup which could REALLY use a "back" feature (I'm sure I'm not the only one who tries stuff to quickly after the 5 minutes of loading); and getting to a console, which takes even more time to load.

      And each time you want to try it out you have to reboot once to try out the GUI and again to reboot to the prompt when it doesn't work -- the whole 15-minute eXPerience over again!

      And for those who say "use Safe Mode Command Prompt" -- try it. It boots the GUI and sticks the command prompt on top. Which won't boot if your GUI doesn't work.

    16. Re:Little content, little meaning... by shyster · · Score: 2
      Still, I'd be willing to argue that the removal of legacy DOS functionality isn't always a good thing. You break functionality with code that used to run on previous MS Operating systems.

      Good. There's not a single DOS app that should be run anymore. If you really need a DOS app, keep using DOS. Your app isn't supported anymore, why should your OS be?

      Furthermore, I'd imagine everyone who's been working in computers for awhile has watched the Windows GUI break, and then need the command prompt to fix it.

      3 answers. (1) DOS boot disk. (2) Linux boot disk. (3) Recovery console. There are many other methods to fix a hosed GUI available. With NTFS finally making headway on FAT32, DOS boot disks (without SysInternal's read/write DOS NTFS driver) will become useless.

      Now on the other hand, this may be a plus. Microsoft might actually believe that Windows is stable enough that you don't need the DOS prompt anymore. Stability is always good. But even on the most stable platform in the world, I'd still rather not have something crippled from my operating system just because MS doesn't think I need it anymore.

      This is insightful? +4?!? One of the main problems with Win9x is the lack of stability caused by legacy code! What do you think the #1 reason that NT/2000 are 10x more stable than 9x is? It's 16-bit code! It's the dreaded "system resources" that that backwards compatibility requires! If moving to a more stable platform breaks your copy of Wordstar (it probably won't...most apps perform admirably well under ntvdm) then you need a new word processor! Don't blame the OS for moving forward, blame yourself for not upgrading your apps but still think you should have all the functionality of a modern OS!

    17. Re:Little content, little meaning... by shyster · · Score: 2
      Yes, it's truly lovely. Ever had win2k die on you? The only solution I've found (since safe mode doesn't work about 7 times out of 10) is to boot to the CD (which most of the time involves changing your BIOS to do that); wait for the entire setup to load; get through the rather annoying setup which could REALLY use a "back" feature (I'm sure I'm not the only one who tries stuff to quickly after the 5 minutes of loading); and getting to a console, which takes even more time to load.

      Put your Win2K CD in. Go to a CLI, and type winnt32 /cmdcons That'll put the Recovery Console on your startup list in the boot.ini file. No more having to load from the CD.

    18. Re:Little content, little meaning... by Anonymous Coward · · Score: 0

      Perhaps it is market positioning related to OS X's sudden command-line friendliness.

  17. 16-bit, 32-bit, 64-bit... by fleeb_fantastique · · Score: 5, Interesting

    With the creation of the 32-bit Windows OSes, Microsoft had these relatively unpleasant hacks involving wowexec and system/system32 folders. I suppose they were relatively necessary (although I'm sure folks here could have thought of a better way, but we have the benefit of hindsight).

    Now they're finally leaving 16-bit behind, only to introduce similiar (if not worse) hacks between 32-bit and 64-bit OSes. Instead of following their old design (which at least would have been consistent), they opted to use the system32 folder to hold 64-bit stuff, and to have another folder (is it system64?) hold the 32-bit stuff.

    Confused yet?

    Oh well...

    --
    And so it goes.
    1. Re:16-bit, 32-bit, 64-bit... by micromoog · · Score: 5, Insightful

      Oh wait, it's better to have /bin for programs, and /usr/bin for programs, and /sbin for, uh, programs . . . some of which depend on files in various subfolders of /lib (or was it /usr/lib?) . . . much cleaner.

    2. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      It is. /bin is for programs needed to boot that user run too /sbin programs for admin
      /usr/bin is programs included with the dist.
      /usr/local/bin is where the programs you install after should be. And the diffrent lib dirs is to know where the libs for the programs should be. Ever wounderd what the --prefix flag to the Counfigure script does?

    3. Re:16-bit, 32-bit, 64-bit... by micromoog · · Score: 2
      Ever wounderd what the --prefix flag to the Counfigure script does?

      No. Never once. And I could come up with loads of examples that break those nice neat "rules" above, but I'll leave this as an exercise to the reader.

    4. Re:16-bit, 32-bit, 64-bit... by Hard_Code · · Score: 2

      Bahaahaahahaha! Don't forget /usr/local/*, and /opt, and /share...

      Linux on the Desktop absolutely has to kill/prune this tangled hierarchy. Explain to me the distinction of "/usr/local" on a desktop machine?? *Everything* is LOCAL.

      --

      It's 10 PM. Do you know if you're un-American?
    5. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      Typical response from a user bred on systems where all users are root equivilant. The /sbin directory contains the executable binaries for the system start and for system administration by the superuser. The /bin directory contains important commands which are not specific for the superuser. The /usr binary subdirectories contain Commands and applications relevant for the user which are used less frequently, which carries over from a time where /usr would be located on a slower disk than the main /bin and /sbin, before disk space was so cheap. Although the original reasons may no longer exist in this case, it works, and there is no reason to abandon it.

    6. Re:16-bit, 32-bit, 64-bit... by user32.ExitWindowsEx · · Score: 1

      In my humble opinion, Windows NT/2000/XP have autocomplete at all the input prompts (Run, the Address Bar, the Command Prompt (cmd.exe), etc.) and so does Linux. They both have filesystems that are capable of astoundingly long names. So, why the heck can't modern OS developers use descriptive directory and file names? /bin, /sbin ,/usr/bin, c:\winnt\system32, c:\winnt\ime, etc. are too short and nondescriptive IMHO. OS makers NEED TO USE FILE NAMES THAT ARE MORE DESCRIPTIVE. Otherwise, we should all just go (back, in some cases) to FAT16 naming rules.

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
    7. Re:16-bit, 32-bit, 64-bit... by richie2000 · · Score: 1
      Confused yet?

      Well, this is the same people that named the boot disk "SYSTEM" and the system disk "BOOT" (Both NT4 and Win2k did this, don't remember about NT3.5x and my XP test box is currently installing Debian so I can't check).

      --
      Money for nothing, pix for free
    8. Re:16-bit, 32-bit, 64-bit... by ethereal · · Score: 4, Informative

      /usr/local is for stuff that didn't come with the standard install. /share is actually useful, believe it or not, although I'm not sure where other OSen put user-shared files like that. It's better than /etc, at least. /opt is an abomination and must die, I agree.

      Responding to the parent post: there's a reason for those different /bin directories: /sbin is for statically linked binaries in case your system is really hosed, /bin is for when you don't have /usr mounted, and /usr/bin is for everything else.

      In practice, distributions may not be setting things up quite this way, but IMHO they should. If you're putting everything on just one filesystem, then most of these don't matter, except for /sbin.

      And in case I forgot to mention it, /opt must die. Especially annoying are RPMs that are non-relocatable so that you can't change the install prefix away from that damn /opt. It's a huge pain if you are striving to have the smallest possible root filesystem and then @$%! KDE dumps tons of stuff in /opt. Yes, it's really the RPM makers' fault. No, it still bugs the heck out of me.

      --

      Your right to not believe: Americans United for Separation of Church and

    9. Re:16-bit, 32-bit, 64-bit... by Ami+Ganguli · · Score: 2

      There's still a good reason to have a distinction between /bin and /usr/bin. /bin is normally on the root partition and the commands there will be available in maintenance mode. /usr/bin will normally be on a much larger disk, so you can put lots of stuff there, but it won't normally be mounted in maintenance mode.

      Keeping the root partition small means it's less likely to get f**ked up on the event of serious problems, so you just put those commands in /bin that you really need in order to recover the machine.

      --
      It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
    10. Re:16-bit, 32-bit, 64-bit... by roystgnr · · Score: 2
      Tell you what - I'll set up a computer mounting /usr/lib over the network (or off a CD-R, or a ROM device), and you try to mount C:\Windows\ (or was it C:\Windows\System?) the same way, and we'll compare notes on what doesn't break and what does.

      Yeah, it seems crazy, but there are good reasons for keeping around most of the Unixisms that Linux still has. There are no good reasons for many of the hacks and 64-bit incompatibilities in the Win32 API, or for Win16 to ever have existed.

    11. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      Hahaha,

      system and system32 are still around in XP.

      And probably will be forever :-)

    12. Re:16-bit, 32-bit, 64-bit... by ananke · · Score: 1

      /bin,/sbin is descriptive enough. it allowes my system to use majority of stuff written 30 years ago. and i can name additions anything i want.

      --
      --- d'oh
    13. Re:16-bit, 32-bit, 64-bit... by Josh+Mast · · Score: 1

      Well, here we go.

      /bin - For binaries you absolutely need. Things you can't live without when booting into single-user for example. (Seeing as how traditionally, /usr would be mounted from another partition and you wouldn't be mounting it in singleuser.)
      /sbin - Same as above, but mostly binaries for your superuser (hence the S).
      /usr/bin - All the other binaries that are part of the default system.
      /usr/sbin - Same as above, but again, for your superuser.

      And of course we have the /usr/local tree for all the things we wind up installing afterwards that aren't part of the default system. This isn't exactly a UNIX-wide standard, however (Solaris comes to mind.)

      As always, IANAE, and I may be wrong. But that's pretty much the gist of things.

    14. Re:16-bit, 32-bit, 64-bit... by jandrese · · Score: 2

      Have you ever actually used the command line in Win2K? It's horrible. Everything has a space in it (space is generally reserved as a delimiter character on the command line!) and you end up having to put quotes around practically ever CD command. Even worse, if you have your prompt set up to display the current directory it doesn't take very long for your prompt to become long enough to start wrapping on almost every command. I consider most directory names in Win2K to be needlessly verbose personally, and I'd love to see them trim some of the directory names down a bit. I can't be the only person who gets annoyed at humongous paths like:
      C:\Documents and Settings\Administrator\Start Menu\Programs\Microsoft Office Too
      ls>

      --

      I read the internet for the articles.
    15. Re:16-bit, 32-bit, 64-bit... by Malc · · Score: 1

      But Debian doesn't label their boot disk "BOOT" either... it's "RESCUE". The first time I tried to install Debian, I immediately put that disk to one side thinking I would only need it if I had problems... and then spent the next age trying to figure out how to the system! No counting for stupidity, eh? ;)

    16. Re:16-bit, 32-bit, 64-bit... by Isle · · Score: 1

      You've been running to much redhat...

    17. Re:16-bit, 32-bit, 64-bit... by WWWWolf · · Score: 2, Informative
      Linux on the Desktop absolutely has to kill/prune this tangled hierarchy. Explain to me the distinction of "/usr/local" on a desktop machine?? *Everything* is LOCAL.

      And what "Linux on the Desktop" has to do with file locations? I run GNOME and Nautilus and Mozilla and all the other stuff (only using command line for "tricky" tasks), and I don't need to know anything other than "um, my files are under directory /home/wwwwolf".

      If we want a "desktop" shell, you just need to get one that supports $PATH - and I think popular shells did this before MS-DOS, our thing of comparison, was even invented.

      And as for the explanation of /usr/local: /usr/local is a tree where, basically, you're allowed to install software that is independent of the packages. dpkg and rpm and whatever else your dist may be using for package handling put their stuff to /usr, and you're free to do whatever you want with /usr/local.

      If you want to manage "packages" under /usr/local, I recommend Stow - Basically, installation of new software that isn't prepackaged for your system can be as easy as:

      ./configure --prefix="/usr/local/stow/package-1.0"
      make
      make install
      cd /usr/local/stow
      stow package-1.0

      This will create appropriate links to /usr/local subdirectories - /usr/local/bin/package will link to /usr/local/stow/package-1.0/bin/package and so on...

      Deinstallation:

      cd /usr/local/stow
      stow -D package-1.0
      rm -rf package-1.0

    18. Re:16-bit, 32-bit, 64-bit... by AnarchySoftware · · Score: 1

      From some jargon file somewhere, this appropriate quote about windows:

      A thirty-two bit extension and graphical shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor which was written by a two-bit company that can't stand one bit of competition.

    19. Re:16-bit, 32-bit, 64-bit... by 42forty-two42 · · Score: 2, Informative

      Very simple:
      /bin - Critical apps, but used by regular users
      /sbin - Critical appes, use by the superuser
      /usr/bin - Not-so-critical apps.
      /lib - Critical libraries
      /usr/lib - Not much difference from /lib, maybe we should symlink them?
      /usr/local - Stuff that didn't come with your linux distro
      /usr/local/lib - libraries that didn't come with your linux distro
      /usr/local/bin - executables that didn't come with your linux distro
      /usr/share - Data that everyone can read
      /opt - No clue. Optional stuff, maybe?
      /var - Datafiles that change frequently. Used because you may want to put it on another partition, to reduce fragmentation
      /tmp - Temporary files

    20. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      As root:

      ln -s /usr/local /opt

      Problem solved.

    21. Re:16-bit, 32-bit, 64-bit... by Tower · · Score: 1

      Well, you can just mount /opt separately (bah), or just have it as a link to an area /usr/local (a nice solution). Still not perfect, but for partitioning, and peace of mind, it helps a little...

      /opt is a major pain on AIX, I'll tell you that much.

      --
      "It's tough to be bilingual when you get hit in the head."
    22. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      AFAIK, /opt is like /usr/local, and originates from other Unices that don't put their third party stuff in /usr/local, but rather called it /opt. It caught on with Linux somehow.

    23. Re:16-bit, 32-bit, 64-bit... by ethereal · · Score: 1

      Yeah, I could do that. I also just like having a clean / directory, which /opt takes away from IMHO.

      --

      Your right to not believe: Americans United for Separation of Church and

    24. Re:16-bit, 32-bit, 64-bit... by CMBurns · · Score: 0

      > Tell you what - I'll set up a computer mounting
      > /usr/lib over the network (or off a CD-R, or a
      > ROM device), and you try to mount C:\Windows\
      > (or was it C:\Windows\System?) the same way, and
      > we'll compare notes on what doesn't break and
      > what does.

      Well, first I have to notice that it's absolutely amazing how every time a valid argument is brought up against Linux, some jerk comes up with a completely useless example of Linux supremacy. In this case it was not even an anti Linux posting. micromoog merely stated that the hierarchy used by Linux is as bewildering to the unsuspecting as the one used by Windows.

      If you're talking about C:\Windows, you should also set up a Linux box and mount / over a network.

      I'm sure some brown-nosed Linux zealot will mod this down as troll, but hey, that's what metamods are for, right?

      Hoogla Boogla

    25. Re:16-bit, 32-bit, 64-bit... by j-pimp · · Score: 2, Interesting

      /opt - No clue. Optional stuff, maybe?
      Ok /opt, which I believe dates back to Solaris or SunOS was intended for commercial software. What usualls happened was you had /opt/maple, /opt/ acrobatreader, /opt/unix_port_of_wordperfect_5.1_for_dos, etc. Then all the executables would get symlinked to /opt/bin and libs to /opt/lib. KDE and gnome decided to do similar being there were complete envirorments with there own programs, libraries, etc. But they both decided on /opt/kde/ and /opt/gnome having thwere own bin lib and share directories. Luckily most distros are moving towards just / /usr and /usr/local to keep tnhe path thing straight.

      --
      --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
    26. Re:16-bit, 32-bit, 64-bit... by user32.ExitWindowsEx · · Score: 1

      I agree that cmd.exe needs to be redone to allow the window to stretch horizontally as well as vertically.

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
    27. Re:16-bit, 32-bit, 64-bit... by Chelloveck · · Score: 2
      Have you ever actually used the command line in Win2K? It's horrible.

      Brother, it's time for you to see the light that is 4NT. Everybody say 'AMEN!'

      --
      Chelloveck
      I give up on debugging. From now on, SIGSEGV is a feature.
    28. Re:16-bit, 32-bit, 64-bit... by The+Madpostal+Worker · · Score: 1

      /opt its for things that are complete sets of applications(usually add on packages). Its nice beacuse you know that the application is nicely contained, and its easy to remove(usually).

      For example I have /opt/mathematica /opt/vmware etc.

      --

      /*
      *Not a Sermon, Just a Thought
      */
    29. Re:16-bit, 32-bit, 64-bit... by user32.ExitWindowsEx · · Score: 1

      Actually, given that ntldr supports boot-time loading of a SCSI card device driver (it may support loading ANY type of device driver, but SCSI card drivers are the only documented ones), it might be possible to come up with a driver that does load the SYSTEM partition over a LAN, from a CD-R, etc. Yes, I know that this would be a 32 bit reinvention of a DOS TSR module. As for swap (partition/file), that can be assigned to a spot (it can be even shut off totally in XP - if you have enough RAM, of course - I have 384 and it is more than enough).

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
    30. Re:16-bit, 32-bit, 64-bit... by The+Madpostal+Worker · · Score: 1

      I think /opt has a valid reason to exist. /usr/local is for things that didn't come with the base system, and /opt works well for applications(or appication suites) that are add-ons. I find it nicer to install things like mathematica in /opt and then fix config files to in clude their libs and fonts rather than letting them slowly pollute my /usr/local tree.

      --

      /*
      *Not a Sermon, Just a Thought
      */
    31. Re:16-bit, 32-bit, 64-bit... by richie2000 · · Score: 1
      But Debian doesn't label their boot disk "BOOT" either... it's "RESCUE".

      Even the installation CD looks like a rescue disk onscreen. It made me look in the diskdrive to see if I had anything in there it could boot from. :-)

      However, that diskette is primarily supposed to be a rescue disk, normally you would want to boot off the hard drive - it just doubles as a boot disk. In MS' case, the partition where NTLDR and BOOT.INI resides is named SYSTEM while the partition where WINNT is, is called BOOT. I honestly don't remember what happens if you have everything on the same partition, I have only made that particular mistake once and that was years ago.

      Once in a while, friends call me and want help reinstalling Windows 2k or NT, most of them have one single NTFS partition. I typically have a 2GB FAT partition with an i386 directory in it (SYSTEM) and the WINNT on a separate NTFS partition (BOOT). I sleep much better at night than they do. And my teeth are whiter too.

      --
      Money for nothing, pix for free
    32. Re:16-bit, 32-bit, 64-bit... by DA_MAN_DA_MYTH · · Score: 1

      Everything has a space in it (space is generally reserved as a delimiter character on the command line!) and you end up having to put quotes around practically ever CD command.

      uhhh no you don't... instead of running command.exe which is the 16 bit version of DOS run cmd.exe which is the 32 bit version. Now the problem is some of your old DOS programs might run a little wacky in the 32 bit. Like old clipper apps and stuff like that. Wait a minute how will those clipper apps run now without a command line??????

      --
      "It takes many nails to build a crib, but one screw to fill it."
    33. Re:16-bit, 32-bit, 64-bit... by abrett · · Score: 1
      As well as autocompletion, there's another way to shorten these paths. All long file names have 8.3 aliases, which are ~.. is allocated on a first come first served basis to ensure uniqueness. So for instance, 'C:\Program Files' is also
      'C:\progra~1'
      . This means you can most likely access the path
      C:\Documents and Settings\Administrator\Start Menu\Programs\Microsoft Office Tools

      using
      C:\docume~1\admini~1\startm~1\programs\micros~1
      (Although it's entirely possible that micros~1 will be micros~2, ~3). Some of the UNIX pathnames I have to put up with at work are far worse, often going 10 or 15 directories deep.
    34. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0
      If you're talking about C:\Windows, you should also set up a Linux box and mount / over a network.

      It's been done. Look up "diskless workstation" for a start.

    35. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0
      And I could come up with loads of examples that break those nice neat "rules" above,

      I suspect that either (1) you still don't understand the differences for whatever reason, or (2) your vendor isn't following the standard...

      but I'll leave this as an exercise to the reader.

      ... or (3) you're just making it up.

    36. Re:16-bit, 32-bit, 64-bit... by Arandir · · Score: 2

      Of course, it's much better to shove everything under / in one big flat file structure. Think of the simplicity. Only a single entry in your PATH. Only a single entry in your ld.so.conf. Heck, why not put your home directory there as well!

      Except when it comes time to upgrade your distro, or try another, then the scheme all comes crashing down.

      The Unix file hierarchy make sense once you think about it. A certain section is reserved for the OS and OS installed software. Another section is reserved for user/admin installed software. And there's even a section (opt) for software that refuses to conform.

      But this system only works well with distros that use a bit of common sense. Unfortunately a lot of them don't, including a few of the big name guys. With FuLinux (as a fictitous example) I have no idea whether a package is installed under /usr, /usr/local, or /opt. Under a sensible distro you know exactly where everything is without having to check.

      Linux is a Unix-like operating system. If you don't want it to be Unix-like, then go roll your own. The rest of us want Linux to be Unix-like, and we'll keep the Unix-like file hierarchy.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    37. Re:16-bit, 32-bit, 64-bit... by hey! · · Score: 2

      The names are perfectly descriptive. They're just terse.

      Is it really better to rename:
      BIN --> utilities we want whenever the system is booted even for recovery
      SBIN --> utilities we want whenever the system is booted even for recovery but that normal users shouldn't muck with

      ...

      OK, if you don't want that, then you end up with a somewhat codified file names rather than perfectly descriptive, e.g.:

      /bin --> SysUtils
      /sbin --> SysAdminUtils
      /usr/bin --> Applications
      /usr/sbin --> SysAdminApplications
      /usr/local/bin --> NonStandardSoftware

      etc.

      However, I can gurantee that most folks will not grasp this distinction automatically; so why not opt for maximal terseness? You can always create symlinks at the root if you like.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    38. Re:16-bit, 32-bit, 64-bit... by Urchlay · · Score: 1

      So if I'm trying to run a program that isn't in my path, I have to type: *

      "/Programs/System Administrator Utilities/ifconfig -a"

      ..instead of:

      /sbin/ifconfig -a

      Just because long names are possible, doesn't make them much fun to deal with. Even GUI-only users would get annoyed if the pathnames are so long that they won't fit in the column they're being displayed in (for some reason, most GUI file managers have the tendency to just put a few dots in a case like that, rather than have the line items break on spaces like HTML table items might do)

      Yes, I use a shell with file & path name completion, but that wouldn't help me any if I were hard-coding the path in a shell script, for example...

      Also, such names would get so long that when two sysadmins are talking about them, they'd end up abbreviating them anyway (``Hey, Bob, run the ifconfig command. It's in progs slash SAU on these new Annoyux boxes''). At least the abbreviations we already have are well-known.

      * I picked ifconfig as an example because it's (almost?) always in /sbin in Linux distributions, yet a normal user still has a use for it (it'll tell any user what interfaces there are & what addresses they have, not just root)

    39. Re:16-bit, 32-bit, 64-bit... by NutscrapeSucks · · Score: 1

      The funny thing is that they all started arguing over Unix paths and nobody really addressed your point.

      System and System32 were invented becauase it was possible to install a NT 3.x installation directly over Windows 3.1, and then boot back-n-forth between them. That broke with 95 and NT4, but MS has told everyone for years to hardcode System32, so that's what we get.

      I don't think WOW is hack at all -- at least compared to 9x -- it's just an app that intercepts 16-bit API calls and reissues them as 32-bit. I agree that it will start to look hacky if System64 appears. Do 64-bit Unixes have two versions of their system libs?

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    40. Re:16-bit, 32-bit, 64-bit... by mce · · Score: 1

      It caught on because it is a logical thing to do if /usr/local is defined as "you can play with this in whatever way you want to your heart's delight". In that kind of context, /usr/local cannot be relied upon for anything, so...

      I know a place where /usr/local is NFS mounted (and has been so for 12 years or more). It's used for all the shared stuff that is site-local (as opposed to machine-local). Then if you have to install an optional compiler on one machine, where do you go? /opt is the answer Sun and HP etc. came up with, because it's the only thing outside (/usr)/bin that they could safely claim some control over.

    41. Re:16-bit, 32-bit, 64-bit... by andkaha · · Score: 2
      Oh wait, it's better to have /bin for programs, and /usr/bin for programs, and /sbin for, uh, programs . . . some of which depend on files in various subfolders of /lib (or was it /usr/lib?) . . . much cleaner.

      It's amazing how many Unix users there are that doesn't know a thing about FHS, the Filesystem Hierarchy Standard!

      The scary part is that some of them is managing large numbers of Unix servers and workstations without knowing the difference between /opt and /usr/local and why it's wrong to have every single piece of additional software installed in /root and run as root.

      Bugger'em

      --
      It's 11pm, do you know what your deamons are up to?
    42. Re:16-bit, 32-bit, 64-bit... by andkaha · · Score: 1
      Windows NT/2000/XP have autocomplete at all the input prompts (Run, the Address Bar, the Command Prompt (cmd.exe), etc.) and so does Linux.

      Linux does not have file name completion, but most Unix shells have.

      OS makers NEED TO USE FILE NAMES THAT ARE MORE DESCRIPTIVE.

      You are free to make /system_binaries a link to /sbin, it's really no that hard. But you may prefer to call it /system_binaries_and_execuatable_files

      --
      It's 11pm, do you know what your deamons are up to?
    43. Re:16-bit, 32-bit, 64-bit... by jjeff · · Score: 1

      Are you sure KDE and gnome decided on using /opt ?
      ive never seen them use this location in any distribution except redhat.(i dont know but im assuming mdk is the same).
      when compiling src, they go into /usr/local
      (i think kde defaults to /usr/local/kde.. dont know how long they have been doing that though).

      anyway, i use debian (have been since 1.3) and i have never had /opt anywhere in my filesystem.

      --
      when everything is working perfectly.. BREAK SOMETHING before something else FUCKS up!
    44. Re:16-bit, 32-bit, 64-bit... by roystgnr · · Score: 2

      The original poster was suggesting that /bin, /usr/bin, and such are obsolescences in the same way that the 16-bit code (and non 64-bit clean code) in Windows is. I was explaining why that is not the case. You are being a unnecessarily insulting jerk.

      Does that explain everything?

      If you're talking about C:\Windows, you should also set up a Linux box and mount / over a network.

      OK.

    45. Re:16-bit, 32-bit, 64-bit... by kimihia · · Score: 1

      Oh dear, you don't seem to have much of a clue about how the Filesystem Hierachy Standard works. Come back and troll again another time.

    46. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      And neither did the moderators....

      Slashdot is going down the pan - we'll just have to see if VA can beat it.

    47. Re:16-bit, 32-bit, 64-bit... by noda132 · · Score: 1
      OS makers NEED TO USE FILE NAMES THAT ARE MORE DESCRIPTIVE.

      • Normal users should not have to remember ANY directory names except the ones they make up -- system directories should be transparent.
      • System administrators prefer a fast, simple, and all-encompassing directory structure.
      Why on EARTH would I type "c:\Documents and Settings\noda\Local Settings\Application Data\Microsoft\Outlook\Outlook.pst" when I could put it where I wanted: somewhere like "/home/noda/mail"? Windows path: 92 characters. Linux: 15. And before you go on about ~1's: I could probably type in /home/no before you typed in ~1 alone. And it's useless in c:\progra~1, since there are tons of micros~'s.

      I think "Documents and Settings" is the worst thing that could ever possibly happen to computers. "Local Settings" and "Application Data" aren't far behind.

      Add to that the fact that the backspace key is in a different spot on every different keyboard....

      I begin to wonder if these horribly long directory structures were implemented to force people to double-click. Or maybe to show off that it's not DOS. Or to discourage newbies from fooling around with the filesystem. Because I'm sure it's not because it's easier.
    48. Re:16-bit, 32-bit, 64-bit... by whiteranger99x · · Score: 1

      IIRC, I believe Slackware is a distribution that uses /opt generally for KDE and "optional packages" as noted here
      I'm not certain if other distros have /opt created on the top of my mind, but i'm pretty sure slackware does.

      --
      Join the TWIT army now!
    49. Re:16-bit, 32-bit, 64-bit... by Anonymous Coward · · Score: 0

      Nice try, work on the completely b0rked "four-bit" part.

    50. Re:16-bit, 32-bit, 64-bit... by eric_ste · · Score: 1

      The way I use opt is: for instance foobar-1.2.3:

      ./configure --prefix=/opt/foobar
      make
      make test
      make install
      mv /opt/foobar /opt/foobar-1.2.3
      ln -s /opt/foobar-1.2.3 /opt/foobar

      this way if I ever need to downgrade, it's as easy as replacing a symlink

    51. Re:16-bit, 32-bit, 64-bit... by user32.ExitWindowsEx · · Score: 1

      All I have to do to get into "c:\Documents and Settings" is type 'docu' and press [tab]. Thanks to autocomplete, it inserts the rest. ~1's don't exist in NT/cmd.exe rigs. cmd.exe accepts straight quote-less full-length file names (including spaces).

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
    52. Re:16-bit, 32-bit, 64-bit... by user32.ExitWindowsEx · · Score: 1

      Addendum: I read that Windows XP supports booting from ROM images. The OS copies itself into RAM and user apps execute straight from ROM. So it probably is really possible to make the SYSTEM volume load from read-only media or over a LAN.

      --
      "Evil will always triumph because good is dumb." -- Dark Helmet
    53. Re:16-bit, 32-bit, 64-bit... by Tower · · Score: 1

      I agree there... like I said, maybe it can help ease the pain :)

      --
      "It's tough to be bilingual when you get hit in the head."
    54. Re:16-bit, 32-bit, 64-bit... by fleeb_fantastique · · Score: 2

      After a little more study, I found the 64-bit stuff is indeed going into the system32 folder, and the 32-bit stuff will be going into the system folder.

      It's all kind of ugly in that, generally, when you see 'system32', you're going to think 'oh, that 32 means 32 bits'.

      OTOH, it keeps to a kind of consistent logic where the greater-bit-handling stuff is kept in the system32 folder, and the lesser-bit-handling stuff is kept in the system folder. I still find it ugly, though, but I guess they had to figure out something.

      The wowexec stuff won't look hacky to your way of looking at things, because they're abandoning 16-bit (according to the original article I was responding to).

      I don't think the 64-bit unixes worry about 32-bit. But, when you think about it, thanks to Posix certification and such, you probably don't have to worry about it; you just compile your application to the available libs. At least I *think* that's how it is, but I have no practical experience.

      --
      And so it goes.
    55. Re:16-bit, 32-bit, 64-bit... by MrFredBloggs · · Score: 1

      "/usr/local/bin - executables that didn't come with your linux distro "

      Hehe..thats pretty intuitive.

    56. Re:16-bit, 32-bit, 64-bit... by NutscrapeSucks · · Score: 1

      Ow, that's fugly.

      (And 64-bit Unixes still have to worry about 32-bit binary closed source apps, so my guess is that the 32-bit libs are necessary. Even 64-bit Linux still runs 32-bit code like Quake.)

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    57. Re:16-bit, 32-bit, 64-bit... by CMBurns · · Score: 0

      > You are being a unnecessarily insulting jerk.

      So we have something in common, I guess? Besides, this is Slashdot, being a jerk is mandatory!

      Regarding the "diskless" client: One of the first things they recommend is creating a bootdisk... hmmmm... next they go on modifying boot ROMs, which I don't think is really great either.

  18. It was alwasys so annoying by vulgarDPS · · Score: 1

    RIP

    Here lies DOS

    "I can't beleive is actually died"

    "Yeah I thought it would never die"

    "Wait a second.. I think its moving"

    "WOW whats in it"

    "I'll find out"

    C:\>ls

    'ls' is not recognized as an internal or external command,

    operable program or batch file.

    "Dammit, I hate DOS, why dont they just use real commands"

    "Wanker"

    1. Re:It was alwasys so annoying by mydigitalself · · Score: 1

      "Dammit, I hate DOS, why dont they just use real commands"

      as in "move" as opposed to "mv" ?

    2. Re:It was alwasys so annoying by terrymah · · Score: 1

      or a "ren" and "move" commands which do basically the same thing?

    3. Re:It was alwasys so annoying by Anonymous Coward · · Score: 0

      Except you can't "ren" a file to another location and using "move" instead of "ren" to rename all of the time would result in far more disk fragmentation.

  19. DOS prompt =Terminal? by AppyPappy · · Score: 1

    Does XP come with a terminal? If not, who thunk of that?

    Gates: "If you need a terminal to get to it, you don't need to get to it". Thanks Bill. No wonder people are losing MS servers right and left.

    --

    If you aren't part of the solution, there is good money to be made prolonging the problem

    1. Re:DOS prompt =Terminal? by pacc · · Score: 0

      You can always hope that the professional server version will have a telnet backdoor as default.

    2. Re:DOS prompt =Terminal? by Anonymous Coward · · Score: 0

      Gates: "If you need a terminal to get to it, you don't need to get to it".

      I guess that's why Linux/Apache runs 70% of the Internet and Windoze/IIS ... well ... doesn't.

    3. Re:DOS prompt =Terminal? by biglig2 · · Score: 2

      XP in fact adds a pile of extra commands for the command line.

      Built-in task list and killing, for example.

      --
      ~~~~~ BigLig2? You mean there's another one of me?
    4. Re:DOS prompt =Terminal? by operagost · · Score: 1

      XP and 2000 both have Telnet and Terminal Services.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
  20. But it *screams*!!! by Anonymous Coward · · Score: 0

    Ok, it was crashy and unstable under heavy load, but man does it boot up and run -fast- on modern hardware. DOS 3.11 and DBaseIII+ on an AMD Athalon 1.1Ghz is a ripping low-end db system...

  21. Hacktastic mate... by purrpurrpussy · · Score: 1

    DOS was fantastic!! Writing TSR proggies to fake DLLs! Hooking int 2f and adding your own services... int 2e backdoor to the interpreter. Grabbing the entire serial port interrupt mechanism so you you write your own serial packet state machines. You started app development by writing a keyboard handler!

    You could stick things anywhere, cruise the operating system, write semi re-entrant code with the use in the InDOS flag, hack hack hack.... Just don't tryu to be hardware independent!

    It was amazing what people did get out of a DOS machine. 640K is still quite a lot you know.....

    Matthew.

    http://www.freshbrains.co.uk

    --
    "None of this shit works" -W.Shatner
    1. Re:Hacktastic mate... by klmth · · Score: 1
      Just don't tryu to be hardware independent!

      That's precisely what killed DOS games/demos. Demosceners in particular wrote some of the most perverted display hacks I've ever seen, but platform independence wasn't in their books. If you didn't have the same setup, tough.

      Many great demos lost their shot at the prize money when they simply wouldn't run on the competion machine. Many great games were a pain to run, often requiring painful fiddling with TSR:s. (I still have my falcon 3.0 bootdisk hung up on my wall - it loaded a mouse driver, a CD driver, and even the Sound Blaster drivers, while still keeping 630kb of base memory free)

      DirectX changed all this, with the cost of some performance, but with the advent of consumer 3d accelerator cards, it was no longer an issue.

    2. Re:Hacktastic mate... by yesod · · Score: 1


      Yeah, but its time to hang up 'Undocumented Dos' and move on.

    3. Re:Hacktastic mate... by dark_panda · · Score: 1

      640K is still quite a lot you know.....

      I'll say! 640K should be enough for anybody!

      J

  22. Heh, bull ;) by Blymie · · Score: 1

    Love it or hate it, I'm sure everyone's got a love story or traumatic memory of the infamous MS-DOS.

    I never used MS-DOS. Everyone I knew had Amigas at the time, since they were far, far superior to MessyDos of the day. I progressed from that, directly to Linux. This doesn't mean I never had the opportunity to type a command or two under MS-DOS, but it does mean that I never *used* it for anything, realistically. I don't have a fond memory, or traumatic memory of MS-DOS.

    I feel like someone who managed to live through a war without any emotional scars. The thing is, I know many, MANY people that NEVER used a Windows or DOS box, yet lived through the DOS era. These are owners of Amiga, Apple, Atari or other boxes of the era. They commanded a significant market share in the beginning of things, and only later on did their number wane to insignificance. You dishonour them by implying that they never existed, and that there was no other option at the time.

    This is supposed to be a place where people realise the significance of computers in history, and know a little of that history. Please keep that in mind.

    1. Re:Heh, bull ;) by Anonymous Coward · · Score: 0

      Oh pahlease...

      Amiga? VToast for graphics 'experts' of a bygone era... niche stuff at best.

      Atari? Yeah, there's a powerful, market dominating, easy to use set up.

      Now, break out the TI and Commodore... no, wait, they used a bastard version of DOS didn't they... hmmm.

      Spare me. The few technofools in their (well paid sometimes) pathetic niche markets are just plain scary. They owe their jobs to MS, even if they didn't work on MS products... MS, right or wrong, drove (and maybe still does) the market for well over a decade. Without DOS and Windows, you would only have what was until OSX.1 a crappy MAC solution, or some flavor of the incredibly complex and non-user friendly *nix. (I guess you could toss in OS2, but that's one I am sad to have seen die it's slow death... not sure how that fits in).

      No thanks.

    2. Re:Heh, bull ;) by Anonymous Coward · · Score: 0

      Fuck you. Amigas suck.

    3. Re:Heh, bull ;) by Anonymous Coward · · Score: 0

      You dishonour them by implying that they never existed, and that there was no other option at the time.

      If your sense of honor is built upon the fact that you went through life with an Amiga, I'm afraid there will be no way to make you happy.

    4. Re:Heh, bull ;) by Anonymous Coward · · Score: 0

      I guess thats why almost all of the demo groups dropped the Amiga in favour of the PC.

    5. Re:Heh, bull ;) by Anonymous Coward · · Score: 0

      In case you didn't read the original topic, this is about DOS. Can't you see ONE article on something, without starting to push everyone around "hey, yanno Amiga exists too! and it is far better than DOS!! And so is Atari!" People don't give a fuck! Here and now, it's about DOS, not about alternatives. Capiche?

  23. Re:Why does Gates get the credit ? by joeykiller · · Score: 4, Flamebait

    Where are my Karma Points when I need them?

    DOS wasn't licensed from Gary Kildall (who actually was the father of CP/M), but from Tim Paterson.

    You would have known this if you had read the article you're commenting on.

  24. What is DOS? by Andy · · Score: 0, Interesting

    I can happily say that my life has been minimally affected by DOS, its coming or its going. I started my career on VAX's and Macs in the 80's, moved to Unixen in the late 80's, and to LiGNUx in the 90's. I pity the people who have been stunted technically by using DOS.

  25. We will always carry it with us... by Faile · · Score: 2, Interesting

    So Bill Gates typed "exit" and (wow!) the prompt closed, no more DOS, no more unreliable crappy OS's, just XP and .NET - hurray!

    It all began with DOS and DOS will end it as well, or something very much like it - GUI's are overrated. Sometimes you just want a Quick and Dirty Operating System that goes well with scripting, say changing your entire folder of mp3 to use a standard name or just organizing images, perhaps you need to do something that the GUI cant handle. There's nothing a prompt cant handle!

    Long boring story short -> DOS as we know it is dead, but Quick and Dirty Operating System's are the future.

    Long live DOS!

    --

    --
    Anataka suki desu. Itsumo. Itsumademo.
    1. Re:We will always carry it with us... by Smuffe · · Score: 1

      So Bill Gates typed "exit" and (wow!) the prompt closed...
      The article didn't say the prompt closed, it just states he typed "exit". I am quite sure he wouldn't test the reliability by actually pressing enter. I know I wouldn't... :D
      /Smuffe

    2. Re:We will always carry it with us... by CrazyBrett · · Score: 1
      There's nothing a prompt cant handle!

      Hmm, I seem to be having trouble playing Max Payne on just the command prompt... any idea what I might be doing wrong?

      ;)
    3. Re:We will always carry it with us... by Anonymous Coward · · Score: 0
      Anataka suki desu. Itsumo. Itsumademo.

      Um, that should be "Anataga suki desu." The particle that indicates the subject of a sentence is "ga", whereas "ka" is mostly used as a sentence particle indicating a question, or is used between two nouns to mean "or". It certainly isn't what you want here.

  26. DOS is Alive! FreeDos..... by Quazion · · Score: 4, Informative

    here @ freedos.org

    I have used it for formating and fdisking fat16
    and fat32 filesystems, or to remove linux
    partitions without a linux bootflop or bootcd.

    And i know people using DOS for there daily
    programming, creation of Embedded Systems and
    ofcourse webbrowsing and chatting....

    Quazion.

    1. Re:DOS is Alive! FreeDos..... by quantum+bit · · Score: 1

      And i know people using DOS for there daily programming, creation of Embedded Systems and ofcourse webbrowsing and chatting....

      Yes, DOS is definitely used for embedded systems. Last time I was at Target I caught a glimpse of one of the "cash registers" (which are actually IBM terminals) rebooting. It was running some vaiant of DOS, I couldn't tell if it was MS or IBM's, and MS Lan Manager (!).

    2. Re:DOS is Alive! FreeDos..... by Jim+Hall · · Score: 1

      DOS is definitely alive and well, and I'm not just saying that because I founded the FreeDOS Project. :)

      DOS is still used in embedded systems all over the world. The last time I checked, McDonald's cash registers were still running DOS with a McGUI. FreeDOS also appears in such cool devices as a pinball machine! (I think that one is my favorite.)

      On our web site we recently posted a news item about running FreeDOS in a PDA. A few weeks ago, we posted a "success story" from someone who uses FreeDOS to support various doctors' offices.

      Is DOS going to remain in the limelight? Well, probably not. DOS hasn't really hit the big news in a long while, and I suspect that DOS will remain the mainstay of embedded programmers for a long time to come. But the desktop war has been taken by Linux (and that other company... they also have a GUI with windows...) While FreeDOS+SEAL is very cool (think KDE) I think we'll see that you'll only find FreeDOS on desktops in places that cannot afford the bigger, newer, shinier systems.

      -jh

  27. DOS was "closer" to CP/M Than most realize by NZheretic · · Score: 5, Informative

    From "Microsoft the Company"
    http://www.aaxnet.com/topics/msinc.html

    * 1982 - Digital Research sues Microsoft and IBM - Wins - . It was obvious MS-DOS and its PC-DOS variant were simply rip- offs of Digital Research's CP/M operating system. It remained only to prove it contained DR code. DR's Gary Kildall sat down at an IBM PC supplied by IBM and, using a secret code, got it to pop up a Digital Research copyright notice.

    It's case won, Digital Research received monetary compensation and the right to clone MS-DOS. This is why Microsoft never sued DR over DR-DOS, but used every other means to destroy it. The settlement was under a strict non- disclosure agreement, so few even know DR sued, never mind that they won.

    Digital Research was purchased by Novel and destroyed by neglect and mismanagement. The products now belong to Caldera, which has filed suit against Microsoft over predatory practices used to destroy DR-DOS's market.

    1. Re:DOS was "closer" to CP/M Than most realize by KingAdrock · · Score: 1

      I used Doctor Dos for a while. Alot of software took a shit with it. Eventually I was forced to move to MS-DOS! I don't think the PC world was ready for variants of the same operating system at that point. Unfortuently for Digital Research, that spelled its impending doom!

    2. Re:DOS was "closer" to CP/M Than most realize by TheMidget · · Score: 2, Insightful
      The settlement was under a strict non- disclosure agreement, so few even know DR sued, never mind that they won.

      So how do you (or the author of the book) know about it, if the suit and settlement were such a well-kept secret? Sure you aren't making this up on the fly?

    3. Re:DOS was "closer" to CP/M Than most realize by Anonymous Coward · · Score: 0

      The settlement was under a strict non- disclosure agreement, so few even know DR sued, never mind that they won.

      They can't have settled their suit and won it. So which is it?

    4. Re:DOS was "closer" to CP/M Than most realize by NZheretic · · Score: 1

      Yes it happend.

      Unfortunately Gary is no longer with us to confirm it in person, but to quote Microsoft's CEO Steve Ballmer

      """And we just told IBM look, we'll go and get this operating system from this small local company, we'll take care of it, we'll fix it up, and you can still do a PC.

      Tim Patterson's operating system, which saved the deal with IBM, was, well, adapted from Gary Kildall's CPM."""

      See
      http://www.pbs.org/nerds/part2.html

    5. Re:DOS was "closer" to CP/M Than most realize by Anonymous Coward · · Score: 0
      I used Doctor Dos for a while.

      <nitpick alert>*ahem*, DR-DOS stands for Digital Research DOS, not Doctor DOS.</nitpick alert>

    6. Re:DOS was "closer" to CP/M Than most realize by 42forty-two42 · · Score: 1

      Was the secret code 'xyzzy'? ;)

    7. Re:DOS was "closer" to CP/M Than most realize by Nater · · Score: 2

      DR-DOS stands for Digital Research DOS, not Doctor DOS.

      HP-UX doesn't stand for "hockey pucks" either, but so what?

      --

      I like to play children's songs in minor keys.
      "We're all sons of bitches now." --J. Robert Oppenheimer

    8. Re:DOS was "closer" to CP/M Than most realize by KingAdrock · · Score: 1

      It was a joke.. I was 8 years old, and it was much easier saying doctor than digital research! Christ!

    9. Re:DOS was "closer" to CP/M Than most realize by damiam · · Score: 1

      I think the code was "echo 'CP/M copyright 19xx by Digital Research'".

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    10. Re:DOS was "closer" to CP/M Than most realize by Chester+K · · Score: 2

      DR's Gary Kildall sat down at an IBM PC supplied by IBM and, using a secret code, got it to pop up a Digital Research copyright notice.

      I happen to have a copy of the secret code he used:

      echo "Copyright 1981, Digital Research Corporation."

      --

      NO CARRIER
  28. So I guess XP finally gets to Mac OS7 level by Uttles · · Score: 1

    OK, I'm not seriously saying that Mac OS 7 was as powerful as XP, but I find it funny that for years the main argument against Macintosh was it had no command line interface, and now here Microsoft is removing MS-DOS from their OS. It doesn't really matter though because XP has so many other arguments against it already. I guess it's time for everyone to switch to Linux.

    --

    ~ now you know
    1. Re:So I guess XP finally gets to Mac OS7 level by gazbo · · Score: 2, Informative

      bash != linux
      bsh != unix
      cmd != dos

      The death of DOS does not mean the death of the Microsoft CLI.

    2. Re:So I guess XP finally gets to Mac OS7 level by Anonymous Coward · · Score: 0

      moron...removing dos is not removing the command line option. i'm not for microsoft, but i am against idiots

  29. Alternate shells by Zocalo · · Score: 3, Interesting
    I dumped COMMAND.EXE for JP Software's 4DOS as soon as I found out about it - way back when it was on version 2.x. It's evolved a lot since then and the current version, 7.0, gives modern *NIX shells a pretty good run for their money and interfaces very well with the GUI.

    There is still the problem of having to wait for each stage of the pipe to finish before the next can begin, but there is definately life in the old DOS yet and I'll be using JP's shells long after COMMAND/CMD has gone the way of the dodo.

    --
    UNIX? They're not even circumcised! Savages!
  30. Not quite yet by mystik · · Score: 1

    I have seen edlin.com living somewhere in system32 on either Professional, and/or Home Edition of XP.

    On the other hand, vi is on almost every unix system (as well as ed) so I guess it's only fair...

    --
    Why aren't you encrypting your e-mail?
    1. Re:Not quite yet by Anonymous Coward · · Score: 0

      Uh-oh! You just dissed vi! You implied it was obsolete. Prepare to be lynched.

      I am writing this post in vi under w3m, by the way. :-)

  31. Serious irony by Anonymous Coward · · Score: 0, Flamebait

    DOS has long outlived its usefulness at age 20. And companies should avoid Linux because it's fundamentally based on 30 year old technology.

    Think about it for a while.

    1. Re:Serious irony by gamgee5273 · · Score: 1

      DAMN! And I was preparing to go out and buy that internal combustion-powered vehicle! I almost forgot that its core technologies are over a century old. Thanks for reminding us that anything based on the past is old - and therefore sux.

  32. Invasion of the gui by rmadmin · · Score: 0

    Its good to see technology evolve. On the other hand, its kind of sad to see the "Most popular desktop operating system" go away from having the ability to use command line interfaces. Too bad redhat is sort of doing the same thing with all their GUI configuration tools =( I'd like to see a command driven side of XP that gives the user more power. Oh wait, the DMCA would probably throw a fit and say that 'Now XP users can easily circumvent copyright protections' >=(.

  33. Hold on, is this a troll ? by Anton+Anatopopov · · Score: 2
    Did anyone else notice that the article was written by slashdot's very own king of trolls - Jon Erickson ? You don't have to be an Insightful genius to realise what is going on here!

    Is it too much to ask the slashdot editors to check things like this before posting ? This troll is not even worthy of inadequacy.org

  34. Hilarious: EMM386 stop error by Otis_INF · · Score: 5, Funny

    What I always found funny was that when a certain DOS program went bezerk, EMM386 thought to jump in and save your ass with... that's right, shutting down the computer before you could save _ANYTHING_, showing words similar to:

    "EMM386 has shutdown your computer to prevent loss of data".

    Thankfully these days are over... o wait, nv_disp.dll just went into a stop 0xea

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:Hilarious: EMM386 stop error by Anonymous Coward · · Score: 0

      "nv_disp.dll just went into a stop 0xea"

      well upgrade to some stable nvidia drivers then, silly!

    2. Re:Hilarious: EMM386 stop error by Otis_INF · · Score: 1

      Which one do you recommend? :) I haven't tried the dev drivers 21.88 yet, but all the others are having this bug (even the WHQL ones (21.83)).

      --
      Never underestimate the relief of true separation of Religion and State.
  35. Two part answer by bluecavy · · Score: 1

    Circa 1990...

    After reinstalling his OS, I informed my associsate that "command.com" is not a game file that can be deleted.

    Oh, the canabalistic power of "format C:". I used to type it and just stare at it with my finger on Enter.

    1. Re:Two part answer by Anonymous Coward · · Score: 0

      The really scary one is "format c: /q /autotest"

      This doesn't even prompt! :)

    2. Re:Two part answer by Anonymous Coward · · Score: 0

      Okay, this made me laugh such that I blew snot particles from my nose!

  36. More Info,they even have a GUI Interface for it =) by Quazion · · Score: 1
  37. Quick and Dirty Interrupt Handler by klmth · · Score: 4, Insightful

    Calling MS-DOS an operating system is stretching the concept quite a bit.
    DOS was nothing but a glorified interrupt handler. It wasn't unstable, since there was practically nothing to be unstable with.

    It didn't protect itself from userland programs, which is generally considered a bad thing. Granted, this gave the programmer freedom to completely work around the operating system, but at the same time allowed said programs to royally mess things up.

    From a single-task, single-user system, it was quite good, provided the programs behaved nicely. DOS Extensions even provided it with protected memory, making life a bit easier.
    New command interpreters, like 4DOS, injected new life into the system.
    If you accepted it as a single-user, single-task enviroment, it was adequate.

    I find the decision to remove any and all CLI from Windows a bit odd, considering that Apple went the opposite direction with Mac OS X.

    1. Re:Quick and Dirty Interrupt Handler by Flakeloaf · · Score: 0

      From a single-task, single-user system, it was quite good, provided the programs behaved nicely

      DOS essentially forced programmers to write stable, robust code and you're calling this a bad thing? Given the trend towards sloppiness and bulk in pretty much every program (read "game") available for Win9X/2K/XP today I'd expect you to be a bit more idealistic :) There's no need to be careful today, because if your program misbehaves Windows will try to shut it down, fail, crash and take all the blame.

      --

      Am I the only one who heard Roxette to sing "I'm gonna get blitzed for some sex"?

    2. Re:Quick and Dirty Interrupt Handler by Anonymous Coward · · Score: 0

      XP still has a CLI, not outstandingly brilliant but pretty good and very useable. XP also has a raft of new command line tools built in to make both local and remote machine management easier (NETSH being one) and more easily scripted. XP's cmd batch files are marginally (but usefully) improved by a few key changes (most notably to SET) but combine XP [or 2000 and even NT 4] with Perl and modules like Win32::LanMan, Win32::AdminMisc & Win32::TieRegistry and you have a very decent base with which to manage large domains [10k-100k systems] without too much trouble. 16bit DOS as an OS may be dead but M$ have (somewhat) seen the light with the command line and scripting over the past few years [even including Perl script examples in the most recent W2K Resource kits].

    3. Re:Quick and Dirty Interrupt Handler by Kamel+Jockey · · Score: 1

      I find the decision to remove any and all CLI from Windows a bit odd, considering that Apple went the opposite direction with Mac OS X.

      Actually, the terminal command is somewhat well hidden from the average user in OS X. The traditional Mac user will never need to open up a terminal window to issue commands unless he specifically sets out to do it. Kinda reminds me of the old job that the most commonly run Xwindows program is Xterm :)

      --
      In case of fire, do not use elevator. Use water!
    4. Re:Quick and Dirty Interrupt Handler by Quarters · · Score: 2

      I find the decision to remove any and all CLI from Windows a bit odd, considering that Apple went the opposite direction with Mac OS X.

      I find it funny how people are equating "DOS is dead" to "No more CLI in Windows".

      DOS was never a part of WinNT, Win2K, or WinXP. Yet, all three have command prompts.

    5. Re:Quick and Dirty Interrupt Handler by hashinclude · · Score: 2, Interesting

      Agreed. Another comment I'd like to add here is that the 8086 processor and related (that includes 8088, 80186/188) did not have the concepts of (a) Multi-tasking and (b) kernel space vs. user user space. Thats why the processor was so damn cheap, as compared to the others available "Out There".

      So you should really be thrashing Intel for making a processor that did not support VM, Multitasking, Task Switching (Interrupts are just that, but a lame form) or kernel/user space differences. Not DOS. Dos was really cool, for the time it existed primarily.

      However, Microsoft *SHOULD* have migrated to 32bit dos with the advent of the 386 processor from intel.

      --
      US is now divided as the "Red" and "blue" states. Red States = communist countries. Coincidence? I think not
    6. Re:Quick and Dirty Interrupt Handler by klmth · · Score: 1

      DOS essentially forced programmers to write stable, robust code and you're calling this a bad thing?

      I sincerely don't recall DOS programs being particularly robust. They crashed just as often as programs today, but instead of an OS coming to the rescue by killing or suspending the offending app, it just hung.

      You picked the sloppiness and bulk of windows games as an example, and I can't help but ask: do you remember early-mid-90s Origin games?

      There's no need to be careful today, because if your program misbehaves Windows will try to shut it down, fail, crash and take all the blame.

      Here you have a completely valid beef, especially with Windows 9x: the error recovery was still poor, leading many to think every applications crash was caused by the OS. This is much, much better with Windows 2k. Still, I can't say applications have become more unstable with time. Bulkier and bloated, certainly, but they're still as (un)stable as they were in the DOS days.

    7. Re:Quick and Dirty Interrupt Handler by cperciva · · Score: 2

      [MS-DOS] didn't protect itself from userland programs, which is generally considered a bad thing.

      How exactly would you implement such protections on processors (eg 8086) which don't support protected memory?

      I'll agree that there are many thing that MS-DOS did not do, but in most cases such things were impossible on x86 hardware until the 286 (and the 386 if you wanted to do things properly).

    8. Re:Quick and Dirty Interrupt Handler by Flakeloaf · · Score: 0

      do you remember early-mid-90s Origin games?

      Touché.

      Maybe the crashes under DOS didn't seem so bad because I could reboot in a few seconds. A crash in Win 98, even with a computer four times as powerful, visibly shortens my lifespan.

      --

      Am I the only one who heard Roxette to sing "I'm gonna get blitzed for some sex"?

    9. Re:Quick and Dirty Interrupt Handler by Surak · · Score: 2

      Calling MS-DOS an operating system is stretching the concept quite a bit.
      DOS was nothing but a glorified interrupt handler. It wasn't unstable, since there was practically nothing to be unstable with.


      Hmmm? You seem to be saying it didn't support multitasking or protected memory so it wasn't operating system. By your definition, CP/M isn't an operating system, Apple DOS and Apple ProDOS aren't operating systems.

      What is an OS? An interface between the application program and the hardware right?

      DOS was all of that. It had an API even (INT 21h). It did the file management, disk access functions, even some rudimentary memory management. (Better memory management came in later releases. EMM386.EXE is surely part of DOS, right? :-)

    10. Re:Quick and Dirty Interrupt Handler by shani · · Score: 1

      Yeah, but the 80286 was available in 1982. MS-DOS 2.0 (released in 1983) could have included memory protection for systems that supported it.

    11. Re:Quick and Dirty Interrupt Handler by demaria · · Score: 1

      /Applications/Utilities/Terminal.app

      Not too hidden. But Apple did a great job eliminating the need for the terminal in most instances (you'll need the terminal to start up named for example, which is included in the distribution but can't be accessed from the gui).

      I find I use Terminal mostly to ssh, file management works well with the GUI.

    12. Re:Quick and Dirty Interrupt Handler by SCHecklerX · · Score: 2

      that's what OS/2 was for. In the day when DOS and Windows 3.x were mainstream, OS/2 was so far ahead, it was ridiculous that it didn't take over. Multitasking multiple DOS VM's and having every misbehaved windoze 3.1 app confined to its own VM, with its own config.sys, autoexec, etc, was an absolute joy.

    13. Re:Quick and Dirty Interrupt Handler by rtscts · · Score: 1

      os/2 wanted way too much RAM. A couple of meg set you back hundreds of $ back then. These days hundreds of megs sets you back a couple of bucks..

    14. Re:Quick and Dirty Interrupt Handler by rtscts · · Score: 1
      EMM386.EXE is surely part of DOS, right? :-)

      Absolutely not! It's a clear case of monopolistic tendencies, and the DOJ should have given MS a reaming on behalf of QEMM a long time ago over such blatant bundling practises.

      :)
    15. Re:Quick and Dirty Interrupt Handler by Cro+Magnon · · Score: 1

      Yeah, and M$ could have extended DOS into a 32 bit multitasking OS for the 386. Instead they gave us Doze.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    16. Re:Quick and Dirty Interrupt Handler by Cro+Magnon · · Score: 1

      At least, when your DOS app crashed, you knew which app blew up. With Windows, it could be any combination of running apps!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    17. Re:Quick and Dirty Interrupt Handler by Anonymous Coward · · Score: 0

      > that's what OS/2 was for. In the day when DOS and Windows 3.x were mainstream, OS/2 was so far ahead, it was ridiculous that it didn't take over.

      Thank IBM's marketing folks and the lack of IBM-written device drivers for that failure. "Snatching defeat from the jaws of victory" was _never_ so true.

    18. Re:Quick and Dirty Interrupt Handler by NutscrapeSucks · · Score: 2

      A great book about the the DOS-Windows relationship is "Undocumented Windows 95" by Andrew Shulman. In it, he describes how Win95 was pretty much just a fancied up Win3, and how to hack Win95 into a 386 Protected Mode version of DOS.

      As to shani's comment, Microsoft did ship a 286-mode version of DOS with memory protection and preemptive multitasking. It was called OS/2.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    19. Re:Quick and Dirty Interrupt Handler by Surak · · Score: 2

      I knew some smarta$$ was going to say that ... :)

  38. No more DOS? by MrFredBloggs · · Score: 1

    Only for new apps. I`ll be writing/fixing DOS apps for years... dont forget the hundreds of thousands of DOS apps running on 2/3/486s and which work just fine, thank you very much. Why change them? I mean, if you cant do it 1) for free, and 2) with 0% chance of no bugs being introduced, forget it.

  39. No more 16-bit DOS code... again? by ksp · · Score: 5, Funny

    [Bil Gates] stated, "It's the end of the MS-DOS era," referring to the exorcism of 16-bit code from the Windows code base.

    What, again??

    --
    What is the sound of one hand clapping?
    cat /dev/null > /dev/audio
    1. Re:No more 16-bit DOS code... again? by zerocool^ · · Score: 3, Funny
      windows 95:


      A 32-bit extention to
      a 16-bit graphical interface running on
      an 8-bit command line coded for
      a 4-bit microprocessor by
      a 2-bit company.

      ~z
      --
      sig?
    2. Re:No more 16-bit DOS code... again? by Chris+Mattern · · Score: 3, Informative

      > windows 95:
      >
      >
      > A 32-bit extention to
      > a 16-bit graphical interface running on
      > an 8-bit command line coded for
      > a 4-bit microprocessor by
      > a 2-bit company.

      That can't stand one bit of competition!

      Chris Mattern

    3. Re:No more 16-bit DOS code... again? by AnalogDiehard · · Score: 1
      [Bill Gates] stated, "It's the end of the MS-DOS era," referring to the exorcism of 16-bit code from the Windows code base.

      What, you mean they took away my favorite Windows repair tool "format c:"?

      --
      Eternity: will that be smoking, or non-smoking? I Corinthians 6:9-10
    4. Re:No more 16-bit DOS code... again? by sid+crimson · · Score: 1

      windows 95:

      A 32-bit extention to
      a 16-bit graphical interface running on
      an 8-bit command line coded for
      a 4-bit microprocessor by
      a 2-bit company.


      that doesn't want 1-bit of competition...

      -sid
    5. Re:No more 16-bit DOS code... again? by Anonymous Coward · · Score: 0

      Hey, I've got an idea, why don't you start quoting Monty Python, too? That shit's real funny.

    6. Re:No more 16-bit DOS code... again? by rabidcow · · Score: 1

      Maybe I'm just too young, but what 8-bit command line? (DOS was 16-bit) and what 4-bit processor? (how many of those did they even *make*?)

      I mean it's cute and all, but it's rather stupid if it's not even true. (and it's getting just a tad old anyway)

    7. Re:No more 16-bit DOS code... again? by lars_stefan_axelsson · · Score: 1
      Intel 4004, arguably the first microprocessor. With two reassamblations, code for the 4004 can be run on the P4. Some say that's too much backwards compatibility, and they're right.

      And the 8-bit command line is most likely a reference to the humble CP/M beginnings of MS-DOS, that was coded to run on 8-bit microprocessors, such as the z80.

      --
      Stefan Axelsson
    8. Re:No more 16-bit DOS code... again? by rabidcow · · Score: 1

      That's what I thought. So in other words, it's clever (but needs to RIP), but only about half of it's accurate at all.

      With two reassamblations, code for the 4004 can be run on the P4.

      Uh... So how do you assemble a piece of code more than once? You assemble it and get machine code, then...? Granted, we've probably got some degree of binary compatibility with the 8085, which is pretty sad, but you can't do that down to 4-bit, I mean you can't even operate on 4-bit numbers.

    9. Re:No more 16-bit DOS code... again? by lars_stefan_axelsson · · Score: 1
      Uh... So how do you assemble a piece of code more than once?

      Should have been "Assambling the code three times (with different assemblers of course) you can run the same code on all Intel chips from the 4004 through to the p4." Now, come to think of it, the start of the line may have been the 8008, the 8-bit variant of the 4004, my memory is unclear as to whether the 4004 will actually work. The 4004 was much more limited than the 8008, that's for certain.

      As for the "operate on 4-bit numbers" the 4004 actually had 8-bit instructions, and either 16 4-bit, or 8 8-bit registers, it wasn't a pure 4-bit machine, much as the 8-bit processors weren't pure 8-bit machines, most handled 16-bit quantities natively, even though they neede two trips over the bus to get them.

      So, the 4004, and 8008 was one line, the 8080 was the next, and the 8088/8086 was the third. All backwards compatible on the assembly instruction level, though binary compatibility was sacrificed.

      My original post was not a model of clarity, that much is certain.

      --
      Stefan Axelsson
    10. Re:No more 16-bit DOS code... again? by Anonymous Coward · · Score: 0

      Ah, ok. Thanks.

  40. Goodbye by Anonymous Coward · · Score: 0

    I noticed on a vidclip on techtv that Mr. Gates said good by to DOS by typing C:>goodbye at a dos prompt, or so it looked.... Any how if dos is gone, where did he get the dos prompt to type it?

  41. DOS software was what made me hate Microsoft by Dr.+Manhattan · · Score: 1
    Specifically, Microsoft SmartDrive (their drive-cacheing software for DOS) and MS Flight Simulator 5.0. They aren't compatible. Tried to install FS5, bombed out during the install. I looked things over, and decided to deltree D:\FS5 and try again.

    It took much longer than I thought it should have. I did a quick 'dir' and... yikes! Everything on D: was gone! I lost a bunch of stuff (fortunately nothing utterly irreplaceable). I reinstalled FS5, and sure enough, it bombed out again, and there was a crosslink from inside D:\FS5 to D:\.

    I did some digging, and found out that if I disabled SmartDrive, it'd work fine. That's right, Microsoft Flight Simulator 5 is incompatible with... Microsoft SmartDrive.

    At that point I started using Linux in earnest.

    --
    PHEM - party like it's 1997-2003!
  42. We can fix that... by Anonymous Coward · · Score: 0

    Open Souce command prompt for Windows XP, anyone?

    1. Re:We can fix that... by Anonymous Coward · · Score: 0

      I use Cygwin on Windows XP. I just love how it shuts up the anti-Microsoft zealots as I compile and run such useful programs as lynx and moon-buggy.

  43. Goodbye old friend by Hasie · · Score: 1

    Moving to Windows was initially fantastic, but I very quickly grew to miss the old command-line interface of DOS. Then I found Linux/Unix and I haven't looked back! I must be the only person in the known universe to have started using Linux/Unix because of DOS!

    1. Re:Goodbye old friend by ankit · · Score: 1

      I must be the only person in the known universe to have started using Linux/Unix because of DOS!

      No, sir... you are not the only one...
      The main reason why I turned to linux from windows 95 (in about a week!) was because I found Linux to be more powerful and more 'dos like'.

      Who can use the crappy windows explorer for anything more than renaming a file.

      --
      Don't Panic
    2. Re:Goodbye old friend by Anonymous Coward · · Score: 0

      no man I started on linux too because of dos

  44. maybe some Linux converts coming by danny · · Score: 1
    I have some users who went with DOS when it was that or MacOS, largely because they weren't willing to give up their command lines. I think some of those may stick with older versions of Windows as long as they can, but others may be ripe for conversion to GNU/Unix/Linux.

    Danny.

    --
    I have written over 900 book reviews
    1. Re:maybe some Linux converts coming by swingkid · · Score: 1

      DOS may be gone, but CMD.exe lives on. For what it's worth, it's a much, much better command processor than command.com ever was.

  45. MS-DOS is dead; long live AI-OS by Mentifex · · Score: 1, Offtopic

    The Nietzschean purpose of MS-DOS was to survive long enough (1981-2001) that the faint rumblings and beginnings of an artificial intelligence operating system (AI-OS) could emerge from the decaying corpus delicti where MS-DOS had gone before.

    Choose your battles, is an ancient dictum. Back in 1978 at a meeting of the Northwest Computer Society here in Seattle, a call went out from the podium for anyone who would be willing to work on the newsletter of the society. Very truly yours Mentifex here shrank back, unwilling to work on anything but a Theory of Mind for AI. To the relief of all us AI and non-AI slackers, a certain historically immortal Tim Patterson of Seattle Computer Products spoke up and volunteered to work on the computer society newsletter. Such a quiet, unassuming fellow -- and yet Tim Patterson turned Bill G*tes into a multi-multi-billionaire, because Tim Patterson was the author of Quick-and-dirty-DOS, or QDOS, which Microsoft bought from Seattle Computer Products for fifty thousand dollars ($50K) and foisted upon the world as MS-DOS. My only real gripe about MS-DOS was the weirdness of Paul Allen in declaring that henceforth all users should use a backslash (e.g., C:\mind.html) path-separator instead of the Un*x forwards-slash separator, as in http://mind.sourceforge.net/alife.html -- the way G*d intended computers to work.

    Now, are there any ankle-biters who would like to follow up here with posts about how the slowly emerging AI OS is somehow off-topic to the passing away of MS-DOS? If so, fire cowardly away.

    1. Re:MS-DOS is dead; long live AI-OS by david+duncan+scott · · Score: 3, Insightful
      My only real gripe about MS-DOS was the weirdness of Paul Allen in declaring that henceforth all users should use a backslash (e.g., C:\mind.html) path-separator instead of the Un*x forwards-slash separator, as in http://mind.sourceforge.net/alife.html -- the way G*d intended computers to work.

      You must not have been a CP/M user -- that's Kildall's fault, not Allen's. CP/M used the "/" for options, as in "program/opt1/opt2", and DOS was first and foremost a CP/M workalike.
      --

      This next song is very sad. Please clap along. -- Robin Zander

    2. Re:MS-DOS is dead; long live AI-OS by hayden · · Score: 1

      Another explaination I've heard is that the original DOS didn't have directories at all -> no need for a directory specifier. By the time they were added programs had been written using the / as an option specifier (probably because of it's close relationship to CP/M) so they used \ to specify directories instead.

      --
      Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    3. Re:MS-DOS is dead; long live AI-OS by david+duncan+scott · · Score: 2
      Well, that's true as well -- nested directories were bolted on in 3 (IIRC). But the "/" for options was there from the getgo.

      Thing was, CP/M was the business OS. A lot of places used Apples, it was true, and the Canadians fell in love with Commodores at work, but most offices ran CP/M, so the idea was to make the transition as easy as possible, both for users and programmers -- most of the 8080 instruction set mapped almost directly onto the 8086 set, and the OS API was almost identical. This is where com files came from, too -- simple 64K (or less) memory images of a program, just like a CP/M com file.

      For some years all my DOS machines had a batch file so that I could still PIP.

      --

      This next song is very sad. Please clap along. -- Robin Zander

  46. Dos gone?? by rob_ert · · Score: 0

    Hmm Bill opens a dos box types in exit and dos is gone. I went to a friend of mine and did a 'start-> run -> cmd 'on his XP..... hmmm looks like a dos box to me let's try 'dir'.... hmm looks like it works... 'edit somefile.txt'....hmmm works. Type exit and the dos box is gone.....
    What do they mean by dos is gone??....I have a dos box and bunch of working commands...

    1. Re:Dos gone?? by Anonymous Coward · · Score: 0

      You've got to understand that this is a reference for the Win 9x platform. XP is the convergence of the NT and 9x platforms. NT never had DOS, just a command line that looks an awful lot like it; the 9x platform still had/has DOS (no matter how much MS try to hide it).

      This the end of DOS becuase its the end of 9x. The (32-bit) command line lives on!

    2. Re:Dos gone?? by Anonymous Coward · · Score: 0

      You one smart guy

    3. Re:Dos gone?? by Anonymous Coward · · Score: 0

      yeah, beats the sh*t out of the normal slashdot rant

  47. er... dead? since when? by the+endless · · Score: 2, Informative

    In announcing MS-DOS's demise, Microsoft founder Bill Gates typed "exit" at the MS-DOS command line during the launch of Windows XP.

    A prize to the person who provides an explanation for how Billy Boy typed "exit" at a command line that doesn't exist?

    I haven't had a chance to get at an WinXP machine to check, but the command line must still be there. There's too many reasons that it's necessary, e.g. SQL Server has loads of command-line utilities. Just because MS have taken it off the start menu doesn't mean that it can't be accessed by someone with half a brain.

    1. Re:er... dead? since when? by Anonymous Coward · · Score: 0

      Excuse my ignorance, as a non-windows user, but how do you use an OS without a shell prompt?

    2. Re:er... dead? since when? by Anonymous Coward · · Score: 0

      You're a moron. Just because there's no DOS doesn't mean there's no command line.

      Go back to your tiny toy OS, loser, and leave the proper computing to the adults. When you've grown up enough to undertand simple facts about Windows, the world's most user friendly and most used OS, then maybe you can talk. Till then: shut your ignorant yap.

    3. Re:er... dead? since when? by the+endless · · Score: 1

      Just because there's no DOS doesn't mean there's no command line.

      Perhaps. But if what is being discussed is MS-DOS itself, then this pronouncement of death has come pretty late. In fact, the corpse was rotting and crawling with maggots by the time this announcement was made.

    4. Re:er... dead? since when? by drwiii · · Score: 2, Informative
      Start > All Programs > Accessories > Command Prompt

      Microsoft Windows XP [Version 5.1.2600]
      (C) Copyright 1985-2001 Microsoft Corp.

      C:\>

    5. Re:er... dead? since when? by donutello · · Score: 2

      DOS is an operating system. A command line is a utility or program that runs on TOP of an operating system. DOS just happened to come with the command line which was the only UI to the OS.

      Just like Linux is not the bash shell, DOS is not the command line.

      The command line is also available on XP as an interface to the OS.

      What's the prize and where can I claim it?

      --
      Mmmm.. Donuts
    6. Re:er... dead? since when? by Spy+Hunter · · Score: 2

      OK. Windows XP has a command line, it is in the start menu. It is much better than the old one, it comes with tab completion (enabled by default, even). However, it is not DOS. DOS is dead. Gone. There still seems to be some sort of emulation there because I can run some old DOS games reasonably well, but it is just emulation.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
  48. DOS was good by ankit · · Score: 5, Insightful

    People keep complaining about DOS all the time... about autoexec.bat, config.sys, and what not. IMHO, DOS was and _is_ one of the best and cleanest operating systems to learn about the intel architecture. Where else can you issue BIOS interrupts, and play around with system memory? Linux doesnt let me do that unless I compile a kernel module, and what not.
    Trey, DOS wasnt the best desktop/server/handheld Operating System, but it surely was a great learning experience for all who used and programmed for it.

    I still use TurboC on DOS when I need to try out some small program, and dont want to wait for linux to load.

    Another point, I dont think you can ever have a successful operating system without any command prompt. Copying and moving files can never be as easy using a dumb GUI file manager.

    --
    Don't Panic
    1. Re:DOS was good by trash+eighty · · Score: 1

      well i dunno about the last point, MacOS did fine without a CLI until v10

    2. Re:DOS was good by ankit · · Score: 1

      well i dunno about the last point, MacOS did fine without a CLI until v10

      You answered your own question!!
      I strongly feel that an OS without a cli is limited in terms of functionality. It may not be so for those who rely solely on GUIs, but I am so much used to a cli, first DOS, and then Linux... I cant live without it!

      --
      Don't Panic
    3. Re:DOS was good by WolfWithoutAClause · · Score: 2

      >DOS wasnt the best desktop/server/handheld Operating System, but it surely was a great
      >learning experience for all who used and programmed for it.

      It was certainly an education!

      - look what dros we can actually sell!
      - Oh look you're computer has crashed again!
      - Clashes between TSR programs anyone?
      - 640K limits anyone?
      - horrible command line interface
      - needed half a dozen separate programs to make it even faintly usable- and not really even then.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    4. Re:DOS was good by trash+eighty · · Score: 1

      the reason MacOS has a CLI now is because of what they put in the blender to produce the system (which is totally different than v9!) rather than any pressing need for a CLI!

      anyway i am not a GUI zealot, i love opening a command window on my OS/2 boxen and playing around

    5. Re:DOS was good by Anonymous Coward · · Score: 0

      DOS -never- caused my computer to crash, and I used it for years and years.. I think one time I froze it up when I made some program with an endless loop in Pascal, but that's it! The greatest advantage of DOS was its rock-solid stability -- probably why many banks and such are still using it.

    6. Re:DOS was good by mr3038 · · Score: 1
      DOS -never- caused my computer to crash, and I used it for years and years..

      I agree. There's practically no way to make DOS crash. Perhaps if you have broken hardware... DOS is practically a boot strapper go get you going. Many people still use it to start linux with loadlin. This allows simple command line with a file system before booting the system. GRUB is a fix for this hack but MS keeps overwriting it without asking when you reinstall Windows again.

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    7. Re:DOS was good by gorilla · · Score: 2

      The 640k limit was not a DOS issue, it could handle as much memory as the system would allocate. It was an IBM PC design issue. The 8088 requires the bottom of memory to be RAM, and the top of memory to be the bootstrap, and therefore almost certainly ROM. When the designers of the PC decided to include memory mapped devices, they reserved the top 384K of memory for the ROM and other memory mapped devices, including the CGI screen at 640k and the mono screen at 768k. At that time, 32k was typical memory installed, and 64k would be a large amount. As the memory usage increased, the location of the color screen butted against the top of the RAM, and the 640k 'limit' appeared. Even on IBM PC clones, with a mono adaptor it was possible to get memory all the way up to the 768k point, and DOS would happily run with that.

    8. Re:DOS was good by Cro+Magnon · · Score: 1

      DOS was an excellent OS for the 8088. It was limited to 640K, but the chip itself couldn't address much more. It couldn't multitask, but neither could the chip. The problem is that M$ didn't update it for later machines. That meant that your new 2Gz Pentium 4 was just an ultra-fast 8088 under DOS. Windows was needed to slow it down to 8088 speeds!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    9. Re:DOS was good by WolfWithoutAClause · · Score: 2

      >There's practically no way to make DOS crash.

      No, no. DOS was trivial to crash.

      DOS itself didn't cause the crash, but the programs that run under it crash all the time, and usually/often take DOS with it.

      >Perhaps if you have broken hardware...

      No just a broken OS.

      Proper operating systems rarely crash when an application crashes. Do I have to point this out on a website devoted to Linux?

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    10. Re:DOS was good by WolfWithoutAClause · · Score: 2

      You should try writing C under DOS sometime. Just running compiled programs from DOS. Uggggh.

      It's certainly possible to get reliability under DOS, DOS itself is reliable, but applications that run under DOS mostly aren't and can take out the OS in a breath. DOS lacked functionality to the point of being broken; literally and metaphorically.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    11. Re:DOS was good by CaseyB · · Score: 2

      There's practically no way to make DOS crash.

      c:>type x > x.exe
      c:>x

      *boom*

    12. Re:DOS was good by Anonymous Coward · · Score: 0
      fucking stop with the "boxen" and "OSen" ...

      fucking annoying and idiotic wordplay!

    13. Re:DOS was good by mr3038 · · Score: 1
      No, no. DOS was trivial to crash. DOS itself didn't cause the crash, but the programs that run under it crash all the time, and usually/often take DOS with it. (emphasis added)

      As I said you practically couldn't crash DOS. Running an app that crashes and takes DOS with it was outside the spec. DOS wasn't supposed to survive something like that. "Heck, Linux cannot even BOOT on C64! Therefore Linux must suck!" - something wrong here? When linux crashes because of broken driver made by nVidia is it Linux that's broken? Or is it the software you happened to use?

      --
      _________________________
      Spelling and grammar mistakes left as an exercise for the reader.
    14. Re:DOS was good by WolfWithoutAClause · · Score: 2

      >As I said you practically couldn't crash DOS.

      Yes, you said that. You were wrong. Try using English. Your car has been crashed whether or not you caused it. DOS has crashed whether or not the bug lay in the OS.

      I repeatedly crashed it without any trouble at all, in every meaningful sense of the word. The fact that my PC was not communicating to the outside world or had blue screen of death or was rebooting is considered a good sign of a crashed OS. In fact DOS crashed often enough that I was able to tell a crashed OS ever more easily.

      >Running an app that crashes and takes DOS with it was outside the spec.

      Yep. DOS was broken already in the specification.

      >When linux crashes because of broken driver made by nVidia is it Linux that's broken?

      Yes. Device drivers are basically part of the OS. When you load a buggy device driver into Linux, you break Linux.

      But in DOS, even the application is part of the OS. That ain't good.

      >"Heck, Linux cannot even BOOT on C64! Therefore Linux must suck!"

      Yes, Linux sucks on a C64. Your point?

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    15. Re:DOS was good by ReelOddeeo · · Score: 2

      DOS was and _is_ one of the best and cleanest operating systems to learn about the intel architecture. Where else can you issue BIOS interrupts, and play around with system memory?

      An excellent point.

      Could it be that a whole new generation will never learn the deep secrets? Have the barriers to low level experimentation become so high as to keep many people out?

      Well, maybe not. On second thought. If you have a seperate "labrat" machine to experiment on, you can play with boot loaders, primitive OSes, OS implementation, BIOS functions, etc. But your point is still good. In the past, you didn't necessarily need a seperate "labrat" computer. But that is balanced by the fact that seperate "labrat" machines can now be had for very cheap. Probably under $100-$200.


      Another point, I dont think you can ever have a successful operating system without any command prompt. Copying and moving files can never be as easy using a dumb GUI file manager.

      I agree with your first sentence. But I can't agree with your second about easy. Especially on your choice of copy/move files. There are other areas of gui's which are much easier to complain about. I wouldn't want to take away anyone's non-gui tools, but don't take away my gui's. I grew up with them and have used them for 18 years now. But I couldn't do without CLI either. I just don't see it as an either/or choice. GUIs are way more productive for some things, but not do to:

      rm *.o

      --

      Those who would give up liberty in exchange for security and DRM should switch to Microsoft Palladium!
    16. Re:DOS was good by ReelOddeeo · · Score: 2

      MacOS did fine without a CLI until v10

      Yeah, but having MPW sure gave you a lot of power. The ability to

      rm *.o

      Powerful scripting. Tools like sed and awk. File globbing. etc, etc.

      While I would agree that these things are not what typical Mac users would do, I would point out that MPW didn't ship with the system either. You had to add it.

      And yes, I know about third party (mac) extensions to let you select all files matching a wildcard pattern. Similar features now exist in KDE.

      --

      Those who would give up liberty in exchange for security and DRM should switch to Microsoft Palladium!
    17. Re:DOS was good by Guy+Harris · · Score: 2
      Another point, I dont think you can ever have a successful operating system without any command prompt. Copying and moving files can never be as easy using a dumb GUI file manager.

      Yes, I sometimes use the command prompt window on my desktop (well, deskside, really) Windows box at work, and on the Windows partition on my home machine.

      Of course, they're both running Windows NT - NT 4.0 on the Windows partition at home, and NT 5.0, err, umm, Windows 2000 on the machine at work.

      The command prompt I use at home is, err, umm, a UNIX command prompt, with Cygwin; I often use it rather than the file manager. I do so less often at work, although I'm not sure if that's because I use the machine at home for software development while I mainly use the machine at work as an X terminal (for the Solaris, etc. boxes on which I do my real work) and platform for Web browsing, and thus don't often copy/move/etc. files on the work machine, or because the Windows NT command prompt isn't as nice as the Bash prompt at home.

      Then again, when I'm running KDE on the FreeBSD partition of my machine at home, I use the GUI file manager rather than the command line to read the various networking standards documents I have stored there, as I find it more convenient than switching to an xterm (or popping up a new xterm) and cding to the appropriate directory and firing up (Acrobat Reader, microEmacs, whatever).

      So, as far as I'm concerned, there's a place for command lines and for GUI file managers.

    18. Re:DOS was good by yesthatguy · · Score: 1

      but...but...640K ought to be enough for anyone!

      --
      Yes! That guy!
  49. Dumbass. by NineNine · · Score: 1, Flamebait

    That's not DOS, dumbass. That's the command line.

  50. Re:Why does Gates get the credit ? by adubey · · Score: 3, Insightful

    Please mod the parent down. It isn't insightful.

    Gates liscensed DOS from SCP. SCP based their product on CP/M, originally written by Gary Kildall.

    DOS was advanced by the standards of microcomputers of the day. CP/M's 16-bit version, CP/M-86 wasn't ready when MS-DOS 1.0 hit the market, and by the time CP/M-86 did ship, MS-DOS already hit version 2.0. Version 2 had neat-o features like subdirectories and a Unix-like C API that pushed it ahead of CP/M. CP/M eventually did surpass DOS, but it was called DR-DOS by that time.

    Of course, DOS was well behind most all versions of Unix, including Microsoft's Xenix. Peter Norton once wrote that Xenix might have been the "operating system" of the future. Unfortunately, Mitch Kapor wrote Lotus 1-2-3 to run under MS-DOS rather than Xenix. In those days, people bought PCs to run Lotus. The operating system was just the black screen with gibberish text you saw before Lotus booted up.

  51. Re:Why does Gates get the credit ? by DenniRuz · · Score: 1

    "I wonder if the geeks that are so rabidly against Microsoft would be so vociferous if Unix was running on over 95% of the world's PCs ?"

    I think yes- There's bad flavors or Unix (imagine 95% of the world running AIX!- Ahhhhh!).

    But seriously, an M$ unix as a base would have made a huge difference in the world today- Imagine a well written 32-bit OS, readily available, widely used, STABLE!, with none of the memory restrictions of the DOS world and Hundreds of easily installed applications. The computing world would be a very different place today, IMHO.

  52. Not only does XP have the command prompt by ch-chuck · · Score: 5, Informative

    it still has 'edlin' -- whoohoo!

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
    1. Re:Not only does XP have the command prompt by shani · · Score: 1

      Thank goodness! I remember explaining my edlin mastery to my colleges (about 5 years ago), claiming that "DOS will always have edlin". The bastards then typed "edlin" and it wasn't in the install (Windows 95?).

    2. Re:Not only does XP have the command prompt by Ed+Avis · · Score: 2

      I started using MS-DOS with version 3.3, where edlin was the only editor available. But it was so yucky I never learned to use it, preferring 'copy con filename' to create a file and 'copy con +filename' to append. I think I used the editor built into XTree for other stuff.

      Then last year I wanted an automated way to reboot some NT machines into Linux, by changing NT's boot menu. This is a text file boot.ini which you edit. How can this be done automatically?

      Well you can guess the answer: good old edlin is still included with NT to this day (though I expect it's a 32-bit rewrite rather than the DOS assembler version). So I dug out an IBM manual for MS-DOS 2.0 and worked out how to change the boot.ini file using the One True Editor. For extra perversity, I wasn't running it myself but rather writing a Perl script which uses the Expect module to telnet to an NT box, run edlin and then reboot it.

      So I never needed to learn edlin for MS-DOS, but it still comes in handy for Windows systems two decades later...

      --
      -- Ed Avis ed@membled.com
    3. Re:Not only does XP have the command prompt by ch-chuck · · Score: 2, Interesting

      typed "edlin" and it wasn't in the install (Windows 95?).

      That interesting - just did a quick check and found that Win95a, Win98SE and ME DON'T have edlin, while WinNT, 2K and XP DO have edlin. I guess they expected the dos/home line to not need it, but the professional line did need it to support old edlin scripts?

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    4. Re:Not only does XP have the command prompt by ch-chuck · · Score: 1

      Yeah, we just decided the Win9x/ME home systems don't have edlin by default, while the professional NT/2K/XP line does.

      though I expect it's a 32-bit rewrite rather than the DOS assembler version

      Well if I type, in Linux, NT4 \system32\ mounted:

      [root@localhost system32]# file tlist.exe
      tlist.exe: MS Windows PE 32-bit Intel 80386 console executable

      and

      [root@localhost system32]# file edlin.exe
      edlin.exe: MS-DOS executable (EXE)

      Must have had better things to do ;)

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    5. Re:Not only does XP have the command prompt by Anonymous Coward · · Score: 0

      > typed "edlin" and it wasn't in the install (Windows 95?).

      That interesting - just did a quick check and found that Win95a, Win98SE and ME DON'T have edlin, while WinNT, 2K and XP DO have edlin. I guess they expected the dos/home line to not need it, but the professional line did need it to support old edlin scripts?


      Not only did Win 9x/ME not have it, i just realised not even MSDOS 6.2x had it. Strange that it should be resurrected ...

      I like my boot in msdos mode option and for that reason, didnt get WinME. I still like to run my old dos games .... :-)

    6. Re:Not only does XP have the command prompt by Guppy06 · · Score: 2

      Even worse, after all this time working on making a new GUI interface, it still has Ye Ole Program Manager.

      That, and Notepad STILL can't open files bigger than about 640 KB.

    7. Re:Not only does XP have the command prompt by Anonymous Coward · · Score: 0

      Notepad on NT is not 32KB-limited like it is on Win9x... (having opened more than a few multi-MB text files with it)

    8. Re:Not only does XP have the command prompt by Anonymous Coward · · Score: 0

      It may not be hand-tuned assembler, but it's not 32-bit. Even the smallest Visual Studio 32-bit application I can make is still around 40 K. Edlin.exe on my Win2k install is 12 K. There is no version block and when I check its properties Windows is treating it like an old 16-bit program (showing settings for virtual memory and the like). I'm willing to bet this version was updated around ten years ago, and they just keep recompiling the code (or just re-stamping the file) whenever they push it into a new release.

    9. Re:Not only does XP have the command prompt by SilentChris · · Score: 2
      *wonders how this guy got a +1 bonus*

      "Even worse, after all this time working on making a new GUI interface, it still has Ye Ole Program Manager."

      It's been kept there for backward compatibility, noone uses it, and if you like to use it you have the option to. Linux is *loaded* with programs like this.



      "That, and Notepad STILL can't open files bigger than about 640 KB."

      Um, I don't know what version of notepad.exe you run, but mine handles several megabyte files just fine. Uh, get with the times?

    10. Re:Not only does XP have the command prompt by Anonymous Coward · · Score: 0

      XP also has VI believe it or not lol.

    11. Re:Not only does XP have the command prompt by ncc74656 · · Score: 2
      That, and Notepad STILL can't open files bigger than about 640 KB."
      Um, I don't know what version of notepad.exe you run, but mine handles several megabyte files just fine. Uh, get with the times?
      Besides, the limit for Notepad used to be 64K, not 640K.

      Notepad also does replace now, where before it only had find, and it handles Unicode as well as ASCII.

      --
      20 January 2017: the End of an Error.
    12. Re:Not only does XP have the command prompt by m_pll · · Score: 1

      Actually XP/Win.NET has many new command line tools that make my life as a developer somewhat easier. Off the top of my head:

      - usable text-mode debugger (ntsd)
      - taskkill and tasklist (finally!)
      - command line interface to perfmon (logman, relog)
      - command line interface to WMI (wmic)

    13. Re:Not only does XP have the command prompt by banuaba · · Score: 2

      sadly enough, assloads of people use 'ye olde program manager'. My old man uses it because he doesn't like left click menus (go figure that one). My boss uses it because he's a curmodgeonly prick. And I know several other people who go out of thier way to use it. Who knows why....

      --


      Brant

      Argle. Bargle.
    14. Re:Not only does XP have the command prompt by NutscrapeSucks · · Score: 1

      The "DOS" environment in NT was forked off of OS/2 which was forked off of DOS 5.0. That's why you get strange things like edlin pre-installed. (Edlin was removed from DOS 6 for disk space reasons, I think -- it's still downloadable somewhere on ftp.microsoft.com last time I checked.)

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    15. Re:Not only does XP have the command prompt by Dahan · · Score: 1
      *wonders how this guy got a +1 bonus*

      Slashdot really needs a -1, WRONG! moderation :)

      Anyways, Windows 2000 still has good old File Manager (winfile.exe) for the people who don't like Explorer. I seem to recall that XP betas had it too, but it was finally yanked for some reason. Heh, I just tried running File Manager on a Win2K machine, and notice that WinZip 7.0 still knows how to integrate with it--there's a WinZip menu, and a couple of toolbar buttons.

  53. Performance - lack of? Expire! by saqmaster · · Score: 1

    Surely any that has _tried_ to use DOS/16-Bit applications under Windows NT and Windows 2000 would be grateful that DOS is being phazed out with XP..

    DOS Virtual Machine? I'd rather not sit there burning up my CPU at 100% load just to run edit.com.

    Hurrah for the demise of the Windows command line :)

    C:\>pkg_add bash2.02.tar.gz
    'pkg_add' is not recognized as an internal or external command,
    operable program or batch file.

    --
    "Never let the truth get in the way of a good story..."
  54. Sidebar... by superflex · · Score: 1
    In related news, thousands of help desk workers were seen screaming, crying and worse in reaction to the announcement.

    Sniffed one worker,"Oh God!!! Why!? How the hell am I supposed to fix anything now? Corrupted registries can't be fixed with ren user.da0 user.dat. I can't del or deltree. And with Microsoft's registration bullshit, the hundreds of Windows reinstalls I'll be doing are going to take even longer! Damn you, Gates! DAMN YOU!!!"

    She then proceeded to wrap her arms around her knees, and rock back and forth, muttering "Where are my bookmarks? It won't print! I don't remember where I saved it! I opened this attachment called iloveyou.vbs, is that ok?" over and over again.

    --
    sigs are for suckers
    1. Re:Sidebar... by Anonymous Coward · · Score: 0

      > the hundreds of Windows reinstalls I'll be >doing are going to take even longer!
      Nope... I just did it realy quick.
      gunix.mine.nu/serious.html for details...
      and it really works!!!

  55. And now Bill can say... by CProgrammer98 · · Score: 0, Flamebait

    All your command lines are belong to us!!

    --
    And the people shall be oppressed, every one by another, and every one by his neighbour Isaiah 3:5
  56. The DOS prompt is still there. by BenHmm · · Score: 2

    It's a publicity stunt, but it's also slightly wrong:
    at least on XP RC2, you can easily get to the command line.

    I use it for Perl stuff sometimes, and ping and things. It might not be full DOS (oh, the loss of that extreme power will be sorely felt), but it is a command line.

  57. Byte: A Eulogy by weave · · Score: 2

    Does Byte still exist as a print mag? I don't remember seeing it in any bookstores recently. Last I remember, it was a pretty thin excuse for a magazine where once it was thick with articles and advertising. :-(

    1. Re:Byte: A Eulogy by wiredog · · Score: 2

      It went to online only a couple of years ago, but Jerry Pournelle reports that it's being resurrected. Even in its last years it had great stuff in it. Go to your library and look at the April 98 issue, "Why Pc's crash, and mainframes don't". They could re-publish it today, just changing the dates, and it would be just as true.

    2. Re:Byte: A Eulogy by weave · · Score: 1

      Thx for the info. btw, when I said "thin excuse for a mag" I meant the size, not the content!

  58. I've heard it before by ch-chuck · · Score: 2

    at a Msft sales, uh, 'technical presentation' here in '96. The showman said, and I quote, "Lets have a moment of silence for DOS... " altho what he was refering to was dropping support for DOS as a seperate product.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  59. But the memory lingers on... by MeerCat · · Score: 1

    DOS itself may be dead, but XP still has a command line prompt (cmd.exe) or, more accurately, the idea of Console-Mode executable. Unfortunately the 32-bit prompt still acts brain-dead to emulate the COMMAND.COM behaviour, so scripting is painful, there are still hacks to "magic" file names (CON, PRN etc.) and, at some levels, the "ohmigod I can't believe that crashes the machine" mentality survives - the following code as a console app will crash an NT, Win2K or XP machine - no BSOD, just plain gone...

    #include

    main(void)
    {
    printf("\t\b\b");
    return 0;
    }

    T

    --
    I spent a lot of money on booze, birds and fast cars. The rest I just squandered. - George Best
    1. Re:But the memory lingers on... by Anonymous Coward · · Score: 0

      Bullshit, Win 2000 here with service pack 2 and this "app" of yours works flawlessly.

    2. Re:But the memory lingers on... by MeerCat · · Score: 1

      Well Win2K with SP3 here, and compiled as a console app with VC++ and it dies a brutish death - but at least I also quote NT BugTraq as a witness (which also quotes that it fails on other platforms)....

      T

      --
      I spent a lot of money on booze, birds and fast cars. The rest I just squandered. - George Best
    3. Re:But the memory lingers on... by Anonymous Coward · · Score: 0

      Win2K SP2, compiled as console app, no issue. Damn Microsoft can't even crash respectfully. Thought I had ofund a new "feature"

  60. Sad to see DOS go? by Anonymous Coward · · Score: 0

    Well, DOS may well be gone, but we've still got DDoS to deal with...

  61. Re:Why does Gates get the credit ? by Anton+Anatopopov · · Score: 1, Troll
    (imagine 95% of the world running AIX!- Ahhhhh!).

    Hell or even worse - HP-UX 9...

    You have a valid point, but it is sad, isn't it to realise just how many human lives have been wasted by Microsofts bug-ridden software.

    Although Microsoft have not actually committed genocide, they must have wasted the equivalent of a few thousand lives if you count all the wasted hours spend looking at BSODs and rebooting...

  62. Farewell by crystal+dragon · · Score: 1

    Alas poor DOS we gnu ye well...

    1. Re:Farewell by Anonymous Coward · · Score: 0

      Ummm....there was no real joke to this...

    2. Re:Farewell by Anonymous Coward · · Score: 0

      Illiterate...

  63. Does Micrsoft still license DOS? by weave · · Score: 5, Interesting
    What is on the floppy when I get a BIOS driver update disk from Dell or other manufacturers? Oh, it boots DOS. Golly. Will Microsoft refuse to license bootable DOS floppies now? Are they now free? Do they have an alternative solution that boots some minimal OS to do firmware upgrades or other needed tasks?

    Somehow I don't think DOS is as dead as they make it out.

    1. Re:Does Micrsoft still license DOS? by ch-chuck · · Score: 1

      Do they have an alternative solution that boots some minimal OS to do firmware upgrades or other needed tasks?

      The utility disk that comes with new Maxtor hard disk drives boots up Caldera DOS to prep the disk, transfer all your system/data, etc. (at least it used to). You can change the autoexec.bat and get a command prompt instead of running the Maxtor stuff, but there's no useful utilities like 'format' etc.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    2. Re:Does Micrsoft still license DOS? by Anonymous Coward · · Score: 0

      ...PartitionMagic 4.0 did the same thing...

    3. Re:Does Micrsoft still license DOS? by uk_greg · · Score: 1

      Yes, Microsoft still licenses DOS, but only via what they call an Embedded Systems Contract. Essentially you have to be a Microsoft OEM to be able to get it.

      There are still many dedicated function devices that are sold with DOS - POS terminals AKA cash registers are one example.

    4. Re:Does Micrsoft still license DOS? by donutello · · Score: 2

      On my new DELL Latitude laptop, I don't need to create a floppy disk to update the BIOS anymore.

      Windows XP/the DELL bios are capable of doing BIOS upgrades without requiring a boot disk.

      --
      Mmmm.. Donuts
    5. Re:Does Micrsoft still license DOS? by kz45 · · Score: 0

      I had a adaptec scsi raid card, and it used a bootable CD, with a version of X-Windows with linux on it. It was kinda cool. You could create a floppy, with drivers on it for the OS of your choice.

  64. Windows for Pens? by carleton · · Score: 1

    At first, I thought this was a joke. But, a quick search to google later, I'm now even more confused. According to this article, Windows for Pens came out some time in 1992. To use the theories of the great Ravenous Bugblatter Beast of Traal, since I have no recollection of this whatsoever, it must have flopped pretty hard. Did anyone actually buy something that can run windows for pens? Can you run Linux on it?

    1. Re:Windows for Pens? by tb3 · · Score: 2

      I worked on a box that ran Windows for Pens. It was Win 3.11, IIRC, with some extra APIs grafted on. The machine itself was nothing special, a GRiD laptop with a pen attached. GRiD had been sold by that time, but I can't remember who bought it. The laptop was probably a 286, so you'd have to work to shoehorn Linux onto it.

      --

      www.lucernesys.comHorizon: Calendar-based personal finance

    2. Re:Windows for Pens? by simong · · Score: 1

      Windows for Pens came out in about mid-'92, not long after Win 3.1. If you believe Jerry Kaplan it was a fast hack by MS to muddy the waters for his Go pad computing product. It was essentially an API extension for Visual Basic and MS C and possibly drivers for some common pen products (can't remember) but I can't imagine that there was much development for it. It was combined into the Win32 API in Win95. It's probably still there.

    3. Re:Windows for Pens? by Anonymous Coward · · Score: 0

      If you intend to run Windows for Penis be sure to have plenty of Viagra available.

  65. Renaming in DOS by ankit · · Score: 1

    A joke that I remembered about DOS :

    Q) How do you rename a directory in DOS?
    A) Create a new directory with the name you want, copy everything there, and then delete the old directory.
    Q) How do you change the color of the walls in your house?
    A) You make a new house, paint it in the new color, shift everything from the old to the new house, and destroy the old house.

    --
    Don't Panic
    1. Re:Renaming in DOS by madenosine · · Score: 1

      Actually, you use the "ren" command

    2. Re:Renaming in DOS by Anonymous Coward · · Score: 0

      'move' also works

    3. Re:Renaming in DOS by Anonymous Coward · · Score: 0

      Actually neither of you have apparently used real DOS since the original post was correct. In real DOS there is absolutely no way to rename a directory.

    4. Re:Renaming in DOS by RJR · · Score: 1

      DEBUG is an excellent tool for renaming directories in ms/pc-DOS. E5 W CHKDSK is still faster than DELTREE /y. Granted it is a tad more difficult on a mega-gig hd, but that's what hex editors are for. Bob

  66. I guess we will never know... by cobyrne · · Score: 4, Funny

    I guess this means we will now never know the correct answer to -

    Error reading drive A:
    Abort, Retry, Ignore?

    1. Re:I guess we will never know... by nitemayr · · Score: 1

      Yes we will(do), the answer is and always will be, 42.

      Seriously, the answer in my case was usually abort, as the usual reason for that one (beyond floppy failure) was that I'd removed said disk without thinking and had no reason to use it anymore.


      --
      Hello Kettle,
      You, my friend are as black as pitch.
      With love, Pot.
    2. Re:I guess we will never know... by The+42+Maniac · · Score: 1



      Oh man, the correct answer is already known for many years. Of couse it's 42.

    3. Re:I guess we will never know... by Anonymous Coward · · Score: 0

      We're still here so that's obviously not the answer.

    4. Re:I guess we will never know... by Ambient+Sheep · · Score: 1

      Who is General Failure and why is he reading my Drive A: ?

    5. Re:I guess we will never know... by Hollinger · · Score: 1

      A)bort, R)etry, I)nfluence with Hammer

  67. DOS Software by cr@ckwhore · · Score: 5, Funny

    Here's my reality... and I'm not kidding about this, but feel free to mod up to "funny".

    I work for a software company, maintaining 15 year old DOS Software. The company is owned by older people that can't move fast enough to be in this industry... but somehow, we're still managing to sell this software to unsuspecting people.

    We have 2 applications... both of which are touted as "high-end", mission critical apps. A typical installation could cost the client somewhere around $50,000 USD, sometimes more. Here's what they get:

    1. A nasty DOS app written in Qbasic, using a Btrieve database on a Novell Server, all running over our favorite protocol, IPX.

    Sounds good? Well, its my nightmare!!!

    When win2k was released, a lot of little things in our DOS app stopped working. Our company's president refused to believe that MS-DOS was anything less than cutting edge. Now that XP was released, and more things are broken, our company's president refuses to believe that microsoft would abandon DOS.

    Anyway, enough rambling about this. Its a sad fact that there are companies STILL working with DOS programs. Sad. Even worse, is that I'm typing here, rather than working on that Qbasic crap.

    c:\> del *.*

    --
    Skiers and Riders -- http://www.snowjournal.com
    1. Re:DOS Software by SubtleNuance · · Score: 2

      Friend, have a look here: http://filewatcher.org/sec/qb2c/int_year.html.

      Drop that QBasic into C, build it up on Linux, and welcome to the present.

    2. Re:DOS Software by Sloppy · · Score: 2

      Its a sad fact that there are companies STILL working with DOS programs.

      This very morning, I am updating a payroll program to handle the new W2 forms for reporting 2001 wages (yes, both the paper form has changed, and also SSA/IRS wants a new file format for electronic reporting). The program is written in Clipper, a DOS language. I see comments in these source files, that I wrote in the 1980s. And people are still paying for this.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    3. Re:DOS Software by jred · · Score: 1

      Hey, you must work here! Seriously, here they have the majority of the programmers supporting the old DOS product, and have a couple of guys trying to port it to winxx. They've only been working on the port for 3+ yrs, so I don't know what's taking so long...

      They do have a kick@55 salesman, though. Obviously they must, since he can still sell that old DOS version...

      --

      jred
      I'm not a mechanic but I play one in my garage...
    4. Re:DOS Software by Anonymous Coward · · Score: 0

      That reminds me of something amusing.
      My father is a doctor, and he had payed a respectable software developing company to write a patient database for him halfway the 80's. It cost a LOT of money, as you could guess. It also ran in DOS, which had some interesting consequences.

      All the integer variables in the program where 16 bits in length (and also signed, for some reason), and so the moment rolled around that my dad accumulated 32000-something patients, with the amusing effect that from one day to the next it became immpossible to add new patients.

      The company obviously wanted a lot more money to entirely rewrite the program, so my dad told them to fsck off and wrote an ms access 2.0 app in 3 days that has the basic functionality of what he wanted, and to this day his patient database still runs in access.

      Ah, the good old days of 16-bit operating systems...

    5. Re:DOS Software by Baba+Abhui · · Score: 1

      Here's my reality... I work for a software company, maintaining 15 year old DOS Software.

      We have 2 applications... A nasty DOS app written in Qbasic, using a Btrieve database on a Novell Server, all running over our favorite protocol, IPX.

      Sounds good? Well, its my nightmare!!!

      Its a sad fact that there are companies STILL working with DOS programs. Sad.


      Well, speaking from a deep well of ignorance (being unfamiliar with your product and it's history), it sounds to me like the problem isn't DOS, it's that you're working with a crufty old app that's been forcefully-evolved for a long time. I think any app (for almost any OS) that had been updated and added to for 15 years would get pretty... eccentric.

      I don't think there's anything sad about still maintaining a DOS app in and of itself. It's sad that management won't always approve the capital expenditure needed to refactor and improve old projects before adding more crap to them. I think DOS still has a place in some applications. While enthusiasts (like us) might be upset at buying a product only to discover that it's a DOS app, business people won't be, if it does the job, and does it well.

    6. Re:DOS Software by Sloppy · · Score: 1

      Well, I wouldn't say the problem you described has anything to do with 16-bit OSes, but rather, foolish app programmers using 16-bit datatypes in a situation where it can quite possibly (indeed, inevitably) overflow. Most language tools for MS-DOS, had support for wider datatypes (e.g. long ints in C compilers). Can't blame the OS itself for that one. (Not that I'm gonna start defending MS-DOS; other aspects of it have cost me a lot of pulled-out hair over the years.)

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    7. Re:DOS Software by Anonymous Coward · · Score: 0

      del *.* /y

    8. Re:DOS Software by onyxruby · · Score: 1

      Plato?

    9. Re:DOS Software by cr@ckwhore · · Score: 2

      Well, you've touched on part of it. Yes, part of our problem is that we've pushed along a 15 year old DOS app... but, DOS really *is* a problem for us.

      1. Dependency on legacy libraries.
      2. Legacy Btrieve database support, which is difficult to impliment on modern systems because the database vender doesn't support the legacy databases.
      3. DOS executible segment size limits have been reached, meaning our application is really too large for DOS. (800,000 lines of code in 500+ modules)
      4. Reliance on outdated ASM code for CPU idle calls, which causes 100% CPU usage on win2k systems.

      I agree that DOS isn't necessarily all of the problem. In fact, besides "DOS", there are applications in which a console interface is advantageous, specifically with heavy DATA apps.

      regards

      --
      Skiers and Riders -- http://www.snowjournal.com
    10. Re:DOS Software by cr@ckwhore · · Score: 1

      WOW! Clipper! I programmed in Clipper back when Summer '87 was released, and then on into the early 90's. I worked on several apps, including a payroll program used by a banks and a criminal justice database for law enforcement.

      There was a /. post a few months ago about the "clipper chip", and I made a sly "summer '87" remark, but I don't think anybody here understood it ;)

      --
      Skiers and Riders -- http://www.snowjournal.com
    11. Re:DOS Software by warrior389 · · Score: 1

      These guys are german, aren't they.

    12. Re:DOS Software by Anonymous Coward · · Score: 0

      Btrieve runs on Linux now? All right. I thought it was obsolete.

    13. Re:DOS Software by EchoMirage · · Score: 1

      cr@ckwhore,

      The really sad thing is I'm almost positive I know who your company is and who its primary customers are. If I'm correct, you develop Point-of-Sale systems to run on 386s and 486s, and one of your distributors is a tiny company called EMF. One of your customers is a small Christian bookstore. Am I right? If so e-mail me.

  68. fud is dead? by Anonymous Coward · · Score: 0
    Got IT. After 20 some years, felonious father william is trading his disk 'operating' system, for some kind of gottiesque softwar gangster payper liesense plan. That's progress?

    No matter, just in case fud is really dead, don't forget to enter our big web address giveaway. Includes a year's free hosting.

    How do you spell freedom?

    1. Re:fud is dead? by Anonymous Coward · · Score: 0

      How do you spell freedom?

      Fuck, you need to ask how to spell more than just "freedom"! Try kindergarten again perhaps.

  69. DOS Could have survived by cr@ckwhore · · Score: 3, Insightful

    MS-DOS could have survived, if back in the early 90's, Microsoft had wanted to continue developing it. They made it obsolete by choice... I'm sure they could have easily turned it into a multitasking, 32 bit, networked OS, and still could have put a GUI on top of that.

    It just wasn't in their best interested to do so.

    --
    Skiers and Riders -- http://www.snowjournal.com
    1. Re:DOS Could have survived by stevey · · Score: 2

      ... I'm sure they could have easily turned it into a multitasking, 32 bit, networked OS, and still could have put a GUI on top of that.

      Which would have turned it into Windows, surely?

    2. Re:DOS Could have survived by Anonymous Coward · · Score: 0

      They tried this with OS/2. OS/2 v1 only had the command shell, the GUI came out in v1.1. Since it sucked (and remained horrible in all versions including OS/2 Warp) I guess Microsoft decided that the GUI would be built into the OS the next time around with Windows NT. Windows 3.x and then 9x were too much of a kludge to seperate the GUI from the kernel code.

    3. Re:DOS Could have survived by moitz · · Score: 1

      Oh yeah...kinda like Unix w/ XWindows....

      moitz:
      C:\DOS>_
      C:\DOS>run_
      Run DOS run

      --
      Screw 'em...who cares what anyone thinks.
    4. Re:DOS Could have survived by Anonymous Coward · · Score: 0

      um HELLO

      Can anyone say Windows 95? Windows 98?
      Windows 98 SE? Windows Millennium Edition???

      Those ARE the "multitasking, 32 bit, networked OS" you are talking about.

      They are also the reason I switched to Mac OS.

      Everyone knows that.
      And that's why those systems have sucked.

      Because DOS was constructed for 640k of memory, etc. and it's ludicrous to try to run a modern computer with it.

      -dan

      PS. the command prompt isn't GONE in Windows XP!! It's even still in the Start menu! Start>All Programs>Accessories>Command Prompt

      OR
      [WIN-key] + R, then type CMD, enter. about 5 keystrokes puts you in DOS when you need it (such as to change a frikkin' file extension without showing all the extn's all the time!!!)

  70. Attendance ... by thos_ · · Score: 1

    I'm surprised General Fay-lure didnt attend the ceremony ....

    1. Re:Attendance ... by Anonymous Coward · · Score: 0

      Who the hell is this General Fay-lure and why is he trying to read my hard drive!?

  71. Re:Why does Gates get the credit ? by antijava · · Score: 1

    What's so bad about AIX? I much prefer it's disk space management scheme to things like Solaris.

    If your / partition is too small in Solaris...tough. Rebuild the box. In AIX, it's trivial to grow a filesystem. You can even do it live without users even being aware that it happened.

  72. Remembering DOS by Delph · · Score: 5, Insightful

    Even through I now solely use Linux I will miss DOS. It was my first operating system and my lifeline whenever the users on the network screwed up with their Window$ boxes.

    With DOS and Doom I learned syntaxsis, options and commands. It gave me the challenge and the boost necessary for me to head towards an IT career.

    So long DOS, you were Window$ last hope!

    --
    Writing: no longer done with the fountain pen, now done with an eraser.
    1. Re:Remembering DOS by stevey · · Score: 5, Insightful

      Even through I now solely use Linux I will miss DOS. It was my first operating system and my lifeline whenever the users on the network screwed up with their Window$ boxes.

      I often think its funny how a lot of people cite the use of the command line as being a factor in slowing its spread.

      Back in the "old days" everybody use DOS, and the command line ruled.

      Maybe my friends weren't typical - but I remember in Windows 3.1 days many of them would say "Oh, that'd be easier in DOS".

      Now with the GUI spread of Windows people are being taught to think of command line utilities as old fashioned - and less powerfull, which is clearly a mistake.

    2. Re:Remembering DOS by Dallan · · Score: 1

      Indeed. I think it says something that using Win98, I _still_ routinely call up a DOS prompt for basic file management (copy, move, delete, etc.), small text-editing, and myriad other little chores.

      Far easier to make a meanigful mis-click/drag/drop than it is to make a meanigful typo, and often easier to correct.

      Some things will always be easier/safer in a CLI, I think. Whichever CLI that happens to be.

      --
      Never attribute to malice that which can be adequately explained by stupidity.
    3. Re:Remembering DOS by Rentar · · Score: 3, Interesting

      I agree with what you most of what you say, but ....

      So long DOS, you were Window$ last hope!

      Don't confuse DOS with the command line. DOS itself was a horrible cludge. The command line (contained in command.com) was not much better, but much better for some tasks than the Windows GUI. Windows NT & 2000 left DOS out long before XP and they both still had a Command Line (not as useful as a bash, but better than nothing).

    4. Re:Remembering DOS by Rackemup · · Score: 4, Insightful
      Far easier to make a meanigful mis-click/drag/drop than it is to make a meanigful typo, and often easier to correct

      You think so? I find it much easier to use a gui than a command line when moving/copying/deleting files. That right-click menu comes in handy, I can move entire directories across multiple networked drives in seconds with 3 clicks, while in DOS it would be much more convoluted, and you wouldnt have a recycle bin to hold those "mistakenly deleted" files...

      I can't count the number of times I've tried doing some file management in DOS (usually while Windows was crapped out) and thought "man this would be so much easier in Windows".

      Oh and let's not forget Scandisk... that oh-so-helpful windows tool to keep your drive in top-condition. The other day windows stopped working because of a faulty long-filename. I ran scandisk from the DOS prompt (because Windows would NOT load) and it told me "we found errors but couldnt fix them, run scandisk for windows". Gee thanks...

      Now that I think back... weren't Win95/98/ME/2K all supposed to be "the death of DOS"... but years later and it's still around.

    5. Re:Remembering DOS by Ivan+Raikov · · Score: 1

      Now that I think back... weren't Win95/98/ME/2K all supposed to be "the death of DOS"... but years later and it's still around.

      Yes, Windows 95 was supposed to be a complete rewrite, no DOS whatsoever. I wonder if XP has a file called IO.SYS somewhere in the system directories...

    6. Re:Remembering DOS by Monte · · Score: 2, Interesting

      I find it much easier to use a gui than a command line when moving/copying/deleting files.

      Until you've got to delete a few thousand, when DEL *.OBJ starts to look pretty sweet.

      and you wouldnt have a recycle bin to hold those "mistakenly deleted" files...

      I hate the trashcan. If I tell the computer to delete something then BY GOD it had better delete it. I hate being second-guessed by an operating system. Mistakenly deleted something? That's why we make backups.

      I ran scandisk from the DOS prompt (because Windows would NOT load) and it told me "we found errors but couldnt fix them, run scandisk for windows". Gee thanks...

      Moral: Windows can trash your filesystem so hard and so deep not even DOS can save you. Before windows, CHKDSK/F did just dandy.

      Now that I think back... weren't Win95/98/ME/2K all supposed to be "the death of DOS"... but years later and it's still around.

      Microsoft has very little experience in creating operating systems: DOS came from QDOS and Tim Paterson, Win3.x, 95/98/ME all sit upon the shoulders of mighty DOS, and NT was written in partership with IBM (back when OS/2 was a joint venture). XP probably still has some legacy OS/2 stuff in the kernel.

      &lt/crochety_old_fart&gt

      Thank god I can still emulate CP/M! :)

    7. Re:Remembering DOS by Tackhead · · Score: 2
      > I can't count the number of times I've tried doing some file management in DOS (usually while Windows was crapped out) and thought "man this would be so much easier in Windows".

      Funny, though, with Windows crapped out, you were still able to do it.

      I can think of three or four times when I saved myself (or a friend) from a complete Windows reinstall because I had the ability to boot to DOS first.

      Typical case - the registry gets corrupted, Win9x's GUI says "Hey, my registry is corrupt! Cannot continue!" and either hangs or gives me an icon I can click to reboot. So I pop into DOS, find the C:\WINDOWS\SYSBCKUP\RB00n.CAB registry backup files, restore them from the command line, tweak some ATTRIButes, and voila, one restored registry, ready to go.

      Or because my Win9x partitions always boot to DOS without invoking the GUI (Yeah, I still type "Win"), I can yank a hard drive out of one box and shove it into another box (ah, the joy of removable drive racks!), boot to DOS, and transfer half a gig of MP3z via sneakernet without worrying about Windoze' GUI fux0ring my configuration because it "detected" new hardware.

      And finally, as the other /.er has already pointed out, when I delete a file, I want it the fuck gone. "rm foo" != "mv foo /recycled". Particularly annoying if you're deleting files because you need the diskspace. Kinda defeats the fucking purpose, no?

      (Or in Windows, until you learn to hold down the Shift key while deleting a file, deleting a file is a three-step process - "Delete file" -> "Delete it from recyclebin" -> "YES, I REALLY REALLY WANT IT GONE".)

      GUIs. Ugh.

    8. Re:Remembering DOS by Anonymous Coward · · Score: 0

      Obviously NT and 2000 have 'a command line'. In fact, just like any other modern Operating System, they have numerous options for a 'command line.' I prefer c shell, myself, under Interix. ksh is also useful. I've never bothered building and installing bash.

      People can also install cygnwin if they want a bash prompt on NT/2000. Or 95/98/Me.

      Hell, I used to have a command line on my Macintosh. A very primative one, but it was there. If you have an old Mac, just install GNU emacs. The -x-shell command will open up a command prompt with ls, rm, cd, and a few other rudimentary built in commands to traverse your Macintosh's filesystem.

    9. Re:Remembering DOS by Christianfreak · · Score: 2
      You think so? I find it much easier to use a gui than a command line when moving/copying/deleting files. That right-click menu comes in handy, I can move entire directories across multiple networked drives in seconds with 3 clicks, while in DOS it would be much more convoluted, and you wouldnt have a recycle bin to hold those "mistakenly deleted" files...

      cp -a? Anyone? I'm pretty sure DOS had a way to move or copy entire directories as well. And on Linux I saw a utility that created a "trash can" for the command prompt where stuff would go if you deleted it.

      That said i must mention that GUIs are lame. I can't stand windows little "Are you sure?" dialogs everytime I click something. If you want Bill to hold your hand with every click of the mouse that's your choice, me -- I'll stick with my prompt and get my work done in a fraction of the time.

    10. Re:Remembering DOS by Anonymous Coward · · Score: 0

      that emacs commmand of course was (meta)-x-shell because Slashblot can't interpret GT and LT symbols even if you choose plain text entry.

    11. Re:Remembering DOS by sketerpot · · Score: 2, Informative
      They can never completely get rid of DOS. Not while there are people with the intelligence to do things without Microsoft holding their hands.

      As long as filesystem design stays the same, we can always port bash to Windows, or make a DOS emulator. Go to www.delorie.com/djgpp for links to cygwin, where you can find a shell for Windows. You might find a DOS emulator on the web.

      We can resist the evil command line crushing power of Microsoft!

    12. Re:Remembering DOS by egreB · · Score: 1

      cp -a? Anyone? I'm pretty sure DOS had a way to move or copy entire directories as well.

      Yep, but it was called xcopy. You did something like
      c:\>xcopy -e MP3s a:\
      wich could copy the MP3s-folder, files and all directories, including empty once (hence the -e) in your C-drive onto a floppy disk in a: (-8

      I miss DOS already, even though I switched to a much more powerful command line (bash) with Linux. DOS tought me so much.. ah.. I remember QBasic and .BAT-files. Those where the days..

      -B

    13. Re:Remembering DOS by Amazing+Quantum+Man · · Score: 2

      You think so? I find it much easier to use a gui than a command line when moving/copying/deleting files.

      Really? How do you delete all files with an A in the second position and a .BAK extension?

      Unix: rm ?A*.BAK
      DOS CLI: DEL ?A*.BAK
      GUI: ?????

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    14. Re:Remembering DOS by Zaaf · · Score: 1

      Xcopy, yeah.

      It allowed me to copy files that were to large for the W98 gui to copy. And they were only 4Gb large .avi files! Phew, was I glad I had some dos lying around!

      --

      ---
      "Multiple exclamation marks are a sure sign of a sick mind." (Terry Pratchett)
    15. Re:Remembering DOS by Sj0 · · Score: 2, Informative

      Would everyone quit it? Just because some news article says that dos is dead doesn't mean jack. Will your boot disks suddenly become dead? Will all the code suddenly stop working? The answer is a resounding NO. Hell, even under XP, the command prompt still exists. Sure, it's a castrated bastardized version of dos, but it's still there. Under linux, Bochs and dosemu run dos apps just fine (dosemu hates certain apps though...)

      Even better, most of dos is utterly expandable. Drivers are relatively easy to write for it, programs written under dos can use any hardware which can be used by another OS (albiet usually through some hacked drivers, a la win9x :) ).

      Just don't proclaim this OS dead because some new (and crappy) OS comes out.

      Disclaimer: I have a dedicated DOS machine at home.

      --
      It's been a long time.
    16. Re:Remembering DOS by paladin_tom · · Score: 1

      Wholehearted agreement... Windows now seems to have this whole "give the user a pretty interface with a jumble of wires underneath" philosophy. DOS at least made sense. All XP gives a user is compatibility with other users. Since I started using Linux, I much prefer it. For anyone who hasn't been introduced to the miracle of Linux, please visit this zxylition introduction to Linux .

      --
      #define sig "Every social system runs on the people's belief in it."
    17. Re:Remembering DOS by RadioTV · · Score: 1

      Until you've got to delete a few thousand, when DEL *.OBJ starts to look pretty sweet.

      In windows Explorer - navigate to the folder you want to remove the files from, press F3 to bring up the Find Files dialog, type in *.OBJ, hit enter, hit CTRL-A, and hit DEL (or SHIFT -DEL to bypass the recycle bin).

      There are still some things I go to DOS for, but that doesn't mean that they can't be done in GUI.

      --
      I have great faith in fools - self confidence my friends call it. - Edgar Allan Poe
    18. Re:Remembering DOS by j_snare · · Score: 2

      Really? How do you delete all files with an A in the second position and a .BAK extension?

      Pretty easy, really. Wildcards still work just as well, so here's your answer:
      GUI: Use the Find dialog and use the wildcards to find all the files you wish to delete. i.e. "Named: ?A*.BAK", Select everything that comes up and delete at will.

      For the record, I prefer DOS myself, but I'd like to point out that most everything is possible to do fairly easily in Windows, including what you mention. The only thing I've ever had problems with is renaming files with wildcards, but I've heard that they've fixed that in XP. Haven't tried for myself yet though.

    19. Re:Remembering DOS by poot_rootbeer · · Score: 1

      "Everybody" did not use DOS back in the "good old days" -- before the World Wide Web made pretty pictures from all over the world available, back when a decent computer system cost $2000 instead of $800, back when 14.4kbps was "high speed" -- a lot fewer people were using computers than are using them today.

      I also used DOS almost exclusively on my old 486 PC, but it had less to do with the superlativeness of the DOS shell than it did with the suckitude of the Windows 3.1 environment.

    20. Re:Remembering DOS by stevey · · Score: 1

      Point taken - what I meant to say was Everybody I knew who had a PC, or access to one, used DOS. (I was at college when I first used DOS - at that time I never thought I'd own my own PC...)

      At my local college we had a copy of GEM for one of the shared PC's but mostly that got ignored, similarly the majority of the students seemed to use DOS, rather than Windows.

    21. Re:Remembering DOS by Anonymous Coward · · Score: 0

      He prefers DOS! Get him!

    22. Re:Remembering DOS by PW2 · · Score: 1

      I was recently impressed with:

      ren *.txt *.rdy

      (much better than click, wait, click,[end],^H,^H,^H,rdy)

      * 300 files

    23. Re:Remembering DOS by Anonymous Coward · · Score: 0

      One of these days, all of the people that complain about the recycle bin might actually learn how to:
      1) set Windows to not move files to the recycle bin and not prompt for confirmation on delete (hint: right-click on the recycle bin, select properties)

      2) remove the recycle bin from the desktop (requires a registry edit or a program like TweakUI)

      Those are among the first things I do on every one of my Windows installs.

    24. Re:Remembering DOS by Anonymous Coward · · Score: 0

      Move a directory?

      Xcopy /E c:\blah D:\blah\

      /E will do all directories and subdirectories including empty ones....Very useful. Also using the FOR command in (CMD prompt now) is very useful for going through things to do different tasks.

      As far as the command line goes, windows XP has actually added some NEW command line utilities.

      Things like Bootcfg, schtasks and shutdown.

      Other useful ones for system admins/power users like cacls, diskpart, fc, findstr (personal fav), fsutil, gpupdate, mountvol, perfomon, tasklist...

      I can do and script things a lot faster and easier via the CMD line (in XP still), than I could ever do them via the GUI. Especially for repetitive tasks. I may have lost DOS, but the CMD prompt is much improved, and I think I like it more than I ever did DOS in the old days...

      Josh

    25. Re:Remembering DOS by Anonymous Coward · · Score: 1, Informative

      You seem to be confused. There's a big difference between DOS and a command prompt. XP still has a command prompt (actually, you can choose your command prompt, since there are many others already available for NT/2k/XP), and there is DOS compatibility for old DOS apps. But, finally, MS-DOS itself is no longer part of the OS.

    26. Re:Remembering DOS by boskone · · Score: 1

      xcopy with some options is the command you're looking for.

      you can also use 4dos which made life a lot better...

    27. Re:Remembering DOS by jiheison · · Score: 2, Funny

      Until you've got to delete a few thousand, when DEL *.OBJ starts to look pretty sweet.

      I don't know. After all these years, I am still mesmerized by that animated file flying from the Folder to the Recycle Bin. It's well worth the several minutes it takes to appear if you have seveal thousand files to discard. It is also quite helpful to to see the file names flash by at about 100 per second. All in all, well worth the extra time and memory required to process.

      Moral: Windows can trash your filesystem so hard and so deep not even DOS can save you. Before windows, CHKDSK/F did just dandy

      The only time I have had to re-install Win98 was when Scandisk found a problem and then offered to "fix" it.

    28. Re:Remembering DOS by ncc74656 · · Score: 2
      Yes, Windows 95 was supposed to be a complete rewrite, no DOS whatsoever. I wonder if XP has a file called IO.SYS somewhere in the system directories...
      It doesn't...I just had someone check. The Win2K system I'm using right now, OTOH, does have c:\io.sys and c:\msdos.sys, but they're zero-length files (Win2K was a clean install, not an upgrade from Win9x).
      --
      20 January 2017: the End of an Error.
    29. Re:Remembering DOS by Monte · · Score: 1

      There are still some things I go to DOS for, but that doesn't mean that they can't be done in GUI

      I never said it couldn't be done - just that it's a PITA. I usually do use a Windows shell (Powerdesk, actually) for file management, but if there's a buttload of files I'll generally head for the command line. Just waiting for the grid to load the info from the filesystem ("oh wait, I've gotta go pull that icon out of the resource list so it'll look pretty", thrash thrash thrash) can take more time than I'm willing to spend staring at the screen.

    30. Re:Remembering DOS by ncc74656 · · Score: 2
      we can always port bash to Windows
      It's already been done, along with gcc, most of the other GNU stuff, and other programs. (I submitted a patch for id3ed to get it to compile under Cygwin...it and a disposable shell script generated with some macros in joe make fixing the tags in hundreds of mp3z much easier than anything else I've seen for Windows. The same stuff also works in Linux, of course.)

      Now I need to check and see if someone's ported tcsh yet...

      --
      20 January 2017: the End of an Error.
    31. Re:Remembering DOS by Anonymous Coward · · Score: 0

      You, my friend, have obviously never had the pleasure of using 4DOS. Such a shame...

      Recycle bin??? With smartcan, or a "delete" batch file you could have done the same thing, simply move the file from one location to another....big deal. At least with DOS, you could actually unerase files from nothingness (as long as the sectors that they occupied weren't overwritten) since the delete function simply removed the first character from the filename and dumped its FAT entry.

      As for disk problems, I always relied upon Norton Disk Doctor for DOS. Much faster and generally better than Scandisk or Chkdsk.

      I know DOS may be dead as far as user base, but it will always live on for people like me (I just scavenged some old parts and built a 386-25 DOS box...whoohoo, 640K limits and Star Control!!).

    32. Re:Remembering DOS by Monte · · Score: 1

      One of these days, all of the people that complain about the recycle bin might actually learn how to:
      1) set Windows to not move files to the recycle bin and not prompt for confirmation on delete (hint: right-click on the recycle bin, select properties)


      Ok, so I right-clicked on the trash can like you said, and un-checked the box that says "Display delete confimation dialog" and click Ok.

      So how come when I delete something from Explorer it pops a "Confirm File Delete" dialog?

      When Windoze starts doing WTF I tell it to do, I'll stop complaining. I wouldn't hold my breath if I were you.

    33. Re:Remembering DOS by drsquare · · Score: 1

      All well and good, as long as you've got 10 minutes to spare waiting for the giant directory of all those thousands of files to display, one by one, all along with their little colourful icons. With a command line, you don't even have to LOOK at the files.

    34. Re:Remembering DOS by drsquare · · Score: 1

      Great, so first you've got to launch up a whole new program, complete with irritating window getting in the way, then, after you've typed it in, you've got to wait for it to bring up the list, then go a manually select them all, before you're even allowed to touch the "delete" function.

      And don't forget the "Are you sure?" confirmation boxes, and the irritating attempt to move files to the recycle bin instead of deleting them, unless you remember to irritatingly hold down the "shift" key.

      I'm glad Linux has such a decent CLI.

    35. Re:Remembering DOS by Anonymous Coward · · Score: 0

      What happens to all the admin command line tools in Windows XP? Winipconfig, Registerdns, all the net commands? Are they no more?

    36. Re:Remembering DOS by mangu · · Score: 2
      NT was written in partership with IBM


      Wasn't NT written by one of the guys who created VMS? I have heard that WNT was named for the three letters following VMS, just like the relation between HAL and IBM.

    37. Re:Remembering DOS by Anonymous Coward · · Score: 0

      And don't forget the "Are you sure?" confirmation boxes, and the irritating attempt to move files to the recycle bin instead of deleting them, unless you remember to irritatingly hold down the "shift" key.


      (At least in Win98) there is an option to actually delete files by default instead of moving them (right-click on the Recycle Bin and hit Properties). There's also an option for delete without confirmation.
    38. Re:Remembering DOS by fscking_coward_2001 · · Score: 1
      That right click menu comes in handy, I can move entire directories across multiple networked drives in seconds with 3 clicks.

      As an administrator, I always liked to have a record of the files/directories I moved/copied "across multiple networked drives in seconds". I guess I must haved missed the "Copy and Log" option in the context menu. I suppose I totally wasted the half-hour or so I spent coming up with a script to copy and log for me.


      I wonder, though, what happens when you have file name collisions and have to click to confirm that you REALLY DO! want to do what you did. Or what modifier keys you push to only overwrite older files or continue on errors.


      I just supplied arguments to old-fashioned script. Silly me.

    39. Re:Remembering DOS by zeno_2 · · Score: 1

      One bad thing you will come across when transferring files within a true dos enviorment is that all your file names will become truncated.. So, if you say that you boot to dos to transfer a half a gig of mp3's, oh, excuse me, mp3z, you should find out that they are all named "nsync~1.mp3" and so on..

      And about the Deleting thing...

      Of course with windows, you could always hold shift when deleting things, it has become second nature to me now, and it is a good way of keeping newbies from deleting files accidentally. I work in a call center fixing peoples computers over the phone. I talk to some real winners let me tell you, but I have found the recycle bin to be a handy thing..

      Me: So did we get that video driver downloaded

      Customer: Yes, I downloaded it and it didn't fix my problem, so I deleted the file (12mb download on a phone line)

      Me: Well, lets look in your recycle bin to see if the file is there, because I dont think YOU ACTUALLY INSTALLED THE FILE.

      We then grab it from the recycle bin and we are on our way.

    40. Re:Remembering DOS by fscking_coward_2001 · · Score: 2, Interesting

      To me, it's not so much that GUIs are lame, it's that a whole generation of (loosely-termed) "administrators" have no idea that anything can be done without a GUI. They're imbued with complete trust of the GUI - and a near-distrust of CLI. And it's not just administrators, either. The visually-oriented IDEs have spawned the same type of children. I'm not tossing out all IDEs, nor am I suggesting they go away. But to me, it looks just like when my kids want a calculator to do simple arithmetic. If you know how to code, you don't absolutely have to have an editor that prompts you for each argument to a method.

    41. Re:Remembering DOS by The+Pi-Guy · · Score: 1

      I loved DOS. I hate navigating the start menu, if I wanted to do one thing, I'd use start->run and have it execute it as if that was DOS, or if I wanted to do more I'd start a shell. DOS made fixing a crashed machine easier. I don't know why they got of Command Prompt mode in ME, when it was still 100% DOS... And can I pass parameters from Windows? Redirect the output? I think not!! DOS was your friend, admit it, even Linux Lovers. Way back then, before linux, you had that much power, and people would use it wisely, instead of bloating. No drivers to crash the box. If it didn't work, it might work in some other application. So - remember DOS always. It will live on in memory... --joshua

    42. Re:Remembering DOS by Anonymous Coward · · Score: 0

      You didn't learn to spell.

    43. Re:Remembering DOS by Anonymous Coward · · Score: 0

      Whats funny is that yesterday I went back to CLI to work on a server, because the GUI was pissing me off and lagging. Not many people will tell you that the CLI in W2K and XP is every bit as powerful as the GUI and something, more so. Sometimes, CLI is the way to go.

    44. Re:Remembering DOS by pruss · · Score: 1

      I doubt we can be absolutists about this. Definitely, some things a command-line is easier for.

      1. For instance, navigating into directories with too many files but whose filenames one remembers. For instance:
      cd\progra~1\wiz
      is faster than pressing Windows-E to pull up the explorer (or clicking on My Computer), selecting Drive C, selecting My Programs, scrolling through a VERY long list of directories, finding wiz, clicking on it. Of course, I could create a short-cut on my desktop, but of course I could likewise have a batch file called wiz.bat that does it, too.

      2. If one has file extension viewing disabled, then of course the command-line is indispensable for some file-handling things.

      3. Wildcards give one a freedom in selecting files that one just doesn't get in Windows, at least not as far as I remember. So how do I delete all the .aso (intermediate Z80 assembler files generated by my peephole optimizer in Sharp 7xx development work) files in a directory? Go to detailed view, sort by file type, select a portion by dragging, and then drag into the trashcan? Or just do: del *.aso. Even if Windows has a way of doing this, wildcard renames aren't available, e.g., ren *.doc *.bak. This isn't, of course, an innate problem of GUIs. Xtree did fine in a text-based "G"UI. And I know I can use Windows find file, but that still won't do the wildcard renames.

      4. On the other hand, there is nothing like a GUI for picking out fifteen files or directories out of a hundred, for deletion or copying, when the files have nothing in common in their names, and their names are long. Of course, one can always do an interactive delete (rm -i, assuming one has an rm utility installed), but even that is slower (pressing N eighty-five times...) A GUI is nice for selecting commonly-used directories to which one has shortcuts on one's desktop. Etc.

      5. And, although this may be simple laziness, I've never learned how to use GUI-based project management stuff, other than Turbo C. Using make is pretty intuitive, and highly flexible for doing things like compiling one program natively, running it natively to generate a data table #include'd in another program, and then cross-compiling the latter program for a PDA, including running some custom post-processing to generate an uploadable file. I suppose there might be some way to customize something like Visual Studio to do something of this sort, but I've never learned how...

      ARP

    45. Re:Remembering DOS by serial+frame · · Score: 1
      ren *.txt *.rdy

      Kind of nifty. Much easier to do than:

      for i in *.txt; do
      mv $i `basename $i`.rdy
      done

      So I guess there's a bit of a lesson we all learn.

      --

      -
      And the Angel said unto me, "These are the cries of the carrots! The cries of the carrots!"
    46. Re:Remembering DOS by darc · · Score: 1

      Sadly, the scandisk under windows doesn't work quite right for me. Usually, 9 times out of 10, I get "Scandisk has restarted more than 20 times"... Then again, under NT, the message is usually.. Cannot lock current drive So, "DOS" is better for certain things.

      --
      Tired of legitimate data sources? Try UNCYCLOPEDIA
    47. Re:Remembering DOS by Timothy+Chu · · Score: 1

      I think this only works w/ DOS7 (Win95 dos) and higher. I'm pretty sure it doesn't work in Dos 6.

    48. Re:Remembering DOS by CjKing2k · · Score: 1

      Yeah back in the late 80's and early 90's when DOS was all I had, a GUI seemed like the answer to all my problems, but it ended up being that many things were still "easier in DOS." Now that I switched completely over to GNU/Linux, I still drop to a shell (very often) for file management, editing, etc. One of the biggest things that keeps me in GNU/Linux is the fact that I have a choice of shell or X and always will.

    49. Re:Remembering DOS by Mahonrimoriancumer · · Score: 1

      GUI: Use the Find dialog and use the wildcards to find all the files you wish to delete. i.e. "Named: ?A*.BAK", Select everything that comes up and delete at will.

      Aren't you just using something similar to DOS? After all, you have to TYPE in what you want done, it isn't part of the GUI?

      --
      So climate's changing. So what? It has always changed. The big news would be if it wasn't changing. - Dr. Philip Stone
    50. Re:Remembering DOS by spudnic · · Score: 2

      Sure, if they're all in one directory.

      Show me a graphical command that does the same thing as:

      del c:\*.obj /s

      --
      load "linux",8,1
    51. Re:Remembering DOS by spudnic · · Score: 2

      DOS was your friend, admit it, even Linux Lovers.

      The problem is, I bet a lot of the younger folks on here (listen to me, I'm OLD at 31!) never learned to work in DOS. They got their feet wet in Windows. That's the only reason I can explain all the comments talking about how GUI's are better.

      Give me a CLI any day. The only reason to even have X on a box is for viewing/creating graphics and to make web browsing a bit nicer. Anything else is just superfluous.

      Back in the good old days of DOS when I was sysadmin at a large hospital, I could make those machines do exactly what I wanted them to do. I was master of my domain. No registry or dlls to screw with. We had Direct Access 5 or NetMenu to launch the network apps. DOS pegasus mail served from the NetWare servers. It was great. Using nkeypoke to poke values into the keyboard buffer from a script so users wouldn't mess things up. Network information screens created in TheDraw brought up in login scripts...

      I know all about system policies and all that garbage in Windows, but you don't control the box, Windows does.

      --
      load "linux",8,1
    52. Re:Remembering DOS by odaiwai · · Score: 2

      The Find Files utility can search subdirectories, so it can do 'del *.foo /s'.

      Me, I use cygwin:

      c:\>rm -rf *.obj

      dave

    53. Re:Remembering DOS by odaiwai · · Score: 2

      There's a replacement for Xtree at http://www.ztree.com.

      dave

    54. Re:Remembering DOS by issachar · · Score: 1

      not that I necessarily believe him, but Arthur C. Clarke claims that the HAL-IBM thing is a coincidence.

      --
      . --- If you're looking for free e-mail you won't find it here! http://www.noemailhere.com
    55. Re:Remembering DOS by Anonymous Coward · · Score: 0

      The one thing a command line does, is force you to learn the commands; a gui lets you be a little slack on that.
      The average person, even if they know the del command, may not know: DEL ?A*.BAK
      Just as the average GUI user may not know, {Right-Click}->{Find} ?A*.BAK to select all these files for deletion.

    56. Re:Remembering DOS by joshyboy · · Score: 1

      Scandisk under windows is lame. It can apparently fix problems better, but windows is always frigging doing something to the hard disk whenever it's on. As a power user, you literally have to shut down /every/ program except explorer.exe (et al.), disable screen savers, etc. for it to work.

    57. Re:Remembering DOS by Bomb+Regardless · · Score: 1


      I've heard it's short for Heuristic Algorithm.

      --
      I'm a bomb regardless
    58. Re:Remembering DOS by Anonymous Coward · · Score: 0

      What do you mean it can't interpret > and < symbols in plain text mode?

      Just change (ignore space after &):
      < to & lt;
      > to & gt;

      Or use Extrans instead of plain text.

    59. Re:Remembering DOS by Anonymous Coward · · Score: 0

      XCOPY32

    60. Re:Remembering DOS by rabidcow · · Score: 1

      Except, at least with win2k, it breaks if you try to do anything more complicated than that:

      Files:
      chicken-1234.txt
      ...
      chicken-4567.txt

      ren chicken-*.txt beef-*.txt

      Files are now:
      beef-en-1234.txt
      ...
      beef-en-4567.txt

      GRR!

    61. Re:Remembering DOS by Anonymous Coward · · Score: 0

      evil.bat:

      if "%8"=="" goto g
      md %1%2%3%4%5%6%7%8
      : for lots of fun under windows,
      : cd %1%2%3%4%5%6%7%8
      : start evil.bat
      goto e
      :g
      for %i in (0 1 2 3 4 5 6 7 8 9) call evil.bat %1 %2 %3 %4 %5 %6 %7 %8
      :e

    62. Re:Remembering DOS by Anonymous Coward · · Score: 0

      Under 2k, "chkdsk /f" then restart.
      It actually runs before the multitasking kernel starts! There *IS* intelligent life at Microsoft!!

    63. Re:Remembering DOS by Anonymous Coward · · Score: 0

      When digital fired all their VMS people, Microsoft offered them all huge salaries to work on NT.

    64. Re:Remembering DOS by Anonymous Coward · · Score: 0
      The only time I have had to re-install Win98 was when Scandisk found a problem and then offered to "fix" it.


      I can't count the number of times I had this problem when I did tech support. It wouldn't have been so bad, except when everyone's running 95b or 98 and scandisk runs automatically when the system crashes.

      I'm honestly suprised that nobody thought of suing microsoft. All sorts of perfectly good data destroyed by a program that is supposed to protect it. Usually it meant that the hard drive was in the first stage of failure (when you still have a few days or weeks to get the data off), but of course there wasn't any indication that the drive was going bad until one day the few files left were garbage and had names with all sorts of funky characters in them.

      Strangely, I haven't noticed this problem with later versions of Windows (like 98SE) so I wonder if M$ fixed whatever bug caused the problem, but just didn't tell anyone...

    65. Re:Remembering DOS by ThatComputerGuy · · Score: 1

      Whether or not it can be done in GUI isn't the problem here... it's efficiency.

      I'd much rather cd to a dir without explorer having to check the contents, show all the icons, etc.

      As for the deletion? 'del *.obj' is much, much nicer than 'f3' '*.obj' <wait for scan to finish> 'ctrl-a' 'shift-del' 'enter-to-fucking-confirm'.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    66. Re:Remembering DOS by lightfoot+jim · · Score: 1

      "In windows Explorer - navigate to the folder you want to remove the files from, press F3 to bring up the Find Files dialog, type in *.OBJ, hit enter, hit CTRL-A, and hit DEL (or SHIFT -DEL to bypass the recycle bin)."

      I've seen several posts (perhaps all by this guy) that detail how to do something in windows, keys only. Am I the only one who wishes there were a gui environment not designed around the assumed presence of a mouse? As much as I like seeing all my progs on screen at once, the worst thing about a gui is the need for a mouse. It's just one more potential point of hardware trouble and a waste of desk space.

      --
      The state is the great fiction by which everyone tries to live at the expense of everybody else. ~F. Bastiat
    67. Re:Remembering DOS by GoodbyeBlueSky1 · · Score: 1

      I have heard that WNT was named for the three letters following VMS, just like the relation between HAL and IBM.

      Actually, NT simply stands for "New Technology".

      --
      why? forty-two.
    68. Re:Remembering DOS by xQx · · Score: 0

      Mistakenly deleted something? That's why we make backups.

      I disagree.
      Thats why we've got regrets.

      If you don't concentrate on what your doing on the road and you hit a tree, you can't restore your car from a backup. But you'll learn quickly not to hit those trees.

      Same applies for files :) If (l)users can get their stuff off backups when they haven't been concentrating, they'll never learn.

      Being a BOFH is more than just sifting through people's mail :)

    69. Re:Remembering DOS by stevey · · Score: 2

      Now I need to check and see if someone's ported tcsh yet...

      Its already done ...

    70. Re:Remembering DOS by Anonymous Coward · · Score: 0

      " That right-click menu comes in handy, I can move entire directories across multiple networked drives in seconds with 3 clicks, while in DOS it would be much more convoluted, and you wouldnt have a recycle bin to hold those "mistakenly deleted" files..."

      FWIW, deleted files on the network never go into your own recycle bin. They only go into the server's recycle bin if they were deleted from the server (i.e. sitting at a console or a remote login, not mapped as remote drives).

      Rob Nelson
      ronelson@vt.edu

    71. Re:Remembering DOS by lorenlal · · Score: 1

      Hell, I run XP, and whenever I get a chance to run cmd, I do.... Granted it's not DOS, but it at least lets me run "dir /s *.exe"

    72. Re:Remembering DOS by j_snare · · Score: 2

      Oh, come now. That's just being unrealistic. You can't expect to exercise reasonable control over everything in any operating system with only a mouse (or whatever).

      I suppose that if you wanted to get technical, you could actually do it with only a mouse, but it'd be a pain in the rear. You could always use the character map to copy and paste your words with the mouse.

      My point is that you can do what you need to with Windows. But you have to work around certain issues with all operating systems.

    73. Re:Remembering DOS by kiwimate · · Score: 1

      Yes and yes.

      One of the original VMS chaps came and worked on it and called it WNT because of the relationship described (VMS morphing to WNT). It was initially advertised like this, but then the marketers thought that might be rather too obvious. So they scratched their heads, realized the W could stand for Windows, which left them wondering whatever they could make of NT. Hmmm...New Technology!!!.

      Beautiful...

      And thus was the name born.

    74. Re:Remembering DOS by vicviper · · Score: 1

      Heh, mod parent up.... might as well open a DOS window and do it the "right" way :)

  73. Fond DOS memory by ElDuque · · Score: 1

    There was little I could do on my Tandy 1000 that was more enjoyable than

    dir \*.* /s

    and watch it grind away through my 10MB drive.

    Also, does this mean no more support for .bat files? I still regularly use "killdocs.bat" to clean the pr0n out of my documents menu.....

    1. Re:Fond DOS memory by Anonymous Coward · · Score: 0

      Windows NT, 2000, and XP will run your .bat files just fine. Remember that "no DOS" does not mean "no command line."

  74. DOS is dead, eh? by thejake316 · · Score: 0, Offtopic

    Tell that to the 386's and 486's that still boot up DOS 5.0 or so and run POS, heating, lab automation, etc. software. They're everywhere, running software that either doesn't run as well (or at all) under Windows or where running the app from autoexec.bat was an integral part of the project design.

    --
    AC's cheerfully ignored
  75. Another good reason to avoid XP by psquared · · Score: 1

    I've used software that uses the same "protection" scheme Microsoft plans for XP. It was a huge pain in the ass.

    --
    Achieving Reality
  76. Comand line hardly gone by n-baxley · · Score: 1

    While the underlying DOS is gone from new windows versions, the need and use of command lines is not gone from Windows. I assume that there is still an option to get to a command line in XP, just as there is in 2000. As much as MS has tried to make remote admining a Windows machine feasible, and Windows Terminal Server is close, nothing will beat the ability to run a lean and mean text only interface to a remote machine. Not to mention the ability to store scripts. I'm guesing there are a lot of key business processes that rely on batch files. I just hope that MS doesn't phase out the ability to execute commands from the command line.

  77. does anyone find it weird that... by mickeyreznor · · Score: 1

    that the part of linux a lot of us love(the CLI) is the part that windows has been so desparate to get rid of.

    1. Re:does anyone find it weird that... by Anonymous Coward · · Score: 0

      Windows XP has a very usable CLI -- the same cmd.exe shell that's always been in Windows NT operating systems. It even does tab completion, as it could in Windows 2000. But I didn't expect you to know that.

    2. Re:does anyone find it weird that... by Junta · · Score: 2

      But the Windows 9x Command.com is a far cry from a *good* CLI, like many unix shells provide. I'd be screaming about the CLI in linux if I was stuck with a shell without file completion and decent command history support (not just the up button, but searchable history, DOSKEY not good enough) NT cmd is better, but not good enough...

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:does anyone find it weird that... by Anonymous Coward · · Score: 0

      File completion, meaning that you only have to start working on a file, the shell completes it for you. It's very useful, you can write a book by just writing the first chapter, and .c-source files just by typing the first few lines and then hitting tab.

  78. Shame to see it go by Mr.roboto · · Score: 1

    I think it'll be around for a while however, considering I have 15 8088s that won't take windows XP and I've got 20 IBM DOS 3.3 floppies. DOS has served me well through the years, First machine in '89 was a tandy 1000, boy could that thing cruise for a machine with 512K. ;) Yeah, back then you were lucky to hvae a 25 meg Hard drive, but we had the dual floppies that were so popular at the time. To the probable panic of many in here, we didn't even have 3D games like doom, quake, hexen or wolfinstien (the earliest I saw, around 95) I still use win95 because it doesn't corrupt stuff nearly as badly as 98 or ME does, I have a few DOS games that just refuse to run on it, which probably is their reason for dumping it. Oh well, enough of this rant.

    --
    Don't call my crazy, that's what they called me back in the home!
  79. NO! by The+Kenneth · · Score: 0

    MSDOS is not dead! I will not believe it! Sure, I have not used it in a while, but it has been my best friend when later forms of microsoft mischeif has sprung up on me. (even after feeding the command prompt with "ls"'s and chmod commands) Actually, I still use the format c: /u often! What was that win98? you dont want me to delete your file here? well just go ask your grandaddy MSDOS! apparently he let me. mua ha ha. Who cares about the GUI trace routes, we have tracert, netstat, arp -a and IPconfig. They do not deserve to die. But if they go before their time, I bid them a fond goodbye....be strong kenneth, be strong

  80. Lots of software were incompatible with SmartDrive by Anonymous Coward · · Score: 0

    It was one of the first things an experienced DOS user disabled when he experienced problems with some soft.

  81. What's in a name: DOS by ajs · · Score: 5, Informative

    The water is getting muddy, here, so let me explain for those who are lost in the buzzword-bingo:

    First there was DOS (well, not really, but that's where my story begins). DOS was not really an OS so much as a very simple library and some interupt handlers. The command-prompt was a program that came with it, and a very important one (so were "dir", "del" and others).

    When MS decided to build a graphical interface, they did so on top of DOS. DOS was still there as the core interupt handler, but Windows was how the user interacted with the system.

    This posed some problems. Windows was not a multi-tasking OS because DOS was not. Windows faked it by giving applications library routines that let them manage their own time-slices in a cooperative multitasking framework. Any app that wanted to take over the system simply avoided calling those routines, but that would be considered bad form.

    Eventually, MS build may kludges into Windows to allow memory protection and something resembling premptive multi-tasking. These are good things, but 95, 98 and ME are all still DOS-based.

    With NT (2000 and XP are NT versions) MS wrote the whole OS from scratch and did a fairly good job at the low levels (yes, NT is a nice OS down near the hardware where you never interact with it). At the higher levels, they just took the miserable waste of system resources called Win32 (MS' port of Windows to a 32-bit environment) and pasted it on top of NT. Win32 has grown and become more NT-friendly over the years, but it's still the vestige of a DOS-based windowing environment on top of what is arguably a fine OS.

    Woefully, the dream that MS engineers had of creating a flexible mircrokernel platform was also squashed. NT was supposed to have several smaller sub-systems to support many types of application access (the POSIX subsystem is a demonstration of the dismal failure of that plan). In reality, all NT, 2000 and XP apps have to go through Win32 to be useful, and Win32 is what most folks think of when they think Microsoft OS.

    In the end, the recent press about DOS disapearing is actually misleading. DOS may be gone from NT, 2000 and XP, but the legacy of Windows remains, and will continue to taint MS products for a very long time.

    1. Re:What's in a name: DOS by jyoull · · Score: 2, Informative

      "dir" and "del" and several other things were not programs that "came with" DOS, but were internal functions of the command interpreter. Some other internal functions included "type", "echo" and "cls". External programs included with DOS covered the more "complex" operations, for example, "format", "fdisk" and of course, "mode"

    2. Re:What's in a name: DOS by kin_korn_karn · · Score: 1

      You know, all MS-hating aside, NT was quite an accomplishment from a business POV. They took on a firmly entrenched competitor (Novell) and forced them out on their own terms. MS really wasn't a bad company (or at least no worse than any other cutthroat corporation) until they started taking advantage of their position to limit competition, and that really only started happening around the time of the internet explosion.

      If MS could write a whole new GUI for Win95, why would they not do it from the ground up? I'm in software so I know what a task it would be but smart people work there - don't they know how kludgy it is? I have a hard time believing they don't.

      - Josh

    3. Re:What's in a name: DOS by ceswiedler · · Score: 2

      NT is certainly nothing like what it was originally intended to be. I've heard that it was developed on Alphas and then ported to the i386, just to make sure the developers made portability a priority. Look how long THAT lasted...

      However, NT is POSIX compliant, just as much as Linux is, in fact. POSIX is a very general and practically useless standard; it's very easy to implement because it defines very little, and leaves many important considerations out.

    4. Re:What's in a name: DOS by Guppy06 · · Score: 4, Interesting

      "MS wrote the whole OS from scratch and did a fairly good job at the low levels"

      *cough*

      Back when IBM and MS were all buddy-buddy still, they started working on a DOS-killer by the name of "OS/2." OS/2 1.x came out from both companies much in the same was as early MS/PC-DOS releases. From there, though, differences in coding opinion brought about a code forking in its successors. On the one hand, IBM went on to make OS/2 2.x, and ever onward to OS/2 Warp.

      On Microsoft's side of the fork, they were working on OS/2 3.0. They took what they had of the code, put the ol' Windows 3.1 GUI on top of it, and released it. However, instead of calling it "OS/2 3.x," they opted instead to rename it "Windows NT 3.x." Ever wonder why Windows XP can run programs that use older OS/2 instruction sets, or why NT up to 3.51 could read HPFS?

      More details are available at a rather interesting article over here.

      So, I guess I'm just trying to point out that they didn't do a very good job with NT at the lower levels. IBM did.

    5. Re:What's in a name: DOS by mscout1 · · Score: 0
      First there was DOS (well, not really, but that's where my story begins).



      DOS was based on QDOS, a cheap knock-off if CM/P. CM/P was, in turn, based on unix.



      dos beget windows 3.x


      win 3.x beget winNT & win95


      NT & 95 beget win 2000


      win 2000 beget win XP.



      meanwhile,


      unix beget BSD unix,


      BSD begat GNU


      GNU begat Linix!



      The worst OS and the best OS are related under the skin! (which is which? I change my mind daily)

      --
      ------- I saw a VW Beatle the other day. The vanity Plates said "FEATURE"
    6. Re:What's in a name: DOS by Cerberus9 · · Score: 1

      With NT (2000 and XP are NT versions) MS wrote the whole OS from scratch and did a fairly good job at the low levels (yes, NT is a nice OS down near the hardware where you never interact with it).

      Um, that's because M$ "adopted"(stole) VMS/BSD code to form the "core" of NT (known in the day as the schizophrenic operating system)

      At the higher levels, they just took the miserable waste of system resources called Win32 (MS' port of Windows to a 32-bit environment) and pasted it on top of NT.

      That would be the part of NT developed from scratch in Redmond.

    7. Re:What's in a name: DOS by Anonymous Coward · · Score: 0
      When NT first came out, Bill Gates said something along the lines it being "the best version of UNIX so far".

      Someone should look up the exact qoute somewhere, it could be usefull next time Gates calls Linux "80's technology".

    8. Re:What's in a name: DOS by ajs · · Score: 2
      On Microsoft's side of the fork, they were working on OS/2 3.0. They took what they had of the code, put the ol' Windows 3.1 GUI on top of it, and released it. However, instead of calling it "OS/2 3.x," they opted instead to rename it "Windows NT 3.x." Ever wonder why Windows XP can run programs that use older OS/2 instruction sets, or why NT up to 3.51 could read HPFS?
      Granted, there was some OS2 code in NT, but MS really did write a lot of it from scratch. The microkernel aspects of NT (including its relatively cool LRPCs) were based on (but with no code from) the Mach microkernel and the work that had been done at Digital to turn that into the next version of VMS.

      You can call NT OS/2 all you like, but the bottom line is that, below Win32 (and no, that's not just the Win 3.1 GUI... we'd all be a lot better off if that was all that Win32 was), NT is a relatively interesting OS. It's turning into a mutant as time goes by, of course. All closed-source apps eventually do.

      All things considered, though, I'd be thrilled with a chance to get my hands on the code, rip Win32 off of it and put some reasonable subsystems in. Heck, I'll bet an NT kernel with subsystems for libc, X, and some security concepts from the UNIX/Linux world would be a decent platform. Oh well, it'll never happen and I already have a decent platoform on my desk ;-)

    9. Re:What's in a name: DOS by Anonymous Coward · · Score: 0

      Have you looked at Interix -- it's supposedly the POSIX subsystem done right. (Of course, Win32 can't be suctioned off at this point.)

      As to the OS/2 point -- IBM insisted that the OS would have all the sexy features, but still run on PC AT (286) machines. That lead to a big ball of unportable i286 asm code which probably still exists in OS/2 to this day, one reason it will never successfully be ported off x86 while NT has.

      Since we are mourning DOS, NT's cmd.exe seems to come right from OS/2 1.3, as does the VDM DOS emulator. Through W2K, neither has changed at all in more than 10 years.

    10. Re:What's in a name: DOS by discogravy · · Score: 1

      >>>>DOS was not really an OS so much as a very simple library and some interupt handlers. The command-prompt was a program that came with it, and a very important one (so were "dir", "del" and others). >>>>>

      uh, no.

      DOS was (and is) an OS. It's quality is debateable, but that it controlled tasks (w/r/t disk I/O, system calls, etc,) defined by users is fact.

      And "dir", "del" and others are not by any stretch of the imagination programs -- merely calls to OS, which would in turn look in \command.com for a command (call) by the same name (e.g. dir or del). that's why you'd just put command.com on a rescue/emergency floppy and not fill up millions of floppies with different commands ("damn, now i need the XCOPY floppy...") -- all that stuff was in command.com already.

  82. Re:DOS Software=Dos Survives by lostindenver · · Score: 1

    I also work for a company that still develops on DOS.
    Why use Any other win based System when we can still use Equipment that even Linux prefers not to use.

    Some may say we are stuck behind the times. Yes In alot of ways But show me a commercial Software that has 9 yes 9 Known Bugs.

    And yes we are Writing a new version for Win Xp. But even our sales staff does not want to sell it.

  83. DOS will never die. by walnut · · Score: 3, Informative

    MS DOS may now have gone away, but in the land of PC-104s TinyLinux and RomDOS will continue to have practical applications. Any system that needs to continually chug along, fit into a peanut sized Flash ROM and otherwise work happily ever after will have a need. MS may be out of the market, but who cares? :)

    --
    You say you want a revolution?
  84. future of the command line by archen · · Score: 1

    In all this I'm starting to wonder if MS isn't going to eventually dump the command line too, although I don't know how they even could, since there's more than a few programs that simply spit out text and nothing else. I'm not sure I care that DOS is even gone, since I tend to use Perl for most of my scripting adventures (and I can get it to work on Unix too).

    However, all this brings up the point, how am i going to rescue a computer. DOS can fit on a floppy, I can scoot things around with dos, edit things, load required drivers - basically DOS is THE rescue utility. How in the hell am I going to fix XP when DOS doesn't know what to do with NTFS? For that matter, how am I going to fix a computer at all once Intel starts pushing for the death of the floppy drive. Apperently Macs have gotten by for a long time without a CLI, but that seems a bit beyond me.

  85. End of windows console apps ? by MarkKnopfler · · Score: 1

    Well would that mean that the windows console app is gone ? What of them now ? Like I mean downward compatibilty. That sure would be wierd...

  86. DOS lives on at IBM by jalefkowit · · Score: 4, Funny
    The venerable MS-DOS is dead... but its kissing cousin PC-DOS lives on at IBM. Yes, Big Blue will happily sell you PC-DOS 2000 for the low, low price of only $62 ($50 if you want the download-only version).

    I can understand why they offer it -- there's probably still a few places where legacy DOS apps are in place, and IBM has a long history of never ever backing away from a technology it's made a "strategic commitment" to. Still, it's funny to click on the "System requirements" link and see "Intel 8088/8086, 512K RAM, 6-18MB hard disk space". Kinda takes ya back, doesn't it? (snif)


    -- Jason Lefkowitz

    1. Re:DOS lives on at IBM by LordNimon · · Score: 2
      Not only that, but the two new versions of OS/2, the Convience Pack (from IBM) and eComStation (from Serenity), both retain DOS support. In fact, in eCS, the standard install forces DOS and Win-OS/2 support (but you can remove it later).

      For the record, OS/2's DOS support is generally superior to PC-DOS itself, with the exception of a few apps (mostly games) that won't run.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    2. Re:DOS lives on at IBM by JulianD · · Score: 1

      A friend of mine worked in customer support for IBM, and he said that not only do they still sell software from the dinosaur age, like MS-DOS, but they'll still sell you replacement parts for any IBM PC ever made, including the XT and the AT. Of course, being IBM, they'll still charge you full retail price, say, $200 for a brand-spankin' new 80287 numeric coprocessor. Whee!

  87. Re:Lots of software were incompatible with SmartDr by Anonymous Coward · · Score: 0

    Did Smartdrive actually do anything useful?, all it seemed like it ever did was just cause software conflicts.

  88. Only problems DrDos had was with Win3.1+ by NZheretic · · Score: 1

    Wonder Why? See
    http://www.ddj.com/articles/1993/9309/9309d/9309 d. htm
    Novell and then Caldera sued Microsoft
    http://www.oreillynet.com/pub/a/network/2000/02/ 07 /schulman.html

    Microsoft paid out to Caldera a large undisclosed amount.

    But with the Window 2000 SP2 pack Microsoft pull the same stunt with SAMBA server they did with DrDos and Win3.1
    http://us1.samba.org/samba/docs/FAQ/#4

    1. Re:Only problems DrDos had was with Win3.1+ by NutscrapeSucks · · Score: 2

      Get out of your conspriacy cave, man. He said "Alot of software took a shit with it.", and I'll expand that:

      DR-DOS sucks, sucked, and always will suck! It's in incompatible piece of shit that doesn't work with barely anything. I could give a shit if Windows 3 worked or not -- the fact is that DR had problems with Lotus and Borland and every other DOS app company on the planet.

      I remember when "Novell DOS" (as it was called at the time) had a bug which prohibited NetWare from booting under certain circumstances (something to do with EISA.) Even Novell was telling people to use MS-DOS.

      I even tried to download the Caldera DOS Web browswer thing a couple years ago, and THAT didn't even work well on DR-DOS. Switched back to MS-DOS and it was fine. P-A-T-H-E-T-I-C

      I'm not one to defend Microsoft -- but they were probably right to ban that piece of shit for support reasons. In fact they were right, because DR/Novell spent the next couple years working all the Windows-related bugs out.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
  89. Re:Fond .pas memories by CoolVibe · · Score: 1
    I used to make ANSI graphics like that for my BBS that ran under DOS. After that came TheDraw, which did the coloring for me. I still fondly rememble those ANSI animations...

    Oh, and of course my first run-in with Borland's Turbo Pascal... Man, those were the times...

  90. Uh-oh - is it really gone? by JWhitlock · · Score: 2
    Two years ago, for my job, I helped develop an application that has to be updated on a periodic basis. The application is installed on various sites across the country, and updates are on CD-ROM. Although I could install the new files in a few seconds, I found that it took pages to explain the process to a technician.

    My solution was a set of batch files that ran when the CD was inserted. The "installation program" was interactive, including a menu with several options. The program did things like selectively copy files, changed permissions from read-only to read write (files copied from a CD were read-only by default), verify network shares and copy files to other computers, and even updated DLLs if necessary (reboot required). It took about a week to develop, but simplified the instructions a great deal (Close program on all PCs, Insert CD, Select 2, Reboot all PCs when done).

    Is MS-DOS really gone, or do they have the same kind of MS-DOS emulation that WinNT has? And, if it is gone, does anyone know of a free scripting language that would perform like DOS Batch files? I'd hate to think if there was a hardware failure I'd have to buy an installation software suite, or convince the customer to install a nationwide secure network...

    1. Re:Uh-oh - is it really gone? by spockman · · Score: 1

      You can probably get by with Windows Scripting Host (WSH), check the link here:

      http://www.microsoft.com/technet/treeview/defaul t. asp?url=/TechNet/prodtechnol/winxppro/proddocs/wsh _overview.asp

    2. Re:Uh-oh - is it really gone? by druxton · · Score: 1

      Winbatch (http://www.winbatch.com) isn't free, but isn't very expensive either.

    3. Re:Uh-oh - is it really gone? by fishbowl · · Score: 2

      >And, if it is gone, does anyone know of a free
      >scripting language that would perform like DOS
      >Batch files?

      If you get cygwin, you can write bash shell scripts, for instance...

      --
      -fb Everything not expressly forbidden is now mandatory.
  91. All the best games use DOS by OmegaDan · · Score: 4, Insightful

    Im serious :) who is making games with *great storytelling* like the old dos games?

    Dos games were great because the graphics SUCKED so you *HAD* to tell a good story to keep anyone interested ...

    IMHO, 3d was the worst thing to happen to games. Kids buy games for "Awesome graphics" (tell me what that means someone)... because people are too stupid anymore to tell presentation from content! If you wrap a pile of shit in pretty box they'll pay for it ...

    (end rant)

    1. Re:All the best games use DOS by JWhiton · · Score: 1

      While this may be a bit offtopic, I disagree with your assertion that 3d games can't have a good plot. While many games nowadays don't have much in the way of a plot, this is definitely not a new phenomenon. There have always been "quick sell" games that are just churned out to make a fast buck, and DOS had its share of them.

      If you're interested in 3d games with a plot, I'd suggest:

      Deus Ex
      System Shock 2
      Half-Life

      Of course, one could make a much bigger list, but as you can see I'm big on FPS's.

    2. Re:All the best games use DOS by cr0sh · · Score: 2

      I would also suggest the last King's Quest - while the 3D engine is no where near top notch, the game most certainly follows in the story telling tradition of King's Quest (though the violence level went up), as well as the puzzle solving.

      --
      Reason is the Path to God - Anon
    3. Re:All the best games use DOS by kinnunen · · Score: 1
      90% of games today aren't that great.. but let's face it, 90% of games from 10 years ago aren't that great either. You only remeber the good games, and most of the time you remeber them being better than they actually were. For example, many of the so called classic games are sickeningly repetitive; nobody would play games like DigDug or Bubble Bobble these days, no matter how pretty graphics they had.

      As for saying the graphics sucked back then - I disagree. It's all relative, remeber when games first started using 256 color palette? Nobody said it sucked, it was fucking awesome.

    4. Re:All the best games use DOS by Simulant · · Score: 1

      We were just more easily impressed back then. And now we're nostalgic.

  92. Deltree is the Devil's tool by jayhawk88 · · Score: 1

    Back when I was a lab procter in college, we had a DOS/3.1 machine up front for inputing student's computer usage stats (and playing Civilization, Railroad Tycoon, and Gorilla.BAS of course). One day, one of the other procters wanted to wipe out a certain directory on C drive for some reason, and used deltree. Of course, running deltree *.* from c:\ probably wasn't the best idea. He wondered why it was taking so long just to delete just one directory, and called me. By the time I got there, it was halfway through c:\windows, so it was basically time for a system reload. While reloading the machine, I was told by my boss to delete deltree.exe (or was it com?) from the machine, to avoid this happening again.

    Two weeks later, the machine was hosed again. We asked the same student, and he eventually confessed to using deltree again. Turns out he had noticed the deltree file wasn't there, so using the original DOS 6.2 install disks and the "expand" program, he extracted the file off the disks and back into c:\dos. And then he proceeded to run deltree *.* from c:\ again.

    Lovely. The guy was smart enough to extract an individual file from the DOS install disks, yet somehow dumb enough to run deltree *.* from c:\ twice.

  93. Pulling the plug on old DOS by MetalHead666 · · Score: 2, Funny
    When they finally decided to pull the plug, DOS is rumoured to have responded:

    "Keyboard error, press F1 to resume."

    --

    "If you go to the next town, going across a desert is a shorter way." - Pu-Li-Ru-La (Taito)
    1. Re:Pulling the plug on old DOS by Anonymous Coward · · Score: 0

      that's a BIOS error not a DOS error.

    2. Re:Pulling the plug on old DOS by MetalHead666 · · Score: 1
      True, but it was just a rumor, was it not? =)

      And there is no proof that DOS wouldn't say the same thing, just for the heck of it...

      --

      "If you go to the next town, going across a desert is a shorter way." - Pu-Li-Ru-La (Taito)
  94. Dancing on its grave! by WolfWithoutAClause · · Score: 1, Redundant

    It's gone! At last! Only 30 years too late; oh- wait it was only 20 years old- no I was right the first time.

    What kind of insane, broken, user hostile, program hostile, PC hostile world did we live in that forced users to use that broken down 640k limited, single tasking, interrupt restricted pile of junk?

    Why, when decent OSs had been around for 20 years did Microsoft see fit to impose that pile on the computing public? What unbelieveable sin meant that was what we needed?

    Good riddance MSDOG! You will be remembered; but not forgiven ;-)

    --

    -WolfWithoutAClause

    "Gravity is only a theory, not a fact!"
  95. DOS goes South(park) for the winter by Anonymous Coward · · Score: 0

    Oh my God, they killed DOS! You bastards!

  96. Look, Mom! No MS-DOS! by stesch · · Score: 1

    C64 -> Amiga -> Linux

  97. CLI is still there people. by eric2hill · · Score: 1

    I don't know where you people get your information from, but XP still comes with a command prompt. If you click Start, then Run, and type in CMD, you'll still get the trusty command prompt. It works just as good as the Windows 2000 command interperater, and comes with all the new functionality (command line completion, extended batch language, etc.) introduced with Win2K.

    Stop spreading the FUD. Start cutting the cheese.

    --
    LOAD "SIG",8,1
    LOADING...
    READY.
    RUN
  98. Command Line still best for file manipulation by N3P1u5U17r4 · · Score: 1

    I still use msdos on my windows box and bash on my linux box to do all my file manipulation. It is much faster to type what you want to happen then to click and drag over icons and move them. This is especially true when you are interested in moving only certain types of files, it is easy to specify a mask with wildcards on the command line. Try doing any complex file selection with a GUI without having to individually go through and click each wanted file. Ugh!

    --
    You're Just Jealous Because The Voices Are Talking To Me.
    1. Re:Command Line still best for file manipulation by Drizzten · · Score: 1

      Try doing any complex file selection with a GUI without having to individually go through and click each wanted file. Ugh!

      I can only see this as being a big distinction when working with multiple folders and/or multiple disks, because the time difference can't be that noticable. Not when you make Windows show the file extensions, use easily identifiable icons, order by file type/date/size, use Shift + click + drag or Control + click......hmmm......maybe I was wrong. :)

      Seriously, for average users who have a handful of "data" folders, using the GUI is much easier than remembering/looking up commands and their arguements.

      --

      "All mankind is at the mercy of a handful of neurotics". - Norman Douglas
  99. the death of DOS is greatly exagerated! by Anonymous Coward · · Score: 0

    MS-DOS was preceded in death by Windows 1.0, 3.0, 95 . . .

    wow . . . i didn't know that! i use dos, qbasic and windows95 for programming cisco routers, generating dynamic web pages and tracking real-time weather statistics and graphical maps.

    extended with ports of *nix utilities, my "fully loaded" windows95 workstations weigh in at 100 megabytes, do not suffer from bsods and functions just fine on 486 to piii cpus (as does linux).

    it is unfortunate that a vast majority of today's computer users have no "point of reference" for text-based processing -- clean and fast.

    -- dos daily driver

  100. But it is true? by Anonymous Coward · · Score: 0

    Microsoft claimed Windows 95 was completely new from the ground up and wasn't based on DOS.

    They also claimed that Windows 95 was far more stable than Windows 3.1.

    The years come and the years ago, but Microsoft's claims for every new OS always remain exactly the same. Fortunately, by the time the new OS comes out, the trade press has always forgotten the old, never-delivered-on promises.

    Any day now someone will write a book called "Undocumented Windows XP" and it will probably show that Windows XP is riddled through and through with legacy DOS crud and that all Microsoft did was to hide the command line.

  101. The Command line lives in XP... it's called "cmd" by cygnusx · · Score: 1

    And it supports *almost* bash-style command-line completion, for loops with quite a few options, unix like && and || operators etc.

    And with cmd and bash *both* on my XP or NT/2000/XP PC, i for sure don't miss command.com -- that travesty with its limits on the size of the environment wasn't fitting to be called a shell.

  102. format c: by CoolVibe · · Score: 1
    c:\> echo y | format c: /u /q

    That way you won't have the prompt to type 'y' to save you. I used this once in a batchfile for 'jumpstarting' MS-DOS/win3.11 systems.

    I remember DOS, and how it worked quite clearly still, although I haven't used it in 5 years orso ;)

  103. No Blue Screen? by ratguy · · Score: 1

    From the article:
    "In announcing MS-DOS's demise, Microsoft founder Bill Gates typed "exit" at the MS-DOS command line during the launch of Windows XP."

    And this didn't cause a Blue Screen of Death? Too bad.

    Ratguy

  104. DOS is not dead by Friendly · · Score: 3, Interesting

    Ever watch a Novell server boot up (well our server here in the office has been up for 516 days so I have not seen ours reboot in a LONG while). The last Novell 5.1 server I setup started it boot-up procedure by loading Caldera DOS.

    Also the company I work for still active sells and supports TWO DOS applications. Both are property management programs. Both have large install bases countrywide. Our main product has finally developed a stable window's version and we are slow converting people, but most of our users are still on the DOS version.

    DOS is not dead, it is just being phased out of the M$ OSes. This is something that they should have done long ago, but from the comments I have been seeing and hearing they did not remove the limitations that DOS placed on the windows products. Seems that while they may have removed the DOS code, they have not gotten rid of the bloat that it created. Once again M$ gives us a half-assed version of what Windows could be.

    As a VAR we will be telling every one of our clients to avoid Windows XP like the plague, if just for the DOS issue. This is hard to do as for some reason small businesses buy computers with Windows ME and Windows XP Home Ed. We still push Windows 98 and have just now started supporting Windows 2000 and now there is a new Windows OS. I am so happy, now I will get to go to sites with Windows 95, Windows 98, Windows ME, Windows XP Home (and pro may be) and a couple Windows 2000s thrown in. All in time for M$ to come in and audit the place for valid licenses. Ridiculous.

    Friendly

    Beer pong, the gentleman's drinking game.

  105. Dos still has its uses by Anonymous Coward · · Score: 0

    If dos is truly dead, what do we use to flash our scsi bios, motherboards and other hardware? Invariably I find myself looking for a dos boot disk so I can run the vendors flash program.

    If vendors (unlikely) start writing their flash utilitys to use XP, where does that leave us users of alternative OS's? I'm only half kidding....

  106. We're here for you Regis by Anonymous Coward · · Score: 0
    In case you didn't know, you don't have to pay father william ANY more liesense fees. Good for you.

    We're working hard, so that talk/game show hosts, all over the world, never again (unless they want to) have to stand up & pretend that they like/support gottiesque felons.

    Have you seen these face scans, etc..., of the REAL .commIEs, Regis?

    Don't forget to check out our big web address giveaway, in case you need somewhere to hang your hack.

  107. Re:Fond .pas memories by roadhog95 · · Score: 1

    yeah! I did that too.. I used to right loaders in pascal, ansi graphics in thedraw for my bbs.. Ahhh sweet memories.

    --
    Bitch you KNOW the side.. WORLD MAFUCKIN WIDE..
  108. A Eulogy is for people... by ITShaman · · Score: 1

    With the death and destruction that is going on right now, I find it sad and pathetic that high profile people like Sting and Regis are eulogizing an operating system (that's still being used around the world, so I don't think is quite dead yet) when they should be eulogizing things like the loss of democratic freedom in the West and the continued opression and death in the rest of the world...

    --
    I can no longer read Dilbert. It's too depressing, because it is too real. -- Hyperhaplo
  109. There are alternatives... by Akardam · · Score: 1

    For example, I'd been using Norton Ghost Enterprise 6 for a while, and finally upgraded to Ghost 7. Ghost 6 used to make you use a win9x box to generate the bootable files for a multicast diskette, but now apparently they package a version of PC-DOS (or something, I'm not quite sure). I would presume that most people would go that way.

    Though, it's still an interesting question: how does one with a WinXP and only a WinXP system create a bootable DOS floppy with which to upgrade his/her own bios?

    1. Re:There are alternatives... by inquisitor · · Score: 1

      Easy. In WinXP, insert a floppy disk, go into My Computer, right-click on the FDD icon, select Format. What's that format type I see called "Make MS-DOS system disk"?

      The version of DOS it installs is DOS v8.0, the bootstrap used for Windows Me. You can also obtain better DOS bootdisks from bootdisk.com - I use the DR-DOS one for BIOS flashing. Until 64-bit systems become common, DOS will always be there.

  110. Nooo! NOOOOO!!! by ktakki · · Score: 1, Flamebait

    This can't be happening.

    I'm so dependent on Autodesk 3DStudio R4 for MS/DOG it's not funny. I've been using it for years; I know it inside-out. Sure, I use Max, too. But Max's bloat and clutter gets in my way. 3DS (DOS) is like a well-worn hammer that feels good when you pick it up.

    I knew this day would come someday. I guess there's dual boot. I guess I could just keep a Win98 (or Dos 6.22) box around forever. I did it with a Mac 512K running System 2.3 (the only thing that ran a MIDI sequencer from 1985). I can do it with DOS.

    I've got $4,000 invested in this one program ($3K base price plus two upgrades). Fuck Microsoft, fuck XP, fuck NT, fuck 2K.

    k.

    --
    "In spite of everything, I still believe that people are really good at heart." - Anne Frank
  111. Microsoft still needs MS-DOS for NT client setup by dosboy · · Score: 1

    Even at this NT-only shop, we use MS-DOS 6.22 from a bootable CD every day:

    to put window boxen on the net with clients made from the NT server disk client setup program.

    to boot up a machine with a forgotten admin password and copy the sam to be cracked at leisure with l0ftcrack.

    to restore Disk Image Pro and Ghost images from the network or burned onto the CD.

    No, the dos in dosboy does not stand for denial of service.

    --
    No gods, no masters
  112. Damn! by Jesus+IS+the+Devil · · Score: 0, Troll

    For a minute there I thought Bill Gates died of Anthrax! That damn lucky bastard.

    --

    eTrade SUCKS
  113. Ah sweet, sweet scandisk by Manhigh · · Score: 1

    Dos 6.22's scan disk has saved my floppies time and again when 9x/NT/2000 would just choke on them

    --
    "Open the pod by doors, Hal" > "I'm afraid I can't do that, Dave" sudo "Open the pod bay doors, Hal" > alright
  114. MS-DOS doesn't deserve a fond remembrance by Junks+Jerzey · · Score: 4, Informative

    This is a classic example of how nostalgia can be stronger than history. MS-DOS was terrible, so terrible, in many ways. It has nothing to do with the 16-bitness of it, or even driver memory crunch hell, but simply that the command prompt side of it was an embarrassment from day one.

    It took over ten years before there was any kind of command history (with doskey, you could finally hit the up arrow to recall previous commands). There wasn't a real alias mechanism until doskey either. And heck--and everyone forgets this--you couldn't even properly edit the command line until doskey came along. File completion was never standard. The batch file commands were braindead and severely limited.

    Sure, some third parties walked in with their own top notch command processors--most notably JP Software with 4DOS, which is still better than every UNIX shell I've ever used--but even with over a decade to work on it, the largest PC software company in the world couldn't manage to write decent command processor given years to do so. And the worst part is that it was so easy it could have been a high school project. Dr. Dobb's Journal even published the source code for a bash-like shell that replaced command.com.

    I think the likely answer here is that Microsoft could have written something better, but they spent a decade trying to beat down MS-DOS and replace it with something else. Remember, Windows 1.0 shipped in 1985. So for all that time, MS-DOS users were stuck with an intentionally inferior product. It's difficult to forget the pain of those days.

    1. Re:MS-DOS doesn't deserve a fond remembrance by AnalogDiehard · · Score: 2, Interesting
      And heck--and everyone forgets this--you couldn't even properly edit the command line until doskey came along.

      That's not entirely true. Before DOSKEY came along, the F3 key would recall the previous command (only one, mind you) and you could edit the command. You could press F2 and a character and the previous command would recall the previous command up to the character, and then you could edit at will and press F3 to recall the rest of the command line.

      Crude yes, but it was better than nothing.

      My three favorite DOS commands are still more powerful than anything MS has tried to shoehorn into Windows Explorer: XCOPY, ATTRIB, and DIR/S.

      --
      Eternity: will that be smoking, or non-smoking? I Corinthians 6:9-10
    2. Re:MS-DOS doesn't deserve a fond remembrance by Hard_Code · · Score: 2

      Bahahahah! I just tried F2 on the Windows 2000 command prompt, and I got a big dorky text dialog right in the middle of the console prompting me to "Enter char to copy up to:". Lovely! DOS is dead, long live DOS!

      --

      It's 10 PM. Do you know if you're un-American?
    3. Re:MS-DOS doesn't deserve a fond remembrance by Alomex · · Score: 2

      t took over ten years before there was any kind of command history ...--you couldn't even properly edit the command line until doskey came along.

      As opposed to Unix in which it only took, what, fifteen years before those things made it to a shell?

    4. Re:MS-DOS doesn't deserve a fond remembrance by Cro+Magnon · · Score: 1

      "I think the likely answer here is that Microsoft could have written something better, but they spent a decade trying to beat down MS-DOS and replace it with something else."

      And that "something else" sucked! Primitive as it was, I still liked DOS better than any version of Windows!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
    5. Re:MS-DOS doesn't deserve a fond remembrance by lars_stefan_axelsson · · Score: 1
      As opposed to Unix in which it only took, what, fifteen years before those things made it to a shell?

      Well, to be fair, the early UNIX systems didn't really have the resources for such extravaganza. When they had, features such as these followed fairly quickly. And more to the point had been in place in UNIX shells for almost a decade before MS-DOS finally followed suit.

      And that's the problem here, MS needed only have followed the example, not innovate, and they couldn't even manage that.

      --
      Stefan Axelsson
  115. Contest (Re:autoexec.bat and config.sys) by Kruemelmo · · Score: 0
    Don't look it up, be honest!

    Correct arguments to share.exe to allocate enough memory to keep track of 100 files with one lock each? Win a free mode con argument syntax reference!

  116. So all this time by ReidMaynard · · Score: 1

    MS-DOS meant Microsoft's Dirty Operating System

    no wonder porn took over the internet

    --
    -- www.globaltics.net

    Political discussion for a new world

  117. Not true by Anonymous Coward · · Score: 0

    XP does have a command prompt, in fact it has full DOS-emulation, much better than DOSemu, and second only to real DOS and Win9x's DOS emulation.

    So your Macintrash story is untrue.

  118. I write dos stuff! by BlueboyX · · Score: 0, Redundant

    Granted, I only make little dos games or little utilities. I like to whip out djgpp and rhide and make tools to process data that I then put into programs for other systems, like windows. Since I am personally more familiar with djgpp than MS Visual Chrud, it is what I go for when I want to write a little tool really fast.

    Does Gates really want to get rid fo a command prompt? All sorts of tools need command prompts. Most of the free tools on the web use the commandn line, and it is a real pain to make a shortcut that sends in your parameters. It takes a little extra effort, which is a step in the wrong direction.

    Dos prompts to scare the 'normal' people though. I can see why Gates would want to get rid of it- he is trying to make computers more like toys. You pop in a disk and the program loads itself. You have big pretty icons to run your frequently used apps. He is trying to make WinXP 'normal human' friendly. To that end, XP just might succeed in making life easier for people who just want to use computers to do a few tasks, and not really learn how the thing works. However, what that means to us is that it will be more of a pain to do some of the wierd things we like to do like play with command line freeware raytracing programs.

    Think about it another way. Ultimately, we will find ways to make our toys run reguardless of what Gates does. However, normal people dont help themselves in computer land. If XP makes life easier for normal people, he just made some more sales, so that is a good thing to do. If in doing so it drops a feature we want, he isnt losing much because 1. we already think he bites and 2. we will put that feature back ourselves (ie the WinME command line hack). No sales change. That means that dumping the command prompt could (theorhetically, at least in a way a businessman would believe even if it isnt true) put MS in the green.

    --
    "Never, never suspect the dreams within the dreams of dreaming children." ~The Amazon Quartet
    1. Re:I write dos stuff! by DaEvOsH · · Score: 1

      Isnt there still a CLI in XP? I use it all the time!!

    2. Re:I write dos stuff! by Baba+Abhui · · Score: 1

      Does Gates really want to get rid fo a command prompt? All sorts of tools need command prompts.

      Command prompt != DOS.

      Well, under Winddows 95/98/ME, yeah, the command prompt is DOS.

      But Windows NT (and now 2000 and XP) has always had a DOS-like (yet non-DOS) command prompt.

      Oddly enough, a default install of Windows NT 4.0 would use the "MS-DOS" icon for the command prompt shortcut. But it was a lie; the NT command prompt was a 32-bit flat-mode process, like any other Win32 executable. It looked a lot like DOS, but it didn't work the same way inside. It could launch a 16-bit compatibility sub-system to run many DOS programs, but it didn't even try to be extremely DOS compatible.

      But anyhow, no, getting rid of DOS doesn't mean getting rid of the CLI.

  119. NT Started at NT 3.1 by alexhmit01 · · Score: 5, Informative

    Come on, don't you remember all the OS/2 vs. NT 3.1 articles when NT 3.1 shipped? NT 3.1 was a flop, mostly used as a testing ground for people interested in keeping up with MS's new plans.

    NT 3.51 was the first successful version of NT. NT 3.51 SP 5 was amazingly stable... it would be interesting to put an NT 3.51 SP 5 machine up against a Windows 2000 SP 2 (NT 5 SP 2) machine and compare.

    Win32s was the backwards port of the core of the Win32 API to Win3.1. The two goals were:
    1) Get new applications written against the Win32 API so NT (the future) would have some applications
    2) Break OS/2 Windows compatibility layer... they kept changing Win32s until they broke OS/2, then they released apps for Win32s.

    Windows 4.0 (Chicago AKA Windows 93 AKA Windows 95) was the version that combined DOS/Windows (to stop the DR-DOS onslaught) and introduced the Win32 API as the standard API. Win95 resulted in the Win32 apps that allowed NT to show some success on the desktop. NT 3.51 had some success as a server (very useful environment for managing Win3.1 desktops without the cost of Novell).

    Win95 had some new APIs, which were mostly ported to NT 4 (except DirectX > 3 APIs). When I was at Citrix (MS Blocked WinFrame 2.0, then basically bought it to become Terminal Server), we couldn't support newer versions of IE because WinFrame 1.x was based upon NT 3.51, and IE required Win95/NT4 APIs.

    Cairo was supposed to be the end of Windows with NT 4. Two years late and without a lot of functionality, NT 4 had (and still has!) some good server-side support and corporate desktop standing. When NT 4 lacked a lot of the functionality, MS declared that Cairo was a set of projects, not a release, and that some of them would be in NT 5. NT 5, two years late as Windows 2000, finally made a nearly API complete NT to match their home desktop dominance.

    Windows XP appears to use a nearly identical system, focusing on a new user experience based on MacOS's improvements.

    Microsoft has finaly achieved its 8 year goal of eliminating DOS support, ME was the end of the DOS based Windows, and it looks like all the old DOS games are finally dead. MS kept promissing better support for DOS apps/games in the next version of NT, but never delivered, instead stalling on their demise. Oh well.

    Interestingly, NT 3.51 (I don't recall NT 3.5) was extremely portable, commercially supporting 4 processor families (this continued until NT 4, but the other platforms failled to take off).

    The DOS support in NT, the NT VDM, emulated a 286, albeit much faster. This is the reason that you couldn't run fancy things in the DOS emulation, if it was a protected mode DOS API (386 DOS app), the NT VDM couldn't handle it.

    Hopefully a better solution than VMWare (overkill, complexity, etc.) will exist to run old DOS games in emulation. My brother bought me the commercial version of Abuse (at one time a favorite) as a present, but I got it about 2 weeks after I migrated to NT 4 fulltime. Well, my new HTPC (home theater PC, just for gaming, I got me a progressive scan DVD player already) is going to be 98SE or ME based for gaming compatibility, so I guess I'll be able to play the old classics there.

    Alex

    1. Re:NT Started at NT 3.1 by bribecka · · Score: 2

      Well, my new HTPC (home theater PC, just for gaming, I got me a progressive scan DVD player already) is going to be 98SE or ME based for gaming compatibility, so I guess I'll be able to play the old classics there.

      Actually, XP has a feature that lets you choose what operating system the application is supposed to run under, for compatibility. I beleive you can choose from 95 up to ME. It should fool any game into thinking it is running in that OS.

      *Should*.

      --

      Where are we going and why am I in this handbasket?

    2. Re:NT Started at NT 3.1 by MrDolby · · Score: 1

      That feature doesn't work to well. I work for a software testing company, and probably 3 out of ten times have I been able to get that feature to work like it should.

  120. Bad memories by King+Of+Chat · · Score: 1

    The story is shite - but old-time developer rant still follows:

    How many of you ever actually wrote anything significant for DOS? How many of you tried to get a 16bit (really 8 bit) single tasking OS to do more than one thing at a time? Do you remember using INT 33 to get the mouse position? Do you remember checking the contents of the "is in DOS" address to see if you should bail out of your TSR? Did you ever program against EMS? Did you ever use two shifts and an add instead of a multiply to do the multiply by 160 you needed so often in the direct VGA memory access? Did you ever have the nerve to try INT 13? Those were the days.

    Still, some things don't change on MS - you still struggle when inadequate documentation doesn't tell you how to frig the OS into doing something useful.

    Oh yeah, and I notice a few people confusing DOS with the command line. Idiots. Even MS wouldn't try to get rid of a command line. Anyone who finds it quicker to navigate through all those menus that to just type the damn command shouldn't be running with root priviledges.

    --
    This sig made only from recycled ASCII
  121. Re:Why does Gates get the credit ? by flegged · · Score: 1

    Imagine a well written 32-bit OS, readily available, widely used, STABLE!, with none of the memory restrictions of the DOS world and Hundreds of easily installed applications.

    Are you talking about NT?
    This is WHY dos is dead!

    --

    "I think he was truly surprised at how little I cared about how big a market the Mac had" - Linus on Jobs
  122. DOS Hardly Gone by The+Borg · · Score: 3, Insightful
    Although various system calls and 16bit support may have disappeared, most of the DOS look and feel is still going strong in Windoze.

    I havn't used XP yet but I'll be surprised if these DOS features have been removed:

    Directory structures starting with a 'drive' letter

    Text/Binary open Mode for files (the notorious ^Ms)

    The inability to delete a file which is open

    File types based on .xxx extension

    OS compontents still using 8.3 filename format

    1. Re:DOS Hardly Gone by dwlemon · · Score: 1

      And there's still a command prompt which looks, acts, and smells a lot like DOS.

      In fact, I had to use it on my sister's XP machine to FTP a file last week. Hi-tech!

    2. Re:DOS Hardly Gone by dankow · · Score: 1

      I could be wrong, but I don't think DOS is gone from Windows XP; it's just that XP isn't built on top of DOS. There is still a command prompt in XP, and as a matter of fact, I used it to run emacs, etc., the same way as you would in any previous version of Windows or DOS.

      --
      I am the hub of Jack's digital lifestyle.
    3. Re:DOS Hardly Gone by FrankDrebin · · Score: 1
      • And of course the annoying backslash filename separator
      --
      Anybody want a peanut?
  123. Re:Why does Gates get the credit ? by Anonymous Coward · · Score: 0

    I wonder if the geeks that are so rabidly against Microsoft would be so vociferous if Unix was running on over 95% of the world's PCs ?

    Of course not, you idiot. Half the reason this crowd hates Microsoft is that they are dominating the desktop market with a piece of crap OS. It's adding insult to injury. If "UNIX" had had the funding that Windows had and developed a coherent GUI early on (please, do not mention the horror of X to me), then everyone would be in love with their computers. But no. Gates claims that using XP over Windows ME will save the average user about a week a year because of increased stability. I'd guess closer to two weeks. But even a week a year? Even if we accept this as a "work week" that's still 40 hours a year people spend rebooting because windows has crashed.

    That is why I don't like MS.

  124. Re:Why does Gates get the credit ? by flegged · · Score: 1

    P.S. NT is based on VMS.

    --

    "I think he was truly surprised at how little I cared about how big a market the Mac had" - Linus on Jobs
  125. Working with Gary by keath_milligan · · Score: 3, Informative

    From 1990 to 1993, I had the unique opportunity to work closely with Gary Kildall.

    By that time, Gary was already in the process of separating himself officially from Digital Research (did you know it was originally named "Intergalactic Digital Research"?) to pursue other interests, but was still in touch with the company on a personal level.

    It was a great experience and a wonderful way to start a geek career. I originally was hired to help build and test wire-wrapped prototypes (for an internet appliance no less! in 1990!). Quickly from there Gary recognized my coding abilities and I was writing embedded code within a few weeks of starting.

    Microsoft had just released Windows 3.1 and boy was Gary pissed - apparently Microsoft had intentionally modified Windows since 3.0 to specifically not work on DR-DOS (and yes, that's Digital Research DOS, not "doctor DOS"). MS claimed otherwise, but it was enough to pretty much kill DR - DR-DOS never reclaimed the lost market share (the first killer-apps were beginning to hit big in Windows at that point) and you all know the rest of that story.

    Now for some ancient history - I was always cringe when I hear the oft-repeated story that IBM chose MS-DOS over CP/M for the PC because Gary was out flying his airplane when they showed up or some variation thereof. This is at best a half-truth.

    Gary was already a wealthy man by that point. CP/M was licensed by a variety of manufacturers and DR was doing reasonably well. At that time, there was no reason to think that one single computer architecture would rise to completely dominate the industry - you had Osbournes, Kaypros, Apples, Commodore PETs, and a host of other machines all with loyal followings.

    When IBM was designing the PC, they didn't want to merely license a DOS from another company they wanted to own a DOS. This put Gary off, he viewed CP/M as having a future and he didn't want to completely sell out to IBM. Microsoft had no such reluctance. Microsoft sold PC-DOS to IBM and continued to produce MS-DOS - hence MS-DOS vs. PC-DOS. It was a happy relationship for a while, but we all know the rest of that story. DR did go on to license CP/M-86 to IBM as an alternative, but by that time, it was too little too late.

    Also, I wanted to comment on the story that during a visit with IBM, Gary typed in some code on MS-DOS and made a Digital Research copyright notice appear - I'm pretty sure this is just an industry legend. Gary never accused them of stealing actual code, just stealing ideas.

    1. Re:Working with Gary by unitron · · Score: 2
      If IBM wanted to own a DOS instead of just licensing it, why did they do a deal with Gates that left him free to license DOS to other manufacturers?

      Is there any truth at all that when they tried to talk to Kildall he wasn't around and since they wanted to keep it secret that IBM was developing a PC they wouldn't tell his wife who they were and she didn't feel like bothering Gary for or with a bunch of mysterious strangers?

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

  126. Kinda Tasteless by Cheesemaker · · Score: 1

    Does it bother anyone else that they had a memorial, with "Ave Marie," "Take A Closer Walk with Me," and "Here I Am Lord" being sung, all for an operating system? In NEW YORK CITY? With all the death and destruction nearby, they hold a funeral for DOS.

    On a lighter note, DOS will always be alive in my apartment as long as I keep hording old computer equipment. As it was in the beginning, is now, and ever shall be, DOS without end. Amen. Amen.

  127. Re:Privacy NOW! by lseltzer · · Score: 1

    I sued /. over this in 1982 and won.

  128. Re:Fond C64 Memories by xtremex · · Score: 0, Offtopic

    Am I the only one old enough to remember the Commodore Vic20 or C64? Blew DOS out of the water. Anyone remember load "$" ,8 ,1?
    My first computer ever was a Commodore Pet my uncle bought me for Christmas in 1979. I never touched an IBM compatible until 1989 (in college). Then I was wondering why I was. Then I found Linux in 1993. I was glad.

    --
    If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
  129. Dear god.. could someone get their story straight? by Anonymous Coward · · Score: 2, Informative

    DOS was never present in the NT kernel. That's one of the reasons it's so much more stable than any of the 9x kernels, because they don't have to support old code.

    Cmd.exe, Command.com, and any other variation is -not- DOS. It never was. Not even in DOS 1.0 was Command.com, "DOS". It was -always- just the commandline interface to the underlying OS which was DOS. Most linux users would understand that distinction between the OS and the UI, but for some reason Windows users don't always grasps this. ;)

    Oh, and by the way, Windows XP is mostly just Windows 2000 with a pretty interface.. don't let MS fool you.

  130. NetHack by Anonymous Coward · · Score: 0

    Does this mean I cannot play the 'graphical' version of NetHack anymore? Damn!

  131. DOS is dead by SnapperHead · · Score: 0, Redundant

    Along with Windows, OS/2, BeOS, Amiga, Commodore 64, Apple 2e, FreeBSD, ....

    hehehe, I just had to :) Anyway, I think DOS has been dead for a very long time. Ever since 98 come along, I knew very few people who even knew what DOS was at that point. DOS was good for the time when I was stupied growing up. Even if there was something else, I might not have installed it. I did however install OS/2 once, which became a nightmare. (This machine was a 286)

    The biggest memorys I have back durring those days, was the Wolfenstien days, and doom. I remeber playing over a 14.4k modem against my friend down the street in a death match. Now, I wouldn't even think of doing that, but it was my first multiplayer game.

    The way DOS handled things was a pain in the royal ass. Think Linux 2.4 kernel series has VM problems ? :) With that ol' 640k barrier, you had every single company making there own memory management apps. There was one called Quarter deck, wich also dubbed as a crash protection took kit. Which ended up crashing the machine even more then normal.

    --
    until (succeed) try { again(); }
    1. Re:DOS is dead by doppleganger871 · · Score: 1

      You left out Commodore Vic-20, 16, Plus/4, 128, and the C64DX (or C65). (Obvious C= freak here, eh?)

      Ohwell, I still use my C128, and I'm planning on upgrading the DOS/Firmware in my SCSI HD for it... :)

    2. Re:DOS is dead by SnapperHead · · Score: 1

      Sure, I also left out the Univac, Ataris, trash 80s, and the long list of other machines :) I still have my Commodore 64, and use it once in a while. I think its a great toy, and was a powerfull machine for its day.

      Times have pasted, I moved to DOS, then to Windows and off to Linux. So, its all good.

      --
      until (succeed) try { again(); }
  132. Most Stable Microsoft OS ever by butch812 · · Score: 1, Insightful

    Dos was the most stable OS that microsoft has ever produced

    1. Re:Most Stable Microsoft OS ever by SnapperHead · · Score: 1

      And that STILL isn't saying much :)

      --
      until (succeed) try { again(); }
    2. Re:Most Stable Microsoft OS ever by ProfMoriarty · · Score: 1
      Dos was the most stable OS that microsoft has ever produced

      Uhmmm ... don't you mean the "most stable OS that microsoft has ever purchased and repackaged"?

      --
      Karma? Karma? I don't need no stinkin' karma.
    3. Re:Most Stable Microsoft OS ever by butch812 · · Score: 1

      Well yeah

    4. Re:Most Stable Microsoft OS ever by Anonymous Coward · · Score: 0

      Hah. Stable. That's funny. DOS's answer to a program that crashed was to freeze. Or reboot with no error.

      It offered very little as far as process protection goes compared to WinNT kernels.

      Cool thing about DOS was you didn't have to worry about stability. When it went down you restarted, and the only real data most people lost was whatever was currently running in the prog that dumped.

  133. Re: Do it in Windows - duh! by Andreas(R) · · Score: 1

    The BIOS can be upgraded from Windows!
    For quite some time, Asus has had a free program that checks for BIOSupdates from FTP, and then automatically upgrades when needed.
    It works on all windows versions.

    Therefore; there is no reason for BIOS-makers to use DOS at all.

  134. Incredible bullshit by lseltzer · · Score: 1

    MS-DOS was written from day one for the 16-bit 8088/8086 and the 16-bit version of CP/M didn't come out for many months afterwards. CP/M was only available for the 8080/Z80 at the time, which was not only an 8-bit chip but had a pretty different instruction set.

    So explain to me how they were supposed to lift code from an 8-bit Z80/8080 program and drop it into a 16-bit 8088 program? Don't know? That's because you're full of crap!

    The compatibility between CP/M and MS-DOS extended to similarities in the PSP (Program Segment Prefix, the first 100h bytes of a .COM file) and some other similar program structures, such as File Control Blocks. The idea was to make it easier for CP/M programmers to adapt their programs to DOS.

    Incidentally, the claim in the Byte piece that this had some relevance to the success of MS-DOS is exaggerated. DOS 2.0 was a complete rewrite and introduced both EXE files (pushing developers away from CP/M-compatible .COM files) and file handles, making FCBs obsolete.

    1. Re:Incredible bullshit by calidoscope · · Score: 1
      QDOS was written from day one for the 8086. Tim Patterson at Seattle Computer wrote it in such a way that it would be very easy to translate Z-80 asm code to SCP's 8086 asm code. 86-DOS (the production version of QDOS) had a utility for reading CP/M disks.

      86-DOS version 1.0 had .exe files, which supported relocatable code - .com files were derived from the .com files in CP/M (see note about translation). 86-DOS v1.14 was released as PC-DOS 1.0 and the rights to 86-DOS were sold to the beast of Bellevue.

      IT is amazing at how many people spout off on the history of DOS when they have no clue as to the origins.

      BTW, my first microcomputer was a SCP 8086 system running 86-DOS. Eventually upgraded to MS-DOS 2.0 - which had the beginings of a UNIX like directory structure.

      --
      A Shadeless room is a brighter room.
  135. No DOS, What are you talking about? by ElectricToothbrush · · Score: 1

    It's right there on my start menu, it just says Windows XP at at the top of the command prompt menu instead of MS-DOS.

    1. Re:No DOS, What are you talking about? by snoozerdss · · Score: 1

      Just because it looks like MS-DOS does't mean it is MS-DOS. The same could be said for any command line system (including linux) if you use your method of identifying OS's.

      --
      Snoozer.
  136. That's a good thing by Altern-X · · Score: 1

    I was getting annoying of those people still making DOS apps in 2001, specialy the ones that would be a lot better under a real GUI.

  137. MUNGEBOOT == a DOS by any other name by bSMfh · · Score: 1
    OK, this is about the Microsoft Embedded NT4 product line... but it's still funny.

    In order to get the NT Boot loader on an embedded system, you can use the handy MungeBoot utility, which is provided on the MS cdroms.

    The MungeBoot is a DOS 6.22 boot image, with a batch file, that uses DEBUG to write the boot loader to the C: Drive! That's their sophisticated NT tool to install the boot loader!

    Munge Me, Baby

    DOS will never go away. Never.

  138. I had fond memories of DOS by PRIME · · Score: 1

    It was my first OS and when I mastered it I used it with pride to accomplish a variety of things. I have fond memories of tweaking the autoexec and config.sys files. I have vivid memories of sqeezing as much as I could into upper memory to free up that valuable 640k of lower memory. I remember writing bat files to automate scheduled tasks and most of all I remember running a T.A.G. BBS over a 14.4 modem. DOS was a good OS to cut your teeth on.

    --
    PRIME - Indivisible by anything but ME!
  139. Ya right by Capt.+Beyond · · Score: 1

    Just because it is now a 32 bit executable, and no longer says it's MS-DOS, doesn't mean that it isn't DOS code in there. They just use a 32 bit compiler now, and have had over 10 years to debug it.

    I don't believe a WORD MICROS~1 says. Death of MS-DOS, right...
    If MS-DOS is dead, why can I still run old DOS executables on my win2k machine?

    --
    -- "Perceptions create reality. By changing your perceptions you change your reality."
  140. Re: Do it in Windows - duh! by Anonymous Coward · · Score: 0
    The BIOS can be upgraded from Windows!

    Therefore; there is no reason for BIOS-makers to use DOS at all.

    So how can Linux or *BSD users upgrade their BIOS? At least DOS fits on a floppy.

  141. Fond/No So Fond Memories of DOS by gsmraxe · · Score: 1

    I used dos for many years, ran a dialup bbs in the 619 (Metal Edge), it had it's limitations, non-multitasking except for Desqview and having to use QEMM for memory management (which crashed sometimes), but it was fun writing batch files for tossing mail, getting files and running my own message net (MetalNet). LORDNet, BRENet etc.,
    <P>
    Now I run my bbs under Linux, (Mystic bbs software) which runs so much better, multi-tasking it runs just like a DOS based bbs but a hell of a lot more functional. BASH scripts are more functional than batch files, I can run LORD, BRE, Clans under DOSEMU now and they're a little slow, but not too bad for a ten node board =]<P>
    telnet://metaledge.darktech.org<BR>
    If your curious =]

  142. Bill can't get no respect... by DavidBrown · · Score: 2

    Wow. After years and years of "Windows is a buggy kludge running on top of DOS", Microsoft finally kills the beast and exorcises the 16-bit code from Windows.

    So what happens?

    "We miss DOS, and Microsoft was STUPID to get rid of it!"

    Micro$oft can't do anything right, can they?

    Let's look at this realistically. How many "ordinary users" out there are still running off the command line with computers that meet XP's installation requirements. Four (more or less). That's not enough reason to keep DOS alive.

    Besides, as I understand it (disclaimer - I have no personal experience with this), XP will run DOS programs. As soon as I get XP (when Dell gives it to me) I'm going to attempt to install WordPerfect 5.1 for DOS. If that works, then those four users will be satisfied, and I will too.

    --
    144l. ph34r my 133t l3g4l 5k1lz!
    1. Re:Bill can't get no respect... by Anonymous Coward · · Score: 1, Insightful

      Listen very carefully, I'm only going to say this once:

      1. There is a CLI in Windows XP Professional (I know, I bought it, I'm running it at home).

      2. The CLI in Windows XP is not DOS, it's Windows XP, based on the NT codebase. The INTERFACE IS NOT THE OS!!! The CLI is just an alternative way of interactive with the OS.

      3. In Windows 95/98/SE/ME, on the other hand, everything was overlayed on DOS, partially explaining the frequency of the blue screen of death.

      4. In Windows NT/2K/XP, there is no DOS layer underneath Windows.

      5. The story is about the fact that the Windows 95-ME line has been ended with the advent of Windows XP Home, the first home consumer edition of the NT code.

      In Windows 3.1, one would boot into DOS, then start a program called win to get into Windows; you could add it to your autoexec.bat to autostart it, but could easily interrupt it. In Windows 95, one would boot into DOS, which would then autostart into Windows; the only way to prevent the autostart was to go into the safe mode dialogue (a DOS dialogue) and select a choice to start into DOS, or to select "Restart in MSDOS Mode" in the Shut Down menu. In Windows NT/2K/XP, there's simply no DOS layer. Everything is Windows code, the GUI, the CLI, everything. All the old DOS code has been ripped out, and backwards compatibility to programs written for DOS has been achieved with new code. So that's what the story is about - the end of the DOS/Windows line of code and the application of the Windows NT line of code to Home operating systems.

  143. Baffling absence of fact by Anonymous Coward · · Score: 1, Interesting

    I guess not a single one of the readers and posters here has actually used or seen a Windows XP system. Command line access has not gone away. Simply go to Start, Run... and type in cmd.exe, voila DOS lives. Of course you cannot access NTFS or the new encrypted file system from a DOS boot floppy... But you can make a DOS boot disk from XP. It is part of the OS.

    It is so typical of this crowd at slash dot that you go on for pages and pages re-iterating material that is quite simply not accurate.

    Bill Gate's point was that there is no more DOS code underlying the OS like in Windows 9x/Me. It is all the newer 32-bit OS. He never indicated that the command line was going away. In fact the Windows Script Host is the most powerful scripting runtime you could want!

    You guys are too eager to be angry and you don't even understand the issues.

    1. Re:Baffling absence of fact by andkaha · · Score: 2
      I guess not a single one of the readers and posters here has actually used or seen a Windows XP system.

      I'm sitting in front of one right now (the people I'm working for are MS slaves and won't even install security updates "until Microsoft tells us to do so").

      My first impression of WinXP?

      Teletubbies!

      --
      It's 11pm, do you know what your deamons are up to?
  144. XP has "headless"-support by rainer_d · · Score: 2, Informative

    According to various articles on the net, MS will ship a version of XP that can run without a gfx-card.

    IIRC, they have extended vt100 for that...

    So, the cmd-line will be around for some time.

    --
    Windows 2000 - from the guys who brought us edlin
  145. DOS Based Windows by linebackn · · Score: 5, Informative

    On occasions I have had to explain to people which versions of Windows really run on top of MS-DOS. It is somewhat confusing because MS changed all the names around. Here is a list that might be of interest here.

    The following versions of Windows run on top of MS-DOS:
    Windows 1.x
    Windows 2.x
    Windows 3.x
    Windows 95 (Bundled MS-DOS 7.00 that is no longer sold as seperate product)
    Windows 95 OSR2 (Bundled MS-DOS 7.10)
    Windows 98 and 98SE (Bundled MS-DOS 7.10)
    Windows ME (Bundled MS-DOS 8.00, but exiting to MS-DOS is now forbidden)

    The following versions of Windows do not run on top of MS-DOS:
    Windows NT 3.1
    Windows NT 3.5x
    Windows NT 4.0
    Windows 2000 (NT 5.0)
    Windows XP (NT 5.1)

    1. Re:DOS Based Windows by Anonymous Coward · · Score: 0
      You total fucking whore!Shame on you and on those who modded you up!

      Any half-decent teccy reading this article should already know the info you've posted...I'm obviously in the wrong job.Perhaps I too should post realms of fucking obvious material to get my karma improved.

    2. Re:DOS Based Windows by arjennienhuis · · Score: 1

      Win95 does not run on top of dos.
      A Call to ReadFile() is not converted to some sort of int21.

      Win95 is only loaded after msdos, the same as loadlin.exe loads linux.

      the bootloader of win95 first loads msdos which starts win.com which loads the vmm. The only reason this is done, is for backwards compatability. Like loading your ms-dos sound card drivers, and starting scandisk or ndd.

      with winME, the bootloader loads the vmm immediately, and you get shorter boot time.

  146. Win2K has name completion... by hawkestein · · Score: 2

    I can't be the only person who gets annoyed at humongous paths like:
    C:\Documents and Settings\Administrator\Start Menu\Programs\Microsoft Office Too


    You aren't the only person, but Win2K has filename and directory name completion. To turn it on, add the "/F:ON" flag when you run cmd.exe. Then, Ctrl-F does filename completion, and Ctrl-D does directory name completion. Don't ask me why the couldn't just use Tab like bash does, but it sure helps navigating those large directory names.

    --
    -- Will quantum computers run imaginary-time operating systems?
    1. Re:Win2K has name completion... by JackDeth · · Score: 4, Informative

      Change this registry setting:
      "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\Completetion Char"
      to 0x09 and TAB will work, even without /F:ON.

      cmd /? will give you more information if you care.

    2. Re:Win2K has name completion... by Yer+Mom · · Score: 1
      If you use the Win2K version of TweakUI, you can set Tab to be the completion character.

      Alternatively, the keys CompletionChar and PathCompletionChar in HKEY_CURRENT_USER\Software\Microsoft\Command Processor are REG_DWORDs containing the ASCII value of the completion char - 9 in this case.

      --
      Never mind Spamassassin. When's Spammerassassin coming out?
  147. Rumors of passing on are vastly overrated by ackthpt · · Score: 3, Interesting
    No MS_DOS prompt is just one more reason I wouldn't move to XP, not that I even plan to. Still on 98 and I've been re-discovering some of my favorite old software and games from 386 days (remember Scorched Earth?) Much of these require the DOS shell, even if you have to fool around with slowing the computer or something.

    Can't expect old dogs like me to leap on the bandwagon just because there is one. Maybe someone will write an MS_DOS emulator for XP ;-)

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:Rumors of passing on are vastly overrated by generic-man · · Score: 1

      I use Windows XP.

      I have Scorched Earth.

      It works.

      --
      For more information, click here.
    2. Re:Rumors of passing on are vastly overrated by ackthpt · · Score: 1

      Please elaborate. How do you run an MS_DOS application under XP? Sounds like MS_DOS is still there and a minor tweak of a shortcut should be able to put MS_DOS on the desktop.

      --

      A feeling of having made the same mistake before: Deja Foobar
    3. Re:Rumors of passing on are vastly overrated by Anonymous Coward · · Score: 1, Informative

      If an MS-DOS program doesn't work when you run it, you can set MS-DOS compatibility mode in the program's properties (right-click, properties, compatibility). It's *like* running a DOS emulator, except that you don't have as much overhead as you would with emulation, because it's just tricking the program into thinking it's running in a DOS environment (a little hard to explain to someone that doesn't understand NT without going into technical detail). Basically, in NT4 (not sure exactly how much this changed in 2k and XP), NT runs ntvdm.exe, which is the NT Virtual DOS Machine, which encapsulates the DOS app, ntio.sys and ntdos.sys, and virtual device drivers, which then talks to the 32-bit NT environment. One virtual machine is run for each DOS app, so if a DOS app fails, it won't take down the OS or other DOS apps running at the same time, the virtual machine just shuts itself down and the OS frees it's address space.

    4. Re:Rumors of passing on are vastly overrated by corky6921 · · Score: 2

      Actually, Windows 2000 and Windows XP have compatibility layers that let you run a program under "DOS" or "Windows 98". It's basically an emulation layer. It comes built-in with Windows XP; for Windows 2000 it is a free download. More information can be found at Microsoft.com.

      And as the other guy said, Scorched Earth does run on Windows XP. I'd recommend the upgrade just to make your system more stable -- what's the point of being able to play old games if your system crashes three times a day?

    5. Re:Rumors of passing on are vastly overrated by ackthpt · · Score: 1

      Thanks! That's actually a pretty helpful explaination. I worked on an NT4 workstation for 3 years and some of that rings a bell. The shell was quite a bit different than it is on w95/98, including directory listings, but I usually had a couple of them going with ftp sessions to Linux/Solaris/HPUX boxes. NT4 was actually pretty cool and only fubar'd a few times, but when it did, it could do some real damage, i.e. lost files/apps/configs and some mangelage.

      --

      A feeling of having made the same mistake before: Deja Foobar
  148. Good subject for your post :) by AtrN · · Score: 2
    When the 8086 was released Intel supplied an 8080 assembler translator. The instruction set was obviously not that different. Many of the first IBM PC programs - BASIC, Wordstar, etc... were simply the CP/M versions run through the translator and then patched up to make them actually work. MS-DOS 1 was like my hacked up CP/M system with the renamed commands and a bit of Z system thrown in (but not enough). The work in MS-DOS was in the CCP - COPY and DEL, woohoo!

    I don't know where you get this "CP/M compatibility" thing, it was pretty much a direct copy and some even say it was a direct copy thanks to the Intel assembler translator and CP/M source access. I recall the old QDOS ads in the top right corner of some mag I was reading at the time, may have been Kilobaud or maybe something a little more techie, can't recall).

    Oh, Kildall said something about the use of '$' as the sentinel in the output call (9) as being special and that only he could explain it. Anyone know something about this?

  149. The last of Gates's own code? by tibbetts · · Score: 1

    With the passing of MS/DOS, I wonder whether any code actually written by the World's Richest Man himself is still part of the operating system. I once picked up a book at a thrift store called Programmers At Work . I got it expecting a blank book, but I was amazed to discover that not only did it have interviews with several programming heavyweights circa the mid-80s (like Dan Bricklin, etc.), but it also had actual code samples from many of the authors. It even had a few pages from Gates's original implementation of MS-DOS, and you'd be amazed at how clean and well-commented the code is. I won't vouch for the algorithms and design, but the coding itself was far cleaner than anything that I've ever seen in an open-source project.

    --
    :wq
    1. Re:The last of Gates's own code? by AsylumWraith · · Score: 1

      That's nice, but Gates didn't write it. QDOS was bought from another developer (forget his name) for 50 grand, and renamed MS-DOS.

      Least that's the way I always heard it.

  150. it's legacy remains, better than ever. by siphoncolder · · Score: 2, Interesting

    even though DOS is pretty much obsolete, i'd like to clarify to all of you that MS has ***NOT*** removed the command prompt from XP.

    Start -> Other Programs -> Accessories -> Command Prompt.

    not only that, but remember when you upgraded to winNT/2K, and couldn't run those old DOS apps that you loved so much?

    XP returns that to you. when i discovered that this was supposed to be the case, i quickly installed one of my old favorites, "Stunts" (by Broderbund software), and found myself happily cruising the old tracks in my F1 racer. since then i've loaded on all my old classic *QUALITY* DOS games (like Doom, id software) and had a rollicking good time with XP.

    (sure, it sounds like it should violate NT's HAL, but try it for yourself. it works, hasn't crashed my system, and by god - it's glorious to have those games back again.)

    --
    i'm amazed that i survived - an airbag saved my life.
    1. Re:it's legacy remains, better than ever. by kawaichan · · Score: 0

      That's different than DOS you see in Win9x here is a rundown on Win9x BIOS DOS SHELL (WINDOWS) For NT, it's BIOS NT (XP) Dos in XP is simply a program, not an OS and that's why some programs won't work on XP or NT

      --

      kawai
    2. Re:it's legacy remains, better than ever. by fataugie · · Score: 1

      Well, I know one thing......Civ I still runs in DOS on my W2K box. Now, if I could only get my hands on Civ III out today, that would be sweet.

      --

      WTF? Over?

  151. General Failure reading drive C. by acq3 · · Score: 1

    Who's General Failure, and how did he get access to my hard drive?

  152. But DOS lives on... by sting3r · · Score: 2
    ...at least in niche applications. For instance, you need to use DOS to get digital satellite service for free. And the FreeDOS project lives on.

    Just because Microsoft stops producing it doesn't mean it's dead. My office still uses MS Winword 1.1 on some PCs because it works and that's all they need.

    -sting3r

    1. Re:But DOS lives on... by Gizzmonic · · Score: 1
      For instance, you need to use DOS [dsstester.com] to get digital satellite service for free.

      What about pitou? Runs in linux, doesn't tie up your whole machine. Plus, you can share it over the internet. It's buggy now, but that just means it needs more help..

      --
      (-1, Raw and Uncut is the only way to read)
  153. What happens if by 42forty-two42 · · Score: 1

    you accidentally delete some critical GUI file? ;) [root@42.42.42.42 /]# exit

  154. Dell sux by Anonymous Coward · · Score: 0

    and is only lused by cancerassholes.

  155. What about Bob? by fataugie · · Score: 1

    I don't see any mention of that revolutionary MS Bob system that was going to make life worth living. Am i the only one who remembers when Egghead had stores, this was a featured software of hte week thingie in one of their fliers. I remember saying to the wife, that it was a stinker. I think the assistant was Bill himself if I remember correctly.

    Ahhh the good old days....

    --

    WTF? Over?

  156. Fond memories by 3ryon · · Score: 1

    I remember the joy when MS-DOS 4.0 came out and I was finally able to partition my entire 40 megabyte hard drive into one partition (DOS 3.x had a maximum limit of 20 Meg per partition).

  157. WinXP has name completion by default by throx · · Score: 2

    Run cmd.exe and tab works for filename completion just fine. There's a registry setting to enable this in NT3.51 and above but it escapes me at the moment.

    Of course you can do wildcards with 'cd' as well (cd \pro* will usually get "Program Files"). cmd.exe is actually a lot better than the original DOS command prompt - you just have to take the time to figure out the syntax required. Naturally it is nothing near bash though...

    --

    Fear: When you see B8 00 4C CD 21 and know what it means

    1. Re:WinXP has name completion by default by kuhneng · · Score: 1

      Want to see something REALLY frightening on Windows 2000? (and possibly other versions, but I've never tried)

      Make a directory. Make two files, such as:
      one.html
      two.htm

      Type del *.htm

      Yup, that's right, they're both gone. Remember that feature where Windows allows you to use 8.3 versions of file names?

  158. Re:Fond .pas memories by buckeyeguy · · Score: 1
    I wore out the manual on Turbo Pascal in those days (ca. 1984? maybe 85)... a full language with built-in editor, all in a 49K .COM file! And the programs ran great, too.

    I've been tempted to load DOS on a modern machine (say a cheaper 800Mhz Duron) and see how the old programs fly without Winblows holding them back. But then I think of all the hacks that were needed (the concept of 'high memory', HIMEM vs. 'expanded memory', EMM386, the horrors of setting up a CD-ROM drive, faux multitasking with Desqview, and a host of others) and I say mmmm, nope, been there done that, I like what I have now better. Ultima II in CGA graphics was cool for me back then, but I'd rather beat up on BG2 in full glorious color and sound, thanks.

    --
    I'd have a personalized plate on my car, but "toxic bachelor" won't fit into 7 letters.
  159. DOS is dead.. Long live DOS! by Ogerman · · Score: 2

    FreeDOS, gcc-dos, dosemu, among others...

    The great thing about DOS was that it wasn't much of an operating system. (-:

  160. Legacy embedded apps by matt_martin · · Score: 1

    As much as it will drive some people nuts, the fact remains that many systems contain embedded DOS PCs. Every tester in my lab has one!

    Would be great to change them over to Linux, but nobodys gonna invest the NRE. And FWIW, they are quite stable with such a simple OS.

    Is Bill saying he doesn't give a rat's arse about these types of customers?

    Its probably way off the MS product map, too little sophistication for WINCE...
    The irony is that these are relatively high margin products!

    --
    Lurking in the desert
  161. Time to switch to a Real OS... by Anonymous Coward · · Score: 0

    Now it's time for Windows users to grow up, quit whining, and switch to a *Real* OS with a command line: Get a Mac with OS X!

  162. You never actually coded this stuff, did you? by lseltzer · · Score: 1

    Are you seriously suggesting that a code translator could work with operating system code? That the "display string" call, which like most of MS-DOS uses BIOS calls on the PC that don't exist for CP/M, would be a simple matter of translating 8-bit 8080 code to 16-bit 8088 code? For an application I can see a translator maybe doing half the job, for an OS what you suggest is a joke.

    1. Re:You never actually coded this stuff, did you? by Nater · · Score: 2

      For an application I can see a translator maybe doing half the job, for an OS what you suggest is a joke.

      Remember, though, that this "operating system" was pretty much a joke too. Its applications didn't run in an environment any different than the OS's. No virtualization, no interruptions, nothing. I think that a translator that did a halfway decent job with application code would have done just as well with OS code, simply because on that particular platform, at that particular juncture in computing history, there was no difference between the two.

      --

      I like to play children's songs in minor keys.
      "We're all sons of bitches now." --J. Robert Oppenheimer

    2. Re:You never actually coded this stuff, did you? by Anonymous Coward · · Score: 0

      CP/M machines did have a BIOS .. judging by IBM DOS, I would gues that the IBM BIOS was very similar to something that already existed.

  163. You Never Can Tell by Erris · · Score: 1

    It was a sweet interface
    and all the old folks wished it well
    but you took that upgrade
    and now you fell like hell.
    The CLI you so loved, isnt there
    It was bad for Bill Gates
    and now its gone away.
    It just goes to show,
    you never can tell.

    --
    DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
  164. What does "Dead" mean? by sharkey · · Score: 2

    Is DOS dead as in gone, kaput, never to be seen again in Redmond? Or is it gone, no longer there as in a major marketing point for Windows 95?

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  165. Even Bill Gates cannot answer by NZheretic · · Score: 1

    From memory the actual quote was

    "Ask Bill why the string in function nine is terminated by a dollar sign. Ask him, because he can't answer, only I know that." - Gary Kildall

    1. Re:Even Bill Gates cannot answer by Anonymous Coward · · Score: 0

      Ask the guy who wrote QDOS. In any case so he copied the API - big deal. Linus copied the API from a Unix manual for Linux and nobody is complaining he stole code.

  166. Re:More Info,they even have a GUI Interface for it by 42forty-two42 · · Score: 1

    And their webpage has a little tiny WinXP logo on its ad frame...

  167. Re:Fond C64 Memories by Anonymous Coward · · Score: 0

    Until I used an IBM clone, I thought it totally natural that one had to learn a programming language to talk to the computer, and that the programming language, for all intents and purposes, was the user interface and operating system. DOS blew my mind because it was nearly as difficult as BASIC to use, except that there was less documentation, and it was 1/10th as powerful in actually getting the computer to do something. It's a true wonder of marketing that DOS-based systems ever got off the ground.

  168. The truth about windoze by DEATH+AND+HATRED · · Score: 2, Funny

    Windoze98 is just a 32 bit extension of a 16 shell designed for an 8 bit o/s written for a 4 bit procceser by a 2 bit company that cant stand 1 bit of competition!

  169. Linux? Present? by Anonymous Coward · · Score: 0

    Linux is based on 1970s technology. Try again.

    1. Re:Linux? Present? by ocie · · Score: 2

      Microprocessors are based on 1940s technology, what is your point?

      --
      JET Program: see Japan, meet intere
  170. Pathnames by crisco · · Score: 2
    I learned the power of *nix when I ran out of room on the Linux partition on a dual boot machine. I cleaned off one of the unused Windows Partitions, formatted it, moved /tmp and /var over, set up my symlinks and suddenly had plenty of space.

    Sure, I can probably move My Documents and /Windows/Temp without rebooting and too much application reconfiguration but what about /Program Files? When I get low on space again and decide to move /usr/local or some such thing it will be transparent. I'd have to reinstall the applications under Windows (and thats as much an application issue as an OS issue).

    --

    Bleh!

    1. Re:Pathnames by morpheus800e · · Score: 1

      Microsoft's TweakUI has the ability to change the location of /Program Files. I don't know if that will fix the applications, but if you have Norton Utilities, run WinDoctor, and it will be able to fix registry entries and whatnot to point to the new location.

    2. Re:Pathnames by Anonymous Coward · · Score: 0

      With Win2k/XP this is very simple.
      1.) Plop in your new harddrive
      2.) Use Drive Manager to mount the drive as a folder, not a drive letter

      there ya go, C:\Program Files is actually your new hard drive.

    3. Re:Pathnames by Danse · · Score: 2

      there ya go, C:\Program Files is actually your new hard drive.


      I think you skipped something there. Does it automatically move the contents of the folder to the new drive? Does it screw up any of the registry entries for your apps?

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
    4. Re:Pathnames by STSeer · · Score: 1

      you can copy the files over during the move and since the path doesn't change none of the reg entries are affected

  171. "He's not really dead, as long as we remember him" by Sloppy · · Score: 2

    Maybe the code is dead, but the API lives on, and will still be around for decades. Even to this very day, I am still getting paid to maintain DOS apps. Nobody actually runs them under DOS, but nobody's gonna pay to have them rewritten, either.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  172. Worst thing about losing DOS is... by Anonymous Coward · · Score: 0

    I won't be able to use edlin anymore! That editor rocked! The power! The ease of use!

  173. anti-Microsoft conspiracy theories by sheldon · · Score: 4, Interesting

    One of the interesting things about most of the anti-Microsoft conspiracies is that they all involve settlements covered under Non-Disclosure agreements. This way there is no way to validate the authenticity of the story.

    It makes it rather convenient.

    At the time there was no secret that the new MS-DOS was very similar to CP/M-80. CP/M is what people were used to using and seeing, and so Patterson designed his new OS for 16 bit processors to behave similarly. But there were also pieces of functionality that arrived into MS-DOS that were similar to Unix.

    It's also entirely possible that it included some similar code. CP/M-80 BDOS could be disassembled and carried in your briefcase. It only took up around 5-7K of RAM and wasn't that complicated at all.

    Besides, if MS-DOS had really been a copy of CP/M, wouldn't it have also implemented the PIP and STAT commands?

    But the real question is... does it matter?

    From everything I've read of Gary Kildall and Digital Research, already at the time IBM first approached them the company was too big for Kildall's liking. He was not a manager, he hated it. But he was also a control freak and couldn't stand someone else running things for him.

    One story I read indicated that he often would walk around the office building afraid to go in, and that at one point he even offered to sell the whole thing to a friend of his for $50,000.

    One of the realities is that some people are willing to grab success, and others aren't. There are a lot of people in this world who purposefully miss an opportunity because they are unhappy or uncomfortable with assuming the responsibility it might entail.

    Kildall was one such person. Obviously Bill Gates is not.

    It's that difference in personalities that is really the secret behind Microsoft.

    Personally, I know that I'm a lot like Gary Kildall in that regard. But knowing this I also try to not be resentful when I pass up an opportunity.

    1. Re:anti-Microsoft conspiracy theories by NutscrapeSucks · · Score: 2

      One of the interesting things about most of the anti-Microsoft conspiracies is that they all involve settlements covered under Non-Disclosure agreements. This way there is no way to validate the authenticity of the story.

      This Kildall Magic Keystroke story is always one of my favorite Internet legends. It's sources are that "MS the Company" page (from a guy with an obvious chip on his shoulder), and a bunch of old pre-Deja Usenet posts which only exist in my head :) Anyway, the story is not just out of the blue.

      The folklore side went a little futher -- The QDOS guy actually wrote the OS, but was running out time so just he translated some of the CP/M utility software. Something obviously had an easter egg in it .. maybe even DEBUG itself.

      Soon after IBM started pouring money in for the substantial DOS 2 rewrite.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    2. Re:anti-Microsoft conspiracy theories by mOdQuArK! · · Score: 1
      Besides, if MS-DOS had really been a copy of CP/M, wouldn't it have also implemented the PIP and STAT commands?

      Ack - PIP! I remember trying to use that to test my 300 baud Hayes Smartmodem (Got the modem before I got a term program :-)

  174. DOS is still useful... by tomknight · · Score: 2

    Amazing, but true. How do you find out the graphics card without opening the box? Using:

    C:\>debug
    -d c000:000

    Gives me:

    U.@..7400.......
    ........D..R.RIB
    M VGA COMPATIBLE
    BIOS. ..f$.....
    .....STB Nitro 3
    D (GX) BIOS. Ver
    . 1.3..(C) 1996
    STB Systems, Inc

    Hey, I still use this on unknown dodgy old boxes!

    Tom.

    --
    Oh arse
  175. Doomed to a lifetime of right click hell by philglanville · · Score: 1

    Try setting the read only attribute on a bunch of files in different subdirectories using the GUI...

    Now try attrib +r *.* /S and tell me that DOS is redundant...

    1. Re:Doomed to a lifetime of right click hell by Legion303 · · Score: 1
      Of course doing it in dos is faster and easier, but Windows (Win98, at least) asks you if you want to apply attrib changes to just the toplevel or all subdirectories and files.

      -Legion

    2. Re:Doomed to a lifetime of right click hell by Anonymous Coward · · Score: 0

      Also, what if you want to delete all of the
      files that end in .VXD, for example. (just an
      example)

      IN DOS:
      c:\windows\system> del *.vxd

      Now do it in Windows.... YOU WILL BE THERE
      FOREVER holding control and clicking on
      each file!!! I like the idea of running
      Windows as a program under DOS. I guess they
      could have improved DOS and made it a 32-bit
      operating system. That would have kicked ass!
      Then, on a rare occasion, if you wanted to
      run an old 16-bit application, it would have
      to be emulated, or you just boot into DOS 6.22

      Paul

  176. XP Eulogy, Xbox? by NSupremo · · Score: 1

    I expect to see condolences for each of these products within 4 months.

    --
    http://en.wikipedia.org/wiki/2004_U.S._Election_co ntroversies_and_irregularities
  177. Re: the meaning of share by greed · · Score: 1
    One nit:
    .../share/... - files that are architecture independent.
    That is, the sharing is across architectures, not users. All of those directories are shared across users (read-only except for /tmp, of course.)

    I have share/bin, share/man, share/lib, share/include; Korn and Perl scripts go in bin, Perl libraries and modules in lib, and so on. (I'm not talking about /share, I've never seen that on systems I work with.)

    The idea was, in a dataless or diskless environment, you'd have one / per client, one /usr per architecture, and one /usr/share overall. Of course, the UNIX vendors never agree on anything, so /usr/share was either empty or misused.

    I've had "make install" put shared objects and binaries in the "architecture independent prefix" directory; it is clear this concept really hasn't sunk in. But it is very useful when running a big server with lots and lots of tools and apps on it.

    And before anyone picks on UNIX's path, could someone examine their %Path% on a reasonably well-populated Windows NT install and tell me what you see?

  178. Last Command Prompt? by Artana+Niveus+Corvum · · Score: 1

    Maybe Windows doesn't run on top of DOS anymore (I am tempted to say that I have my doubts ;-) ), but at least in XP they brought back the ability to create a DOS bootdisk! (a feature that I wanted to repeatedly kick Win2k for not having....)... maybe I'm being redundant, who knows?

    --
    -----------------------------------------
    Remove the Greed which plagues mankind.
  179. Don't tell Novell users DOS is dead..... by Newer+Guy · · Score: 1

    Because Novell uses DOS to run a very powerful, superbly reliable networking protocol.

    1. Re:Don't tell Novell users DOS is dead..... by Carnivore24 · · Score: 0

      That would be JetDirect?? Am I correct??

  180. Re:Fond C64 Memories by Anonymous Coward · · Score: 0

    Good god. One of those melvins who preferred the Commie!

    Sheesh, I though you all died out, or were lost forever at that disaster at the 'Smurf collectables swapmeet' in Topeka, Kansas, 1993.

  181. hier(7) by Mad+Marlin · · Score: 1
    You've been running to much redhat...

    I most certianly agree. See hier(7) for a good explanation of how the filesystem hierarchy is supposed to look.

  182. Ha! You are WEAK. by Kasreyn · · Score: 2

    And clearly have never used DOS. The actual error message, the bland, high-handed, and uncaring epithet of the insane god of your reality, is, and I quote:

    "Bad command or file name."

    (bows down in worship)

    -Kasreyn

    --
    Kasreyn: Cheerfully playing the part of Devil's Advocate to hairtrigger /. flamers since 1999.
  183. Funny you should mention that... by aidoneus · · Score: 2

    I was doing some research this morning and came across this article in Smart Computing from November of 1994, seven years ago.The article? "Is DOS Dead?" It almost sounds just like the eulogy for DOS that this /. post is about.

  184. Retard.. how the fuck is this "Insightful" by Anonymous Coward · · Score: 0

    Oh wait, it's better to have /bin for programs, and /usr/bin for programs, and /sbin for, uh, programs . . . some of which depend on files in various subfolders of /lib (or was it /usr/lib?) . . . much cleaner.

    Then you clearly have no understanding of WHY this is done. Let's explain REAL SLOW for yet another Slashtard.

    "bin" is short for "binary."

    "sbin" is short for "system binary"

    They're placed in different trees based on relevance to a particular system. Sames goes for libraries.

    If that's stupid, then why does Windows put some programs in "Program Files", some in "Program Files"/Accessors, then in "Program Files"/Plus!, others in /winnt, others in /winnt/system, still others in /winnt/system32, then others in /winnt/system64, then others in /winnt/...

    That sickening mess DOESN'T make sense. Would anyone else care to elaborate for the anti-*nix troll?

    1. Re:Retard.. how the fuck is this "Insightful" by Anonymous Coward · · Score: 0
      They're placed in different trees based on relevance to a particular system. Sames goes for libraries.

      You've got a whole shitload more explaining to do, moron. Let's hear you rationalize /usr/* vs /usr/local/*. And what is /usr/local/sbin, if sbin is a "system" file? And then, cite even one distro that follows these imaginary rules vigorously.

      If that's stupid, then why does Windows put some programs in "Program Files",

      Oh, brilliant, the "but MS is stupid too" argument. I bet you also compare yourself to Down's Syndrome kids when defending your own idiocy.

    2. Re:Retard.. how the fuck is this "Insightful" by lars_stefan_axelsson · · Score: 1
      Well, sbin is both for "system files" i.e. binares that absolutely must be there for the system to function AND for system administration binares (of programs) that are considered a must for running the system. These are often one and the same, ifconfig for example is typically run by the boot scripts to configure the network interfaces, but can be used by root to bring then up/down temporarily, do fault finding, and a host of other things.

      Hence the /usr/local/sbin is for the latter, i.e. administratitive commands that the user typically has no business running (or even cannot run due to insufficient privileges). A typical UNIX installation includes the 'sbin' directories in root's path, but not the path of ordinary users.

      Now, as for /usr/local itself, the origins if I'm not mistaken is for files that are "local" to the installation (not necessarily the workstation, I've seen /usr/locals long before workstations were in vogue). In a Redhat Linux system this is often translated to /usr etc is for files handled by RPM, i.e. prepacked binaries, that are part of distributions. More informally managed packages, or applications that you've developed yourself goes into /usr/local. You untar into /usr/local/src, configure, make and make install from there, and the files end up in /usr/local/{bin, lib} etc.

      You know, these standards often make sense, and were developed in a time where you could actually OAM a machine, apart from the three 'R's of MS sys admin (reboot, reboot, reinstall). With UNIX you still can.

      --
      Stefan Axelsson
  185. Should have followed the OS/2 model by yerricde · · Score: 2

    Which would have turned it into Windows, surely?

    Yes, the GUI would have turned into Windows. Microsoft should have followed through with the OS/2 plan (a powerful OS with task and memory management, support for networking, a CLI interface, and a GUI on top that could be shut off to save resources). Thus, workstations would run "Windows 2000" on top of "DOS 2000" (like the other guys run "XFree86 4.1 with KDE 2.2" on top of "Linux 2.4"), and servers could shut the Windows for more performance.

    Did Sony call the PlayStation 2's operating system "OS2" by analogy with PS/2 -> OS/2 ?

    --
    Will I retire or break 10K?
  186. So long to crap by Anonymous Coward · · Score: 0
    I was doing Unix(tm) shell scripting long before I had to deal with MS-DOS.


    I still hate DOS for all the things that it can't do.

  187. Microsoft Bob. by saintlupus · · Score: 4, Funny

    I don't see any mention of that revolutionary MS Bob system that was going to make life worth living. Am i the only one who remembers when Egghead had stores, this was a featured software of hte week thingie in one of their fliers. I remember saying to the wife, that it was a stinker. I think the assistant was Bill himself if I remember correctly.

    When a friend of mine was working at Computer City, they had the launch party for Microsoft Bob. The store had preordered something along the lines of 7 thousand copies to meet the anticipated demand. They sold four.

    Not four thousand. Four.

    And then they were all returned within a week.

    (Adding insult to injury, the mylar balloons with the Bob logo were floating around the barnlike interior of the store and setting off the security alarms for weeks.)

    Truly a stellar product, eh?

    --saint

  188. The end of the DOS Prompt. by petepac · · Score: 1

    When they outlaw the DOS-Prompt, only Outlaws will have DOS-Prompts!

    --
    >> Practice Safe Hex
  189. Re:Fond C64 Memories by Anonymous Coward · · Score: 0

    I still have a working PET. And use an Amiga every day. And Unix at work.

    ac

  190. I don't think so. by FattMattP · · Score: 2

    If it's the end of the DOS era, then how come everything in the WINDOWS\system32 still has 8.3 character filenames under WinXP?

    --
    Prevent email address forgery. Publish SPF records for y
  191. Just wasted the morning playing Warcraft in DOS. by Anonymous Coward · · Score: 0

    Before even starting windows this morning I wasted a few hours playing Warcraft II. I still use IBM PC-DOS 7.0 and Windows 3.11 because it remains to this very day the best OS ever delivered for the PC. I would not trade it for linux if a million dollars were thrown into the equation.

    While I have tried to figure out what forces lead developers to deliver the perversions and abominations of Windows and Linux, nobody has been able to reach the simplicity and ease of pure DOS dispite its technical shortcomings.

    DOS *IS* THE BOSS OS!!!!

    Please e-mail me if you think you can help me develop the next DOS. =)

    alangrimes@starpower.net

  192. Eulogy: Linux by Anonymous Coward · · Score: 0

    Yes people its time to admit it and move on with your pathetic lives

    Linux is dead
    This pet project of Alax Cox, Linus Tolvad was official declared as obsolete by the Lord of all Bill Gates. The future is xp, those who choose to deny this, will face the same conclusion and extiniction that Linux is facing now....

    ONE OPERATING SYSTEM shall bind them all.................

  193. Does this mean that XP lacks the 16-bit subsystem? by Animats · · Score: 4, Informative
    NT, in its various forms, has a "16 bit subsystem" for running 16-bit programs. (In NT 3.x, you could choose not to install it; it was a separate module.) Was the 16-bit capability removed from XP? Finally? Please?

    The thing that looks like an MS-DOS window under NT isn't. That's a 32-bit command line interpreter that runs on top of NT, looks vaguely like DOS, but has no involvement with the 16-bit system.

  194. Use SUBST! by alansingfield · · Score: 1
    Just use SUBST to create a virtual drive for your desktop:

    subst l: "c:\documents and settings\Administrator\Desktop"

    I put this in my Startup folder, then work from my L:\ drive.

  195. In the Beginning... by Webmoth · · Score: 4, Funny

    ...there was QDOS. This stood for "Quick and Dirty Operating system."

    Then, Microsoft bought it, got rid of the "Quick" and kept the "Dirty."

    That left us with MS-DOS.

    --
    Give me my freedom, and I'll take care of my own security, thank you.
  196. Comparing Gary Kildall's personality to Bill Gates by NZheretic · · Score: 1

    One Eulogy that closest to the real Gary Kildall
    http://www.ece.umd.edu/courses/enee759m.S2000/pa pe rs/wharton1994-kildall.pdf

    In comparison...

    In the Jan. 8 issue of the New Yorker magazine, Judge Jackson said Mr. Gates "has a Napoleonic concept of himself and his company, an arrogance that derives from power and unalloyed success, with no leavening hard experience, no reverses."

    Separately, the judge compared Microsoft to the Newton Street Gang, which the judge sentenced on charges of racketeering and murder.

    Your correct of course, It's that difference in personalities that is really the secret behind Microsoft.

  197. Re:Nooo! NOOOOO!!! by Legion303 · · Score: 1
    (Score:1, Flamebait)

    Don't drink and moderate.

    (This message brought to you by MADM: Mothers Against Drunk Moderating.)

    -Legion

  198. Confessions of an elin master by Laplace · · Score: 2

    In my first year of college I had to use Matlab on an i386, under dos, with almost no memory. Once Matlab was up and running there wasn't enough memory to run my editor of choice, edit. I found out that I could run edlin, and became a master at writing Matlab scripts in it. I amazed my friends. I confounded my enemies. I was an edlin god.

    I now wonder why it took me so long to switch to Linux. I would have been much happier for it.

    --
    The middle mind speaks!
  199. Re:Fond C64 Memories by secolactico · · Score: 1

    Oh, yeah... and remember:

    XIO 33,#1,0,0,"D1:filename.ext"

    No wait... that was the delete command for Atari DOS 2.5.

    Those were the days... thank gods for emulators. Sometimes nostalgia hit me pretty bad (then I remember writing school papers on AtariWriter and nostalgia goes to hell...)

    --
    No sig
  200. 4DOS by Watts+Martin · · Score: 2

    In a certain sense 4DOS predates MS-DOS. It's actually a relative of ZCPR, a Z80 replacement for CP/M-80's command shell. And, yes, with ZCPR, you got basic scripting, I/O redirection, command line editing, stacking and history.

    It was quite a step backward to go from my Intertec Superbrain (a circa 1979 Z80 machine somebody gave me when I was at college!) to a 386-based PC with MS-DOS. 4DOS (and the Norton repackaging of it as "NDOS" helped a lot).

    When I ran Windows NT at work, and now that I run W2K at home, I use a descendant of 4DOS called "Take Command/32". Set it up and alias Unix commands to the DOS ones, and it's a livable working environment. (Granted that's not much of a slogan. "Buy our product and Windows becomes livable!")

    1. Re:4DOS by Christopher+Biggs · · Score: 1
      I still to this day maintain a DOS boot disk with 4dos and several other useful tools. I use it for troubleshooting and for setting up systems.

      I call it "The One True Boot Disk" and my cow-orkers are forever coming by and begging to borrow it. (Make a copy from the disk image on the file server, I tell them, but do they listen...)

      --
      -- veni vidi nuclei deceri --- I came, I saw, I dumped core.
  201. Similar situation here... by allism · · Score: 1

    I work for a company that makes medical devices. The software used for the interface is written in compiled basic that we run on DOS 6.22. The laptops that are used for the interfaces are 486's with 20 megs of memory. Our entire division is built on creating custom data collection software--we ship about six custom software packages per month, and we generate most of the profits for the company.

    Attempts to create a Windows-compatible version of our software have always failed (don't ask me why, I work on the DOS-based stuff, not the Windows-based stuff). Another attempt to go to Windows has been going on for a year and a half unsuccessfully. Meanwhile, we jsut keep plugging along at what has worked for our company for 20 years.

  202. I have a suggestion for the internet. by Sj0 · · Score: 1

    For dos, use arachne at www.arachne.cz for browsing the web. It's a very decent application, and given the choice of using either this or the monstrocity of trumpet winsock and netscape under windows 3.1, I'd use(and have) arachne in a heartbeat.

    --
    It's been a long time.
    1. Re:I have a suggestion for the internet. by NutscrapeSucks · · Score: 1

      Either that or try to find Internet Explorer 5.0 for Windows 3.1 (yes, it was released, but it's not for download anymore). Seemed much better than any 16-bit version of Nutscrape.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    2. Re:I have a suggestion for the internet. by unitron · · Score: 2

      Anybody who has IE 5 for 3.1 and doesn't want it, or anybody who knows where it might still be available for download, please get in touch with me.

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

    3. Re:I have a suggestion for the internet. by NutscrapeSucks · · Score: 1

      My suggestion is to find the pile where the IT guys throw the old MSDN and TechNet CDs. It will be in there along with Excel 2000 for Alpha, MS DirectAnimation, and other wonders.

      --
      Whenever I hear the word 'Innovation', I reach for my pistol.
    4. Re:I have a suggestion for the internet. by Sj0 · · Score: 1

      Finding stuff for DOS is much easier than finding stuff for Windows 3.1

      --
      It's been a long time.
  203. I liked DOS, so sue me by Angst+Badger · · Score: 2
    When Apple killed off the CLI-driven Apple II line and produced the Macintosh, I moved on to the IBM PC and DOS. When Microsoft started trying to kill DOS, I moved on to Linux with a great sense of relief, since the GPL assured me that I wouldn't have the rug yanked out from under me again. Don't get me wrong, I'm not opposed to GUIs, but they aren't enough by themselves, and many things are much easier if you can use a commandline, especially scripting.

    DOS wasn't much of an OS -- and there are those who have argued, with some fairness, that it wasn't a complete OS -- but it did what it did reliably, unlike any other MS software, and it did it with a tiny smidgen of memory. For some purposes, that makes it a much better deal than Linux, depending on what you need to do.

    --
    Proud member of the Weirdo-American community.
  204. Byte is boggle-brained... by KC7GR · · Score: 1

    So we're supposed to believe that DOS is dead just because some magazine says so?

    Sorry, gang... There are STILL things you can do simpler, easier, and quicker in DOS than you can with any version of Windoze. Specialized areas such as electronic test/measurement equipment control (via GPIB or serial), some embedded devices, and simple go/no-go peripheral testing on legacy hardware are all areas where DOS will still find a good home. Outside of early minicomputer OS's, DOS is still one of the few OS's that can easily run in less than a meg of RAM.

    Don't like MS-DOS? No problem. See http://www.drdos.com. And that doesn't even touch on the availability of Lord only knows how many copies of MS-DOS made it to the surplus arena, and are often available for $5 or less.

    I don't care what Byte or any of the other trade journals are blabbing about. DOS still has a warm place in my lab, and I suspect those of a lot of other companies and end users as well.

    --

    Bruce Lane, KC7GR,

    Blue Feather Technologies

  205. Missing the point by jeffy210 · · Score: 2, Informative

    I think most of these posts are missing a point... DOS and the CLI are two different things. MS programmers routinly release cli based programs for doing all sorts of things. I think what's dead is the DOS based programs. But for most basic things (copy/ren/del) the cli is still living on strong.

    --
    ------
    "And may your days be long upon the earth."
  206. IMHO, DOS was garbage by Broccolist · · Score: 2
    Oh please. It's arguable whether DOS is an operating system at all, let alone a good one. Perhaps it was the best that could be done with the hardware of the early 1980s; but it hardly improved over the years and continued up 'till version 7 to lack basic features that were present in the earliest Unices.

    For starters, basic functions of an operating system are to multitask, provide memory protection, and provide an uncircumventable layer of abstraction between applications and hardware. DOS did none of these things. Applications had the computer all to their own, and could even remove DOS from memory if they so wished. DOS did very little; it was in a sense nothing more than a glorified interrupt handler with a shell.

    And these interrupts are not even any good. The FAT filesystem used by DOS, aside from its obvious deficiencies like lack of support for long filenames, is incredibly slow and wasteful. If you browse through the FAT code in Linux you'll see it's full of pejorative comments (of the sort "I hate doing this, but FAT is brain-dead"). The drive letter system (C:, D:) is ugly and inflexible compared to the Unix system, and it's sad that we're stuck with it to this day. And the memory management ... well, to be fair, this was mostly the hardware's fault, but if you've ever done any DOS programming you know it's a royal pain.

    The command prompt supports a half-assed version of piping that isn't well-supported by applications, has a limit of (I think) 256 characters per command, and does not even expand wildcards. A friend who was working with DOS batch files was telling me how most of his time was spent circumventing the limitations of the command prompt, sometimes even writing C programs for obvious, simple things (e.g. an "xargs" equivalent).

    I used to be nostalgic about the good ol' DOS days but since then I've come to realize how terrible it really was. Bye DOS, and good riddance :).

  207. DOS will never truely die by HaloMan · · Score: 1

    DOS will never truely die. I'm a teenager and I still use DOS every day. Perhaps I'm just geeky, or maybe people are trying to kill something far too useful.

    Is there an easier way to move around files without problems like accidently dragging onto the wrong folder? If so, I would like to see it.

    DOS will never die out in whatever form it is in, whether Command Prompt, command.com or some floppy disk and you haven't used in a couple of years.

    Maybe it's time I moved to Linux, or perhaps, one day, Microsoft will not try to completely kill a good product because of it's age.

  208. Re:Fond C64 Memories by xtremex · · Score: 1

    Ah yes..I had the Atari 800XL. I happened to love it, although not as much as my commodore. Ever get Antic magazine? I still have a box of old Antic magazine from 82-84

    --
    If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
  209. Re: the meaning of share by elmindreda · · Score: 1

    well, my system gives this

    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\>path
    PATH=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\ Wbem;C:\Program Files\Microsoft Platform SDK\Bin;C:\Program Files\Microsoft Platform SDK\Bin\WinNT;C:\Program Files\Perforce;C:\Program Files\Intel\VTune50;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin


    which is rather ghastly. but I do wish UNIX had something resembling Program Files. actually, FreeBSD does have it, it's called /usr/local, but Linux seems to ignore that solution.

  210. MS takes command line away after apple introduces. by dork_vomit · · Score: 2, Funny

    This is kinda funny... Just as apple introduces the unix command into its products for the first time ever, Microsoft seems to think it is a good time to end it. Well more than 80,000 apple users spent $30.00 on the OS X beta but there are still Windows people who use a four year old OS because everything new that MS puts out if crap.

  211. Tasteless... by seldolivaw · · Score: 2

    Does anybody else think it's a bit tasteless to hire a bunch of celebs to sing at the funeral of a shitty software program in the same week that celebs are singing for free at the funeral of thousands of victims of terrorist attacks?

    The "you can fly" motto was bad enough...

    1. Re:Tasteless... by JesterzWild · · Score: 1

      That might be why they changed to the motto to "yes you can", because they knew it wouldn't be appropriate anymore (the original "you can fly" motto was developed before the attacks"). And I'm not sure there's anything tasteless about hiring celebrities to show up at your launch event, just b/c others are doing it for free at funerals and what not for the victims. Now if it was the other way around, then yeah that would be extremely tasteless. While not their biggest fan, I just think they are trying to move on and not let this whole thing shut America down... and make some money of course.

  212. I like a consoles. by golrien · · Score: 1

    No, really... trying to kill off the console is a stupid idea. I'd like to see Bill Gates try to, say, rename five thousands files from ZIP to BAK. Of course, I could just type REN *.ZIP *.BAK and be done by the time Bill was on his fifth file, heh. But I use DOS, so I'm outdated, and should be completely alienated so I have to go and buy another version of Windows. Though all they are really achieving is locking me out of ever wanting to use Windows. And SOMEONE at MICROS~1 must have realised this, because there is a 'command prompt here' powertoy. Which is insanely useful.

  213. CommandPrompt still here by JesterzWild · · Score: 1

    Just thought I might set the record straight for some of you that obviously didn't do any research on this. It is true that DOS has been removed from Windows, starting with ME and now complete with XP. However to say the XP does not have a command prompt or command line is, well, ignorant. The command prompt is still alive and well in XP and works much like it always has. Yes there are commands that used to work in DOS and 9x that are no longer there, but I can still do much of what I need to do with it. For those of you who think that MS has given up on the command prompt, you might want to check out the PowerToys for XP release with its command prompt additions. The whole point of MS removing DOS was to remove the very cause of alot of the stability problems in Windows. Windows itself was created (well actually Xerox's GUI) to make a move away from command line interfaces (CLI), not away from command prompts, which will be around for a long time to come. Of course I'm dual booting XP and Linux so I really don't have anything to worry about, got command prompts and command line interfaces and whatever else you want to call them out the...

    1. Re:CommandPrompt still here by JesterzWild · · Score: 1

      Well I didn't spend $100 on an upgrade, I'm running a preview version and plan on going back to Win 2000 afterwards. Morally superior huh? Maybe you ought to read a dictionary, because this has nothing to do with morality. I was simply pointing out that XP does have a command prompt that can still be used to do a variety of things one could previously do at the command line in DOS.

      Oh and this is a message board.

  214. MIPS not Alpha by SuperGrut · · Score: 1

    Even thought there was an Alpha version. They actually did the development with a MIPS processor.

    --
    The city is being overrun by a herd of Lucy Liu's.
  215. Re: the meaning of share by Anonymous Coward · · Score: 0

    What are you smoking? linux does have and use /usr/local.

  216. you forget : by holstein · · Score: 1

    a 2-bit company
    that can't stand 1-bit of competition

  217. Nomenclature by Gumshoe · · Score: 1

    One thing that really irks me is that
    people always refer to MS-DOS as just DOS.
    There is/was a vast array of DOS like
    OSs, MS-DOS was just one.

  218. Re:Why does Gates get the credit ? by mangu · · Score: 1
    Are you talking about NT?


    No, he isn't. He said "well written" and "stable".

  219. MacOS's vastly inferior and triumphant rival by tim_maroney · · Score: 2

    What I remember best about DOS as a Mac guy is this. From 1984 through 1994, there was no comparison between the two platforms. Ordinary mortals couldn't even install a font on their DOS machines, and keeping either DOS or the almost-DOS Windows 3.x alive required daily screwing around with the autoexec.bat and windows.ini files by skilled DOS maintainers. Applications and peripherals were opaque, balky, and unstable. The Macintosh worked -- DOS and Windows 3.x did not. Every TCO study showed order-of-magnitude gaps between the platforms, all in the Mac's favor.

    Yet for all that time, the majority of the people in the industry insisted that DOS and Windows 3.x were superior, and the market share gap in favor of DOS was enormous.

    Finally, when Microsoft won its IP battle against Apple and the reasonably usable Windows 95 came out as a clone of the Mac, the argument shifted overnight to say that Microsoft machines were now as good as the Mac, without any admission that they had been inferior for the last ten years. As soon as the revolution could legally be embraced on Intel hardware, it was instantly admitted that the Mac/W95 way was superior. The people admitting this were the same ones who had been insisting the Mac was inferior for ten years.

    This historical hypocrisy was a measure of just how absurd and partisan critical standards are in the computer industry, how little the market can be trusted to select a superior product, and how little honesty is involved in platform advocacy. It has a great deal of bearing on current platform advocacy issues.

    Tim

    1. Re:MacOS's vastly inferior and triumphant rival by man_ls · · Score: 3, Funny

      History is written by the winners. Not by the losers. Because of this, there are always three sides to a story. The winner's side, the loser's side, and the truth. It's not possible to know all 3 at any given time.

  220. Re:NT Started at NT 3.1 - Run DOS in VirtualPC by Anonymous Coward · · Score: 0

    I haven't run VirtualPC on Windows, but I run it on a Mac once in a while to play my old DOS games and it works great. I'm sure that VirtualPC with DOS on a Windows box will be a great solution for old DOS games. You get the full oomph of your CPU (which you don't really need anyway, since these DOS games are running great on an emulated Intel chip running on PowerPC), and you can keep separate "hard drives" (just files) for each version of DOS you want to run. You can also run them simultaneously, so you can have Doom running on DOS 5 in one window, and something even older running on DOS 3 in another window.

    Also, I have some of my favorite old DOS games in Classic Mac versions, such as Doom and X-Wing (the original versions of both), and Wolfenstein 3D, and they work fine on Mac OS X. It is especially funny to play Wolfenstein on a 22" 1600x1024 flat panel and it initially appears as a little 320x400 window or something like that until you change the display resolution. I'd love to see the publishers of these games open them up at least enough that somebody could turn the Classic Mac versions into native Mac OS X applications ... the original X-Wing is so much fun to play, transcending its graphical limitations and the technology of the day. Doom is also fun to revisit once in a while if you were at one time addicted to it ... I get little flashbacks to the music I was listening to at full volume all the time while playing Doom in the old days (Faith No More and Metallica and such are great Doom soundtracks).

  221. DOS is dead? by Anne+Thwacks · · Score: 1

    It all depends what you mean by dead

    Or should that be Reports of my death are greatly exaggerated

    AFAIK, you can still buy legit, supported IBM-DOS or PC-DOS or whatever IBM call it. M$-DOS may be dead, but, M$ is committed to not supporting its products anyway. I shan't be buying it, as I own more DOS licences than PCs.

    I shall continue to keep a copy installed in a partition of almost all my PCs. Its really handy for sorting out the odd hardware support problem.If I ever do run out, I bet that IBM will be happy to sell me a new copy for at least the next five years and support it too.

    --
    Sent from my ASR33 using ASCII
  222. *nix hierarchy explained. it's simple, & clean by Lethyos · · Score: 2

    There exists a hierarchy in *nix file systems. Programs and libraries placed right off the root are essential for booting. These are contained in /bin, /lib, and /sbin (system binaries or superuser binaries, your pick).

    "usr" is short for "user". Meaning this is where user programs are located. /usr has often been (and continues to be) a remote-mounted file system. Say you had a centralized network server that hosted programs that everyone on a network used. Instead of speanding hundreds of man hours installing Windows and required software at each seat, you can install it on ONE location and have everyone NFS mount the share. Simple. Only one set of programs to maintain. The paradigms for /bin, /sbin, and /lib are similar to those in /usr/*.

    /usr/local, which means "local user files" is a mount point for a local disk that stores programs specific to a workstation. This is incase you want to install software that only you can use, located on your disk. Again, the paradigms are the same. This is very similar to the /opt file system on other *nix platforms that aren't GNU.

    Try doing this with Windows. Microsoft has specially designed Windows such that you *have* to buy licenses for each and every seat, instead of buying one copy that everyone can use. I guess if you have N machines, it's better to buy N copies of a program rather than just 1. Spending money is better, right, to you Windows users? It's much better to give your money to Microsoft than to your employees. Sure.

    As for where Windows puts files... it sticks practically the entire system in one directory, and otherwise scatters things out across different locations. Why does \winnt have so many subdirectories? Why are some system files in \Program Files? Try figuring out how *your* hierarchy works before you start cutting down on *nix, which has been developed and refined over 30+ years.

    So, the original poster is certainly being inflamatory, he's certainly right when it comes to the obvious nature and elegance of *nix. Windows is just a disaster area... much like what happens when a building collapses as a result of building without any real plans in mind.

    But you most definitely have to grow up a bit and understand that computers work much better when there is some thought put into their design, rather than marketing gimmicks.

    --
    Why bother.
  223. Re:Comparing Gary Kildall's personality to Bill Ga by sheldon · · Score: 2

    That eulogy is a good one, and it does reinforce my point. Gary didn't miss any chance by not providing CP/M-86 for the PC... he didn't really want that chance. As it says, he wasn't in search of fame and money.

    Unfortunately you distorted this point into an insult towards Bill Gates, which is sad. The reality is that you do need people like Gates to lead the market in these directions.

  224. Re:3.1 and 3.5 were... by Anonymous Coward · · Score: 0
    "3.1 and 3.5 were pretty useless, being rushed out the door in full bugginess"

    Whereas every other OS release from Microsoft limped out the door full of bugginess.

  225. DOS? DR-DOS? by Anonymous Coward · · Score: 0

    DOS?
    Wasn't that a cheep knockoff of
    the C shell?

    Didn't a company named Digital Research
    finally put DOS into the public domain?

    Is it illegal to run these now?

    What is the company called Microsoft?
    I went to sleep in 1984 and just woke up. . .

  226. DOS != CLI by basilfawlty · · Score: 1
    A screenshot proves the point.

    Easy on the bandwidth! Please mirror if you like.

    --
    There are 10 types of people in the world. Those who know binary, and those who do not.
  227. DOS IS NOT DEAD by Anonymous Coward · · Score: 0
  228. run linux by Anonymous Coward · · Score: 0

    Tell me that you don't already have
    your own command line processor?

    The best and cheepest way to get a commandline
    is to run LINUX.

    MS-DOS and Windows are both dead~
    Long live Linux

  229. What makes you think it's dead? by Cardbox · · Score: 1
    I just fired up the command line prompt in my copy of Windows XP Professional and ran Cardbox-Plus on it. Bona fide 16-bit DOS program, copyright 1982-1990. Ran with no problems. DOS may be officially dead and buried, but XP seems to give quite a good imitation...

    Come to that, I can still run Microsoft's 8080 assembler (bona fide 8-bit CP/M program, copyright 1980) on XP.

    Write all the obituaries you like, DOS and CP/M never die!

  230. Bill Gates is a money mongering twit by Anonymous Coward · · Score: 1, Insightful

    If you can't write your own command line
    processor
    then what the heck are you doing in the computer
    business?

    Anyone who needs one can make one.
    Microsoft didn't invent the ROM monitor.
    DOS was crap, everyone knows it.

    JUST AS AN EXCERCISE:

    create your own commandline processor.

    I've done it two or three times for four
    or five different companies.

    It is not hard.

    PS: Bill Gates is a money-mongering twit.

  231. IBM still sells DOS for POS reasons by Anonymous Coward · · Score: 0

    Yes it's a Pile O' Shit, but it's also widely used in Point Of Sale terminals (aka cash registers), still a big biz for IBM.

  232. Isn't the MAC OS FREE-BSD thred? by Anonymous Coward · · Score: 0

    Isn't the APPLE OS a flavor or UNIX?
    Is it a thred off of the FREE-BSD?

    I think it is. . .
    Not sure which flavor of UNIX it is, so it
    must be.

    It's kinda hard to do command scripts without
    some kind of a Command line interpreter.

    UNIX needs that stuff to boot usually

  233. Wiping-out DOS software base by mbstone · · Score: 0

    So if I develop software for Windows, does that mean Bill G. can come along and declare all the previously written Windows software obsolete like he did with DOS? Lest anyone forget, many thousands of useful DOS applications, representing millios of man-hours of development effort, had to be trashed because of MS' decision to abandon DOS. And when you hit "Print" in a DOS program, stuff would actually print (now, not 5 or 10 or 15 minutes from now.......)

  234. What i liked best by khofTim · · Score: 0

    1) FAST Boot
    2) i knew what EVERY dir on my HD contained
    3) Xtree Gold
    4) PCTools
    5) arj a a:games -vva
    6) all the old games
    7) laughably low cpu/mem usage
    8) tweaking config.sys and autoexec.bat
    9) wtf is a "registry" ?
    10) no goddamn "are you sure"'s

    As soon as i have a little money left, i'll put my old P200 to some good use and install DOS on it along with all my favorite Tools and games of the time...
    Luckily i have my set of DOS disks backed up on a CD-R ;-)

    Can anyone here remember of a reason to "reinstall" DOS? Well I can't, thats for sure.

    .

    --
    . take off every .sig for great justice
  235. I will give up DOS... by Reziac · · Score: 1

    ..when they pry my cold dead computer from around it!!

    --
    ~REZ~ #43301. Who'd fake being me anyway?
  236. Have you ever learned how to use DOS? by narfbot · · Score: 2, Insightful

    In the very early DOS days, I knew the basic stuff, changing directories, running programs, using GW-Basic. I didn't experiment too much because the machine I used wasn't mine.

    Then in the late 80's, my parents got me a Mac Plus. It was an interesting machine, to learn and use. I had a few games, Microsoft Word and Works, a spreadsheet program, and some disk utilities. I learned how to use hypercard, and learned all the settings in the apple menu.

    After about a year's use, I found it to be less and less intersting.

    My parents put a modem in their computer and got prodigy, one of the fore-runners to the internet. It was awesome. Two, they got me a programming book, I found it very enjoyable.

    I'd wonder, why didn't I have this stuff for Mac, more programs, or even a Hard Drive? They were too expensive and too hard to find.

    I soon was given my parents XT. It was fast, and stable. Not this constant editing of config.sys or autoexec.bat, once you set up it is done.

    It is true, side by side, the XT was more stable. If it would hang up, you were probably trying out a new program. Just reset, and your back in seconds. If that happened on the Mac, it would happen all the time, with almost all the programs! It would corrupt disks, and the disks were expensive! On the XT, I used 360 KB disks, and I remember only once corrupting a disk.

    The reset button for the Mac was funny, because it was removible, and had a debug window, and something else wierd with it I can't remember. The programmible menu had a commands that I knew out of a book I had, but there was never any help for it on the computer, you couldn't use it like even the debug command in DOS because I didn't know what the options were.

    Well there are lots of things I can talk about the Mac, but lets finish by talking about a little of what you said.

    By the time DOS and Windows 3.x rolled around, I found that they were definately superior. My brother put Win3.1 on his computer, a 386 with VGA, and later bought a sound card. It was the first time that I had seen Full Motion Video with AVI in windows. It was very cool. And it only costed him a few hundred dollars. This was 1992 technology, and I compared this with the Macs at the time. I found them unbelievibly behind. They were still selling Mac Pluses, SE's and Mac II's were way too expensive. You had to buy a Mac IIfx to get any where near what my brother could do.

    And another note, Apple sued Microsoft over Windows 1.0, way back in 1985 I believe, so that has nothing to do with Win95.

    Conclusion, I've learned both OS's, and I know how they work side-by-side. It is true that Mac's are technologically inferior. They have always been overpriced. And their standards have always leaned on the rest of the industry. Even today, I've admin Mac networks, and it's the same.

    The people that compared Win95 to Mac are right when they said they are the same, because they looked the same, but that doesn't have any bearing on the other argument-they always have been technologically inferior. If there was hypocrisy from and DOS person, he doesn't know what he's talking about to start-he's just repeating what everyone else says-But I've have learned for the fact, Macs have always been inferior.

  237. When '95 came out, and even before... by dbCooper0 · · Score: 1
    I referred an entity, "GOD" as in "Good Old DOS". Invoking this blasphemy never caused any stir with my clients - because without it I could not get things done. Tweaking files & buffers, quick 'n dirty batch files, you name it - it was easier, and more efficient.

    Windows ME is *not* supported by this crusty old tech, and any fool who goes for XP can gracefully exit my client base (don't let the door hit you in the...) as well. You have been warned.

    I waited awhile to post this; even though common sense told me not to bother posting at all: "there, I said it."

    --
    db
    Cig:
    ôô
    /`
  238. Find by Timothy+Chu · · Score: 1

    The Find utility is the best feature of Windows' file management system (over Win31 or DOS). It's great to be able to search through a directory of 100 files and immediately find files you need based on the content or name of those files.

    A better solution for finding all files ending in *bak is to sort your directory by file type (in Windows Explorer), then simply select all the *.bak files and del.

  239. Re:Why does Gates get the credit ? by flegged · · Score: 1

    Well, my copy of NT 5.0 SP2 is perfectly stable - it hasn't crashed this year.

    As for "well written"; without seeing the source I don't know. How do you?

    --

    "I think he was truly surprised at how little I cared about how big a market the Mac had" - Linus on Jobs
  240. fa! by Anonymous Coward · · Score: 0

    Finally!

  241. That's just because there's no "dumb" mod... by raistlinne · · Score: 1

    ...so that "troll" is the best approximation thereof.

    The original poster claimed that microsoft's organization of files has no valid justification. The first responder claimed that linux's organization of executables (and libraries) was similarly unreasonable. The guy that you responded to then pointed out that there is in fact a reason for the organization, it just turns out that the guy in the middle didn't know it.

    You just misunderstood just about everything posted in this thread, most likely because you have below-average mental facilities. However, you could just be a clever troll. It's not really relevent.

    Anyhow, c:\windows is not the equivalent of /, c:\ is. More precisely, a:\ & b:\ & c:\ & ... & z:\ (has windows added the ability to have more than 26 drives yet?) is the equivalent of /.

    That being said, people can mount / over a network just fine - it was often done in the days when hard drives cost substantial amounts of money and people wanted to save disk space. When I was a freshman the computer science lab was set up this way with a bunch of sun workstations nfs mounting / from a linux server.

    Virtually noone does it anymore as disk space is so cheap, but it also offers easier administration and greatly diminishes the number of things that can break. Workstations of this kind, like the sun sunray, might make a comback if microsoft office can be killed. As it stands it's probably most often used in things like POS terminals if they're not actually dumb terminals.

    Still, for large installations (say hundres or thousands of users), a big centralized server with X terminals is still probably the best way to go in terms of administrative efficiency as well as reliability and monetary efficiency.

    --
    They laughed at Einstein. They laughed at the Wright Brothers. But they also laughed at Bozo the Clown. -- C. Sagan
    1. Re:That's just because there's no "dumb" mod... by arjennienhuis · · Score: 1

      Sun sunrays are actualy more like X teminals, with the screen cached at the huge sun server you need.

  242. QDOS? by kimihia · · Score: 1

    Don't forget where most of Microsoft's good ideas come from: their competitors.

    DOS came from their purchase of QDOS: "Quick and Dirty Operating System".

    (IE came from Mosaic, Frontpage came from Vincent Technologies, Age of Empires came from that company with the strange sphere logo, Inspire?)

  243. DO NOT GO THERE! by Anonymous Coward · · Score: 0

    Oh, god... sickos...

  244. correction by characterZer0 · · Score: 1

    Windows XP (NT 4.9)

    --
    Go green: turn off your refrigerator.
  245. Re: Do it in Windows - duh! by Anonymous Coward · · Score: 0

    err, a well we can A) Create a boot disk on either two flopies or if you have skills, it can still be done with one. OR you can just go down to single user mode kill all the demons and its just as safe

  246. Re:Ha! You are WEAK. by Anonymous Coward · · Score: 0

    Why doesn't DOS say "Excellent command or filename" when a valid command is typed?

  247. Re:Why does Gates get the credit ? by mangu · · Score: 1
    Well, my copy of NT 5.0 SP2 is perfectly stable - it hasn't crashed this year


    My 1962 Volkswagen hasn't crashed this year either -- which does NOT make it a "stable" car by any definition...


    (have you ever heard of something called "statistics"? - one example proves nothing)

  248. Sperry DOS by Anonymous Coward · · Score: 0

    In the late '70's through the early '90's my dad worked for Sperry Univac (which merged in the '80's with Boroughs to become Unisys).

    The first PC we had at home was a Sperry 8086-based clone that ran Sperry DOS. This would have been about '84/85, something like that.

    The one thing I do remember is that Sperry DOS wasn't very compatible with MS-DOS - only a handful of commercial apps (ie, games, I was about 5 or 6 at the time) would run properly.

    Eventually we moved up to an XT clone (CGA graphics, 2 low density 5.25 floppy drives, no hard drive) which my dad got with a bootleg copy of MS-DOS 3.1. It ran more games, and was pretty much the minimum requirements for most apps, although I was stuck with an old version of a word processor called "Multi-Mate" in which I had to use printer escape codes to do bold or italics... The nightmares....

    My point in all of this is that there were many DOSes, and some of them were, well, unique, either deliberately or by accident. For nostalgia's sake I wonder if anyone has a copy of Sperry DOS kicking around...

    Glenn

  249. Oh...Damn! by davcorp · · Score: 1
    Umm... Does this mean I have to throw out my copy of MSDOS 2.0?

    Seriously folks... I still have it... *sigh*, the memories... hacking all night to make that "just right" ansi.sys square menu line up right! Ooooh, and don't forget 4dos.com!! Win3.11 would never be the same... I can even remember downloading a sweet little program called NCFtp for Dos... "Why do they keep giving thanks to this think called Linux?"

    --
    Gravity!... It's not just a good idea... It's the Law!
  250. Re: Do it in Windows - duh! by Anonymous Coward · · Score: 0

    go down to single user mode kill all the demons



    Why does this sound like some twisted role-playing game?

  251. And we saw DOS, and it was good.... by Jestrzcap · · Score: 1

    I know exactly the feeling you're describing.
    Even have a name for it. We call it....

    Nerdvana

    Not until I found linux did I ever again achieve nerdvana after the days of dos.

    --
    "I have great faith in fools: Self confidence my friends call it." ~Edgar Allan Poe
    1. Re:And we saw DOS, and it was good.... by khofTim · · Score: 0

      Thou art so right, brother *sniff*
      One day, i shall master the art of linux and achieve ultimate geekness myself.

      seriously: is there an xtree gold open source clone out yet? something like ktree gold?

      .

      --
      . take off every .sig for great justice
  252. DirectX, all you need for games by CrazyJim0 · · Score: 1

    I remember making a dos MMORPG back in 1992, and hearing that they're porting out DOS, and that DOS gets no Winsock support, and then when there was winsock support, windows switched to 2.0 which is extra convoluted...

    Dos may only have a black screen, but Dos never blue screens...

    Dos was solid, you could know all the commands there are to know in Dos. But when windows came out there was tons of functionality and no documentation... Almost dileberately so armchair dos programmers couldn't get in the game. I mean it took me 10 years and I only am starting to get the hang of Visual C++ vs DJGPP.

    I like windows and all, but the phase out of DOS means I'll never be able to commercially release my game even if I wanted to put work into it. I remember vividly when I tried to work on my game at school, but they ported to NT so my code no longer worked, and late night warcraft sessions didn't work either.

    As long as Microsoft can keep technology moving, they can keep it so obscured that no mere mortal can keep up.

    Bleh, I've given up legitamate program coding, and moved on to 3rd party hackathon! By hacking some other jerkwad corporation's software, you can compete without wrestling with unsightly overhead of trade secrets.

    Don't try and make something new Microsoft will just see it and crush you, but if M$ does something new, then latch on and suck all the blood you can from them. What's M$ gonna do? Sue an intelligent, out of work scientist? Maybe... But what happens if all the intelligent out of work scientists are jumping on M$'s back for a ride? Climb up on, there's money to be had in hacks :)

  253. Actually, you don't need quotes around "cd" by ericvids · · Score: 1
    ... you end up having to put quotes around practically ever CD command
    Try it yourself on a Win2K box without adding quotes:

    cd c:\program files

    It worked on mine, and I've been using it regularly to the point that I forget about it when I switch to a 95/98/ME box, in which case I would promptly (pardon the pun) get an error message. Actually, you'll have to enable the Command Extensions for this to work (it's enabled by default).

    The "rd" command even removes directories recursively now, so "rd \ /s/q" is just about as dangerous as "rm / -rf". ;)

    In any case, type "help" on that prompt and find a few niceties that may help change your mind about Win2K's CLI. I find PUSHD and POPD rather useful when moving through directories in different hierarchies.
    --
    Pet peeve: Profane people propagating perfunctory pedantry.
    1. Re:Actually, you don't need quotes around "cd" by xQx · · Score: 0

      Actually there are a few things in WindowsNT, 2k and XP's cmd.exe that make me never want to go back to command.com

      Granted they're all stolen from *nix, but *nix probably stole them anyway.

      First:
      Set the value of:
      HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar to 9

      Now:
      (the most commonly run command on my NT boxes: [Winkey]-R cmd.exe

      "cd /pro[tab] " gives: C:\>cd /"Program Files"
      "cd \Program Files " gives: C:\Program Files>
      "cd \Pro* " gives C:\Program Files>

      mkdir Mydir -- Makes the directory
      doskey is installed by default. (up arrow goes to previous command)
      And (I never use it) F7 lets you choose from a list of your previous 10 commands.

      There is a handful of other improvements, but I can't think of them.

  254. deleting items from "recent document" menu by Anonymous Coward · · Score: 0

    1. right click on taskbar -> "properties"
    2. select the 2nd tab (called something like "programs in start menu")
    3. press "delete" to delete the content of your doc. menu

  255. Re:Why does Gates get the credit ? by flegged · · Score: 1

    How the hell can you compare a car-crash to a computer crash?

    unless you meant that crashes are only caused by bad drivers...

    one example proves nothing

    No windows 2000 machine I have come in contact with have ever crashed. I can crash a windows 98 machine by looking at it, or a Linux box by a little playing.

    --

    "I think he was truly surprised at how little I cared about how big a market the Mac had" - Linus on Jobs
  256. Proof That Slashdot Is Dead/Dying by Anonymous Coward · · Score: 0

    There are many troll posts made that are actually in some ways funny or intelligent. This is obviously a troll that wasn't funny and certainly shows the author is absolutely clueless.

    ...and he got moderated up to 5, Insightful. If I go and say "green is the wrong color for Slashdot's main page just because I don't like it", I'm not being insightful, I'm just being stupid. This guy has said "I don't like *nix file system layout because I don't understand it." How is that any different?

    When a moron like this gets raised above the noise of the conversation to prevent such an uninformed and trollish viewpoint, we know we're in a sorry state.

    Oh well, hopefully CmdrTaco's ANUS will put the last nail in the coffin when he starts that advirtising shit on /. Then we can all go over kuro5hin where they actually have an intelligent community.

  257. WNT's creator by Anonymous Coward · · Score: 0

    IIrc, Dave Cutler.
    Some commentary I read long ago said he wasn't exactly a sweetheart.

  258. Re:Fond C64 Memories by Anonymous Coward · · Score: 0

    Actually it was 'load "$",8' the ', 1' loaded it to a location specified by the first 2 bytes of the file

  259. Re:Fond C64 Memories by xtremex · · Score: 1

    Actually..it was load "*", 8, 1 which executed the program on cd...the load "$" was a directory listing :)

    --
    If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
  260. corny DOS joke by Anonymous Coward · · Score: 0

    c:\dos
    c:\dos <run>
    <run>dos</run>

    hehe...sorry, I'm prolly the only person alive who thinks thats funny