Downloads & Free Reading Options - Results

xvi, 488 pages

xvi, 488 pages

xvi, 488 pages

There are no author-identified significant results in this report.

Notes On Using Applications with Ms-DOS0.

Notes On Using Applications with Ms-DOS0.

From the bitsavers.org collection, a scanned-in computer-related document. digitalResearch :: concurrent :: Dahmke Using Concurrent PC DOS 1986

xxii, 262 p. ; 23 cm

xxii, 262 p. ; 23 cm

xxii, 262 p. ; 23 cm

xxii, 262 p. ; 23 cm

Includes index

Includes index

Includes index

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This Validation Summary Report describes the extent to which a specific Ada compiler conforms to the Ada Standard, ANSI/MIL-STD-1815A. This report explains all technical terms used within it and thoroughly reports the results of testing this compiler using the Ada Compiler Validation Capability. An Ada compiler must be implemented according to the Ada Standard, and any implementation-dependent features must conform to the requirements of the Ada Standard. The Ada Standard must be implemented in its entirety, and nothing can be implemented that is not in the Standard. Even though all validated Ada compilers conform to the Ada Standard, it must be understood that some differences do exist between implementations. The Ada Standard permits some implementation dependencies -- for example, the maximum length of identifiers or the maximum values of integer types. Other differences between compilers result from the characteristics of particular operating systems, hardware, or implementation strategies. All the dependencies observed during the process of testing this compiler are given in this report. The information in this report is derived from the test results produced during validation testing. The validation process includes submitting a suite of standardized tests, the ACVC, as inputs to an Ada compiler and evaluating the results. (KR)

This book, Using MS-DOS on the Amstrad PC, introduces the reader to MS-DOS methods for those users who have some small prior knowledge of computing but no previous experience of MS-DOS or CP/M. The book is divided into parts, each of which deals with a number of topics, one section to each topic. In each section, there is text and examples which show in detail how the commands of MS-DOS are used. The order of the sections follow the logical path of the user who will experiment first with simple operations and eventually work up to advanced uses of MS-DOS. A very full index makes it easy to obtain information. The disk system Formatting disks Simple internal commands Batch commands Using the MODE command Errors and error messages Inputs and outputs Utilities

ICT is increasingly used in the last decade. One of the greatest challenges in this area is system and information security. This security is threatened by cyberattacks on networks. New techniques have been devised for the field by expanding research into network security. Among the most popular techniques, various data mining algorithms can be noted that are used either alone or in combination for intrusion detection. In this study, neural network technique was used for intrusion detection. The results of simulation of this technique on KDD dataset and MATLAB software indicated high precision of 98%. Comparison of this technique with other techniques such as CNN and BiLSTM suggested that these techniques had a less precision than the proposed one. In addition, the technique had a low error rate.

1993, MS-DOS ISBN: 0-672-30399-X

1993, MS-DOS ISBN: 0-672-30399-X

1993, MS-DOS ISBN: 0-672-30399-X

1993, MS-DOS ISBN: 0-672-30399-X

1993, MS-DOS ISBN: 0-672-30399-X

DV_Tech_Note: Using MS-DOS 6.0 with Quarterdeck Products.

DV_Tech_Note: Using MS-DOS 6.0 with Quarterdeck Products.

Includes index

Includes index

Apple DOS 3.2 manual

Apple DOS 3.2 manual

Includes index

xx,1115p. ; 24 cm

xx,1115p. ; 24 cm

Includes index

Includes index

A profile on computer pioneer Gary Kildall and the important contributions he made to the PC industry including the true story on how IBM ended up using MS-DOS rather than CP/M. Kildall developed CP/M, the first personal computer operating system. He was also a co-host on the early Computer Chronicles series. Includes comments by Gordon Eubanks, Symantec; Tom Rolander, DRI; Tim Bajarin, Creative Strategies; Lee Lorenzen, DRI; Jacqui Morby, TA Associates; Alan Cooper, CP/M applications developer. Originally broadcast in 1995. About Computer Chronicles: The Computer Chronicles was an American television series, broadcast during 1981-2002 on Public Broadcasting Service (PBS) public television, which documented the rise of the personal computer from its infancy to the immense market at the turn of the 21st century. The series was created in the Fall of 1981, by Stewart Cheifet (later co-host), then the station manager of the College of San Mateo's KCSM-TV (which co-produced the show with Harrisburg, PA's WITF-TV), initially broadcast as a local weekly series. Jim Warren was its founding host for its 1981-1982 season. It aired continuously from 1981 to 2002 with Cheifet co-hosting most of its later seasons. Gary Kildall served as co-host for six years (1983 to 1990) providing insights and commentary on products as well as discussions on the future of the ever-expanding personal computer sphere. More Info: http://stquantum.xtreemhost.com/cc/index.htm Source: https://www.youtube.com/watch?v=bLVbSjDq0DE Uploader: Jesús Zafra Upload date: 2012-09-06

A profile on computer pioneer Gary Kildall and the important contributions he made to the PC industry including the true story on how IBM ended up using MS-DOS rather than CP/M. Kildall developed CP/M, the first personal computer operating system. He was also a co-host on the early Computer Chronicles series. Includes comments by Gordon Eubanks, Symantec; Tom Rolander, DRI; Tim Bajarin, Creative Strategies; Lee Lorenzen, DRI; Jacqui Morby, TA Associates; Alan Cooper, CP/M applications developer. Originally broadcast in 1995. About Computer Chronicles: The Computer Chronicles was an American television series, broadcast during 1981-2002 on Public Broadcasting Service (PBS) public television, which documented the rise of the personal computer from its infancy to the immense market at the turn of the 21st century. The series was created in the Fall of 1981, by Stewart Cheifet (later co-host), then the station manager of the College of San Mateo's KCSM-TV (which co-produced the show with Harrisburg, PA's WITF-TV), initially broadcast as a local weekly series. Jim Warren was its founding host for its 1981-1982 season. It aired continuously from 1981 to 2002 with Cheifet co-hosting most of its later seasons. Gary Kildall served as co-host for six years (1983 to 1990) providing insights and commentary on products as well as discussions on the future of the ever-expanding personal computer sphere. More Info: http://stquantum.xtreemhost.com/cc/index.htm Source: https://www.youtube.com/watch?v=bLVbSjDq0DE Uploader: Jesús Zafra Upload date: 2012-09-06

A profile on computer pioneer Gary Kildall and the important contributions he made to the PC industry including the true story on how IBM ended up using MS-DOS rather than CP/M. Kildall developed CP/M, the first personal computer operating system. He was also a co-host on the early Computer Chronicles series. Includes comments by Gordon Eubanks, Symantec; Tom Rolander, DRI; Tim Bajarin, Creative Strategies; Lee Lorenzen, DRI; Jacqui Morby, TA Associates; Alan Cooper, CP/M applications developer. Originally broadcast in 1995. About Computer Chronicles: The Computer Chronicles was an American television series, broadcast during 1981-2002 on Public Broadcasting Service (PBS) public television, which documented the rise of the personal computer from its infancy to the immense market at the turn of the 21st century. The series was created in the Fall of 1981, by Stewart Cheifet (later co-host), then the station manager of the College of San Mateo's KCSM-TV (which co-produced the show with Harrisburg, PA's WITF-TV), initially broadcast as a local weekly series. Jim Warren was its founding host for its 1981-1982 season. It aired continuously from 1981 to 2002 with Cheifet co-hosting most of its later seasons. Gary Kildall served as co-host for six years (1983 to 1990) providing insights and commentary on products as well as discussions on the future of the ever-expanding personal computer sphere. More Info: http://stquantum.xtreemhost.com/cc/index.htm Source: https://www.youtube.com/watch?v=bLVbSjDq0DE Uploader: Jesús Zafra Upload date: 2012-09-06

A profile on computer pioneer Gary Kildall and the important contributions he made to the PC industry including the true story on how IBM ended up using MS-DOS rather than CP/M. Kildall developed CP/M, the first personal computer operating system. He was also a co-host on the early Computer Chronicles series. Includes comments by Gordon Eubanks, Symantec; Tom Rolander, DRI; Tim Bajarin, Creative Strategies; Lee Lorenzen, DRI; Jacqui Morby, TA Associates; Alan Cooper, CP/M applications developer. Originally broadcast in 1995. About Computer Chronicles: The Computer Chronicles was an American television series, broadcast during 1981-2002 on Public Broadcasting Service (PBS) public television, which documented the rise of the personal computer from its infancy to the immense market at the turn of the 21st century. The series was created in the Fall of 1981, by Stewart Cheifet (later co-host), then the station manager of the College of San Mateo's KCSM-TV (which co-produced the show with Harrisburg, PA's WITF-TV), initially broadcast as a local weekly series. Jim Warren was its founding host for its 1981-1982 season. It aired continuously from 1981 to 2002 with Cheifet co-hosting most of its later seasons. Gary Kildall served as co-host for six years (1983 to 1990) providing insights and commentary on products as well as discussions on the future of the ever-expanding personal computer sphere. More Info: http://stquantum.xtreemhost.com/cc/index.htm Source: https://www.youtube.com/watch?v=bLVbSjDq0DE Uploader: Jesús Zafra Upload date: 2012-09-06

Version: 4.1 EDITV is a character based DOS ASCII textfile editor with an intuitive Windows-like interface. It can be used for simple text-editing tasks, like creating or modifying batch files or program sources. It is based on the TFileEditor object included with Borland’s Turbo Vision v2.0 for DOS. Features: Mouse support Menu driven Multiple document editing in separate windows Context-sensitive on-line help EGA support (screen height 25 or 43/50 lines) Selectable display modes: color, gray shades and monochrome Adjustable color palette Cut and Paste functions Cut/Paste clipboard can be viewed, edited and saved to disk Undo function Read Only mode Find/Replace text (forward, backward, all, from cursor/entire text) Text markers Find matching bracket ({ ]}) Find matching Quote (‘..’ and “..”) Auto-indent option Insert and display control-characters Optional display of ruler and line numbers Option to create backup file when saving a document Select recently opened/saved files from File menu Select special characters (also ASCII 128-255) from a list Print support with optional margins, headers, footers, etc. DOS shell function Execute Command feature with configurable command list Support for Unix file format (using LF line-ends) Display file statistics (character, word & line count) Built-in clock Optional separate input/output directories Restrictions: No WYSIWYG page formatting No word-wrap Maximum document size 64 kb Files included: EDITV.EXE Executable program (LZE compressed) README.TXT Description (this text) EDITVUS.HLP Help file EVHSTUS.TXT Release history Installation: Copy EDITV.EXE and EDITVUS.HLP to a directory that’s in in your DOS-path. Both files must be in the same directory. If you want a minimal installation, just copy EDITV.EXE without EDITVUS.HLP. You will then have a fully functional editor, but no on-line help. Usage: EDITV [filename] Credits: The people at the former Borland Co., now Inprise, made this thing possible by providing the editor kernel and a superb DOS user interface called Turbo Vision. Special thanks go to Jose Luis Rivera-Noriega from Mexico, who suggested several excellent ideas to improve this editor. This program may be used and copied freely without charge, but only for non-commercial purposes. The author is not responsible for any damage or loss of data that may be caused by using it. Original metadata: Title: EDITV Version: 4.1 Date: Apr 03,1999 Author: J.R. Ferguson, Amsterdam, The Netherlands Download: http://www.xs4all.nl/~ferguson/dosedit.html E-mail: j.r.ferguson @ iname.com

How to use MS-DOS from 1988 made by M-USA Video Source: https://www.youtube.com/watch?v=aEoc4cNm2V4 Uploader: Notelu Upload date: 2016-08-05

The bulk chemical compositions of planets may yield important clues concerning planetary origins. Failing that, bulk compositions are still important, in that they constrain calculation of planetary mineralogies and also constrain the petrogenesis of basaltic magmas. In the case of the Earth, there is little or no debate about the composition of the Earth's upper mantle. This is because our sample collections contain peridotitic xenoliths of that mantle. The most fertile of these are believed to have been little modified from their primary compositions. Using these samples and chondritic meteorites as a starting point, small perturbations on the compositions of existing samples allow useful reconstruction of the bulk silicate Earth (BSE). Elsewhere, I have argued that the next simplest case is the Eucrite Parent Body (EPB). Reconstructions based on Sc partitioning indicate that the EPB can be well approximated by a mixture of 20% eucrite and 80% equilibrium olivine. This leads to a parent body that is similar to CO (or devolatilized CM) chondrites. Partial melting experiments on CM chondrites confirm this model, because the residual solids in these experiments are dominated by olivine with minor pigonite [3]. The most difficult bodies to reconstruct are those that have undergone the most differentiation. Both the Moon and Mars may have passed through a magma ocean stage. In any event, lunar and martian basalts, unlike eucrites, were not derived from undifferentiated source regions. Reconstructions are primarily based on compositional trends within the basalts themselves with some critical assumptions: (i) Refractory lithophile elements (Ca, Al, REE, actinides) are presumed to be in chondritic relative abundances; and (ii) some major element ratio is believed to exist in a chondritic ratio (e.g., Mg/Si, Mg/Al). The most commonly used parameter is Mg/Si.