SPONSORED LINKS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ThinkPad 760's Mwave v2.25 - Problems




About 3 months ago I upgraded the Mwave DSP in my IBM ThinkPad 760CD
(P120, 40MB RAM, 1.12GB HD) with the new driver v2.25 (for windows95)
from IBM, which enables 33.6kbps modem speed. The previos version
(2.24) has a 28.8kbps maximum.

Firstly, whilst on-line at the 33.6kbps speed setting, all sound
functions are disabled - irritating when trying to listen to web radio
broadcasts!This is a known and documented in the release notes. Is
there a work-around, or any plans of a fix/upgrade in the near
future?

Second and more importantly, occasionally, whilst online, suddenly
there is modem inactivity and I get a message informing of an Mwave
internal error, then the system hangs, requiring me to press
ctrl-alt-del followed by shutting down the program 'discrim',
thereafter the system works fine although the modem will not function
unless I reboot. Rebooting solves this everytime. As I say, this
doesn't happen often and doesn't bother me too much, but it'd be nice
to know what's going on.

These are the details:

"MWAVE 0001: Mwave modem internal Error
File: MWMSPCFC.C
Line 1857"

After clicking 'OK', this is followed by system freeze.

On pressing ctrl-alt-del, I find the program DISCRIM not responding,
so I shut that particular program down.

This follows by another message:
"MWAVE 0001: Mwave modem internal error
Primary code: 2(0*0002)
Secondary code: 4(0*0004)
File: MWMSPCFC.C
Line: 1580"

After clicking 'OK', I get another message:
"MMTASK. This program has performed an illegal operation and will be
shutdown. If problems persist contact the program vendor."
Details: "MMTASK caused a general page fault in module USER.EXE..."

After clicking 'CLOSE' on the above dialogue box, all is apparently
back to normal - except Mwave modem doesn't work unless I reboot.

After shutting down and performing a Test (from the
Easy Setup), every components (including the test for the DSP) pass
the test.

This is consistent and, as I said earlier, only happened once every
few days since I upgraded from v2.24 to v2.25

A few weeks ago, I installed Microsoft Internet Explorer 4.0 (release
version) with the new active desktop. I started having lots of
problems - plenty of crashes, including those similar to the above.
So, I decided to clean-up my system by formatting the hard disk and
start over - a long and laborious process. I left the Mwave modem
setting at the default 28.8kbps maximum (not the 33.6kbps maximum,
which will disable sound function whilst online).

Now, I regularly (1 in 3 to 1 in 5 times) have problems with the Mwave
modem. As before, suddenly there is online inactivity during
downloading data (e.g. loading a Web pade or downloading a list of
uselet messages), followed by a crash. Each time, at least a copy of
IE4.0 and 1copy of Forte Agent are open. I can usually recover from
such a crash by shutting down (after ctrl-alt-del) one (or both -
depending on which is unresponsive) of the following: 'iexplore',
'explorer'. The result is that I am no longer online, although the
Mwave modem seems to think that I'm still online! There is no way to
get modem functionality again unless I reboot. Interestingly, this
time, there are only very occasionally the Mwave internal error
message. Although, I sometimes get the additional Error 201 after
rebooting (before Win95 loads), which prompted me to Test the system
(via Easy setup) - all tests were passes at each and every instance
and rebooting is always possible thereafter.

If anyone can shed light on this, I'd be most grateful. I have asked
IBM's tech support who were very curteous, yet ultimately unhelpful. I
also asked around on usenet. The general advice is that I should wait
for a new driver to be released - is there anything on the way? I've
waited over 3 moths already. Alternatively, I should revert back to
version 2.24. I have resisted doing this previously since I wanted the
33.6kbps connectivity. However, today, since I'm now on 28.8 max
setting anyway, I thought I would give the old version a go to see
once and for all if this is Mwave problem or a problem with soemthing
else on my system.

I am glad to report that for the past day (consisting of 4 half-hour
to 2 hour online sessions), under similar conditions as before, I've
had no symptoms as described above *at all*. So, it really does appear
as though it is the driver (v2.25) which is causing th problems.
Anyone from IBM out there to comment?

Any comments at all, especially (but certainly not exclusively) those
with similar experiences, would be most appreciated.

Nick

P.S. Sorry for the long-winded posting - this message also serves a
mental therapeutic purpose - this Mwave thing has driven me crazy!:).