 | NAGY ENGINEERING - SOFTWARE |
General Program Information for Nagy Engineering Programs
General Program Background.
Programs from Nagy Engineering are downloadable with or without the support runtime modules. For the experienced computer user, the programs can be downloaded by themself. These types are usally the smallest and least time consuming downloads. There is a good chance that the computer used already have the required runtime module. The runtime needed to be obtained only once, regardless how many programs may use it.
For those few users who are not sure, or not interested to find it out, a much larger "packaged" version is also available. This download produces a folder after unzipping, which can be moved anywhere and the program would always run correctly.
None of the programs from Nagy Engineering write anything permanent into the Registry, or anywhere into any of the computer's drives (other than the program folder itself). For the benefit of simplicity, there is no installation required. Unzip the downloaded file into a new folder, and just run the executive (.EXE) file. To uninstall, simply delete the program folder with all of it's contents.
Use of the DLLs.
Many current computer programs use the built in software routines residing in the BIOS of present day personal computers or within their operating system folders. Programs written to function in a Microsoft Windows environment usually keep their support routines in Dynamic Link Libraries [DLL].
The original DLL idea was to deposit these runtime subroutine collections into the Windows "System" directory were it languished along with all other DLLs. That way - in theory - all DLL's may be shared as a callable resource, a time saving and efficient idea. In reality, few other programs ever calls on other than the Microsoft Windows component DLL's for the simple reason that their internals and entry points are not publicized and known.
Microsoft grudgingly allows (only bacause it's compilers fail to generate standalone codes) that standard runtime modules be distributed along with user created programs. Needed or not, these huge runtime modules contain all possible callable subroutines. In its infinite greed, Microsoft prohibits the separation of the few actually used and called subroutines of these bloated runtime modules. If the cutting up of these DLLs would be possible, most probably the traffic on the internet could be significantly reduced at an instant.
Just to illustrate how greed causes inefficiencies consider the following; the size of our MiniCalc program is only 18 KiloByte [KB] alone. The required VBRUN300.DLL is 390 KB. Divide 390 with 18 and the result is about 21.6. Thus at this example, the run time module is more than 26 times the size of the application program. In higher compiler versions this example runtime DLL - written for Visual BASIC version three - begins to look like a bargain. It is easy to see that downloading the program only, would be the way to go, especially as most windows installations already have the required DLL already.
Different Program Types.
16-Bit programs work on most computers with Windows versions 3.0 and above, they require the VBRUN300.DLL run time library file. If (when used as a - program only - the smallest download) a "no DLL found" message appears, just dowload the latest copy from Microsoft, and either run the (Microsoft) install (self extract) program, or place the DLL into the program folder.
32-Bit programs work on computers running Windows versions 9.X, and above, they require different run time library files. The Visual BASIC version six compiler generated programs expect to find the vbrun60.dll runtime module. If a "no DLL found" message appears, just dowload a freshly updated copy from Microsoft, and either run the install/unpack program, or place the DLL into the program folder.
Another excellent location for these DLL files is the Windows System directory. Placing them anywhere within the computer's active "path" would also work great.
Programs from Nagy Engineering are downloadable with or without the support runtime modules. For the experienced computer user, the programs can be downloaded by themself. These types are usally the smallest and least time consuming downloads. There is a good chance that the computer used already have the required runtime module. The runtime needed to be obtained only once, regardless how many programs may use it.
For those few users who are not sure, or not interested to find it out, a much larger "packaged" version is also available. This download produces a folder after unzipping, which can be moved anywhere and the program would always run correctly.
None of the programs from Nagy Engineering write anything permanent into the Registry, or anywhere into any of the computer's drives (other than the program folder itself). For the benefit of simplicity, there is no installation required. Unzip the downloaded file into a new folder, and just run the executive (.EXE) file. To uninstall, simply delete the program folder with all of it's contents.
Use of the DLLs.
Many current computer programs use the built in software routines residing in the BIOS of present day personal computers or within their operating system folders. Programs written to function in a Microsoft Windows environment usually keep their support routines in Dynamic Link Libraries [DLL].
The original DLL idea was to deposit these runtime subroutine collections into the Windows "System" directory were it languished along with all other DLLs. That way - in theory - all DLL's may be shared as a callable resource, a time saving and efficient idea. In reality, few other programs ever calls on other than the Microsoft Windows component DLL's for the simple reason that their internals and entry points are not publicized and known.
Microsoft grudgingly allows (only bacause it's compilers fail to generate standalone codes) that standard runtime modules be distributed along with user created programs. Needed or not, these huge runtime modules contain all possible callable subroutines. In its infinite greed, Microsoft prohibits the separation of the few actually used and called subroutines of these bloated runtime modules. If the cutting up of these DLLs would be possible, most probably the traffic on the internet could be significantly reduced at an instant.
Just to illustrate how greed causes inefficiencies consider the following; the size of our MiniCalc program is only 18 KiloByte [KB] alone. The required VBRUN300.DLL is 390 KB. Divide 390 with 18 and the result is about 21.6. Thus at this example, the run time module is more than 26 times the size of the application program. In higher compiler versions this example runtime DLL - written for Visual BASIC version three - begins to look like a bargain. It is easy to see that downloading the program only, would be the way to go, especially as most windows installations already have the required DLL already.
Different Program Types.
16-Bit programs work on most computers with Windows versions 3.0 and above, they require the VBRUN300.DLL run time library file. If (when used as a - program only - the smallest download) a "no DLL found" message appears, just dowload the latest copy from Microsoft, and either run the (Microsoft) install (self extract) program, or place the DLL into the program folder.
32-Bit programs work on computers running Windows versions 9.X, and above, they require different run time library files. The Visual BASIC version six compiler generated programs expect to find the vbrun60.dll runtime module. If a "no DLL found" message appears, just dowload a freshly updated copy from Microsoft, and either run the install/unpack program, or place the DLL into the program folder.
Another excellent location for these DLL files is the Windows System directory. Placing them anywhere within the computer's active "path" would also work great.
| Copyright © 2011 K Nagy - http://www.NagyEngineering.com - All Rights Reserved Page Revised: 2011-04-01 - - Privacy Policy - Site Map |