It certainly shouldn't do that, Karen.
Did the output that you saw look anything like this?
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 10 ms 21 ms 10.255.172.1
3 11 ms 55 ms 11 ms brhm-t2cam1-b-v128.inet.ntl.com [213.106.229.77]
4 31 ms 12 ms 11 ms brhm-t3core-1b-ge-013-0.inet.ntl.com [195.182.17
6.77]
5 22 ms 30 ms 34 ms bir-bb-b-so-020-0.inet.ntl.com [213.105.174.5]
6 15 ms 59 ms 17 ms man-bb-a-so-230-0.inet.ntl.com [62.252.192.85]
7 20 ms 65 ms 24 ms 212.187.136.125
8 23 ms 28 ms 19 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
9 47 ms 37 ms 18 ms ae-1-100.ebr2.London1.Level3.net [4.69.132.118]
10 91 ms 105 ms 92 ms ae-42.ebr1.NewYork1.Level3.net [4.69.137.70]
11 94 ms 102 ms 92 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
12 101 ms 92 ms 92 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.134.81]
13 131 ms 125 ms 125 ms ae-2.ebr1.Chicago1.Level3.net [4.69.132.65]
14 114 ms 120 ms 112 ms ae-11-55.car1.Chicago1.Level3.net [4.68.101.130]
15 124 ms 121 ms 131 ms WBS-CONNECT.edge5.Chicago1.Level3.net [4.71.182.
14]
16 145 ms 121 ms 120 ms lw-core4-ge9.rtr.liquidweb.com [209.59.157.38]
17 120 ms 122 ms 129 ms lw-dc2-dist3-ge2.rtr.liquidweb.com [209.59.157.1
22]
18 139 ms 124 ms 121 ms 72.52.252.198
Also, was the application running the window "system32/cmd.exe" (it'd say on the bar above the window)? The DOS window should stay open until you close it (either via typing "Exit" at the prompt or clicking the 'close window' icon). An alternative way of getting to the command line is via the Start menu. There should be an option titled Command Prompt under Accessories.
Yeah, it was something like that... and I've never had the DOS window close on me like that before; I did it 3 times just to check. I'll have to try the other route next time and see what I get.
Of course, I had to try again... got this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>tracert martialtalk.com
Tracing route to martialtalk.com [72.52.252.198]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 11 ms 73.85.232.1
3 8 ms 7 ms 7 ms ge-2-35-ur01.denver.co.denver.comcast.net [68.85
.220.73]
4 8 ms 7 ms 7 ms te-8-3-ar01.denver.co.denver.comcast.net [68.86.
103.1]
5 10 ms 13 ms 9 ms 68.86.84.74
6 11 ms 9 ms 9 ms te-0-0-0-4-cr01.cleveland.oh.ibone.comcast.net [
68.86.84.73]
7 10 ms 9 ms 11 ms te-4-4.car2.Denver1.Level3.net [4.79.82.57]
8 11 ms 17 ms 17 ms ae-32-52.ebr2.Denver1.Level3.net [4.68.107.62]
9 46 ms 35 ms 36 ms ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]
10 35 ms 35 ms 35 ms ae-68.ebr1.Chicago1.Level3.net [4.69.134.57]
11 85 ms 34 ms 35 ms ae-11-55.car1.Chicago1.Level3.net [4.68.101.130]
12 45 ms 45 ms 43 ms WBS-CONNECT.edge5.Chicago1.Level3.net [4.71.182.
14]
13 47 ms 45 ms 44 ms lw-core3-ge9.rtr.liquidweb.com [209.59.157.10]
14 62 ms 45 ms 45 ms lw-dc2-dist4-ge1.rtr.liquidweb.com [209.59.157.1
26]
15 44 ms 44 ms 43 ms 72.52.252.198
Trace complete.
I don't know what happened the first time... but if it freezes out again, I'll let you know.