English
Français
Español
Deutsch
Italiano
日本語
Nederlands
العربية
简体中文
繁體中文
Português
Download Now: Windows Error Repair Tool
**SmartPCFixer will repair Windows Error and registry data errors on your PC
File extension Details of DBA, DCF, DCT, DD, DDP, DEB, DEF, DEF, DEF
| Name: | DBA |
| File Type: | DarkBASIC source code |
| Popularity: | 4 |
| Category: | Source code and script file |
| File Description: | File extension is used by DarkBASIC. File contains source code. |
| Open Programs: | DarkBASIC Company / developer: DarkBASIC Professional is the most advanced games development package built on the BASIC language currently available. No other package out there makes it as easy to incorporate all of the special features and effects you see in todays games and no other package natively offers the benefits of Microsofts DirectX 9 technology. |
| Name: | DCF |
| File Type: | D-Lib generic bytecode |
| Popularity: | 2 |
| Category: | Source code and script file |
| File Description: | D-LIB is script programming language. D-LIB has the typical structure of Basic and all main Basic statements. D-LIB has some interesting features. It compiles to small stand-alone EXEs with an 18.5 Kb header only. The code may be compressed for fast compiling and linking. It fully supports WinAPI (over 44000 known Windows API-Constants and over 9800 known Windows API-Functions) and about 150 implemented functions. D-LIB offers dynamic arrays, procedure, user functions, code includes to split the the source in several pieces of code. The package contains some examples and a practical code editor. D-Lib does not nativly manage forms. The D-Lib scripting language has undergone an extensive overhaul and a beta release of version 2 is available. It is essentially a different language to the original one, although the concept is the same. The syntax is very similar to Basic The concept of having user-made external functions as the core to the language has been retained. Structure type variables have been added and all Windows structures are pre-defined, along with all Win32 API functions and constants. The documentation has been completely rewritten and improved. |
| Open Programs: | D-Lib Company / developer:
|
| Name: | DCT |
| File Type: | Delphi component template |
| Popularity: | 2 |
| Category: | Source code and script file |
| File Description: | File extension is used by Delphi. |
| Open Programs: | Delphi Company / developer: Delphiis a software development package created by Borland, now owned by Borland's subsidiary - CodeGear. |
| Name: | DD |
| File Type: | Deployment diagram file |
| Popularity: | 4 |
| Category: | Source code and script file |
| File Description: | File extension is used by Microsoft Visual Studio. Deployment diagram file. |
| Open Programs: | Microsoft Visual Studio Company / developer: New tools tailored to help you take on your software development challenges. Visual Studio provides a range of tools that offer many benefits for individual developers and software development teams:
|
| Name: | DDP |
| File Type: | Delphi Diagramm page from compiler |
| Popularity: | 2 |
| Category: | Source code and script file |
| File Description: | Delphi diagram portfolio file (Delphi 7 or older). Used by the diagram editor. |
| Open Programs: | Delphi Company / developer: Delphiis a software development package created by Borland, now owned by Borland's subsidiary - CodeGear. |
| Name: | DEB |
| File Type: | Debug script of DOS MS Debug |
| Popularity: | 4 |
| Category: | Source code and script file |
| File Description: | In 1980, Tim Paterson began working on a 16-bit OS for the 8086 S-100 Bus card he had designed for SCP (Seattle Computer Products) the previous year. To help in getting QDOS (later called 86-DOS) to work correctly, Tim created a debugger in a ROM chip; the code for that ROM version was released into the Public Domain. Later, Tim adapted the code to run as a .COM program under QDOS, and also added the ability to disassemble 8086 machine code. In the meantime, Microsoft® had been busy purchasing the rights to sell Tim's QDOS to IBM® for their 'secret' PC project. Tim was then hired by Microsoft as the primary author of their first OS. When he completed his work on IBM's Personal Computer™ DOS 1.00 in 1981, his DEBUG.COM utility was included with it. All the functionality that Tim put into DEBUG is still there and little has been added to it (the major exception being the Assemble command; added under DOS 2.0).
With the release of DOS 2.0, DEBUG gained the ability to assemble instructions directly into machine code (the A command). This is one of the most important commands for many of its users. Though lacking much of the functionality of a stand-alone Assembler, e.g., all Jumps must be to hexadecimal addresses (no labels can be used), many useful .COM programs have been assembled with this command. Under DOS 3.0, the P (Proceed) command was added, so DEBUG could quickly execute subroutines; at the same time, it became possible to attempt stepping through Interrupts with the T (Trace) command. When DOS made EMS (Expanded Memory) functions available under DOS 4.0, the four commands xa, xd, xm and xs were also added to DEBUG. It appears they were rarely, if ever used though, even by programmers. For most of us, the only noticeable change in DEBUG was the addition of the help command (type a '?' while inside DEBUG) under DOS 5.0; when all DOS commands finally got the /? command-line switch. DEBUG's code went through a number of changes (and 'bug fixes' too) over the years! Some of these internal changes were related to DOS system calls and screen output, then there was the change in file type from a .COM to an .EXE program under DOS 5.0. But in spite of all those changes and others which followed, DEBUG has never had an official revision since 2.40 (those digits have been embedded inside all versions of DEBUG since DOS 3.0). We can only guess about the real reasons that Microsoft® never updated DEBUG to handle instructions beyond those of the Intel® 8086/8087/8088 processors. Microsoft® did create their own Assembler (MASM), 'C' compiler and Debugger (CodeView ); which you could use too, if you were willing to pay extra, so that could have been one of their reasons. Rather than using MASM and CodeView, many opted for the less expensive Borland® assembler (TASM) and Turbo™ Debugger when they appeared, or some other commercial product. However, users and students alike can still learn a great deal about Assembly language by using DEBUG. |
| Open Programs: | MS DOS Company / developer: MS-DOSMS-DOS (short for Microsoft Disk Operating System) is an operating system commercialized by Microsoft. It was the most commonly used member of the DOS family of operating systems and was the dominant operating system for computers based on the Intel 8086 family of microprocessors, particularly the IBM PC and compatibles, during the 1980s. It was gradually replaced on consumer desktop computers by operating systems offering a graphical user interface (GUI), in particular by various generations of the Microsoft Windows operating system. It was originally known as QDOS (Quick and Dirty Operating System) and 86-DOS. MS-DOS was originally released in 1981 and had eight major versions released before Microsoft stopped development in 2000. It was the key product in Microsoft's growth from a programming languages company to a diverse software development firm, providing the company with essential revenue and marketing resources. It was also the underlying basic operating system on which early versions of Windows ran as a GUI. |
| Name: | DEF |
| File Type: | ADS source code file |
| Popularity: | 2 |
| Category: | Source code and script file |
| File Description: | Source code file used by some Autodesk applications. |
| Open Programs: | AutoCAD Company / developer: AutoCAD® OEM is a CAD development platform that provides tools to build custom AutoCAD-based software products for specific markets and extend design information to users outside the traditional CAD community. You can easily create industry-specific products that offer only the features, commands, menus, and design data that your customers require. AutoCAD OEM is licensed to independent software developers, corporate developers, and system integrators who need to
|
| Name: | DEF |
| File Type: | Microsoft Visual C++ definition file |
| Popularity: | 4 |
| Category: | Source code and script file |
| File Description: | Definition file used by Microsoft Visual C++. |
| Open Programs: | Microsoft Visual Studio Company / developer: New tools tailored to help you take on your software development challenges. Visual Studio provides a range of tools that offer many benefits for individual developers and software development teams:
|
| Name: | DEF |
| File Type: | Modula-2 definition module file |
| Popularity: | 2 |
| Category: | Source code and script file |
| File Description: | Modula-2 is a computer programming language invented by Niklaus Wirth at ETH, around 1978, as a successor to his intermediate language Modula. Modula-2 was implemented in 1980 for the Lilith computer, which was commercialized in 1982 by startup company DISER (Data Image Sound Processor and Emitter Receiver System) as MC1 and MC2. DISER sold 120 units worldwide. The Modula-2 language was understood by Niklaus Wirth as a successor to his first major programming language Pascal. The language design was also influenced by the Mesa programming language and the new programming possibilities of the early personal computer Xerox Alto, both from Xerox, that Wirth saw during his 1976 sabbatical year at Xerox PARC. |
| Open Programs: | Modula-2 for Java Company / developer: Canterbury Modula-2 for Java is a Modula-2 programming language compiler for Java. It is distributed and supported by MHCCORP.COM. The compiler is implemented in Java and generates Java source code. The current downloadable trial version is good till the end of September 2008, and it has some language restrictions. |
| Name: | DEF |
| File Type: | Microsoft Linker input definition file |
| Popularity: | 4 |
| Category: | Source code and script file |
| File Description: | Module-definition (.def) files provide the linker with information about exports, attributes, and other information about the program to be linked. A .def file is most useful when building a DLL. Because there are linker options that can be used instead of module-definition statements, .def files are generally not necessary. |
| Open Programs: | Microsoft Visual Studio Company / developer: New tools tailored to help you take on your software development challenges. Visual Studio provides a range of tools that offer many benefits for individual developers and software development teams:
|
Download Now: Windows Error Repair Tool
**SmartPCFixer will repair Windows Error and registry data errors on your PC
