[Xitami] devices problem

[Jason Ozin at Technica Solutions]

 > I'm wondering if the key difference from the last set of problems is
 > whether or not there is an actual device (modem, printer, whatever)
 > installed on the particular port name in question (aux, lpt, etc).

Yes we already established that 2 weeks ago I thought.

 > Also, can those who have crashes with "http://localhost/lpt1" please try
 > "http://localhost/prn" (which ought to be the same device, according to
 > DOS tradition), and see if it gives the same effect.

Just tried, it does.

 > (a) the exact URL used during testing (including the exact upper/lower
 >     case, etc)

I'm not keen to do this on an open list. So it's http://www2.xxx.com/lpt1
(but not xxx) and http://www2.xxx.com/prn but the case doesn't seem to
matter as http://www2.xxx.com/LPT1 will also bring it to its knees.

Just to clarify, it doesn't always happen first time, you have to refresh
the page a bit. Also it is NOT restricted to local connections. Remote
connections will bring it down just as easily.

 > (b) the version of Xitami being used (2.4d9, 2.5b5, windows gui, windows
 >     console, nt service)

v2.4d9 (W2K service)

 > (c) the version of Windows you have

Xitami Server is W2K Pro SP2 - clients can be anything.

 > (d) what web browser you used (name, and version)

I've tried IE4.0, IE5.0, IE5.5, IE6.0, Opera 5, Netscape 4.7 (in other words
it is probably not browser related)

 > (e) any service packs, patches, etc that you have

SP2, Fully up to date from windows update site.

 > (f) what devices you have installed (modem, printer, etc)

EPSON EPL-5200 laser on LPT1

 > (g) what crashes (eg, just xitami so you can kill it off and keep going;
 >     the OS freezes so you need to ctrl-alt-del and reboot; the OS
 >     freezes so hard that you can only turn the machine off/hit reset)

Xitami, stops responding to requests and the service will not shutdown. You
can not force it to shut by using the services applet or by using
taskmanager but you can be using pskill.exe from sysinternals.com. The OS is
not effected.