From: "Hrvoje Mesing" 


"Geo."  wrote in message
news:4122847d$1{at}w3.nls.net...

> I'm not running NTmail on XP, that was just an example I was trying to use
> to
> show how this can affect programs. Why should a programmer be limited to
> 127.0.0.1 when it's the whole class A block that is considered loopback?
> Why
> would MS block the rest of that block, it's not like the addresses are
> routable?

*. That's kewl! I just pointed out that 127.0.0.1 should be fine. Then
again, You are right, that must work!

> nmap is broken, not all of it but all the good functions, also that unix
> subsystem (I forget the name) that allows you to run unix utilities on NT
> is
> broken because of the raw sockets limitations, no more good tools.

*. I'm not aware of anykind of "unix" subsystem in WinXP. Altho, You could
use SFU (MS Services for Unix) or CYGwin or UWin or simply use reCompiled
utils. I have reCompiled utils for Win so if You are in need I can send via
E-Mail, still they are easy to find on the Web.

> I read something about sysprep, it's changed so if you upgrade from SP1 to
> SP2
> you need to run sysprep from SP1 or it won't work. If you do a slipstream
> install of XPsp2 to a fresh drive then sysprep from SP2 works. I don't
> know
> why.

*. Yes, there is Sysprep 2.* out which works only with WinXP directly
upgraded to SP2 or slipstreamed to SP2. It sure do work nice, still, there
is some kind of a "hang" after Sysprep is entering it's final
stage. Altho, it's working pretty fine to me and first Images Loaded with
"everything" for my Production env. are ready for deploying.

*. Thank You!

-+-
M.

--- BBBS/NT v4.01 Flag-5