Big, big problems...
Neil Hunter
Ok, how many people here are playing with full-duplex audio and application
sharing on Win95?
Why? Because we've come across some *major* problems! Try this:
1). Start up NM
2). Start up Internet Explorer (we're using v3.02).
3). Now open up the Intel Connection Adviser and make it stay on top. Make
sure you can still see the Internet Explorer menus as well as the %CPU
on ICA.
4). Now click on a menu in IE. Nothing else. Don't select an option,
don't move, don't do nothing. Just drop down a menu.
5). Look at the %CPU.
Does anyone else see the %CPU hit 100???!!!
Now open up MS Access 95. Don't open a database, just the app. Again, %CPU
hits 100!!
We've found that full-duplex audio is great for supporting application sharing
sessions - but only as long as the CPU has a bit of room to do the audio. If
you have too much processor use, the audio loses out and becomes unusable.
This would be fine if it only happened every once in a while, but we're
finding examples of applications that hog the processor. This kills the audio.
Interestingly, this scenario doesn't occur under NT - I guess it multitasks
properly. Sadly until we have full-duplex audio support and decent video for
NT it's not an option. (Ok Robert, I need to check out Winnov ;)
I'd be interested to hear whether this problem is affecting others!
Cheers,
Neil
-------------------------------------------------------------------------------
Neil Hunter Virtual Working Phone: x.6819
Keyworth Scholar Systems Group Email: ne...@scs.leeds.ac.uk
-------------------------------------------------------------------------------
"..Whoops Mrs. Miggens - you've sat on my artichokes.." - B.Adder
Jeffrey A. Durham
This is a multi-part message in MIME format.
------=_NextPart_000_01BC547D.8A7E27E0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
We haven't hit this problem yet. Yesterday, I was doing full-duplex audio,
video, and application sharing without any problems whatsoever. The audio
sounded great. This was under Windows 95 on a LAN. However, NetMeeting
was told that it was using 28.8 for audio.
What machine configuration do you have? Memory, CPU, MMX, video capture
card, etc.?
Jeff Durham
jdu...@one.net
Neil Hunter <ne...@scs.leeds.ac.uk> wrote in article
<01bc5487$1cda06a0$83930b81@cshpci01>...
------=_NextPart_000_01BC547D.8A7E27E0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<html><head></head><BODY bgcolor=3D"#FFFFFF"><p><font size=3D2 =
color=3D"#000000" face=3D"Arial">We haven't hit this problem yet. =
Yesterday, I was doing full-duplex audio, video, and application =
sharing without any problems whatsoever. The audio sounded great. =
This was under Windows 95 on a LAN. However, NetMeeting was =
told that it was using 28.8 for audio.<br><br>What machine configuration =
do you have? Memory, CPU, MMX, video capture card, =
etc.?<br><br>Jeff Durham<br>jdu...@one.net<br><br><br><br>Neil Hunter =
<<font color=3D"#0000FF"><u>ne...@scs.leeds.ac.uk</u><font =
color=3D"#000000">> wrote in article <<font =
color=3D"#0000FF"><u>01bc5487$1cda06a0$83930b81@cshpci01</u><font =
color=3D"#000000">>...<br>> Ok, how many people here are playing =
with full-duplex audio and application<br>> sharing on Win95?<br>> =
<br>> Why? Because we've come across some *major* problems! Try =
this:<br>> 1). Start up NM<br>> 2). Start up Internet Explorer =
(we're using v3.02).<br>> 3). Now open up the Intel Connection =
Adviser and make it stay on top. Make<br>> =
sure you can still see the Internet Explorer =
menus as well as the %CPU<br>> on =
ICA.<br>> 4). Now click on a menu in IE. Nothing else. Don't select =
an option,<br>> don't move, don't do nothing. =
Just drop down a menu.<br>> 5). Look at the %CPU.<br>> <br>> =
Does anyone else see the %CPU hit 100???!!!<br>> <br>> Now open up =
MS Access 95. Don't open a database, just the app. Again, %CPU<br>> =
hits 100!!<br>> <br>> We've found that full-duplex audio is great =
for supporting application sharing<br>> sessions - but only as long =
as the CPU has a bit of room to do the audio. If<br>> you have too =
much processor use, the audio loses out and becomes unusable.<br>> =
This would be fine if it only happened every once in a while, but =
we're<br>> finding examples of applications that hog the processor. =
This kills the audio.<br>> <br>> Interestingly, this scenario =
doesn't occur under NT - I guess it multitasks<br>> properly. Sadly =
until we have full-duplex audio support and decent video for<br>> NT =
it's not an option. (Ok Robert, I need to check out Winnov ;)<br>> =
<br>> I'd be interested to hear whether this problem is affecting =
others!<br>> <br>> Cheers,<br>> Neil<br>> =
<br>> =
-------------------------------------------------------------------------=
------<br>> Neil Hunter		 Virtual =
Working	 Phone: x.6819<br>> Keyworth =
Scholar	 Systems Group	 =
Email: <font =
color=3D"#0000FF"><u>ne...@scs.leeds.ac.uk</u><font =
color=3D"#000000"><br>> =
-------------------------------------------------------------------------=
------<br>> "..Whoops =
Mrs. Miggens - you've sat on my artichokes.." - B.Adder<br>> =
<br>> </p>
</font></font></font></font></font></font></font></body></html>
------=_NextPart_000_01BC547D.8A7E27E0--
Arvin Meyer
Hi Neil,
First, the Intel ICA is often inaccurate. Second, it uses from 3% to 15% of
the processor, depending on your machine.
Now I have gotten rid of the ICA, and don't use IE a lot during my app
sharing, so I can't really comment on whether or not it is using up all the
resources.
But being an Access programmer, I can comment about Access. On Win95 (or
even 3.1 for that matter) Access uses 100% of the processor. I have even
noticed this on my 200MHz machine. What's more, Access will use almost as
much RAM as you can feed it. I suggest no less than 24Mb for a desktop
running Win95, and Access 7 or 8, 32Mb for NT.
You should also notice that this activity dies down in about 30 seconds,
less on faster, higher powered machines. Windows, adjusts the priority of
processor use depending upon the app. NT allows this to be configured by
the user. Access priority is normally fairly low. I can tell you that I
have successfully app shared Access 7.0 (the worst version in terms of
being power hungry) from a 486DX33 16Mb of RAM at 1/2 duplex with all but
the final version of NetMeeting (haven't put that on the 486 yet).
Also, in all but the final version of NetMeeting, I have had to
occaisonally return to 1/2 duplex to improve sound quality. This on a
200MHz machine with 64Mb of RAM and Matrox Millenium video card. I
attribute this mostly to slow routers, or heavy internet traffic (confirmed
by slow ping returns).
And yes, you do need to check out the Winnov card, if only to get full
duplex on NT.
--
Arvin Meyer
On-Site Solutions
e-mail: ons...@esinet.net
phone: (804) 973-9140
http://www.esinet.net/cabg/consult/onsite.html
--------------------------------------------------------------------
Rowby
I
> attribute this mostly to slow routers, or heavy internet traffic (confirmed
> by slow ping returns).
>
Can you recommend a program for win95 which I can use to test Ping?
Thanks
Robert Scoble
Just open up an MSDOS session and do a trace route.
Type tracert 208.203.3.120 to see how bad the Internet is to my machine,
for instance.
Robert Scoble
http://www.netmeet.net
Rowby wrote in article <336686...@earthlink.net>...
Julie
Arvin Meyer
Hi Julie:
There are a number of utilities built into Win95 which make it easier to
diagnose network problems, and communication. Some of these are:
1. Winipcfg.exe (in NT this is ipconfig) - This will return your current
IP address, subnet mask, gateway(router or occaisonally bridge) and lease
information. While all these are important to a network connection, the
only one of interest for most Internet network connections, is your IP
(Internet Protocol) Address. This address is usually dynamically assigned
by your provider when you connect. You can use the IP address to directly
call another computer running NetMeeting. At Start...Run, type winipcfg
2. Ping.exe - This will return connection results based on 4, 32 byte
signals sent to the computer you dial, and the time in milliseconds that it
takes for the trip. Typical times are in the 200 to 400 ms range, longer
than 400 milliseconds means a slow connection due to busy Internet. At the
MS-Dos prompt (Start menu) Type ping [space] and the Domain Name of the
Server or IP address of the computer you are trying to reach. For instance
"ping microsoft.com" will return:
C:\WIN95B>ping microsoft.com
Pinging microsoft.com [207.68.156.53] with 32 bytes of data:
Reply from 207.68.156.53: bytes=32 time=212ms TTL=56
Reply from 207.68.156.53: bytes=32 time=203ms TTL=56
Reply from 207.68.156.53: bytes=32 time=237ms TTL=56
Reply from 207.68.156.53: bytes=32 time=205ms TTL=56
3. Tracert - also executed from the MS-Dos prompt, will trace the route of
your connection.
Example:
C:\WIN95B>Tracert microsoft.com
Tracing route to microsoft.com [207.68.137.62]
over a maximum of 30 hops:
1 126 ms 120 ms 115 ms max1.esinet.net [208.197.151.3]
2 122 ms 118 ms 116 ms esi-t1-1.esinet.net [208.197.151.1]
3 164 ms 125 ms 124 ms Loopback0.GW2.DCA1.Alter.Net [137.39.2.154]
4 136 ms 126 ms 124 ms 422.atm11-0.cr2.dca1.alter.net
[137.39.13.198]
5 376 ms 324 ms 308 ms 101.Hssi8-0.CR2.SCL1.Alter.Net
[137.39.72.146]
6 197 ms 259 ms 187 ms Fddi0-0.AR1.SCL1.ALTER.NET [137.39.19.2]
7 210 ms 210 ms 202 ms Dist1-SCL.MOSWEST.MSN.NET [137.39.100.58]
8 208 ms 202 ms 200 ms 207.68.145.46
9 217 ms 209 ms 207 ms microsoft.com [207.68.137.62]
Trace complete.
The first hop is between my computer and my ISP's router, the last is the
computer (or in this case, the server I called). The addresses in between,
are all the routers, gateways, etc. used to make this connection.
There are other utilities as well (telnet, loopback, etc.) but this should
get you started.
--
Arvin Meyer
On-Site Solutions
e-mail: ons...@esinet.net
phone: (804) 973-9140
http://www.esinet.net/cabg/consult/onsite.html
--------------------------------------------------------------------
Julie <bro...@haltonbe.on.ca> wrote in article
<01bc552a$b4fe8de0$b97bebc7@BBrock8489>...
Arvin Meyer
Rowby <ro...@earthlink.net> wrote in article
<336686...@earthlink.net>...
> Can you recommend a program for win95 which I can use to test Ping?
>
See my answer to Julie in this thread below:
Joel Estes
Go to your Dos Prompt and then type ping and the IP address or the URL
address and it will respond.
Joel
Julie <bro...@haltonbe.on.ca> wrote in article
<01bc552a$b4fe8de0$b97bebc7@BBrock8489>...
> What exactly is Ping. Thanks.
>
> Julie
>
> Rowby <ro...@earthlink.net> wrote in article
> <336686...@earthlink.net>...
> > I
> > > attribute this mostly to slow routers, or heavy internet traffic
> (confirmed
> > > by slow ping returns).
> > >
> >
> >
> >
> > Can you recommend a program for win95 which I can use to test Ping?
> >
> > Thanks
> >
>
Julie
When I typed ping plus IP address, it said the program cannot be run in DOS
mode.
Julie
Joel Estes <jes...@southwind.com> wrote in article
<01bc5577$43a22420$73bac9c7@joel->...
Joel Estes
Julie, just what did you type? Try to ping my ISP, just go to the DOS
Prompt, and type out
ping southwind.com
Let me know what you get back. You should have four returns.
Joel
Julie <bro...@haltonbe.on.ca> wrote in article
<01bc558c$d3cc5f60$b07bebc7@BBrock8489>...
Julie
When I typed "ping southwind.com at c:\windows prompt while online, the
response was "This program cannot be run in DOS mode." When I used Find to
search for ping, it found c:\windows\ping.exe, c:\windows\help\pingname.bat
and c:\windows\pingnum.bat. When I clicked on pingname in the Find window,
the system opened an MS dos prompt window and displayed the following
information:
C:\WINDOWS\HELP>ping www.microsoft.com
Pinging www.microsoft.com [207.68.137.53] with 32 bytes of data:
Reply from 207.68.137.53: bytes=32 time=361ms TTL=54
Reply from 207.68.137.53: bytes=32 time=232ms TTL=54
Reply from 207.68.137.53: bytes=32 time=227ms TTL=54
Reply from 207.68.137.53: bytes=32 time=459ms TTL=54
C:\WINDOWS\HELP>ping ftp.microsoft.com
Pinging ftp.microsoft.com [198.105.232.1] with 32 bytes of data:
Reply from 198.105.232.1: bytes=32 time=249ms TTL=117
Request timed out.
Reply from 198.105.232.1: bytes=32 time=231ms TTL=117
Reply from 198.105.232.1: bytes=32 time=226ms TTL=117
...
Click the Help window to continue with the Internet troubleshooter.
------------
What exactly is the above system response trying to tell me. Where is the
help window to continue with Internet troubleshooter. When I later opened
a new dos prompt window, I changed to the Help directory, and typed in
"ping southwind.com", "ping ftp.southwind.com", or "ping www.southwind.com"
(at different times). I got the same response "This program cannot be run
in DOS mode."
When I clicked on the pingnum.bat in the Find window, my system got locked.
When I pressed alt-ctrl-del, the system automatically re-booted. There was
no End task selection list. The modem connection stayed open until the
desktop appeared after boot up and then hung up. (An aside: I had Quicken
open at the time of reboot. Now, report info. feature can't access any
report information after July/96. Error in disk). Anyway, what is
"pingnum.bat" used for. Why doesn't "ping + address" at prompt not work on
my system.
Thanks for any help.
Julie
Joel Estes <JEs...@digiscape.com> wrote in article
<01bc55b5$62596ac0$6d4984d0@joel->...
Matt Andres
Hi Julie!
You do need to be on some network where you could hope to send a ping to
another computer address - in this case you probably what to be on the
internet and then use Start/Programs/MS-DOS prompt ---- so you will still
have windows running and be logged onto the Internet while you run ping.
Good NetMeeting!
matt
ma...@primenet.com
Neil Hunter
Getting back onto the original thread of this message ;)
We have good network connectivity - the machines being used are connected to
separate ports on a 10Mbit Ethernet switch - plenty of bandwidth.
What I'd love to know is whether some of you Win95 NM users also experience
the 100% CPU usage with menus in IE3. If so, this is a pretty fundamental
problem!
So, can anyone confirm/deny this??!! Anyone else reproduce it?
Cheers,
Neil
-------------------------------------------------------------------------------
Robert Scoble
Sorry,
I should have said "the simple act of dragging a window around the screen
rapidly if you have the full-window dragging capability uses up quite a bit
of processor power." In fact, I can get it to consistently peg at 100% when
I do that. There are also several other things that I've been able to do to
get my system to peg at 100% (open up any application, for instance) or
play a 3DFX video game, etc. There are lots of things that are processor
intensive.
Robert Scoble
http://www.winnov.com
Just my opinions on this one.
Robert Scoble wrote in article ...
>Neil,
>
>The simple act of moving your mouse around rapidly uses up quite a bit of
>processor power. I'm not suprised at this behavior. How long does the
>processor stay at 100%, though? That's the real question. If it's there
for
>less than four seconds, it probably won't impinge much if at all on the
>quality of NetMeeting. Also, it's a lot more complicated than what you
are
>making it seem. Every task in Windows has a priority, and most will share
>the processor if there isn't any spare processor to go around.
>
>For instance, if you run a few Java applets that are processor intensive
in
>the background, you'll notice that the processor utilization goes up to
>100% (I have a few that stress the processor utilization). However, these
>things are fairly well behaved and I can work in my other apps all day
long
>and if I didn't have that processor monitor, I would never even know that
>something is using my processor power.
>
>What I'm trying to get at is, don't be scared because something takes up
>100% of your processor, unless it is impinging on NetMeeting's audio or
>video quality. If IE3 is hurting the quality of NetMeeting, then we want
to
>know about it. It wasn't clear from your messages whether IE3 was really
>hurting the quality of your NetMeeting session, or whether you just
noticed
>that the processor utilization is really high.
>
>Could you also be more specific about what you were doing in the menus so
>we can test it here and see what happens? I do want to try to reproduce
>stressful situations on the processor to make sure our drivers are
>well-behaved under these conditions. Thanks!
>
>Robert Scoble
>http://www.winnov.com (A leader in Windows-based video and audio
>communications)
>http://www.netmeet.net (The place for NetMeeting users)
>
> Neil Hunter wrote in article <01bc5619$87c5a760$83930b81@cshpci01>...
Joel Estes
Julie, all I can offer is that there is a strange configuration on your
computer.
For instance, right now, I can go to Start/Programs/Dos Prompt and type
ping ils2.microsoft.com and get four responses. By the way southwind.com
is no longer in business as of this morning, so it will not work, under any
circumstances.
Of course, you must be connected to the internet in some manner for the
information to travel to the destination and back. It is always a hope
that the response will be within 200ms; however, there are instances when
it is above that or the system timed out. (no connection within the time
limit)
The ping us used to provide knowledge that you can in fact reach a
destination on the internet. Sometimes one has problems making
connections, then by using the ping they can confirm one way or the other
if they can in fact reach the desired destination.
Joel
Arvin Meyer
Hi Julie:
Seems like you have some big problems. The pingnum, and pingname are
nothing more than simple Dos batch files used by the Help system to ping MS
WWW and FTP servers, either by name (pingname.bat) or IP address
(pingnum.bat).
When involked on your system, they appeared to work.
Two things disturb me though:
First, why does this not work from a Dos prompt when you do it?
Second, your Quicken corruption. The second is more serious, since it can
involve potential data loss. You need to see if you can repair your Quicken
indices. Not using Quicken, I am unfamiliar with their system of doing
this. I would call their help desk ASAP, describe the symptoms, and how it
happened and try to get your Quicken files working.
After Quicken is fixed, you can probably fix, the ping problem with a
registry entry which should be found at:
HKEY_LOCAL_MACHINE ... System ... CurrentControlSet ... control ...
InstalledFiles ... ping.exe
You may have to reinstall Windows if this can't be fixed in the registry.
--
Arvin Meyer
On-Site Solutions
e-mail: ons...@esinet.net
phone: (804) 973-9140
http://www.esinet.net/cabg/consult/onsite.html
--------------------------------------------------------------------
Julie <bro...@haltonbe.on.ca> wrote in article
<01bc55f8$f8a5d840$b27bebc7@BBrock8489>...
> (at different times). I got the same response "This program cannot be
run
> in DOS mode."
>
> When I clicked on the pingnum.bat in the Find window, my system got
locked.
> When I pressed alt-ctrl-del, the system automatically re-booted. There
was
> no End task selection list. The modem connection stayed open until the
> desktop appeared after boot up and then hung up. (An aside: I had
Quicken
> open at the time of reboot. Now, report info. feature can't access any
> report information after July/96. Error in disk). Anyway, what is
> "pingnum.bat" used for. Why doesn't "ping + address" at prompt not work
on
> my system.
>
> Thanks for any help.
>
> Julie
>
> Joel Estes <JEs...@digiscape.com> wrote in article
> <01bc55b5$62596ac0$6d4984d0@joel->...
> > Julie, just what did you type? Try to ping my ISP, just go to the DOS
> > Prompt, and type out
> >
> > ping southwind.com
> >
> > Let me know what you get back. You should have four returns.
> >
Matt Andres
Julie,
I think you need to tell these guys that you have had some success - they
are really going overboard here - heh-heh - I hope you appreciate their
enthusiasm to help. But dont get confused by the additional trouble
shooting. ;-) I know what you did - just prior to my message below - I
closed windows and restarted in MSDOS mode and ran ping ---- ofcourse this
does not work as I expained below - but it does verify where you got that
message about "not run in dos mode" - One might guess from the message
alone.... ;-)
Anyway, dont you think you should let these guys off the hook? (snicker)
Good NetMeeting! -matt - ma...@primenet.com
Matt Andres <ma...@primenet.com> wrote in article
<01bc5599$c5fa3e40$0f16...@primenet.primenet.com>...
> Hi Julie!
> You do need to be on some network where you could hope to send a ping to
> another computer address - in this case you probably what to be on the
> internet and then use Start/Programs/MS-DOS prompt ---- so you will still
> have windows running and be logged onto the Internet while you run ping.
>
> Good NetMeeting!
> matt
> ma...@primenet.com
>
Matt Andres
Whoops Sorry Arvin and Joel & Julie,
Just found Julie's most recent post - really didnt realize she was still
having problems -
matt
Arvin Meyer <ons...@esinet.net> wrote in article
<01bc564a$15d3c520$3597c5d0@onsite>...
> Julie <bro...@haltonbe.on.ca> wrote in article
> > (at different times). I got the same response "This program cannot be
> run
> > in DOS mode."
> >
> > When I clicked on the pingnum.bat in the Find window, my system got
> locked.
> > When I pressed alt-ctrl-del, the system automatically re-booted. There
> was
> > no End task selection list. The modem connection stayed open until the
> > desktop appeared after boot up and then hung up. (An aside: I had
> Quicken
> > open at the time of reboot. Now, report info. feature can't access any
> > report information after July/96. Error in disk). Anyway, what is
> > "pingnum.bat" used for. Why doesn't "ping + address" at prompt not
work
> on
> > my system.
> >
> > Thanks for any help.
> >
> > Julie
> >
> > Joel Estes <JEs...@digiscape.com> wrote in article
> > <01bc55b5$62596ac0$6d4984d0@joel->...
> > > Julie, just what did you type? Try to ping my ISP, just go to the
DOS
> > > Prompt, and type out
> > >
> > > ping southwind.com
> > >
> > > Let me know what you get back. You should have four returns.
> > >
Julie
The command.com is configured to run in Dos mode so I guess that's why ping
won't run in Dos mode when I accessed the Dos prompt through Windows.
Also, the properties also say prevent MS-DOS based programs from detecting
Windows. When I changed the Advanced setting to "Suggest DOS mode as
necessary", and typed "ping" plus address, it worked.
Re: Quicken - it did attempt to fix the files after re-boot because of
shutdown without closing Quicken. I don't think the disk errors had
anything to do with the "pingnum" freeze. I also did have at least 5
applications open when I clicked on "pingnum" so I may have hit the end of
the resources. I did do a disk scan and defrag afterwards and managed to
get back more information. Now only one month's data can't be gathered for
report info. However, if I change that month's date to the previous month,
the info is picked up. The data following that corrupted month is fine too.
Thanks for everyone's help.
Julie
Arvin Meyer
> Re: Quicken - it did attempt to fix the files after re-boot because of
> shutdown without closing Quicken. I don't think the disk errors had
> anything to do with the "pingnum" freeze. I also did have at least 5
> applications open when I clicked on "pingnum" so I may have hit the end
of
> the resources. I did do a disk scan and defrag afterwards and managed to
> get back more information. Now only one month's data can't be gathered
for
> report info. However, if I change that month's date to the previous
month,
> the info is picked up. The data following that corrupted month is fine
too.
Julie:
Your Quicken data was corrupted because the database was open to
"read/write" during your crash. This will happen to all desktop, and
file-server databases. True client/servers databases like SQL-Server, or
Oracle are not as affected by this problem, although Oracle is over-kill
for businesses doing less than $50 million a year or with less than a dozen
users.
How you go about fixing it is proprietary to Quicken, but most databases
are fixable. You should at most lose only a few records. If there isn't a
built-in utility to fix it, then Quicken's Tech support should be able to
help. BUT fix it first, before you enter any more data, or you could make
it impossible to fix. It is the indices which usually get corrupted, not
the data (perhaps a record or 2). So it is important to fix it before you
try to use it again.
Julie
Actually, I noticed that sometimes the missing report info was picked up
but most times it depended on which report dates I wanted info. on. I
narrowed it down to the last 3 days in what I thought was the whole missing
month. I re-dated one record with the previous day's date and re-dated
back and lo and behold the program could pick up the last missing day's
info.
Julie
Arvin Meyer <ons...@esinet.net> wrote in article
<01bc5661$1eb005c0$4497c5d0@onsite>...
Arvin Meyer
Hi Neil,
I don't know if you saw my reply to your message earlier in your thread on
the IE and Access 100% processor usage. If not, e-mail me back, and I'll
send you a copy.
In your first post, you didn't mention the version of Access you were
using, but now I see you mentioned Access 95. My advice as a professional
Access programmer is to upgrade as soon as possible to Access 97, which is
FAR better in this respect, and FAR more stable.
In fact, I definitely would not recommend the use of Access 95 with
NetMeeting. The risk of corruption and data loss is too great.
Arvin Meyer
On-Site Solutions
"Developing results-orientated databases for companies
that demand a tangible return on investment."
e-mail: ons...@esinet.net
phone: (804) 973-9140
http://www.esinet.net/cabg/consult/onsite.html
--------------------------------------------------------------------
Neil Hunter <ne...@scs.leeds.ac.uk> wrote in article
<01bc56e4$4ecb2680$83930b81@cshpci01>...
> Robert,
> I agree with your comments on processor usage - there are situations
where
> the processor hits 100% usage - but only for a short period. We don't
have
> a problem with that sort of behaviour. You expect the processor to get
> used every now and then ;)
>
> As you say, the key is the length of time the processor stays at 100%
> usage - and in most applications it is not long enough to trouble NM.
If the
> %CPU gets too high for too long, the audio suffers - badly.
>
> > What I'm trying to get at is, don't be scared because something takes
up
> > 100% of your processor, unless it is impinging on NetMeeting's audio or
> > video quality. If IE3 is hurting the quality of NetMeeting, then we
want to
> > know about it. It wasn't clear from your messages whether IE3 was
really
> > hurting the quality of your NetMeeting session, or whether you just
noticed
> > that the processor utilization is really high.
>
> Right, here's where the problem is! It wasn't watching the %CPU that
got
> us interested. We were running a NM session using full-duplex audio and
> application sharing. I was sharing the IE running on my client machine
> and was talking through using a Web interface to our system. The remote
> person was complaining that for large periods of time, the audio would
> break up so badly that they could make out around 1 word in 20....
> So, we started doing things really slowly to see when the audio got
really
> bad - and used the chat application so I knew when he couldn't hear me!
>
> It turned out that the major problem was in using menu's in IE. Of
course,
> actually loading IE caused a bit of break up - but that was acceptable.
>
> > Could you also be more specific about what you were doing in the menus
so
> > we can test it here and see what happens? I do want to try to reproduce
> > stressful situations on the processor to make sure our drivers are
> > well-behaved under these conditions. Thanks!
>
> To reproduce this problem, load NM and open up the Intel Connection
Adviser.
> (I know it's supposed to be inaccurate - but it's good enough). If you
like,
> start an audio call to someone else as well. Now load IE. You'll see
the
> processor use climb initially (no problem), then drop back down. No
> complaints there. Now click on, say, the View menu. By that I mean just
> click on the menu bar where it says View - don't select any menu
choices,
> don't move the mouse around, don't use the keys - just drop the menu
down,
> let go of the mouse and back away from the keyboard!!
>
> On *all* our Win95 PC's the %CPU hits 100% - and STAYS there
*indefinitely*!
> So far, IE is the only app we've found this particular problem with -
other
> apps seem to have far more friendly menu handling routines. This is
also not
> an issue under NT - I suspect due to better task handling.
>
> Another culprit is MS Access 95. Just loading this application results
in
> 100% CPU usage seemingly for as long as the app is loaded.
>
> I hope this is enough information for you - please, please let me know
what
> you find if you get chance to try this out. I would *love* to find
others
> experiencing this behaviour so I know it's not an isolated problem!
>
> Cheers,
> Neil
>
>
----------------------------------------------------------------------------