• 0

Personal Web Server & Windows XP problem


Question

I have a site and use asp for serving a database. I installed PWS from Microsoft windows98 cd rom and my asp pages working fine in the inetpub directory that pws creates.

The problem is in Windows Xp . I installed the pws tha comes with winXp but my asp pages are not working. Any idea...

Thnaks in advance..

pcdolfin administrator

Link to comment
https://www.neowin.net/forum/topic/2412-personal-web-server-windows-xp-problem/
Share on other sites

19 answers to this question

Recommended Posts

  • 0

Why you are using Personal Web Server on XP you should use IIS ( Internet Information Service )...

You have to install it from Add & Remove in Control Panel...

I also have used it... & also I have installed PHP support onto it...

Let me know if this things works for you...

:evil: :evil: :evil: :evil:

  • 0

pcdolfin, i'm experienced with ASP and M$ seem to change the syntax for some of their ASP tags between different versions of PWS and IIS. I use ASP on IIS so if you want to send me some excerpts of the code that the web server throws up as containing the error i'd be happy to give it a look over. My email is attached to my name :)

  • 0
Originally posted by Nick_Jones

pcdolfin, i'm experienced with ASP and M$ seem to change the syntax for some of their ASP tags between different versions of PWS and IIS.

IIS 5 and above uses ASP 3.0 which has extra stuff. Microsoft DO NOT change the syntax between PSW and IIS.

Dave

  • 0
Originally posted by Nick_Jones

Actually, they do change some things. The thing i was referring to was they way they handle the date function, which has changed numerous times between the different builds of XP which is why some of my pages didnt work.

so there :p

So are you saying it has changed between builds of XP or like your original comment between builds of PWS and IIS ?

Dave

  • 0
Originally posted by Dave B

So are you saying it has changed between builds of XP or like your original comment between builds of PWS and IIS ?

Dave

erm Dave, if its changed between builds of XP then one of them must be different to PWS

* Moderator Edit * No need for name calling.

pcdolphin: are the permission errors the only errors? if they are then you need to make sure each directory has script permissions enabled. This may also be called "execute" but that is dependent on your web server. In IIS, execute is not needed to run ASP, only CGI.

if you're getting errors other than permission errors, then send the ASP my way and i'll have a look at it. my email is attached to my name.

  • 0
Originally posted by Nick_Jones

erm Dave, if its changed between builds of XP then one of them must be different to PWS

You originally said ASP tags changed between IIS and PWS, then you said between XP versions.

All I said was NO tags changed between PWS and IIS.

Yes tags will change between XP versions as it goes through the different BETA stages.

Dave

  • 0
Originally posted by Dave B

You originally said ASP tags changed between IIS and PWS, then you said between XP versions.

All I said was NO tags changed between PWS and IIS.

Yes tags will change between XP versions as it goes through the different BETA stages.

Dave

wot don't you get?! if it changes between builds of IIS then ONE MUST BE DIFFERENT TO PWS. do you not understand the logics of physics or something?

  • 0
Originally posted by Dave B

Could you please tell me which function have changed then ?

Dave

the date function for a start, 2 versions produce two different outputs. I have been using XP for a year, i have gone through builds 2428,2446,2462 etc... up til 2600 (including server versions 2462, 2491 and 3505) and i've had to modify my ASP along the way to account for the changes. Not every one of these versions is going to be the same as PWS, because if they are all different, then thats physically impossible.

  • 0
Originally posted by Nick_Jones

the date function for a start, 2 versions produce two different outputs. I have been using XP for a year, i have gone through builds 2428,2446,2462 etc... up til 2600 (including server versions 2462, 2491 and 3505) and i've had to modify my ASP along the way to account for the changes. Not every one of these versions is going to be the same as PWS, because if they are all different, then thats physically impossible.

I see where you are coming from here but the way I understood your original comment was that some ASP tags had changed between PWS and IIS and I replied to that. At that time no mention of XP etc...

So is IIS on XP version 5 or has it been updated ?

Are you referring to ASP 3 code or .NET code ?

EDIT: What exactly is the problem with the date function, as we will probably be moving to XP soon and I would like to know before hand ? Also are you sure it's actuallu a IIS change and not a change in the locale setting in XP ?

Dave

  • 0

The version of IIS that comes with Windows XP Pro is 5.1 (with standard ASP support) and Windows .NET server is 6 (with standard ASP support and ASP.NET support). What i was saying that because it changed between different builds of IIS 5.1 and different builds of IIS 6, at least one of them had to be different to PWS and this may be the problem. He may find that if he were to try his ASP code on a different build of IIS that it would actually work first time without any tweaking, but that is not the case with his IIS.

However, now that he has mentioned permissions, this makes me think it is not actually the different builds that is the problem, but he's just put the ASP files in a folder that don't have script permissions.

pcdolfin: simply erradicated doing the following:

Start Menu -> Programs -> Administrative Tools -> Internet Information Services

Once there, expand it all and right-click on the folder that the ASP files are in that you are trying to execute. Where it says "Execute Permissions:", make sure it says "Scripts only" and not "None". That should fix the permissions problem. If you still get problems after this contact me.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!