Browser woes

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
My default browser is FireFox.

If I execute:

Code:
start ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf
with TCC12, FireFox starts, partially shows the document, then just sits there using 25% PCU (all of one processor).

If I give the same command to CMD it works correctly; FireFox shows the complete ducument and then idles at 0% CPU.
 
Aug 9, 2009
133
0
#2
FF is a little slow at everything .. I'd blame FF snapin/plugins
What happens if you start it from cmd first, then tcc
could it be cached already?


> -----Original Message-----
> From: vefatica [mailto:]
> Sent: Thursday, 17 February 2011 1:48 p.m.
> Subject: [Support-t-2612] Browser woes
>
>
> My default browser is FireFox.
>
> If I execute:
>
>
> Code:
> ---------
> start ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf
> ---------
> with TCC12, FireFox starts, partially shows the document, then just
> sits there using 25% PCU (all of one processor).
>
> If I give the same command to CMD it works correctly; FireFox shows
> the complete ducument and then idles at 0% CPU.
>
>
>
>
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#3
What happens if you start it in TCC using
this command?

start /pgm "ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf"

If you run Process Explorer, can you
see any difference in the way the processes are started (between cmd and
tcc)?

-Scott

vefatica <> wrote on 02/16/2011
07:48:19 PM:


> vefatica <>
> 02/16/2011 07:48 PM
>
> Please respond to
>
>
> To
>
> Samintz@ra.rockwell.com
>
> cc
>
> Subject
>
> [Support-t-2612] Browser woes
>
> My default browser is FireFox.
>
> If I execute:
>
>
> Code:
> ---------
> start ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf
> ---------
> with TCC12, FireFox starts, partially shows the document, then just

> sits there using 25% PCU (all of one processor).
>
> If I give the same command to CMD it works correctly; FireFox shows

> the complete ducument and then idles at 0% CPU.
>
>
>
>
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#4
> with TCC12, FireFox starts, partially shows the document, then just sits
> there using 25% PCU (all of one processor).
>
> If I give the same command to CMD it works correctly; FireFox shows the
> complete ducument and then idles at 0% CPU.
Interesting, but I don't think it's a TCC issue. What I see is it failing
every other time I execute it, whether from CMD or TCC.

I would suspect either your ftp server or FireFox.

Rex Conn
JP Software
 
#5
On Wed, 16 Feb 2011 20:44:11 -0500, rconn <> wrote:

|Interesting, but I don't think it's a TCC issue. What I see is it failing
|every other time I execute it, whether from CMD or TCC.
|
|I would suspect either your ftp server or FireFox.

I just saw it work well 10 times in a row from CMD and then fail as described
earlier 5 times in a row from TCC.

Either way, FireFox's startup command is the same:

Code:
"D:\FireFox\firefox.exe"  -requestPending -osint -url
"ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf"
(probably coming from some shell DLL).

I don't think TCC is handling the start correctly (DDE?, ShellExecute?) because
while FireFox is unresponsive, so is TCC (and that's after TCC's prompt has
returned). And that unresponsiveness includes **other** instances of TCC, too
... and does not include other running apps.
 
G

Glennbo51

Guest
#7
On 02/16/2011 21:50, Charles Dye wrote:

> ---Quote (Originally by vefatica)---
>
> Code:
> ---------
> start ftp://lucky.syr.edu/mat122/stat11t_formulas.pdf
> ---------
> ---End Quote---
> That command works fine here:
>
> TCC 12.10.52
> Firefox 3.6.13
> Adobe Reader 9.4.2
>
As it does here as well

TCC 12.10.52 x64 Windows 7 [Version 6.1.7600]
TCC Build 52 Windows 7 Build 7600

Firefox 3.6.13
Adobe Reader X
 

rconn

Administrator
Staff member
May 14, 2008
10,099
85
#8
> I just saw it work well 10 times in a row from CMD and then fail as
described

> earlier 5 times in a row from TCC.
Not reproducible here -- it fails 50% of the time in CMD, and it fails 50%
of the time in TCC.

That command is not executed by TCC; it is passed to Windows to handle.

And it is impossible for TCC to be affected by Firefox after TCC has
returned to the prompt -- unless you've got a (substantial) Windows bug.
(Which unfortunately is NOT impossible.)

Rex Conn
JP Software