EXE spits out , it can also load itself as a TSR and automatically decompress the program on int21,4b! If started with. However, due to our "don't change or put anything in the game directory" policy, this is not what we should do.
DOC , which probably contains exactly what we need for both question 2 and 3, seems to have vanished from the Net. Here's the source code for another Diet unpacker. The tombexcavator project is licensed under the GPL v3 , so we could easily use that in our setup. It sounded kind of weird to me too, but yeah, that was the plan. Turns out that there are indeed two major problems:. However, given the fact that the assembly doesn't look exactly perfect to me, it might still be possible to optimize this for decent performance after I made it work in the first place.
All of the PC games require a CPU anyway, and tapping into the extended instruction set most notably BSWAP might help in that regard as opposed to just compiling everything for the because you don't know better. And yes, I've verified that this works on real hardware. But remember that I'm in the PC business for the fun, so it should be clear what I'll be trying wasting my time on first.
So the biggest problem here is getting a bit build of the SHA algorithm. Since there's no way of setting a certain bitness for a C source file, I first tried adding a.
The linker was complaining about something like "can't mix bit and bit segments". This behavior might be specific to PC? But apparently, there are problems with relocations etc. Oh well. Then let's try to just create a bit build containing just the SHA example code.
And there we already have the next problem: Finding a protected mode runtime that works on any system. And lo and behold, suddenly we're at 80 KB per second on the recommended configuration, and the generated assembly still leaves a lot of room for improvement. This can be default,alsa,oss,win32,coreaudio,none. In Windows put the id of the device you want to use. On auto the mode is determined by sblaster type. Patch sets used with Timidity should work fine.
For auto Tandysound emulation is present only if machine is set to tandy. Covox Voice Master and Speech Thing compatible.
Can be disabled, dummy, modem, nullmodem, directserial. Additional parameters must be in the same line in the form of parameter:value. Parameter for all types is irq. Happy, happy, happy, happy, happy! I hope that Happy Feeling Lasts though, and the game actually runs good. Posted 28 October - PM Okay, set the Prebuffer for the sound up to 20 and not too bad, so upped it to 24 now. Game runs good although may be a little slow but not really with my 3. And if downloading from Underdogs then find the sound files.
That music is really needed and good in this game. It is errie and atmospheric. This game was not changed for the Collector's Edition. I know I own both versions and it is the same version. So far so good. M: Apocalypse Both versions ms-dos or Windows actually the same version.
It runs in ms-dos better though, I guess, well, probably. Otherwise, the only way to assure it would run smoother and again it is not all that bad at all, is to totally probably have DosBox in machine language or what is known as assembly language. Otherwise it almost runs like normal in DosBox, but again one can download the source code at the SourceForge. Well, perhaps later take a look at the source code and probably only being a beginner programmer, not acheive much in that department.
But so far, even with a "Standard" game install and all and using the CD, the game is about running the best it can. I might try more "Prebuffer" with the sound like up to 40 or 50 perhaps, but still because of the way that DVD-ROM seem to not spin all the time, and the access time to acess the CD in the Drive it runs -- good enough to play the game.
Another reason why critical routines like accessing a CD Drive needs to be like they are - in the fastest code possible to acheive smoothness in any program or game.
Posted 29 October - PM Ah, ya, if DosBox reported the harddisk drive space like Windows does, then I would have had enough room for a complete install, so that would be something to look at in DosBox, or why every logical drive I have reports in DosBox being only mB instead of what Windows show those logical drives. I mean my ms-dos FAT16 logical drive is 1gB and every other logical drive is at last 8gB and major ones 20gB out of the complete gB harddrive. It is the way they make harddisk from even a few years ago and cram the data on in smaller parts of the harddrive.
If that was fixed perhaps in DosBox then the complete game could be installed in DosBox, and also at Microsoft you can also download ms-dos 6. Something to consider, but right now I would not know exactly how that would work and interfere with the commands from DosBox unless you just started the shell and left everything else false and then somehow were able to actually start real ms-dos version 6.
But then DosBox slows things down, and that is very important but having some programs of ms-dos would also help like the complete commands of the "mem" program which does not exist in DosBox. Well, something to think about with the source code download of DosBox, but it uses Makefiles and not really what I know, without learning all about that and I think it was programmed more with Unix than Microsoft VisualStudio.
NET the only version I have as the rest is too expensive to consider without using another compiler and all of that. Well, something to think about, if that routine could call the Windows's routine to get the amount of harddisk space Windows shows for the logical drive.
Then the complete game could have been installed in DosBox, and that seems to be the best way to go, to get the game running with the xcom. Other work to do right now, and all of it would have been installed if the harddisk space would have been reported correctly in DosBox, and then the game would run even better although it is alright as of now with the "Standard" install and accessing the CD disk in the DVD-ROM drive.
Posted 05 November - PM Less reading time is needed to gather the data files off the CD, which is very slow. Particularly noticeable if you were to play it on a computer that it was built for back when it came out. The largest installation doesn't even put all of the files onto the hard drive.
In fact, it leaves the movies and music on the CD. Use the 'internaldriver' option to try Dosemu internaldriver. Use the 'emulate3buttons' for 3button mice. Therefore, there is no need to load IPX. The following option does not emulate LSL.
COM , etc. The smaller the number, the more frequent. A value of 20 gives a frequency of about one per second, which is very slow. A value of 4 is recommended in most cases, but if you have a fast system or link, you can decrease this to 0. Use the following to enable the IBM character set. This is the normal case "title" string default "dosemu" What you want dosemu to display in the title bar of its window.
Must be monospaced. QuickStart: Start with only text video using the following line, to get started. This is not always necessary, but a word to the wise shall be sufficient. NOTE: Make sure no more then one process is using this feature! Note: May interfere with serial ports when using certain video boards. This really only has an effect on kernels prior to 1.
For ems, you now can set the frame to any 16K between 0xc You can only map in entities of 4k, you give the address, not the segment. The default is 'off'. Thin glass wire designed for light transmission, capable of transmitting billions of bits per second. Unlike electrical pulses, light pulses are not affected by random radiation in the environment.
NIST Modifying a program to improve performance; e. A relational database programming system incorporating the SQL programming language.
A registered trademark of the Oracle Corp. ISO In a calculator, the state in which the calculator is unable to accept or process the number of digits in the entry or in the result. See: arithmetic overflow. IEEE An exception that occurs when the result of an arithmetic operation exceeds the size of the storage location designated to receive it.
Contrast with serial. IEEE A constant, variable or expression that is used to pass values between software modules. Syn: argument. An error detection method in data transmissions that consists of selectively adding a 1-bit to bit patterns [word, byte, character, message] to cause the bit patterns to have either an odd number of 1-bits [odd parity] or an even number of 1-bits [even parity]. ISO A binary digit appended to a group of binary digits to make the sum of all the digits, including the appended binary digit, either odd or even, as predetermined.
ISO A redundancy check by which a recalculated parity bit is compared to the predetermined parity bit. Contrast with check summation, cyclic redundancy check [CRC]. A high-level programming language designed to encourage structured programming practices.
ISO A character string that enables a user to have full or limited access to a system or to a set of data. IEEE A change made directly to an object program without reassembling or recompiling from the source program. IEEE A sequence of instructions that may be performed in the execution of a computer program. IEEE Analysis of a computer program [source code] to identify all possible paths through the program, to detect incomplete paths, or to discover portions of the program that are not on any path.
IEEE Software maintenance performed to improve the performance, maintainability, or other attributes of a computer program. Contrast with adaptive maintenance, corrective maintenance. IEEE A requirement that imposes conditions on a functional requirement; e. Equipment that is directly connected a computer. A peripheral device can be used to input data; e.
Syn: peripheral equipment. Synonymous with microcomputer, a computer that is functionally similar to large computers, but serves only one user. IEEE An audit conducted to verify that a configuration item, as built, conforms to the technical documentation that defines it.
See: functional configuration audit. IEEE A requirement that specifies a physical characteristic that a system or system component must posses; e. IEEE 1 In image processing and pattern recognition, the smallest element of a digital image that can be assigned a gray level. This term is derived from the term "picture element". The hardware and software which must be present and functioning for an application program to run [perform] as intended.
A technique a CPU can use to learn if a peripheral device is ready to receive data or to send data. In this method each device is checked or polled in-turn to determine if that device needs service.
The device must wait until it is polled in order to send or receive data. This method is useful if the device's data can wait for a period of time before being processed, since each device must await its turn in the polling scheme before it will be serviced by the processor. Contrast with interrupt. A type of microelectronic circuit in which the base material is positively charged. The relative degree of repeatability, i.
It is the result of resolution and stability. See: accuracy, bias, calibration. IEEE 1 The process of analyzing design alternatives and defining the architecture, components, interfaces, and timing and sizing estimates for a system or component.
See: detailed design. IEEE A review conducted to evaluate the progress, technical adequacy, and risk resolution of the selected design approach for one or more configuration items; to determine each design's compatibility with the requirements for the configuration item; to evaluate the degree of definition and assess the technical risk associated with the selected manufacturing methods and processes; to establish the existence and compatibility of the physical and functional interfaces among the configuration items and other items of equipment, facilities, software and personnel; and, as applicable, to evaluate the preliminary operational and support documents.
A flat board that holds chips and other electronic components. The board is "printed" with electrically conductive pathways between the components. The computer file that contains the establishment's current production data. Processing may include the use of an assembler, a compiler, an interpreter, or another translator to prepare the program for execution.
The instructions may include statements and necessary declarations. IEEE A specification language with special constructs and, sometimes, verification protocols, used to develop, analyze, and document a program design. IEEE A computer program that has been purposely altered from the intended version to evaluate the ability of program test cases to detect the alteration.
See: testing, mutation. A programmable logic chip. See: programmable logic device. A logic chip that is programmed at the user's site. Contrast with PROM. A chip which may be programmed by using a PROM programming device. It can be programmed only once. It cannot be erased and reprogrammed. Each of its bit locations is a fusible link. An unprogrammed PROM has all links closed establishing a known state of each bit.
Programming the chip consists of sending an electrical current of a specified size through each link which is to be changed to the alternate state. This causes the "fuse to blow", opening that link.
IEEE A language used to express computer programs. See: computer language, high-level language, low-level language. IEEE Analysis to ensure that all portions of the program follow approved programming guidelines. See: code audit, code inspection. NIST A management document describing the approach taken for a project. The plan typically describes work to be done, resources required, methods to be used, the configuration management and quality assurance procedures to be followed, the schedules to be met, the project organization, etc.
Project in this context is a generic term. Some projects may also need integration plans, security plans, test plans, quality assurance plans, etc. See: documentation plan, software development plan, test plan, software engineering. PROM programmer. NBS The use of techniques of mathematical logic to infer that a relation between program variables assumed true at program entry implies that another relation between program variables holds at program exit.
IEEE An exception that occurs when a program attempts to write into a protected area in storage. ISO A set of semantic and syntactic rules that determines the behavior of functional units in achieving communication. Using software tools to accelerate the software development process by facilitating the identification of required functionality during analysis and design phases. A limitation of this technique is the identification of system or software problems and hazards.
See: rapid prototyping. A combination of programming language and natural language used to express a software design. If used, it is usually the last document produced prior to writing the source code.
FDA Establishing confidence that process equipment and ancillary systems are compliant with appropriate codes and approved design intentions, and that manufacturer's recommendations are suitably considered. FDA Establishing confidence that process equipment and sub-systems are capable of consistently operating within established limits and tolerances.
FDA Establishing confidence that the process is effective and reproducible. FDA Establishing confidence through appropriate testing that the finished product produced by a specified process meets all release requirements for functionality and safety.
IEEE 1 A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements. The operational techniques and procedures used to achieve quality requirements. High frequency electromagnetic waves that emanate from electronic devices such as chips and other electronic devices.
An electromagnetic disturbance caused by such radiating and transmitting sources as electrostatic discharge [ESD], lightning, radar, radio and TV signals, and motors with brushes can induce unwanted voltages in electronic circuits, damage components and cause malfunctions. See: electromagnetic interference. The term random access means that each memory location [usually 8 bits or 1 byte] may be directly accessed [read from or written to] at random.
ISO A limit check in which both high and low values are stipulated. A structured software requirements discovery technique which emphasizes generating prototypes early in the development process to permit early feedback and analysis in support of the development process.
Contrast with incremental development, spiral model, waterfall model. See: prototyping. A memory chip from which data can only be read by the CPU. The CPU may not store data to this memory. IEEE Pertaining to a system or mode of operation in which computation is performed during the actual time that an external process occurs, in order that the computation results can be used to control, monitor, or respond in a timely manner to the external process.
See: conversational, interactive, interrupt, on-line. A fast-response [immediate response] on-line system which obtains data from an activity or a physical process, performs computations, and returns a response rapidly enough to affect [control] the outcome of the activity or process; e.
Contrast with batch processing. Documentation of changes made to the system. A record of change can be a written document or a database. Normally there are two associated with a computer system, hardware and software. Changes made to the data are recorded in an audit trail. IEEE 1 The process of defining or generating a process or data structure in terms of itself.
Computer architecture that reduces the complexity of the chip by using simpler instructions. Reduced instruction set does not necessarily mean fewer instructions, but rather a return to simple instructions requiring only one or a very few instruction cycles to execute, and therefore are more effectively utilized with innovative architectural and compiler changes.
Systems using RISC technology are able to achieve processing speeds of more than five million instructions per second. Regions are used to separate testing from production [normal use]. Syn: partition. A small, high speed memory circuit within a microprocessor that holds addresses and values of internal operations; e.
Each microprocessor has a specific number of registers depending upon its design. See: testing, regression. Database organization method that links files together as required.
Relationships between files are created by comparing data such as account numbers and names. A relational system can take any two or more files and generate a new file from the records that meet the matching criteria.
Routine queries often involve more than one data file; e. Contrast with network database, flat file. IEEE The formal notification and distribution of an approved version. See: version. IEEE The ability of a system or component to perform its required functions under stated conditions for a specified period of time.
See: software reliability. IEEE 1 A condition or capability needed by a user to solve a problem or achieve an objective. See: design requirement, functional requirement, implementation requirement, interface requirement, performance requirement, physical requirement. IEEE 1 The process of studying user needs to arrive at a definition of a system, hardware, or software requirements. See: prototyping, software engineering.
IEEE The period of time in the software life cycle during which the requirements, such as functional and performance capabilities for a software product, are defined and documented. IEEE A process or meeting during which the requirements for a system, hardware item, or software item are presented to project personnel, managers, users, customers, or other interested parties for comment or approval.
Types include system requirements review, software requirements review. Contrast with code review, design review, formal qualification review, test readiness review. ISO The length of time specified for data on a data medium to be preserved.
IEEE A trace produced from historical data recorded during the execution of a computer program. Note: this differs from an ordinary trace, which is produced cumulatively during program execution. See: execution trace, subroutine trace, symbolic trace, variable trace.
Relative to software changes, revalidation means validating the change itself, assessing the nature of the change to determine potential ripple effects, and performing the necessary regression testing. IEEE A process or meeting during which a work product or set of work products, is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Types include code review, design review, formal qualification review, requirements review, test readiness review.
Contrast with audit, inspection. IEEE A measure of the probability and severity of undesired effects. Often taken as the simple product of probability and consequence. DOD A comprehensive evaluation of the risk and its associated impact.
The degree to which a software system or component can function correctly in the presence of invalid inputs or stressful environmental conditions. IEEE A subprogram that is called by other programs and subprograms. Note: This term is defined differently in various programming languages.
See: module. Data is transmitted and received in serial format. DOD Freedom from those conditions that can cause death, injury, occupational illness, or damage to or loss of equipment or property, or damage to the environment. DOD A term applied to a condition, event, operation, process or item of whose proper recognition, control, performance or tolerance is essential to safe system operation or use; e.
DOD Those computer software components and units whose errors can result in a potential hazard, or loss of predictability or control of a system. A peripheral input device which senses some variable in the system environment, such as temperature, and converts it to an electrical signal which can be further converted to a digital signal for processing by the computer.
Contrast with parallel. A high speed computer in a network that is shared by multiple users. It holds the programs and data that are shared by all users. ANSI 1 An automatic device that uses feedback to govern the physical position of an element. An unintended alteration of a program's behavior caused by a change in one part of the program, without taking into account the effect the change has on another part of the program.
See: regression analysis and testing. During testing the computational hardware, the external environment, and even code segments may be simulated. Contrast with emulation. IEEE A device, computer program, or system that behaves or operates like a given system when provided a set of controlled inputs. Contrast with emulator. A simulator provides inputs or responses that resemble anticipated process parameters.
Its function is to present data to the system at known speeds and in a proper format. IEEE The process of estimating the amount of computer storage or the number of source lines required for a software system or component.
Contrast with timing. A standard method of interfacing a computer to disk drives, tape drives and other peripheral devices that require high-speed data transfer. ANSI Programs, procedures, rules, and any associated documentation pertaining to the operation of a system. Contrast with hardware. See: application software, operating system, system software, utility software.
An inherent, possibly accidental, trait, quality, or property of software; e. IEEE A representation of software created to facilitate analysis, planning, implementation, and decision making. The software design description is used as a medium for communicating software design information, and may be thought of as a blueprint or model of the system. See: structured design, design description, specification. NIST A collection of material pertinent to the development of a software module.
Contents typically include the requirements, design, technical reports, code listings, test plans, test results, problem reports, schedules, notes, etc. Syn: software development file. NIST The project plan for the development of a software product. Contrast with software development process, software life cycle. IEEE The process by which user needs are translated into a software product. Note: these activities may overlap or be performed iteratively.
IEEE A software development technique in which two or more functionally identical variants of a program are developed from the same specification by different programmers or programming teams with the intent of providing error detection, increased reliability, additional documentation or reduced probability that programming or compiler errors will influence the end results.
See: specification; specification, requirements; specification, design; software design description; test plan, test report, user's guide. IEEE A deliverable or in- process document produced or acquired during software development or maintenance.
Specific examples include but are not limited to:. IEEE The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; i. See: project plan, requirements analysis, architectural design, structured design, system safety, testing, configuration management. IEEE The hardware, software, and firmware used to perform a software engineering effort.
Typical elements include computer equipment, compilers, assemblers, operating systems, debuggers, simulators, emulators, test tools, documentation tools, and database management systems. ODE, CDRH The identification of safety-critical software, the classification and estimation of potential hazards, and identification of program path analysis to identify hazardous combinations of internal and environmental program conditions.
See: risk assessment, software safety change analysis, software safety code analysis, software safety design analysis, software safety requirements analysis, software safety test analysis, system safety. IEEE Source code, object code, job control code, control data, or a collection of these items. Contrast with software element. NIST Period of time beginning when a software product is conceived and ending when the product is no longer available for use.
The software life cycle is typically broken into phases denoting activities such as requirements, design, programming, testing, installation, and operation and maintenance. Contrast with software development process. IEEE 1 the probability that software will not cause the failure of a system for a specified time under specified conditions.
The probability is a function of the inputs to and use of the system in the software. The inputs to the system determine whether existing faults, if any, are encountered.
IEEE An evaluation of software elements to ascertain discrepancies from planned results and to recommend improvement. This evaluation follows a formal process. Syn: software audit. See: code audit, code inspection, code review, code walkthrough, design review, specification analysis, static analysis. IEEE Analysis of the safety-critical design elements affected directly or indirectly by the change to show the change does not create a new hazard, does not impact on a previously resolved hazard, does not make a currently existing hazard more severe, and does not adversely affect any safety-critical software design element.
See: software hazard analysis, system safety. IEEE Verification that the safety-critical portions of the design are correctly implemented in the code. See: logic analysis, data analysis, interface analysis, constraint analysis, programming style analysis, noncritical code analysis, timing and sizing analysis, software hazard analysis, system safety. IEEE Verification that the safety-critical portion of the software design correctly implements the safety-critical requirements and introduces no new hazards.
See: logic analysis, data analysis, interface analysis, constraint analysis, functional analysis, software element analysis, timing and sizing analysis, reliability analysis, software hazard analysis, system safety.
IEEE Analysis evaluating software and interface requirements to identify errors and deficiencies that could contribute to a hazard. See: criticality analysis, specification analysis, timing and sizing analysis, different software systems analyses, software hazard analysis, system safety.
IEEE Analysis demonstrating that safety requirements have been correctly implemented and that the software functions safely within its specified environment.
Tests may include; unit level tests, interface tests, software configuration item testing, system level testing, stress testing, and regression testing. Contrast with object code. See: source program, programming language.
IEEE A computer program that must be compiled, assembled, or otherwise translated in order to be executed by a computer. Contrast with object program. See: source code. Program source code written without a coherent structure. Implies the excessive use of GOTO instructions. Contrast with structured programming. NBS Test data based on input values that are likely to require special handling by the program.
See: error guessing; testing, special case. IEEE A document that specifies, in a complete, precise, verifiable manner, the requirements, design, behavior,or other characteristics of a system or component, and often, the procedures for determining whether these provisions have been satisfied.
Contrast with requirement. See: specification, formal; specification, requirements; specification, functional; specification, performance; specification, interface; specification, design; coding standards; design standards. IEEE Evaluation of each safety-critical software requirement with respect to a list of qualities such as completeness, correctness, consistency, testability, robustness, integrity, reliability, usability, flexibility, maintainability, portability, interoperability, accuracy, auditability, performance, internal instrumentation, security and training.
NIST A specification that documents how a system is to be built. Contrast with design standards, requirement. NIST 1 A specification written and approved in accordance with established standards. NIST A specification that documents the functional requirements for a system or system component. It describes what the system or component is to do rather than how it is to be built.
Often part of a requirements specification. NIST A specification that documents the interface requirements for a system or system component. IEEE A document that sets forth the performance characteristics that a system or component must possess. These characteristics typically include speed, accuracy, and memory usage. IEEE A document which describes the as built version of the software. NIST A specification that documents the requirements of a system or system component. It typically includes functional requirements, performance requirements, interface requirements, design requirements [attributes and constraints], development [coding] standards, etc.
IEEE A diagram that depicts all of the specifications for a given system and shows their relationship to one another.
IEEE A model of the software development process in which the constituent activities, typically requirements analysis, preliminary and detailed design, coding, integration, and testing, are performed iteratively until the software is complete. Syn: evolutionary model. Contrast with incremental development; rapid prototyping; waterfall model. Written procedures [prescribing and describing the steps to be taken in normal and defined conditions] which are necessary to assure control of production and processes.
IEEE 1 A condition or mode of existence that a system, component, or simulation may be in; e. IEEE A diagram that depicts the states that a system or component can assume, and shows the events or circumstances that cause or result from a change from one state to another. Syn: state graph. See: state-transition table. Beizer A representation of a state graph that specifies the states, the inputs, the transitions, and the outputs. See: state diagram.
0コメント