Windows 2003/IIS 6 issues...new and improved ones.

[Fairlight]

Okay, my latest configuration:

F:\>type markshell.bat

@echo off
set PFDSK=f
set PFDATA=f:
set PFPROG=f:
set PFDIR=
set PFMENU=f:\FP\MENUS
set PFGLOB=
set PFCONFIG=
set PFCMARK=20
cd\
f:

Just found I needed PFCMARK=20 to not get /OV in a date field.

That said, I was just trying to get a debug screen. Whether I'm on C: or
F:, dscreen does actually create/modify a screen.  However, dclerk refuses
to see that there is, indeed, a screen available called debug1 in my
database--the same one dscreen just created one for.

That's one problem.

The other is how to get the equivalent of stdout/stderr redirection to
debug under IIS 6.  I've read that this is really a cmd.exe function, but I
get an error when trying to system() off that as well.  Yet I -have- been
able to system() off a command in another script, so I know that
functionality of system() works in general.  I think I'm hitting fP errors,
mainly because when I checked the main record I sit on with -sr in dreport
(I do a write of 1=@td;2=@tm;write), the record -is- being affected.  So it
seems to be running.  I'm simply not (so far) able to trap output as I
would in *nix to look at the screen trash and sift through it to find the
exact cause of the error.  But being that fP runs and yet my return code is
not 0, I do suspect a crash or error within dreport at this time...I just
can't 100% prove it, or show what it is.  That's why I need a bit of advice
from someone more intimate with the IIS 6 environment.

Ironically, I'm hitting these problems while using OneGate.  The irony is
that 1) I have zero problems getting it perfect inside 10min with apache on
Windows, and 2) I -know- I have customers that use OneGate under this
platform, so I know it works just fine.  It's been tested and used in
production environments under 2003/IIS6.  So it's not a technical
limitation of my product, and it should work just fine.

I'm suspecting that it's either still some confusion as to fP config vars
that are acting differently than I'd expect from my *nix use, or it's due
to some configuration issue with IIS.

Any help is appreciated, believe me.  This keyboard is bruising my
forehead.  This is like...-trivial- stuff to set up.  I have no idea why
it's being so difficult under this environment.  That makes it that much
more frustrating.

mark->
-- 
Fairlight->   ||| "People say they've heard about    | Fairlight Consulting
  __/\__      ||| our deviation / but you've never   |
 <__<>__>     ||| looked so good..." --Le Bon        | http://www.fairlite.com
    \/        |||                                    | info at fairlite.com