yes, I never really appreciated how much of a bad thing it was, until I started testing my loginbox.exe activeX control. I mean, it doesn't look too nice (professional) if your running a full windows gui, but there's still a DOS box hanging around in the background. I tried HIDING the DOS box at the top of the script, but then you get an annoying looking DOS BOX FLASH (you know, its there for a fraction of a second) ...

I think it has something to do with the DOS Console window being the primary owner (toplevel) window of all child windows, and showing a child automatically activates the parent ... just guessing at this point.