Truth, Computing and Fail

  • Home
  • About

Whats the point?

anomit | February 22, 2008

Follow this link.

DOS is dead. It’s 16-bit. It’s obsolete. The only people that still write DOS assembly are crazy old hackers that are too attached to their 386s to throw them away.

Couldn’t agree more. I see no reason to be working with 16-bit registers on systems where you can afford 32-bit mode. Developing assembly programs for DOS using 8086/8088 code means you are forced to run them in ‘real mode’, that the processor can address only 1MByte of memory. Also that you will be tearing out your hair keeping track of segments and also that you would never know when a segfault would be staring you in the face. Take into account the fact that unlike linux which would give an error like Segmentation fault(Core dumped) and then come back to its helpful self, if you are working on the Command Prompt you would only get to see something like An illegal instruction occured at and two so called ‘options’ (close and ignore) which anyways, would lead to the same thing i.e. you having to terminate the process. If it is the real 16-bit MS-DOS, then God save you or to be more precise, the reset button.

I have no idea though why our colleges are so obsessed with totally obsolete standards that are out of sync with the requirements of modern computing.

Categories
Coding, GNU/Linux
Comments rss
Comments rss
Trackback
Trackback

« Preventing atheros card from being disconnected often WTF »

2 responses

....cos it gives u ur fundamentals. (same as why we learn

surjodeb | April 16, 2008

….cos it gives u ur fundamentals.
(same as why we learn addition before multiplication) :)

How about going back to programming the archaic Atari machines?

anomit | April 16, 2008

How about going back to programming the archaic Atari machines? Or maybe even back to those days when one had to write only in hex opcodes…..ok, let my imagination run wild, lets write machine code in 0s and 1s! :P

Seriously though, I have issues with the way DOS blows up in my face when i write a wrong code. So much for protected mode programming.

Leave a comment

You can use these tags : <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

What’s in

  • Apologies
  • Examining the Linux VDSO
  • Symlinks in a libfs virtual file system: The Pains
  • Small rant on the FUSE API reference
  • Kernel module debugging: a simple technique

Blogroll

  • Akshay Kothari
  • Ankur Shrivastav (OS)
  • Ankur Sinha
  • Harsh J
  • Hullap
  • LUG manipal
  • Swap

Tags

aircrack airfail airtel assembly blues build c Coding college country cryptography dean faculty file systems fuckery gnuplot hacking India kernel linux mangalore manipal mpd music NASM plugin politicians pub culture python rant rock sam scheduler simulation SSFNet stupidity supernatural suppression syscall syscalls system calls unix vim xchat xml

Archives

  • December 2010
  • April 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • January 2009
  • November 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • October 2007
  • September 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007

License

Creative Commons License
This work by Anomit Ghosh is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 India License.
rss Comments rss valid xhtml 1.1 design by jide powered by Wordpress get firefox