test drive unlimited download pc tpbvirtual light lab model downloadstar wars galaxies download trialvideo vault free download
ALL downloads featured listed here are on my MUST HAVE list, also seen in, portion of my Windows 9x/NT4/2000/ME/XP/2003 DOS /8.00 Tricks Secrets files , FREEware.
Some these files are archived in ZIP, RAR, 7Z or CAB format. You need a file decompression unZIPping/unARChiving/unRARing tool to extract their contents. I recommend freeware:
Target Operating Systems/software/hardware REQUIRED for installing upgrades/patches/fixes/drivers!
Installing Windows OS components/upgrades/patches/fixes/drivers/tools might require you to be logged i'll carry on with Administrative/Power User/Sysadmin privileges.
Windows Vista/2008/7/8/8.1/2012/10 users: right-click each file and select Run as Administrator temporary fix or disable User Account Control UAC permanent fix in:
Items defined as discontinued! : obsolete, unmaintained/- abandoned.
I usually do not recommend any shareware/trialware/retail programs, except the few essentials in my MUST HAVE list, and just if I could hardly find any freeware alternative.
Check back often for NEW tools UPDATEs.
WINDOWS NEW TECHNOLOGY NT 4.0
NT 4.0 Links: Windows NT 4.0 Info Updates within the Internet:
Windows NT 4.0 Post-SP6a Updates Fixes
MUST reboot into Safe Mode copy from C:Program FilesMicrosoft Visual StudioVB98WIZARDSPDWIZARDREDISTNT4 default to %windir% SYSTEM32 %windir% usually C:WINNT as well as %windir% SYSTEM32DLLCACHE if any reboot normal!
BUG: This fix breaks the ability of removing annoying arrows from Desktop shortcut icons!
Microsoft DCOM Scan tool v1.0 for Windows NT4/2000/XP/2003 scans networks to distinguish host computers WITHOUT RPC Buffer Overrun Fix installed:
Install this Fix AFTER the Help Support Center Fix below!
Windows NT 4.0 Service Pack 6.0a SP6a
NT4 SP6a requires 2-36 MB of disk space based on system configuration.
Compaq Smart Array Controllers users MUST also install this Fix!
I usually do not promote, speak from the behalf of, advertise or be employed by any computing, news or internet profit business. All copyrights and registered trademarks retain owners property.
FREE WINDOWS 9x/NT/2000/ME/XP/2003/Vista/2008/7/8/8.1/2012 ESSENTIAL SYSTEM COMPONENTS ADD-ONS
FREE WINDOWS NT4/2000/XP/2003/Vista/2008/7/8/8.1/2012 NTx EXTRAS
DIRECTX DX ESSENTIAL FREE UPGRADES, FIXES TOOLS
1000 Windows 9x/NT/2000/ME/XP/2003/Vista/2008/7/8/8.1/2012 POWER TOYS
MSKB: Tips for Troubleshooting Windows NT 4.0 Installation Problems.
Microsoft Windows NT 4.0 SP6a OLE Automation 2.40.4520.0 Security Vulnerability Fix:
Unofficial Windows 95/OSR1/OSR2/98/98 SP1/98 SE/NT4/ME TZ Environment Variable Errors 6.1.9848.0 Fix:
Unofficial Windows NT 4.0 256 Colors Icons Explorer 4.0.1381.7096 Fix English:
Unofficial Windows NT 4.0 SP6a Microsoft Foundation Classes MFC Security Vulnerability Fix:
Unofficial Windows NT 4.0 SP6a WMF Graphics Rendering Engine GRE Security Vulnerability Fix English:
WinNT4 Terminal Server 4.0.1381.33567 Fix 180 KB.
Unofficial Windows 98/98 SP1/98 SE/NT4 SP6a/ME Hyperlink Object 5.2.3790.2748 Security Vulnerability Fix:
Unofficial Windows 98/98 SP1/98 SE/NT4SP6a/ME Embedded Web Fonts 5.00.2195.7348 Security Vulnerability Fix:
Microsoft Windows NT 4.0 SP6a License Logging Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server SP6a Cursor Icon Handling Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server WINS Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server Kernel and LSASS Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server HyperTerminal Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server DHCP Security Vulnerability Fix:
Microsoft Windows NT 4.0 SP6a Shell Remote Code Execution, Security Vulnerability Fix:
Microsoft Windows NT 4.0 SP6a Option Pack OP Remote Code Execution Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server SP6a Remote Code Execution, , , , Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server SP6a NetDDE Remote Code Execution Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server SP6a RPC Disclosure Denial of Service, Security Vulnerability Fix:
Microsoft Windows NT 4.0 SP6a IIS 4.0,, , , , , , , Security Vulnerability Fix:
Microsoft Windows NT 4.0 SP6a POSIX Security Vulnerability Fix English:
Microsoft Windows NT 4.0 SP6a RPC/DCOM Cumulative Security Vulnerability Fix English:
Microsoft Windows NT 4.0 SP6a, , , , , , , , , , , , , Security Vulnerability Fix English:
Microsoft Windows NT 4.0 SP6a Multiple Networks Errors, , Fix English:
Microsoft Windows NT 4.0 SP6a Messenger Service Buffer Overrun, , Security Vulnerability Fix English:
Microsoft Windows NT 4.0 Server NetBIOS Flaw Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server Flaw Security Vulnerability Fix:
Microsoft Windows NT 4.0 Named Pipes Connection Error Fix:
Microsoft Windows NT 4.0 SMB Buffer Overrun Security Vulnerability Fix:
Microsoft Windows NT 4.0 IIS 4.0 Web Server Unchecked Buffer Security Vulnerability Fix:
Microsoft Windows NT 4.0 Indexing Services Cross Site Scripting Security Vulnerability Fix:
Microsoft Windows NT 4.0 Locator Service Unchecked Buffer Security Vulnerability Fix:
Microsoft Windows NT4/2000 100 MB Networks High Rate Collisions Registry Fix.
Microsoft Windows NT 4.0 Certificate Flaw Deletion Security Vulnerability Fix:
Microsoft Windows NT 4.0 DoS Unchecked SMB Buffer Security Vulnerability Fix:
Microsoft Windows NT 4.0 Server RAS Phonebook Buffer Overrun, Security Vulnerability Fix English:
Microsoft Windows NT 4.0 Debugger Authentication Flaw Security Vulnerability Fix:
Microsoft Windows NT 4.0 SNMP Unchecked Buffer Security Vulnerability Fix:
Microsoft Windows NT 4.0/98/98 SP1/98 SE System Preparation Tools WinNT4 Win98/98 SP1/98 SE allow Windows NT4/98/98 SP1/98 SE automated OS install/deployment on in excess of 1 computer:
NT 4.0 SP6a: Microsoft Windows NT 4.0 Service Pack 6.0a SP6a 128-bit SSL encryption installs ALL previously released OS Service Packs Fixes Updates English:
Microsoft Windows NT 4.0 Post-SP6a Security Rollup Package SRP:
Microsoft Windows NT 4.0 Post-SP6a Winsock Fails Without Administrator Rights Fix:
WINDOWS 9x/NT/2000/ME/XP/2003/Vista/2008/7/8/8.1/2012 ESSENTIAL SYSTEM COMPONENTS ADD-ONS.
DIRECTX DX ESSENTIAL FREE UPGRADES, FIXES TOOLS.
WINDOWS MEDIA PLAYER WMP 6/7/8/9/10/11/12 ESSENTIAL FREE FIXES UPDATES.
FREE WINDOWS NT4/2000/XP/2003/Vista/2008/7/8/8.1/2012 NTx EXTRAS.
jetzt mit UnterstРЎРЉtzung fРЎРЉr Windows 10, Visual Studio 2015
Abstract: Microsoft has released version 2.0 on the Windows Installer runtime files and also the Windows Installer SDK. Besides support for Windows XP and 64 bit applications, this version includes bug fixes and introduces useful os properties, to detect whether setup is running on NT Workstation or Server, or perhaps XP Professional or Home Edition. It also significantly simplifies updates by reduction of the need for complicated ADDLOCAL and REINSTALL constructs, with out longer needs a reboot after installing the runtime files. The good news is that one could benefit from these improvements inside your existing projects. Some modifications within your authoring tool may be needed to install the newest runtime files. As a result in the improvements and fixes in MSI 2.0 you might find that your setups and patches behave differently compared to what they used to as well as fail. Even if you dont include MSI 2.0 inside your own setup, the newest version may already be present for the target machine, and that means you should at l
If youre much like me you want to go on and play with the newest version prior to into the theory. Be warned that installing the revolutionary SDK will update common files that InstallShield uses to make your releases. In order to keep your production machine within a known good state in anticipation of having fully explored the implications of MSI 2.0 you should employ a test machine to learn with the newest SDK and runtime files.
For Windows 95, Windows 98 and Windows Me:
Please remember that the system requirements have changed for Windows NT which now requires Service Pack 6. For previous MSI versions Service Pack 3 was sufficient.
Both redistributable files are named For use with InstallShield you ought to rename the Unicode version for Windows NT/2000 to, plus the ANSI version for Windows 95/98/ME to
If you've downloaded the MSI 2.0 redistributables before September 25, 2001, you need to redownload the version for Windows 9X. MSI 2.0 has first been published on August 28, 2001 that has a version variety of 2.0.2600.0. However this release is withdrawn online site three or more weeks later. On September 25 MSI 2.0 became available again, having a new version 2.0.2600.1 for Windows 9X. The Unicode version will not be affected by this transformation. There is no official information regarding the reasons behind this, but rumors has it that problems were detected with Windows ME.
MSI 2.0 introduces lots of new properties. Many of them deal with all the installation assemblies and 64 bit applications, such as MsiNetAssemblySupport and System64Folder properties. To support these new technologies you might have to use InstallShield Developer 7. But there are numerous other new properties which come in handy for traditional applications, too. These can be used to spot the exact type or flavor of Windows your setup is running on, and never have to get this information from registry entries. The following table summarizes some these new properties, together together with the value on the VersionNT property.
Windows NT 4.0 Workstation
Windows NT 4.0 Domain Controller
Information around the Windows 2003 server versions is susceptible to change, because they're still in beta.
MsiNTSuiteBackOffice will likely be set to just one if Microsoft BackOffice components are installed.
MsiNTSuiteDataCenter is going to be set to a single if Windows 2000 Datacenter Server is installed.
MsiNTSuiteSmallBusiness are going to be set to a single if Microsoft Small Business Server is installed.
MsiNTSuiteSmallBusinessRestricted are going to be set one if Microsoft Small Business Server is installed with restricted client license.
Although there won't be official release notes that list issues fixed in MSI 2.0, testing implies that several bugs are already fixed, much like the following:
Combo box scroll bar: The drop down list is now offering a scroll bar if there are other items than can look at one time.
Version comparison when applying a patch: This is now being employed as documented inside the latest version of MSI help, which conflicts using the settings in lots of authoring tools. This will likely behave badly for existing patches - see below.
Other errors are not fixed, such as the MinVersion field from the AppSearch table not being employed as documented the file version have to be greater than the worth you enter within the MinVersion field, not greater or equal because the MSI 2.0 help file says.
MSI 2.0 removes some from the weird limitations and rules you needed to follow when making a new version within your product:
You may add components to existing features. While this is very much a most rudimentry thing, it had been causing a myriad of strange behavior in the past versions of MSI.
You may add new sub features and produce their selection state dependent around the selection in the parent feature, while not having to use ADDLOCAL. You do this by setting the Required property in the feature to yes this is actually the equivalent on the msidbFeatureAttributesUIDisallowAbsent flag in MSI help and selecting Favor Parent through the Remote Installation settings.
For patches the effects with the Version Relationship setting have changed - actually it now works as intended. If you might have created a patch that targets multiple older versions, and still have accepted InstallShields default of New version previous version it is likely to fail! Users have reported error 2768: Transform in patch package is invalid after they tried to apply a real patch. It is highly recommended make use of New version previous version instead. The wording within the patch wizard is misleading, actually the meaning is Existing version base version, where base version will be the version that this patch targets. Suppose you could have a patch that ought to update version 1.0.1 within your product to version 1.0.2, then this base version will be 1.0.1. This patch should basically applied to a method where version 1.0.1 is installed, but not on higher versions. This is all really perplexing, because it had been documented incorrectly in earlier versions with the Windows Installer SDK, and in addition never worked as docum
Several other bugs inside patching process also have already been fixed.
Get you security identifier: The UserSID property which will not be valid on Windows 9x systems can also be retrieved in deferred execution custom actions.
Setup can detect unique being stripped away from control panel or by way of a major upgrade: When a major upgrade removes a preexisting product it sets the UPGRADINGPRODUCTCODE property.
Note: The initial discharge of MSI 2.0 was version 2.0.2600.0 for both Unicode and ANSI versions. However an issue was detected while using ANSI version, so it is replaced with version 2.0.2600.1. The Unicode version remains to be at version 2.0.2600.0.
Version 2.0 of can be utilized to update the Windows Installer runtime files on Windows 2000 and Windows Me. Windows XP already comes together with the latest files. Note that Service Pack 6 becomes necessary on Windows NT 4, while Service Pack 3 was sufficient for previous versions of Windows Installer.
included, can't be installed
InstallShield Developer 7.00 can update the Windows Installer runtime files on all os's including Windows 2000, however right now some modifications are needed, as described below. InstallShield Developer 7.01 fully supports for MSI 2.0, and so the below instractions usually do not apply.
Before you start while using modifications create backups coming from all affected files.
After you might have downloaded the apply for Windows NT/2000 and Windows 95/95/Me rename these phones and respectively. Copy these phones the redistributables folder that may be normally located at ProgramFilesFolderInstallShieldDeveloperRedistLanguage Independenti386.
HKEYLOCALMACHINESoftwareInstallShieldDevloper7.0
and customize the string entry named Msi Version to 2.0.2600.1.
Another required update for the template is to affect the service pack number for Windows NT 4 to make certain SP 6 or over is installed. In section WinNT4 change the importance of ServicePack looking at the default of 768 for SP3 to:
Remark: 768 0x300, 1536 0x600
You also need to adjust larger than fifteen message which is displayed if it requirement just isn't met. In directory ProgramFilesFolderInstallShieldDeveloperSupport youll find INI files with error messages for each and every language, for English messages. Open the file that has a text editor and change string entry 1150 to suggest that service pack 6 becomes necessary on Windows NT 4.
This step is optional. With MSI 2.0 you'll be able to postpone a reboot that are usually necessary after installing the runtime files until after your setup has finished. The internal facts are described below. InstallShield Developer 7 has a option in release wizard to delay the MSI engine reboot. However in version 7.00 this option will not be being written for the file. To suppress the reboot you are able to manually add this entry inside the Startup area of :
If you are applying this for the template your entire releases will suppress the reboot. Note that Microsoft suggests after a reboot following installation if that it was suppressed during installation from the MSI engine. ISD 7.00 doesnt manage this so that you have to feature a ScheduleReboot action yourself.
InstallShield - Windows Installer Edition 2.03 IPWI can be accustomed to update the Windows Installer runtime files on Windows 2000, but requires which the launcher be replaced using a special version. Note that suppressing the reboot after installing the MSI 2.0 runtime files is just not supported by this
After you've got downloaded the apply for Windows NT/2000 and Windows 95/95/Me rename the crooks to and respectively. Copy those to the redistributables folder that's normally located at ProgramFilesFolderInstallShieldProfessional - Windows Installer EditionRedistLanguage Independenti386.
Download the special from InstallShield knowledge base article Q105501. Copy it on the redistributables folder that may be normally located at ProgramFilesFolderInstallShieldProfessional - Windows Installer EditionRedistLanguage Independenti386.
Note that the newest should not be familiar with distribute MSI 1.2, and is not used with previous versions of InstallShield for Windows Installer.
HKEYLOCALMACHINESoftwareInstallShieldISWI2.0
You should adjust the mistake message that's displayed if something requirement just isn't met when setup starts. Open file ProgramFilesFolderInstallShieldProfessional - Windows Installer that has a text editor. Youll see sections with error messages for each and every language, 0x409 for English messages. Change string entry 1150 to point out that service pack 6 is necessary on Windows NT 4.
InstallShield Express 3.51 and 3.52 for your German Edition can update the Windows Installer runtime files on all os including Windows 2000, however at this moment some modifications are important, as described below. The next maintenance pack is anticipated to include support for MSI 2.0 without modifications.
After you've downloaded the register for Windows NT/2000 and Windows 95/95/Me rename the crooks to and respectively. Copy these phones the redistributables folder that may be normally located at ProgramFilesFolderInstallShieldInstallShield ExpressRedistLanguage Independenti386.
HKEYLOCALMACHINESoftwareInstallShieldExpress3.5
You must also adjust whole body message that may be displayed if it requirement will not be met. In directory ProgramFilesFolderInstallShieldInstallShield ExpressSupport youll find INI files with error messages for each and every language, for English messages. Open the file using a text editor and change string entry 1150 to suggest that service pack 6 becomes necessary on Windows NT 4.
This step is optional. With MSI 2.0 it is possible to postpone a reboot that may be needed after installing the runtime files until after your setup has finished. The internal information and facts are described below. InstallShield Express 3.51 posseses an option inside the release properties called Suppress MSI Engine Reboot you set to Yes. Note that Microsoft suggests using a reboot following installation if it absolutely was suppressed during installation in the MSI engine. ISX 3.51 doesnt handle this and that means you should add Schedule Reboot at End on the Custom Action Gallery.
InstallShield Express will not officially support updating the Windows Installer engine on Windows 2000. However Express 3.0 is internally somewhat comparable to InstallShield - Windows Installer Editon 2.0, and users have reported that this method described above for InstallShield - Windows Installer Edition 2.0 also is employed by InstallShield Express 3.0, such as special from your knowledge base article.
If you're using a non Windows Installer based product like InstallShield Professional Standard Edition but need to put in or update the MSI engine because you intend to run a Windows Installer based setup as child install, it is possible to use these hints.
To detect the version of Windows Installer currently present within the machine you may check the version information of within the system directory WINSYSDIR. To update Windows Installer operated with Windows NT/2000 or on Windows 95/98/ME.
In the past in several cases it absolutely was required to reboot laptop computer after installing or updating the Windows Installer runtime files, prior to the actual setup might be launched. The reason is that the main system has running in memory therefore the Windows Installer files are certainly not replaced until as soon as the reboot. This usually may be the case on systems that has a shell version that features the Windows desktop update, like Windows 98 and 2000, and Systems with IE4.01 SP1. For more specifics of this see Microsoft Knowledge Base article Q262974.
With Windows Installer 2.0 you may avoid this additional reboot. It has a command line replacement for suppress the reboot, and you may load and use the newest version of in the directory it may be installed to. To make this work this system launching should be aware of this and tell the primary setup to reboot at the end when a required Instmsi reboot is suppressed.
Both will suppress the reboot prompt, your second will perform an absolutely silent installing of Windows Installer 2.0.
will return ERRORSUCCESS 0 if no reboot is necessary, or ERRORSUCCESSREBOOTREQUIRED 3010 in case a reboot is necessary but was suppressed. The bootstrapper must catch these return values and act accordingly, pass REBOOTForce on the msi package if ERRORSUCCESSREBOOTREQUIRED was returned. This will cause the setup to request a reboot after installation.
Get the location in the newly installed Windows Installer runtime files. This directory is stored in a very string value called InstallerLocation in registry key HKEYLOCALMACHINESoftwareMicrosoftWindowsCurrentVersionInstaller.
Change the latest working directory towards the location obtained in step three and launch from that point. This way your setup will use the newest runtime version even with out a reboot. If the parent install calls the MsiInstallProduct API as opposed to running, it has to load on the directory obtained in step # 3.
Stefan Krueger is doing its job freelance setup consultant, offering support, custom programming and workshops independently from InstallShield Software Corporation. Besides his contract work, he answers questions in a variety of newsgroups and maintains your website, a spot where setup developers share resources and knowledge among peers.
If you've got any comments with this article, or need to suggest a topic that Stefan should discuss in the future article, please write to. To read Stefans articles from previous issues in the InstallShield Newsletter, please go to
Copyright by InstallSite Stefan Krueger. All rights reserved. Legal information.
Attualmente hai javascript disabilitato. Diverse funzioni potrebbero non funzionare. Si prega di riattivare javascript per accedere alle funzionalit complete.
150Mbps 2.4GHz Wireless-N - - USB2.0 Adapter, MIMO, 1T2R Realtek
300Mbps Wireless PCI Adapter Windows utility 25, 800KB
300Mbps 2.4GHz Wireless-N - - 32-bit PCI Adapter, MIMO, 2T3R Ralink
300Mbps Wireless PCI Adapter Windows utility 10, 570KB
150Mbps 2.4GHz Wireless-N - - 32-bit PCI Adapter, MIMO, 1T2R Ralink
Parallels Desktop 5.0 for Mac Run every one of the applications you will need without switching between Windows and Mac OS X! Better integration of Mac and Windows. Supports Windows 7 Aero, with graphics peformance nearly 7 times more than before. Supports Apple trackpad gestures, new Crystal mode, speech recognition, good notebook battery, and much more.
Parallels could be the clear winner running each number of Desktop 5 runs 30% faster with Windows XP, and 43% faster with Windows 7, than VMware Fusion 3.0.1.
Mac OS X 10.2 Jaguar Cross-Platform Report