[REBOL] Re: Why does my html ACTION call merely display and not execute my scrip
From: gjones05:mail:orion at: 25-Feb-2001 16:48
From: Michael Harleman
> Could the problem be that I am running Windows 2000 Professional Beta
> Frontpage 98 was installed, IIS was then installed, Frontpage 98 was
> removed with the Windows 2000 Remove wizard, Windows IIS component was
> removed, Windows 2000 IIS was then reinstalled, and now I am finding
> remnants of Frontpage 98 in Windows 2000 IIS(the wwwroot directory is
> there)? Is the only way to fix it to remove and then reinstall
> Beta 3? Must I be running a normal copy of Win2000Pro or
> Could I dump Win2000Pro Beta 3 and run Win NT 4.0 or can I continue to
> Win2000Pro Beta 3? Is it also possible that I have created the
> known to man on this planet?
Hi, Mike, I can see that you've had a "fun" weekend. You've gone from
trying to run a simple example REBOL cgi to discovering that you need to
reload your OS!!
Actually, I again have to claim ignorance of particulars of the
NT/Win2000 line, but I can speak from experience on loading Microsoft
Beta's on a "production" machine. Mine was a few years back with
combination of Interdev, J++, and Frontpage. Within in short order, my
registry and a number of directories were hopelessly mangled after a J++
crash. A day and a half later, I had everything back in working,
including low level repiecing together of the more important files
(backup?, what backup?). Like Poe's raven, I said, "Never more," at
least not on a machine on which I rely (backup or not). I've been
tempted to give the .NET beta a whirl, but then I break out in a sweat.
So, it may not have been Microsoft's software's fault, but they seem to
set up some of the most complicated sets of interdependencies I can
imagine. So much for orthogonal programming. After hearing my story
retold a thousand times over (read Jerry Pournelle of Byte!), I suspect
that you'll need to reload the OS. But first, on Win95 and now 98 I
always try uninstalling all the offending software. Checking
Microsoft's site for recommendations on loading order and try reloading
the software first. Good chance it may work, and a lot quicker than a
full OS and software reload.
That's my 2 cents, but what do I know? Good luck!