Challenges and Design Issues in MS-DOS Development

Windows faced difficulties in enabling multitasking while integrating with non-multitasking MS-DOS and device drivers. MS-DOS lacked multiprocessor synchronization capabilities, limiting shared resource access. Security features like unalterable password identifiers and command-based usage reduced virus risks but required user familiarity. Software developers initially favored CP/M-86 over MS-DOS, leading to partial adaptation. MS-DOS design criteria, emphasizing speed, efficiency, and assembly language development, shaped its evolution.

• MS-DOS
• Operating System
• Multitasking
• Security
• Software Development

hika_66 Follow

Uploaded on Sep 19, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. Not designed for pre-emptive multitasking use--Windows has to perform many nasty tricks to allow even non-pre-emptive multitasking with non-multitasking MS-DOS and its non-multitasking device drivers.

2. platforms--MS-DOS is inherently a singleprocessor OS, so MS-DOS device drivers are utterly incapable of synchronizing access to shared resources in a multiprocessor situation.

3. Group C Page 14

4. 3.6 SECURITY

5. password identifier which cannot be altered by someone who is not authorized. Password can be set for some programs starting from MSDOS like QBASIC.

6. virus. Also it MSDOS cannot be used by someone who does not know the commands limiting the risk of harming the system. Group C Page 15

7. 4.0 DESIGN ISSUES

8. MS-DOS Design Criteria

9. Computer was interested in. There was partial success: those software developers who chose to translate their CP/M-80 programs found that they did indeed run under MS-DOS, often on the first try. Unfortunately, many of the software developers Seattle Computer talked to in the earlier days preferred to simply ignore MSDOS. Until the IBM Personal Computer was announced, these developers felt that CP/M-86 would be the operating system of

10. greatest speed and efficiency. The last design requirement was that MS-DOS be written in assembly language. While this characteristic does help meet the need for speed and efficiency, the reason for including it is much more basic. The only 8086 software- development tools available to Seattle Computer at that time were an assembler that ran on the Z80 under CP/M and a monitor/debugger that fit into a 2K byte EPROM (erasable

11. 5.0 IMPLEMENTATION

12. written through commands); without the knowledge of those commands, the user cannot execute a job. Despite its command-line interface, it is easy to learn. The commands of MSDOS are not case sensitive. MSDOS is supported and embedded in other operating system like Microsoft windows, MacOs; it can be launched in windows by:

13. (i) Start -> All programs -> accessories -> command prompt or

14. (ii) Start -> run -> type cmd -> ok

15. (IO.SYS, MSDOS.SYS, COMMAND.COM, CONFIG.SYS and AUTOEXEC.BAT). The commands in MSDOS can be categorized in two forms:

16. INTERNAL and EXTERNAL commands.

17. Group C Page 17

18. containing the program is in drive. They can be used for peripheral devices like printer. A file s full name is called FILESPEC. The FILESPEC for a disk file has four parts: drive name, directory name, file name and extension. Characters like. / \ [ ] : | < > + = ; , cannot be used in naming files because they mean other things in MSDOS. When you start up DOS, the current directory is automatically the root

20. cd ROOT DIRECTORY\SUB- DIRECTORY (Level 1)\ SUB- DIRECTORY

21. (level2)...\filename.ext. CLASSIFYING MS-DOS COMMANDS

22. will be specified for each command of MSDOS in this text. MS-DOS commands fall roughly into three categories;

23. Group C Page 18

25. report on or affect the operating system environment. Examples are CLS (clear screen), TIME, DATE, VER (display MS-DOS version number), and HELP.

26. BREAK (internal): Used from the DOS prompt or in a batch file or in the

27. CONFIG.SYS file to set (or display) whether or not DOS should check for a Ctrl +

28. Break key combination.

29. BREAK =on|off

30. CLS (internal) clears screen: Clears (erases) the screen. CLS

31. DATE AND TIME (internal): Displays and/or sets the system date. DATE mm-dd-yy or DATE

33. GRAPHICS (external): Provides a way to print contents of a graphics screen display.

34. GRAPHICS [printer type][profile] [/B][/R][/LCD][/PB:(id)] [/C][/F][/P(port)]

35. MODE (external): Sets mode of operation for devices or communications.

36. MODE n

37. MODE LPT#[:][n][,][m][,][P][retry]

38. MODE [n],m[,T]

39. MODE (displaytype,linetotal)

40. MODE COMn[:]baud[,][parity][,][databits][ ,][stopbits][,][retry]

41. MODE LPT#[:]=COMn [retry]

42. MODE CON[RATE=(number)][DELAY=(n umber)]

43. MODE (device) CODEPAGE PREPARE=(codepage) [d:][path]filename

44. MODE (device) CODEPAGE PREPARE=(codepage list) [d:][path]filename

45. MODE (device) CODEPAGE SELECT=(codepage)

46. MODE (device) CODEPAGE [/STATUS]

47. MODE (device) CODEPAGE REFRESH

49. VER (internal): Displays the DOS version number. VER

50. and installs country-specific information and keyboard codes (starting with DOS Version 6, this command is no longer available).

Load More ...