WiMP9 - memory issue - network stack???
US
vers of new Windows Media Player-9 Series Release Candidate (WiMP9) and when
playing any kind of local or even remote content I get "Your computer is
running low on memory. Quit some apps and try again." Error code pops out as
C00D11C6 for which MS, of course, offers no help. Some other person told me
the error stems from WiMP9's interaction with the netowrk stack requesting
or allocating the wrong memory amount and that I should troubleshoot this
problem as a "network stack" issue. (Seems odd and completely unrelated but
I have no other solutions/suggestions currently) and as I check around on
Google, etc., I seem to be the only one seeing this.
In Control Panel>Network I have the following:
Client for Microsoft Networks, Dial Up Adapter,
Intel 21041 based Ethernet Controller,
Microsoft PPP on ATM Adapter,
Microsoft Virtual Private Networking Adapter,
IPX/SPX-compatible Protocol -> Dial Up Adapter,
IPX/SPX-compatible Protocol -> Intel 21041 based Ethernet Adapter,
NDISWAN -> Microsoft PPP over ATM Adapter,
NDISWAN -> Microsoft Virtual Private Networking Adapter,
TCP/IP -> Dial Up Adapter,
TCP/IP -> Intel 21041 based Ethernet Controller.
In BOOTLOG.TXT I have the following:
LoadFailed = ndis2sup.vxd - I read at MS KB 127970 that this and other
loadfailures do not necessarily indicate a problem, but I thought I'd throw
it in just in case someone sees a problem with it.
Normally with this configuration every other "network" usage-based
program/application/feature runs perfect from what I can tell. Nothing fancy
running here, computer (NIC) just plugs into the cable modem and out the
door. I've tried all of he following in order and/or collectively - telling
WiMP9 to "Connect to the internet", tried explicitly setting it's network
detection speed(s), completely disabling (via MSCONFIG and reboot) all AV
and Firewall apps, completely disabling (via MSCONFIG and reboot) all
apps/TSRs except for SYSTRAY), and even booting to safe mode: Same error all
the time. So, before I chase the proverbial tail any longer, my question(s)
are:
1) Does this "network stack" problem assessment sound
plausible/reasonable/rational? (To me it doesn't, but...)
2) If 1) is true, and given the fact that my "network stack" hasn't been a
problem up to this point, where does one go to test or analyze or evaluate
the operation of the network stack?
3) How difficult is a "network stack" issue to troubleshoot or resolve
generally?
4) If there's an inexpensive way (freeware/shareware) to dig in, what
suggestions might the group propose before I turn this over to a shop or
have to call MS at $40 an incident?
5) Anyone else using WiMP9, seen this happen? And yes I know it's beta but
I'm absolutely convinced when the real 9 Series gets published, I'm going to
have the same issue.
Thank you all.
Richard G. Harper
"pre-release version of software, may exhibit problems on some systems, may
not work on any system".
Since it's not at the commercial release stage yet, it may exhibit symptoms
that will be corrected before the release of the final version.
--
Richard G. Harper (MVP Win9x) rgha...@email.com
* PLEASE post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
Help US help YOU ... http://www.dts-l.org/goodpost.htm
"US" <WHFT...@HOTMAIL.COM> wrote in message
news:0JWR9.569456$WL3.160338@rwcrnsc54...
daytripper
>Running Win98SE at home on cable w/ PIII and 512 Meg RAM. Applied correct
>vers of new Windows Media Player-9 Series Release Candidate (WiMP9) and when
>playing any kind of local or even remote content I get "Your computer is
>running low on memory. Quit some apps and try again." Error code pops out as
>C00D11C6 for which MS, of course, offers no help. Some other person told me
>the error stems from WiMP9's interaction with the netowrk stack requesting
>or allocating the wrong memory amount and that I should troubleshoot this
>problem as a "network stack" issue. (Seems odd and completely unrelated but
>I have no other solutions/suggestions currently) and as I check around on
>Google, etc., I seem to be the only one seeing this.
This actually sounds like the notorious Win98SE Vcache bug. It usually only
affects systems with more than 512MB of ram, but I have read testimonials that
it can also affect systems with just 512MB.
The following can't hurt, and it might just help.
In your system.ini, add the following line:
MaxFileCache=128000
This sets the upper limit of memory that the MS file caching agent ("VCACHE")
can use (in this example, roughly 128Megabytes). You can also set the minimum
memory reserved for vcache by adding:
MinFileCache= {some_value < or = to MaxFileCache}
There is also an advantage (memory fragmentation avoidance) to setting both
Min and MaxFileCache to the same value. Back when I was still running Win98SE,
I ran into the vcache bug with a full gig of ram, and fwiw, these are the
settings I used (note that the string "[vcache]" is simply an optional,
non-functional label":
[vcache]
MinFileCache=128000
MaxFileCache=128000
As I said, you can add these entries to the system.ini file and they can't
possibly hurt anything (though depending on your application & hardware mix,
it is possible these specific values may not be optimal). Reboot, and see if
your problem goes away...
hth
/daytripper
TheCrewser
specifically need. In most cases, all that is necessary is
Client for Microsoft Networks
Your Ethernet adapter(Intel 21041)
TCP/IP
Unless you are using the Dial-Up adapter and the Virtual Private
Networking adaptor for dial-up Internet access or to access another
remote system, you will be fine with the minimum configuration.
One other possiblity is the infamous Win98 issue with systems >= 512MB
RAM:
http://support.microsoft.com/default.aspx?scid=kb;en-us;253912
Good Luck...
GLCrews, MCP
On Sun, 05 Jan 2003 13:48:44 GMT, "US" <WHFT...@HOTMAIL.COM> wrote:
US
even one other person experiencing this, but my research shows it's not
happening elsewhere. But, I'll try to take some solice in the fact that it
is "beta" and not "bettah". The real version should be out tomorrow or in a
couple of days. I'll try to post back here with further results.
Thanks again.
"Richard G. Harper" <rgha...@email.com> wrote in message
news:#udUvGNtCHA.2308@TK2MSFTNGP09...
US
rebooted and still yields the same results. I'm still wondering about the
network stack and it's part (or missing part). There is another post with a
plausible answer however.
Thanks again for trying.
"daytripper" <day_t...@REMOVEyahoo.com> wrote in message
news:jr7h1vo8f89tlq8oj...@4ax.com...
US
Network > Configuration) all the extraneouse entries. Then also at the same
time visited System Config Util >Advanced and set the upper mem limit to
510. Rebooted. Checked IE and Outlook to ensure I still had network
connectivity - I did! Laumched WiMP9 - same result - same error code.
Don't ask how mad I was!
I then said, let me try the old Media Player (mplayer2.exe) ver 6.4 which is
left residual after you install WiMP9. Guess what - it now says, "Ran out
of memory" on it's status bar!! That thing was working perfectly a few
short days ago before I got into this soup.
So if the original advice from zach(ms) regarding "your network stack is
causing the problem" is still correct, I really need to concentrate more on
the stack, I think.
Maybe I'll just sit tight and wait for the real WiMP9 to appear. I'm pretty
tapped out now - this troubleshooting is resource intensive, to say the
least. Meamwhile, I'm willing to try any other solution, including
investigating this stack issue (which admittedly I don't know too much
about)
Thanks again to this group and it's participants for the help. If I do find
an answer I'm definitely going to post back.
"TheCrewser" <NOS...@MYMAIL.COM> wrote in message
news:i38h1v8cba87r7q3c...@4ax.com...
Shane
Got a spare hard drive lying around?
Take out your current hard drive and put it away safely.
Do a clean install of your operating system on the spare hard drive
Install WMP9
Still get the same results?
What ever the outcome, remove the spare and replace your original hard
drive, and work from there
I've come across in the field of computer support, that even hardware can be
a problem.
I came accross a client, his pc kept on freezing, we tried every damn thing
under the sun, final outcome, ^#&%#@ mouse, hehe, replaced mouse and never
had a problem again.
"US" <WHFT...@HOTMAIL.COM> wrote in message
news:0JWR9.569456$WL3.160338@rwcrnsc54...
US
Ya know, I thought about that - no - seriously I actually did, really. This
is such a strange prob. I think I saw 20 giggers at Sam's Club for $89 or
something ridiculously cheap like that. But, I'm going to wait a few more
days and see if the actual WiMP 1st rel has any better luck. I don't relish
the thought of ripping into this thing - who has time! If it still fails,
then I may just wander over to the store and try that out. I can always use
a spare drive anyway.
From your experience, as a technician, does this "network stack" suggestion,
stack up???
H
"Shane" <nospam...@westendcomputers.co.za> wrote in message
news:avctea$ld9$1...@ctb-nnrp2.saix.net...
Shane
that to someone who is qualified.
What I would first do, based on experienced gather in the technical field,
as I do all my clients using Internet is remove all the network protocols,
(write down all the information first, you may need it when configuring them
again), reboot the pc and reinstall the networking protocols again, in most
cases, this works for normal internet comnfiguration, because you are
installing the drivers over the old ones, but can not guarantee that this
will work concerning the "network stack" Would someone out there add to
this? Thanks.
The other thing you can try concerning the memory, if you have 2 or more
sticks in there, remove half of it and try that. My opinion that 256Mb is
more than enough for Win9x/ME and may differ from another persons opinion,
unless you have some serious resource hungry software that you are using.
If you are only using internet, and gathering from the info you have given,
given that I have no knowledge on cable, as we don't have it in our country
yet, I presume the cable is using your network card, so depending on the
configuration required by your ISP, I'd start of with just using the
following protocols (bare minimum) Dial-Up Adaptor & Your network card &
TCP/IP. Add protocol as required by your ISP.
Troubleshooting can take long and somtimes days, but in the end, when you
find the fault, you are that much of a stronger pc user :) and you feel
impressed with yourself, cause now you can brag to your friends, "...look I
can do this..."
"US" <WHFT...@HOTMAIL.COM> wrote in message
news:4WmS9.266289$qF3.23864@sccrnsc04...
Michiel
by 80 gig hard drive at newegg.com for 108.00 $20 more and 60 gigs larger.
"US" <WHFT...@HOTMAIL.COM> wrote in message
news:4WmS9.266289$qF3.23864@sccrnsc04...
Ruth Kaye Trujillo
don't have enough memory (RAM that is) b) have way too many things open
or running in background (check your systray and taskmanager) or c) your
swap file is needing some tweakage.
a) is simple enough. upgrade to some more and/or some bigger ram.
b) check in system information->system configuration utility->startup tab
and see how many programs are being run at startup and how many of them
are being duplicated. "load power profile" usually checks in at least
twice. if you have virus software, it usually gets loaded twice, etc.
sometimes the duplicates take up twice the memory usage.
c) defrag your hard drive (how big *is* your hard drive anyway?). i know
it is kind of simplistic, but if you haven't done it in awhile, your swap
file will have trouble, especially if your drive is filled up.
or it could just be a bug in wmp9 that they haven't quite worked out yet.
make sure you keep yourself updated on when newer beta versions are
released.
HOIB
Make sure what you buy isn't 5400 RPM...
H
"Michiel" <NOmpahlSPAMatORcharterYOUAREdotNOTnetMYFRIEND> wrote in message
news:##l13aftCHA.2448@TK2MSFTNGP09...
HOIB
Thank You Ruth. Unfortunately, I've been there, done that. 512 Meg RAM, 20
gig drive - kept clean and mean by Diskeeper (runs nightly), disabled
everything out of StartUp including the firewall and NAV. That's as
barebones as I can get it. Nothing else running according to System
Monitor/Resource Monitor. It's definitely something to do with this network
stack (that's the only clue I have - mentioned by zach(ms). I wish he would
chime in here with a few tips on how to resolve/analyze a network stack
issue.
H.
"Ruth Kaye Trujillo" <truj...@csd.uwm.edu> wrote in message
news:Pine.OSF.3.96.103010...@alpha2.csd.uwm.edu...
Michiel
That's still pretty darn steep for a 20 gig. My 2 80 gigs are both 7200 rpm.
As a side note, the 20 gig in question is 7200, not 7800. There is not a
hard drive manufacturer that makes a 7800 IDE hard drive. SCSI are usually
10,000 and I doubt Sam's Club would sell SCSI components.
"HOIB" <WHFT...@HOTMAIL.COM> wrote in message
news:#R9C$1jtCHA.2640@TK2MSFTNGP11...
HOIB
OK, OK - I give up - you win!
"Michiel" <NOmpahlSPAMatORcharterYOUAREdotNOTnetMYFRIEND> wrote in message
news:#kA495jtCHA.2396@TK2MSFTNGP10...
HOIB
(today) released version. Richard G. Harper gets the award for putting his
finger dead-right on it. Beta doesn't mean "bettah". Thank you Richard for
a valuable lesson learned! Series 9 now working here just fine with no low
memory error. Installation notes/tips - I had minor problems installing
this but here's what I did to make go through. Your mileage may vary.
First, I took the old "Release Candidate" off through Add/Remove Programs.
I rebooted just to clear off any bad karma. Next, I visited \Windows\System
and renamed QUARTZ.DLL to QUARTZ.OLD because I knew in advance that wm_setup
was not going to like it. I could always rename it back later. As the
system came up, I got an error box stating that MSDXM.OCX was not found or
corrupted. I did find one copy of it in \Windows\System and looked at it's
properties. This is a DirectShow filter file. After poking around I found
I could update/reinstall DirectX 9 which I did. Upon reboot, the MSDXM.OCX
error never reappeared. I then killed everything running I could out of
the StartUp locations/groups. I did this just because I wanted to - not
because of any "science" - my motto - less is better in these circumstances.
Rebooted again and the system came up quite well in its barebones mentality.
I then decided to keep the minimalist philosophy and use "Run" rather than
work with Win Explorer, drilling down to the setup and launching it.
Browsed to the MPsetup.exe, took a deep breath and in about 35 seconds WiMP9
smoothly cleared all hurddles and installed straight away. Very easy
install - not a lot of questions to swim thru. Anyway, I opened my favorite
MP3 (Rushe - "Leilani"). It was a beautiful thing! I then reassembled my
normal boot up procedure and rebooted yet again (to see if it really worked
with everything loaded) and indeed it does. And, just as a plus, I never
bothered to rename QUARTZ.DLL - didn't seem to matter. At some point, I may
need to but until then...
Nothing beats success like success.
The program is feature rich, IMHO! Will it stay running for more than a
couple of hours - who knows - right now, I'm on hour three. Will it
uninstall if I want - cross that bridge later. It will take some getting
used to but it does what it's supposed to with some surprising goodies
tucked in there. It's kind of fun finding out where they are. A plus = The
audio equalizer is quite responsive and uncharacteristically bright. It
also accepted all my WinAmp playlist formulations. Some folks will be loyal
(to the death) to their favorite player - who can blame them. But WiMP9
makes switching very tempting although after my "Release
Candidate"experience, not as easy as it might have been. I also learned
about and cleaned out the apparently extraneous crud in my Network settings
panel!
Hoib.
"US" <WHFT...@HOTMAIL.COM> wrote in message
news:0JWR9.569456$WL3.160338@rwcrnsc54...
Richard G. Harper
Congrats! I'm glad you were able to resolve your issues.
--
Richard G. Harper (MVP Win9x) rgha...@email.com
* PLEASE post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
Help US help YOU ... http://www.dts-l.org/goodpost.htm
"HOIB" <WHFT...@HOTMAIL.COM> wrote in message
news:ejLGrDstCHA.2516@TK2MSFTNGP09...