You can run the following command to see what Apache module is loaded
apachectl -t -D DUMP_MODULES
or,
httpd -t -D DUMP_MODULES
Read MoreYou can run the following command to see what Apache module is loaded
apachectl -t -D DUMP_MODULES
or,
httpd -t -D DUMP_MODULES
Read MoreI am pleased to extend to you, on behalf of myself and the whole DriverIdentifier Team, wishes for a very Happy Thanksgiving and an enjoyable holiday season.
Read MoreTo install all the drivers are ready, we can begin to install the driver. Driver installation methods there are many, following slowly from easy to difficult to see.
1. The easiest one – From Installation Disk –Â Install from setup.exe
Now hardware vendors have increasingly focused on the humanity of its products, including the installation of the driver simplification, where so many drivers come with a “Setup.exe” to executable file, simply double-click it, then all the way “Next (Next)” to complete the driver installation. Some hardware vendors provide drivers joined the Autorun CD files from the start, as long as the CD into the computer’s optical drive, the CD will start automatically.
Then click the appropriate starting interface name of the driver can automatically start the installation process, this very user-friendly design makes installing the driver is pretty easy.
2. Manual Install
Installing drivers from CD is a traditional and most used approach to install required drivers as you can get thousands of drivers in a single CD and you don’t even need an Internet connection for installing drivers from a CD.
Right Click on “My Computer” from desktop and go to “Properties” from the menu.
Click on Hardware and then on Device Manager
You will see a yellow icon alongside un-installed drivers.
Right Click on that Yellow icon and select “Update Drivers”
Now, a new box will appear with couple of options, check the Last option and click on NEXT.
From the next page, click on NEXT again.
Now, Select the location you keep the drivers ( where the .inf file located)
After Installation, Click on Finish and Restart your computer.
Thats it!
Problem:
I am trying to access few files from C:\Windows\System32\Winevt on Windows 7 – 64 bit machine through .net application.
When I build my application in 32 bit , I am not able to access this Winevt directory. It complians about directory not found.
But If I build my application in 64 bit mode, I am able to access this directory without any problem.
Do I have to do anything special to access this directory using 32 bit application on 64 bit machine?
Reason:
a computer that is running a 64-bit version of Windows Server 2003 or of Windows XP, a 32-bit application cannot access the following folder: %WinDir%\System32
This behavior occurs because Windows on Windows 64-bit (WOW64) provides file system redirection.
In a 64-bit version of Windows Server 2003 or of Windows XP, the %WinDir%\System32 folder is reserved for 64-bit applications. When a 32-bit application tries to access the System32 folder, access is redirected to the following folder:
%WinDir%\SysWOW64
By default, file system redirection is enabled.
Solution:
As a walk-around solution, 32-bit applications can access the native system directory by substituting %windir%\Sysnative for %windir%\System32. WOW64 recognizes Sysnative as a special alias used to indicate that the file system should not redirect the access.
So, if we want to access C:\Windows\System32\Winevt folder from 32-bit application, we can use C:\Windows\Sysnative\Winevt instead.
We created some basic video tutorial to help you using Driver Identifier easier.
You can see them here at.
http://www.driveridentifier.com/video.php
We’re pleased to announce the new version of DriverIdentifier is available to download. We’ve been making great headway with development and thanks to everyone who’s reported bugs or suggested features! 🙂
Change log:
Improve the driver scanning process.
Lots of UI tweaks and bug fixes.
By default cron jobs sends a email to the user account executing the cronjob. If this is not needed put the following command At the end of the cron job line .
>/dev/null 2>&1
For example:
* 1 * * * php /www/daily.php >dev/null 2>&1
Hi Folks,
As part of improving our commitment, we have just moved our server to a new data center with much more powerful bandwidth , more high end servers.
I hope you enjoy this new enhancements.
Read MoreWe updated our database structure today , this improved the speed of finding the drivers for your machine.
Please let us know your feedback.
Read MoreToday , we just added about 1.000+ new drivers. This is the result of long hour working to release these new drivers.
We hope this will help you save more time.
The DriverIdentifier.com Team.
Read More