home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!microsoft!hexnut!leefi
- From: leefi@microsoft.com (lee fisher)
- Subject: Re: More TCP/IP install problems
- Message-ID: <1992Jul30.194635.12119@microsoft.com>
- Date: 30 Jul 92 19:46:35 GMT
- Organization: microsoft corp., redmond, wa
- Keywords: nt
- References: <145@sc.sni.ie>
- Lines: 26
-
- [this person was trying to install TCP/IP on windows NT, after 'net start
- tcpipsvc /trace', the trace window gets created and then immediately goes
- away. the question was how to keep the trace window on the screen long
- enough to read it.]
-
- the tcpipsvc.exe is run via the 'net start' code and doesn't have any
- stdout/stderr to write to. so what it does is creates a new console window
- to display its output. however, when it exits the window gets removed
- during process cleanup.
-
- sometimes, the TCP/IP service exits very quickly, not giving you a chance
- to see the trace output. one thing to try is to type CTRL+S a bunch of
- times, sometimes you'll get the timing right and freeze the output. if
- that doesn't work, if you have a second machine setup as a kernel debugger
- (i386kd.exe, mipskd.exe), you can 'net start tcpipsvc /dbgtrace', which'll
- send the output to the debugger instead of a new console window.
- similarly, if you don't have a kernel debugger, you can use NTSD or WinDbg
- on the net start and TCP/IP service code, you can trace through this error
- codepath before the console window goes away.
-
- it has been suggested to add a pause to the end of this trace output or add
- a new switch to send the output to a file. but we don't have a version with
- these changes at this time, sorry.
- __
- Lee Fisher, (not a spokesperson for) Microsoft Corp., Redmond, WA, USA
- leefi@microsoft.com, {uunet,uw-beaver,sun,sco,decvax}!microsoft!leefi
-