Items filtered by date: December 2014

Internet Explorer opens with a blank page when you open in a new window or a new tab or one these similar issues below

• open in new tab/window not working
• Find on this page "empty"
• tabs on Favorites pane missing
• about screen and other dialogs "empty"
• IE8 closes immediately (not if caused by an add-on!)
• can't print (interface not registered)

Run the following  script from IEFAQ making sure you run either the x86 or x64 version as required.

Script from IEFAQ

Faulty tab issues can also be caused by third party addons. You should consider disabling/removing all addons to see if the issue is fixed. Lastly you should reset all internet explorers settings and restart internet explorer

You have one or more WAN Miniport that you cannot delete such as the ones below even if they are disabled. They will not reinstall either and usually have an exclamation mark on them

You might also experience error code 31.

• WAN Miniport (IP)
• WAN Miniport (IPv6)
• WAN Miniport (L2TP)
• WAN Miniport (Network Monitor)
• WAN Miniport (PPPOE)
• WAN Miniport (PPTP)

Use the following commands to be carried out as the user Administrator (Run as Administrator) from Command prompt (cmd):

The following example will delete the WAN Miniport with a hardware ID of ms_sstpminiport.

netcfg -e -u ms_sstpminiport

To delete other failed WAN Miniports you have to find the Hardware ID for the Device from the Device Manager

• Open the Device Manager
• Selecting the Details tab
• select Hardware IDs from the drop down menu
• replace the hardware ID in the example above and run for each failed WAN Miniport

When an Apple Mac twats your pendrive files so they are all hidden and archive bit set you cannot remove these via windows because it has messed up the file structure.

run the following command in a command prompt

attrib *.* -A -H -R -S /S /D

Microsoft .NET Framework Version 2.0 is required to continue even though windows 7 has this technology built in.

The .Net Framework 2.0. error is associated with hardware drivers not being compatible with windows 7, typically printer drivers after a windows 7 upgrade are still associated with the previous OS.............

Go to your printer or other hardware manufactures site to download and install windows 7 drivers for your hardware this should eliminate the 2.0 error. You might also need to uninstall the old driver first.
 

That error appears to be a Windows Update error, which makes sense since you encounter it when doing a check for upgrade - which uses Windows Update.
Can you successfully check for updates using Windows Update in Windows?
I found the following information on how to deal with this error in Windows update:

Error number: 0x80248014 (Originally was 0x8024001D) when applying Windows Updates
Suggestion 1: Rename temporary folder SoftwareDistribution

1. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.

net stop WuAuServ

2. Click Start, Run, type: %windir% and press Enter.
3. In the opened folder, rename the folder SoftwareDistribution to SDold.
4. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.

net start WuAuServ

Please go to the Windows Update site to test this issue. If that works then it was a corrupted Windows Update file and we needed to remove the folder in which it resides.

Installing Q2004R2 on your shiny new Vista box initially looks bad, a dialog says that C:\Program Files\Quicken\qwapp.dll and C:\Program Files\Quicken\qwinver.dll cannot be registered (or something similar).

Then when you try to start Quicken after install (or after upgrading to Vista) you get:

The application has failed to start because MFC70.dll was not found.
Re-installing the application may fix this problem.

:-(

Anyway, not being one the shirk a challenge and more importantly expecting to upgrade to Vista one day but wanting to carry on using Quicken I've spent some time this afternoon trying to get it going.

To sumarise to the minimun number of steps (and cut out the pain and experimentation I've been through) here we go:

1. Make sure you are an Administrator of the Vista PC. If you only have one account you probably are, if you need to check: Start | Control Panel | User Accounts | Add or remove User Accounts.

2. Goto www.dlldump.com and download the 3 dlls MFC70.dll, msvcr70.dll and msvcp70.dll. Ideally download them straight to where Quicken is installed (C:\Program Files\Quicken) but Vista would not let me do that, I had to download them to my user Documents folder first then copy them from there to the Quicken install dir.
http://www.dlldump.com/download-dll-files_new.php/dllfiles/M/MFC70.DLL/7.00.9466.0/download.html
http://www.dlldump.com/download-dll-files_new.php/dllfiles/M/msvcr70.dll/7.00.9466.08/download.html
http://www.dlldump.com/download-dll-files_new.php/dllfiles/M/msvcp70.dll/7.00.9466.08/download.html

3. Open a DOS box (Start | All Programs | Accessories | Command Prompt).

4. At the DOS prompt type (you'll need to change the dll location if Quicken is no installed in C:\Program Files\Quicken):
regsvr32 /s "C:\Program Files\Quicken\qwapp.dll"
regsvr32 /s "C:\Program Files\Quicken\qwinver.dll"

That's it - Quicken will now run and you can load your file (BACK IT UP SEVERAL TIMES AND PUT THE BACKUPS SOMEWHERE SAFE FIRST).

originally from here

when trying to login to prestashop you receive the following error message:

501 Method Not Implemented

GET to /admin not supported.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

A list of Apache Server Environmental Variables from zytrax
All the variables are described for easy reading.

This is a current list of Apache 2.2 Server Environmental Variables

This is an old list of Apache Server Environmental Variables

Usually I develope my projects locally on my pc. Needless to say that you sometimes have to send an email from your script to external mail to check if everything is fine. So you need to configure your system in a way that your local apache webserver is able to send mail to external addresses.
I always use XAMPP for Windows because it contains everything you need for developing PHP applications as well as all the stuff for sending mails: fake sendmail und Mercury Mail Transport System. I reference to XAMPP 1.6.5 (for Windows) and Mercury 4.5 here. Mercury is already pre-configured in XAMPP - all settings that I don't explicitly address stay as they are

I'm writing this because I'm not a mail professional and read a lot of tutorials and none of them really worked. So I extracted what I needed and put it all together. An important assumption for this tutorial is that you have your own SMTP server, for example the one that your webspace hoster provides.

So let's get started:

1. start Mercury (using the XAMPP Controlpanel) and then open the admin panel.
2. first of all we disable the HTTP server of Mercury so that it doesn't conflict with the apache:
   1. "Configuration" -> "Protocol modules"
   2. disable the check "MercuryB HTTP web server"
   3. I also disabled "Mercury IMAP4rev1 server" because I won't need that one
   4. leave the window opened, we'll need it immediatly
3. to be able to send external mail we have to disable "MercuryE SMTP end-to-end delivery client" in the same dialog and enable "MercuryC SMTP relaying client". Click "OK" and restart Mercury!
4. now let's configure Mercury in general:
   1. "Configuration" -> "Mercury core module", tab "General"
   2. we want to send from localhost, therefore we check if "localhost" is the value of "internet name for this system" and adjust that if not
   3. all other settings stay the same as they are already configured, but we'll have a look to the checkboxes beneath:
   4. disable all but "Send copies of all errors to postmaster"
   5. check under the tab "Local domains" if the entry "localhost (local host or server) localhost (internet name)" is there, if not, add it
   6. click "OK" and leave the dialog
5. next we focus on the MercuryS SMTP Server for outgoing emails:
   1. "Configuration" -> "MercuryS SMTP Server"
   2. choose the tab "General" and add a wonderful name for your SMTP server under "Announce myself as", simply fill in any name, I've chosen "CS SMTP".
   3. under "Listen on TCP/IP port" fill in "25", that's the SMTP port
   4. add "127.0.0.1" to "IP interface to use", that's the local IP of your pc. With the IP of the pc within the network (192.168.0.X) it doesn't work (at least for me)
   5. now we limit the access to the server so that only our local machine can access it:
      1. under "Connection Control" click on "Add restriction" and add the IP range from "127.0.0.1" till "127.0.0.1" (it's that simple, isn't it?)...
      2. and select "Allow connections"...
      3. and leave all checkboxes deselected
   6. with a click on "OK" we quit the dialog and we're looking forward to the next one
6. now let's configure the MercuryP POP3 Server:
   1. "Configuration"-> "MercuryP POP3 Server", select the tab "General"
   2. "Listen on TCP port" -> "110" and "IP interface to use" -> "127.0.0.1"
   3. choose the tab "Connection control" and proceed as already written under 5.5 (see above)
   4. that's it already, leave the dialog by clicking "OK"
7. now we have the important one "MercuryC SMTP Client"
   1. "Configuration" -> "MercuryC SMTP Client"
   2. to send mail to external addresses we need to have an external SMTP server. If you're renting webspace somewhere and have mail included then you normally have access to a SMTP server. My webspace is hosted at HostEurope and I'll use the SMTP of my domain. Without such an external server the whole thing won't work because domain names won't be resolved among other things. I've chosen this path because I didn't feel like configuring around the whole day.
   3. enter the address of your SMTP under "Smart host name", for example "mail.meinedomain.com"
   4. depending on the way you access the server fill the values under "Connection port/type":
      1. for a "normal" SMTP that would probably be port 25 and "Normal (no SSL encryption)"
      2. I access my SMTP via SSL, that would be port 465 and "SSL encryption using direct connection"
      3. if you have other parameters simply try around a little
   5. we finally fill in the "Login username" and the "Password" that normally is supplied by your webhost and we've nearly finished...
8. let's check the Mercury users that are normally pre-configured:
   1. "Configuration"-> "Manage local users"
   2. there should be at least the users "Admin" and "postmaster", both with administrative rights. If not you have to add them.
9. now we finished with Mercury, but we still need to configure PHP for sending mail with our scripts:
   1. we search and open the appropriate php.ini, using XAMPP you find it under "xampp/php/php.ini" in newer version and under "xampp/apache/bin/php.ini" in older versions
   2. we search for "[mail function]"...
   3. and we add/adjust the following:
      1. "SMTP = localhost"
      2. "smtp_port = 25"
      3. "sendmail_from = postmaster@localhost"
   4. save the php.ini and restart the Apache
10. now everything should work! But we'll test it first:
    1. within Mercury choose "File" -> "Send mail message" and send an email for testing purposes, I've chosen to send it to my googlemail account
    2. if the windows in Mercury are at sixes and sevens, choose "Window" -> "Tile" enjoy the view
    3. within the window "Mercury Core Prozess" we'll see our test mail at first:
       1. "13:38:41 JOB XXXXXX: from postmaster@localhost (local) To: XXX@googlemail.com (non-local) (JOB XXXXXX) -OK"
    4. the mail was received in Mercury and processed, after some seconds the window "Mercury SMTP client (relay version)" should show some actions:
       1. "05 Jan 2008 13:39, Servicing job XXXXXX ...OK"
       2. if you see this message, everything went fine and the mail was sent!
       3. if you don't get the message you have to find out why, possible reasons could be:
          1. wrong connection values for the SMTP server
          2. SMTP server doesn't allow relaying (from your host)
    5. now we'll test the whole thing from a PHP script and we'll write a wonderful one-liner into a PHP file:
       1. "mail('xxx@googlemail.com', 'Mercury test mail', 'If you can read this, everything was fine!');"
       2. call the PHP file within your browser, a command window should pop up shortly (or maybe not), it's from the fake sendmail of XAMPP, and focus back on Mercury:
          1. the produre is the same as above only that the SMTP server receives the mail from php before everything else happens
          2. you can watch this in the window "Mercury SMTP Server" and should see something like this: Mercury SMTP

I hope that worked for you, if not, feel free to leave a comment but as I already said, I'm not a professional but I'll help you as far as I can!

EDIT:
If you get the error message "SMTP server response: 553 We do not relay non-local mail, sorry." while sending from PHP go to Mercury under MercuryS -> Connection Control -> "Uncheck Do not Permit SMTP relaying to non-local mail" an check this option. Should fix the problem. Thanks to ron!

These are other links and tutorials that is used for research. These might help when setting up Mecury Mail

• How To: Setup Mercury Mail on an XAMPP Package - This video is in my video library
• Setting up Mercury SMTP for XAMPP
• Configure XAMPP Mercury Mail
• Configure Mercury mail transport system for external mail sending
• Configure Mercury mail transport system for external mail
• Using Mercury mail to send mails - forum thread
• Mercury mail - forum thread

There have been loads of times when updates are ready but i want the computer / laptop off and ready to move asap (to go home from work and take my laptop with me). was so annoying having to wait for windows to update when i didn’t want to.

I have found a way to shutdown windows 7 without being forced to install the updates…

Run regedit (search in start menu)

Under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
if the keys “WindowsUpdate” and “AU” aren’t there just add them (right click > New > Key)
right click > New > DWORD
name it “NoAUAsDefaultShutdownOption” double click it and enter value 1.

the “shutdown” button will never be changed by Windows Update from your default action to “shutdown and install updates”.
If updates are ready to be installed “shutdown and install updates” is instead displayed in the [>] menu to the side of the shutdown button

On my system it happend almost as soon as the registry value was added, but you may need to reboot before the change is applied.

Also important is “NoAutoRebootWithLoggedOnUsers”, also a DWORD in the same location with value 1. This stops Windows from rebooting automatically if a user is logged in or you leave it working overnight for example.