Quite often you can resolve web connection issues by flushing your possibly corrupted or out of date system DNS cache. To flush the DNS cache whilst using Microsoft Vista, Windows 7 or Windows 8 is relatively trivial, making use of the standard ipconfig executable.
First, we need to open a command prompt running under Administrator rights:
- Click the Microsoft Start Button in the bottom left corner of the screen
- Click All Programs
- Click Accessories
- Right-click on Command Prompt
- Select Run As Administrator
In the command window type the following and then hit enter:
If everything runs correctly, you should see the following confirmation:
Windows IP Configuration Successfully flushed the DNS Resolver Cache
If you already have a web development environment set up on your machine and don’t necessarily want to run the whole Zend Server package and instead just want to create Zend projects using the Zend Framework, then this simple how to install Zend Framework tutorial should be perfect for you.
Step 1) Grab Zend Framework
Download the latest version of the framework from http://framework.zend.com/download/latest and unzip it to where you want it installed/located on your machine.
Step 2) Set up System PATH Variable
Add the newly extracted Zend Framework package to your system PATH variable: In VISTA right click on the Computer (My Computer) icon and click on the Advanced System Settings link under the tasks menu on the left. At the bottom of the resulting System Properties dialog will be a button that reads Environment Variables. Click this.
Browse through the list of Variables under the System variables section of the Environment Variables dialog. If you already have a PATH variable, click Edit. If you don’t click on New. Variable name should be set to PATH. The value should be set to the folder in which you extracted the framework: e.g. C:ZendFramework-1.11.4bin
Note that while you are here, you may as well check if your PHP bin directory (basically the directory containing php.exe) is listed under the PATH variable. If not, add it. Mulitple locations can be defined under the PATH variable, using semi-colon ‘;’ to delimit them: e.g. C:ZendFramework-1.11.4bin;C:xamppphp
To test that this has been done correctly, open a command prompt (Windows button->Run…->cmd) and type in zf. If it complains about zf not being an executable, then your path setting is wrong. If it works, you’ll get some help information from the zf command.
Step 3) Generate Zend project
Now to generate your Zend project. Still in the command prompt, browse to where you want to create your project: e.g. cd c:vhostszend-projects. Now, enter:
zf create project MyProjectName
where MyProjectName is the name of your Zend project. This should generate a folder structure under c:vhostszend-projectsMyProjectName that will contain all the necessary Zend folder/file structures necessary for your work. For example, you should see folders under the root like application, library and public.
Note that sometimes this process doesn’t properly generate the necessary library contents. To get around this, go to the folder in which you originally extracted the Zend Framework to, locate the library folder in its root and copy its contents to the library folder under your project’s root.
Step 4) Set up Virtual Host
Locate your Apache2 httpd-vhosts.conf file. If it isn’t using a separate file to maintain its list of virtual hosts, then locate its httpd.conf file. In it, you need to add the virtual host information for your new project. Locate the section dealing with virtual hosts and add the following:
<VirtualHost *:80> DocumentRoot c:/vhosts/zend-projects/MyProjectName/public ServerName MyProjectName <Directory "c:/vhosts/zend-projects/MyProjectName/public/"> DirectoryIndex index.php AllowOverride All Order allow,deny Allow from all </Directory> </VirtualHost>
Save your .conf file and restart Apache2.
Step 5) Edit Your hosts File
Finally, we just need to edit our Windows host file so that we can work on our project. Locate and open in notepad (PSPad is my favourite) C:windowssystem32driversetchosts. Add the following line and save:
Step 6) Test Installation
And we’re done. If you now hit http://MyProjectName/ from a browser you should be presented with a Zend Welcome splash page. (If you are presented with a failed to open stream error, remember the library contents note I made in step 3.)
Nifty – or should that rather be, Good Luck!? :)
As a part-time designer, I love installing and using new fonts all the time. However, with the plethora of fonts available online, this can quickly become quite out of hand, and before you know it, you’re sitting with a computer with well over 5000 fonts installed on it! Needless to say, this has quite a negative impact on your machine’s performance, particularly when it comes to booting up graphics applications like Adobe PhotoShop and GIMP, all of which need to load up the entire list of fonts before starting up.
Now restoring your Windows XP or Vista installation to the original set of installed fonts turns out not to be a particularly easy manual task, based on the way in which font handling and manipulation is executed on the Windows Explorer platform.
So enter FontFrenzy, an aptly named application from a not so aptly named software development group, namely Sound Doctrine Ministries (under the leadership of a great big bearded man called Timothy Williams).
FontFrenzy essentially allows you to strip away all your excess fonts and restores your system to Windows essential fonts only, all with the click of a friendly big button labelled “Defrenzy”.
What it does is simply save a snapshot of your current font set up and then move all extraneous fonts into a separate system folder, which you can then use at a later stage to restore fonts from. It’s simple interface allows you to add and remove fonts based on your saved snapshots, view font lists in any point-size using a customizable test phrases, view font samples in both upper- and lowercase characters and numerals, and just manage your system’s fonts in general.
Ture, it doesn’t have the most modern of interfaces, or perhaps the most polished of looks, but FontFrenzy is free to download and use, does the job extraordinarily well and most importantly of all, has given me back PhotoShop and GIMP by quickly and efficiently stripping out all those non-essential fonts I was bloating my system with, all with the click of a single button!
And I liked that! :)
Related Link: http://sdsoftware.org/default.asp?id=5929
So we all know about the cool little Quick Launch panel sitting on the left hand side of the Taskbar (just next to the Windows Start button) at the bottom of the screen, which usually holds a variety of shortcuts to ‘often used applications’ (like Internet Explorer for example) and applications for which you simply weren’t bothered to uncheck the ‘Add Quick Launch’ option when you installed them.
But did you know that you can quick launch your Quick Launch items?
Well it’s quite simple really. Look at the sequence of the items on your Quick Launch bar. See the ‘Show Desktop’ shortcut sitting at position 1? Well hold down the Windows key and press 1.
Back again? This obviously applies to all options sitting in your Quick Launch bar, so using the example image below, Windows key + 3 would result in Windows Media Player launching.
Right, you’ve got a shiny new copy of Adobe Photoshop CS3 in your hands and a desktop loaded with Microsoft Vista in front of you. However, each and every time you attempt to install CS3 the installer just bombs out with nary a single error message.
Not cool when you consider how much the application actually cost in the first place!
Anyway, run the installer from the command line and see if it spits out an error. If it does, and the error reads “End Adobe Setup. Exit code: 4” then you are in luck.
The problem is caused due to the MSI installer code running custom Jscript and to fix it one simply needs to re-register the jscript DLL file.
So without any further ado:
Open an administrive cmd prompt
Note: you might have to run the cmd prompt as Administrator in order to gain the necessary rights in order to re-register the offending DLL.