Forums
This topic is locked
Installing PWS on XP home
Posted 10 Jan 2002 11:38:19
1
has voted
10 Jan 2002 11:38:19 gordon knapp posted:
Has anyone out there found a way to install PWS on XP Home edition yet? And before anyone starts posting quotations from the Microsoft web site, I would rather eat razor blades than upgrade to XP pro. <img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>
Thanks in advance
G
Replies
Replied 10 Jan 2002 14:58:46
10 Jan 2002 14:58:46 TC McFall replied:
wt~
which PWS? MSPWS4, I assume? This would be the PWS that ships with 98SE and is available for download from the NT option pack. Or perhaps MSPWS 1.0 (which I liked better, but needed an ASP.exe add-on)? Or perhaps you are stepping away from Micro-daddy and trying an O'reilly or Netscape, or ...well, anyway...you get the picture.
The official stance of MS's is because the PWS technology is being phased out of their "vision". They will no longer distribute any PWS versions and the support for PWS technology is being completely throttled. WinME and WinXP have been designed not to allow a functioning PWS. In MS's opinion, if you want to serve, get IIS. Unfortunately, if you want XP, this means Pro. I am not entirely sure why you believe that Home is somehow superior to Pro but I assure you that based purely on the merits of the OS differences, you are making a mistake. I really do not want to start an OS debate, and I don't know what your other criteria are, I am just stating (as an MS insider) that XP Pro is superior (especially for developers) than XP Home.
Having said that, I do know of ways that you can get a PWS to function on WinME (if, for some ungodly reason you are using ME) but I have not attempted similar steps on XP. However, in the hopes that this might prove useful to you, I will post this information so that you can glean from it what you can. To be honest, if you are successful, I would be interested in knowing. It would please some of my clientele to know that they have the (unsupported, thank God) option! Let me compile the info for you and remove all the MS-internal shtuff....I will post later today (hopefully within the hour).
<img src="www.chromehenge.com/images/tao_smiley.gif" border=0>
~kr0m3
There are no "webmasters"...only "webstudents". Now, snatch the floppy from my hand, grasshopper.
which PWS? MSPWS4, I assume? This would be the PWS that ships with 98SE and is available for download from the NT option pack. Or perhaps MSPWS 1.0 (which I liked better, but needed an ASP.exe add-on)? Or perhaps you are stepping away from Micro-daddy and trying an O'reilly or Netscape, or ...well, anyway...you get the picture.
The official stance of MS's is because the PWS technology is being phased out of their "vision". They will no longer distribute any PWS versions and the support for PWS technology is being completely throttled. WinME and WinXP have been designed not to allow a functioning PWS. In MS's opinion, if you want to serve, get IIS. Unfortunately, if you want XP, this means Pro. I am not entirely sure why you believe that Home is somehow superior to Pro but I assure you that based purely on the merits of the OS differences, you are making a mistake. I really do not want to start an OS debate, and I don't know what your other criteria are, I am just stating (as an MS insider) that XP Pro is superior (especially for developers) than XP Home.
Having said that, I do know of ways that you can get a PWS to function on WinME (if, for some ungodly reason you are using ME) but I have not attempted similar steps on XP. However, in the hopes that this might prove useful to you, I will post this information so that you can glean from it what you can. To be honest, if you are successful, I would be interested in knowing. It would please some of my clientele to know that they have the (unsupported, thank God) option! Let me compile the info for you and remove all the MS-internal shtuff....I will post later today (hopefully within the hour).
<img src="www.chromehenge.com/images/tao_smiley.gif" border=0>
~kr0m3
There are no "webmasters"...only "webstudents". Now, snatch the floppy from my hand, grasshopper.
Replied 10 Jan 2002 15:27:55
10 Jan 2002 15:27:55 TC McFall replied:
okeee-dokeee~
here's what I have for you. Sorry that it is specific to WinME, but I simply haven't attempted this with XP yet. I hope it helps!
*************************************************************
-----Original Message-----
From:
Sent: Wednesday, September 19, 2001 6:07 AM
To:
Subject: Personal Web Server vs. WinME
Importance: High
If you...XXX ...the following unsupported information...
***- understand that the following steps are in NO WAY supported by Microsoft or its employees. The following information is being forwarded to you for informational purposes only.
NO ATTEMPT TO ASSIST OR TROUBLESHOOT THE INFORMATION BELOW IS TO BE INITIATED UNDER ANY CIRCUMSTANCES.
Q268549 HOWTO: Install Visual InterDev on Windows Me-based Computer
Details how to install the PWS on winME in order to install VI without errors.
Or...XXX... (keeping in mind that several of the links below are no longer valid...)
While checking out the ...XXX...
Although it is unsupported, if you have a customer that really needs some options to work with, you might point them (with appropriate warnings on support) to this:
which states (in part):
> Windows Millennium Edition (Me) does not include Microsoft Personal Web
> Server (PWS) 4.0, and PWS 4.0 is not supported in Windows Me. >
> <support.microsoft.com/support/kb/articles/Q266/4/56.ASP> >
> However, you may want to try this, courtesy of XXX, Microsoft >
> MVP?DTS: >
...XXX...
and Bill's input (from the link above) lays out some interesting steps to get it to work (pasted below)...!
1) Download the newest version of PWS from download.microsoft.com/msdownload/ntoptionpack/en/x86/win.95/download.exe. Yes, this is the NT 4.0 Option Pack, but it includes the version of PWS for Win95 which can be used on WinMe with the following tweaks. After downloading Download.exe, run it and select the option to download PWS for Win95.
2) See support.microsoft.com/support/kb/articles/q246/0/81.asp. Download the patch and implement per the instruction in this KB article.
3) Important! Do a Custom install of PWS, installing only the Transaction Server component. To do this, uncheck all the options, then check Transaction Server - it will add checks to the other components needed for it, but not the Personal Web Server option.
4) After Setup completes and a reboot, re-run Setup and add PWS. Reboot after Setup completes.
5) PWS should now work. Easiest way to implement using it for local copies of your web pages is to copy the contents of the entire local folder structure of your web site to C:\Inetpub\wwwroot (or the folder you selected during PWS setup). To clarify, if the local copy of your web site is in D:\MyWebSite, with the default start page and all sub-folders located there, you copy all the files and sub-folders, but not the D:\MyWebSite folder itself.
6) If you are using ASP and your start page is default.asp, allow your file to overwrite the default.asp file already in C:\Inetpub\wwwroot. If you are using index.htm or some other start page, you need to rename the PWS default.asp file so it is not the default page for the local site.
7) In your web browser address bar, type... localhost ...to bring up your start page. Other installation issues I encountered:
1) PWS Setup replaced regsvr32.exe with an old version. Extract regsvr32.exe from the WinMe Setup files to C:\Windows\System to replace the old version that PWS installed there.
2) My linked .js files would not work at first because they were in a folder called "Scripts", but PWS comes pre-configured with a Virtual Directory by that same name. So, references to that folder were actually going to the Virtual Folder, and the requested .js file did not exist there.
Solution: Open the Advanced Options page of PWS manager and remove or rename the "Scripts" Virtual Directory.
...XXX...Revised 29/Oct/2000 20:54
***********************************************
that's it....good luck!
<img src="www.chromehenge.com/images/dead_smiley.gif" border=0>
~kr0m3
There are no "webmasters"...only "webstudents". Now, snatch the floppy from my hand, grasshopper.
here's what I have for you. Sorry that it is specific to WinME, but I simply haven't attempted this with XP yet. I hope it helps!
*************************************************************
-----Original Message-----
From:
Sent: Wednesday, September 19, 2001 6:07 AM
To:
Subject: Personal Web Server vs. WinME
Importance: High
If you...XXX ...the following unsupported information...
***- understand that the following steps are in NO WAY supported by Microsoft or its employees. The following information is being forwarded to you for informational purposes only.
NO ATTEMPT TO ASSIST OR TROUBLESHOOT THE INFORMATION BELOW IS TO BE INITIATED UNDER ANY CIRCUMSTANCES.
Q268549 HOWTO: Install Visual InterDev on Windows Me-based Computer
Details how to install the PWS on winME in order to install VI without errors.
Or...XXX... (keeping in mind that several of the links below are no longer valid...)
While checking out the ...XXX...
Although it is unsupported, if you have a customer that really needs some options to work with, you might point them (with appropriate warnings on support) to this:
which states (in part):
> Windows Millennium Edition (Me) does not include Microsoft Personal Web
> Server (PWS) 4.0, and PWS 4.0 is not supported in Windows Me. >
> <support.microsoft.com/support/kb/articles/Q266/4/56.ASP> >
> However, you may want to try this, courtesy of XXX, Microsoft >
> MVP?DTS: >
...XXX...
and Bill's input (from the link above) lays out some interesting steps to get it to work (pasted below)...!
1) Download the newest version of PWS from download.microsoft.com/msdownload/ntoptionpack/en/x86/win.95/download.exe. Yes, this is the NT 4.0 Option Pack, but it includes the version of PWS for Win95 which can be used on WinMe with the following tweaks. After downloading Download.exe, run it and select the option to download PWS for Win95.
2) See support.microsoft.com/support/kb/articles/q246/0/81.asp. Download the patch and implement per the instruction in this KB article.
3) Important! Do a Custom install of PWS, installing only the Transaction Server component. To do this, uncheck all the options, then check Transaction Server - it will add checks to the other components needed for it, but not the Personal Web Server option.
4) After Setup completes and a reboot, re-run Setup and add PWS. Reboot after Setup completes.
5) PWS should now work. Easiest way to implement using it for local copies of your web pages is to copy the contents of the entire local folder structure of your web site to C:\Inetpub\wwwroot (or the folder you selected during PWS setup). To clarify, if the local copy of your web site is in D:\MyWebSite, with the default start page and all sub-folders located there, you copy all the files and sub-folders, but not the D:\MyWebSite folder itself.
6) If you are using ASP and your start page is default.asp, allow your file to overwrite the default.asp file already in C:\Inetpub\wwwroot. If you are using index.htm or some other start page, you need to rename the PWS default.asp file so it is not the default page for the local site.
7) In your web browser address bar, type... localhost ...to bring up your start page. Other installation issues I encountered:
1) PWS Setup replaced regsvr32.exe with an old version. Extract regsvr32.exe from the WinMe Setup files to C:\Windows\System to replace the old version that PWS installed there.
2) My linked .js files would not work at first because they were in a folder called "Scripts", but PWS comes pre-configured with a Virtual Directory by that same name. So, references to that folder were actually going to the Virtual Folder, and the requested .js file did not exist there.
Solution: Open the Advanced Options page of PWS manager and remove or rename the "Scripts" Virtual Directory.
...XXX...Revised 29/Oct/2000 20:54
***********************************************
that's it....good luck!
<img src="www.chromehenge.com/images/dead_smiley.gif" border=0>
~kr0m3
There are no "webmasters"...only "webstudents". Now, snatch the floppy from my hand, grasshopper.
Replied 10 Jan 2002 18:15:08
10 Jan 2002 18:15:08 gordon knapp replied:
Thanks Guys,
The reason I would rather eat razor blades than upgrade to XP pro is financial<img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>
I run 98SE and ME on two desktop machines. I use PWS (personal web server) on both of these machines when developing with UltraDev etc. I also run IIS on another NT.
Problem is that I have a laptop that came with XP home. I want to use the laptop for demonstrating ASP sites I am working on to customers. However, for that I need to install a server on it (pws) and Bill Bloody Gates seems to want me to make him richer by upgrading to XP pro for the privilage.
So I was wondering if there was a work around (as with ME) Short of which I will just flatten the laptop and stick 98 on it.
Cheers
G
The reason I would rather eat razor blades than upgrade to XP pro is financial<img src=../images/dmxzone/forum/icon_smile.gif border=0 align=middle>
I run 98SE and ME on two desktop machines. I use PWS (personal web server) on both of these machines when developing with UltraDev etc. I also run IIS on another NT.
Problem is that I have a laptop that came with XP home. I want to use the laptop for demonstrating ASP sites I am working on to customers. However, for that I need to install a server on it (pws) and Bill Bloody Gates seems to want me to make him richer by upgrading to XP pro for the privilage.
So I was wondering if there was a work around (as with ME) Short of which I will just flatten the laptop and stick 98 on it.
Cheers
G
Replied 11 Jan 2002 09:42:56
11 Jan 2002 09:42:56 Viktor Farcic replied: