E.1.7- NotePad Adds a .txt Extension

NotePad Adds a .txt Extension

Notepad may add .txtto the end of each page so you get, for example, MyPage.asp.txt.Then VBScript does not execute since PWS or IIS is looking at an extension of .txt instead of .asp.

Solution 1

When naming your file select File Type *.* All Files. Name your file with its name andextension, for example MyPage.asp.Notepad will not add a .txtextension.

Solution 2

Rename your file using Windows Explorer after saving it. Ifyou are FTPing your files up to a server, do the rename before the FTPoperation.

Solution 3

When typing in the name of a file put double quotes aroundit. Then Notepad will save it exactly as typed.

Solution 4

Change the way Notepad saves names on files. There are twoways of doing this:

1.  OpenWindows Explorer and click on View | Options. Uncheck Hide FileExtensions for registered types.

2.  Onthe desktop open My Computer, and click on View | Folder Options.Choose the View taband uncheck Hide file extensions for known file types.

IE Erroneously Changes the URL type

In some set-ups of IE, when you type http://MyComputer/MySite/MyPage.asp IE automatically adds.com. So, it becomes http://www.MyComputer.com/MySite/Mypage.asp,which causes a "file not found" message.

Solution

Open IE and select View | Internet Options | Advanced| Browsing. Uncheck UseAutocomplete.

In Internet Explorer 5 you can find the same informationunder a different path: click Tools | Internet Options andselect the Advanced tab. You will need to uncheckUse inline AutoComplete for Web addresses.

Installation Error Message: Requires 32 bit TCP/IP Networking or MissingWinSock

When running the Personal Web Server setup.exe file on Win9x, you may get a message WinSock 2 is required to run this setup utility. Please clickOK. Alternatively, you may find that on first running Front Page afterinstalling PWS you get an error message along the lines ofFrontPage requires 32 bit TCP/IP networking… not installed. These are both caused by PWS not being able to see a Dynamic Host ConfigurationProtocol.

Solution 1

Both of these problems can be solved by Start | Settings | Control Panel | Network | Add | Protocol. Add the Microsoft TCP/IP protocol & bindto a dial-up networking adapter. Save and reboot. Adding the TCP stack willprovide not only TCP/IP but also the WinSock.

Solution 2

Sometimes the version of Winsock causes this problem. Youmust revert to WinSock version 1.1, then run the Windows Sockets 2 update.

1.   Restore Windows Sockets 1.1 with Start| Run C:\YourWindowsDirectory\ws2bakup\ws2bakup.bat.If you get a sharing violation message, strike a key to abort. Repeat this stepuntil the batch file has finished running.

2.   Restart the computer in MS-DOS mode.

3.   Enter c:\YourWindowsDirectory\ws2bakup\ws2bakup.batand ignore the any errors about updating the registry.

4.   Enter exitto leave DOS mode and restart Windows.

5.   Download the W95ws2Setup.exefile from the following Microsoft URL and save it in your Temp folder: http://www.microsoft.com/windows/downloads.

6.   Click Start | Run and execute c:\Temp\W95ws2Setup.exe.

7.   When the Windows Sockets 2 Setup program has finishedrunning, restart the computer. You will now have Windows Sockets 2 installed.

PWS Install Can't see IE 4.01

Install of PWS requires IE4.01 or higher.  In some cases,particularly with the FrontPage 98 PWS and Windows 95, there is an errormessage that setup cannot continue because setup requires IE4.01, even thoughIE4.01 is installed and working. 

Solution

There are multiple problems with installing the NT4 downloadversion over the FP98 version with Win 95. The first option would be to upgradethe OS to Win98 and use the PWS on the Win98 CD. In addition this problem isusually solved if you have run the IE4.01 Service Pack 1 or upgrade to IE5.

Synchronizing Default Pages

Every site must have a page set as the default page. FrontPage uses Default ( .htm, .htmlor .asp all work the same).Other web servers (perhaps the one on your host) use Index.xxx. When you create a site using FrontPage you mayget a default page that is not recognized by your host.

Temporary Solution

Change the name of your file before uploading to your ISP.When using PWS on your local machine, your home page is default.htm. Before FTPing the site to your ISP, changethe filename or make a copy of it with the correct default name for your hostsuch as Index.html.

Solution 1

Change the name of your PWS default file name to match yourhost's default file name:

1.   Start PWS (if it doesn't start automatically)

2.   Right mouse click on the PWS icon in the Windows tray

3.   Select Administer

4.   Select WWW Administration

5.   Click the Directories tab, thenscroll to the very bottom of the page

6.   Enable Default Document shouldbe checked on

7.   Change the Default Document tothe name specified by your host

8.   Close the Internet Services Administrator

With NT4 Service Pack 4, Option Pack 4, PWS, double clickon the PWS icon on the taskbar. In the left pane select Advanced, then pick upwith step 6 above.

If PWS is running when you make the change you may have tostop and restart PWS for the change to take effect. Assuming that PWS isrunning:

1.   Right mouse click on the PWS icon in the Windows tray

2.   Select Properties

3.   Click on the Startup tab

4.   Click on STOP, wait for themessage to change to "The server is stopped"

5.   Click on Start, wait for themessage to change to "The server is running"

6.   Close the Personal Web Server Propertiesdialog box

Solution 2

If replacing the name of the home page doesn't work, tryadding it. You can set

"Default Document" = Default.asp,Index.asp. Note that multiple names are separated by a comma.

Solution 3

You can create a file that is named according to your host'srequirements but that redirects visitors to your actual home page. This may beyour best bet if you don't have control of the server.

The following code is put in a small file named Default.htm:

<HTML><HEAD>

<TITLE>Redirect Default.htm toIndex.asp</TITLE>

<META HTTP-EQUIV="REFRESH"CONTENT="0; URL=index.asp">

<BODY></BODY></HTML>

In this case the file is named according to the hostrequirement Default.htm andredirects to your home, named Index.asp.Note that this will have to go in every directory where your host expects tosee Default.htm. There is aperformance hit for this solution as the server must open two files instead ofone.

Of the above solutions, I recommend modifying your PWS toaccept the default file accepted by your host. This only has to be done onceand you will not suffer a performance penalty.

MTS registry not installed

At the end of some installations there is a message that theMicrosoft Transaction Server was not installed. Although MTS is required withIIS it is not required for PWS. This message can be ignored and PWS will run ASP fine.

More Troubles and Troubleshooting

If you encounter other problems, there are newsgroups thatdiscuss PWS install issues. Several can be found at http://www.dejanews.com/, or by performing a search for"PWS".