Re: Memory Reference???

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The error result from *what* is 32? We can't possibly guess what's causing
an error when we don't even know what call is returning it! Use the Error
Lookup tool in Visual Studio and I think you'll find that 32 is "The process
cannot access the file because it is being used by another process."
Without knowing where that's coming back from and how you got there, I have
no idea what that might indicate, other than you trying to do something to
some device that is already doing whatever it is that the device does for
someone else.

Paul T.

"AlexB" <AlexB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:14F46323-B261-40EF-97FE-463794067D45@xxxxxxxxxxxxxxxx
Sorry, I have to make a correction in a hurry. It is not NOSUPPORTED
error, a
different one.

The error result is 32. I thought it was the offset but it seems not the
case.

I will have to find out an get back later.

--
AlexB


"AlexB" wrote:

Paul & Chris hi,

I am getting an error NOTSUPPOTED.

Could you commnet on it or you need more detail?

What is not supported? Does it mean that recording could not be done on
my
machine? In this particular run I tried to do a record.

Can it be overcome? Is there a way around it? Any thoughts?

Thanks.
--
AlexB


"Paul G. Tobey [eMVP]" wrote:

You just need to ask, if you have a question. At worst, you'll get
nothing
back, but you'll be no worse off than if you didn't ask. At best,
you'll
get a good answer from someone, maybe Chris, maybe not.

Paul T.

"AlexB" <AlexB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D8CCE0C9-6CCA-4F55-AC60-73654ACC30C8@xxxxxxxxxxxxxxxx
Hi Chris,

A stage report:

Took about an hour (after got tired of other project) to find out
that all
the functions I need are in winmm.dll not user.dll or kernel32.dll.
Those
have nothing to do with sound devices as far as I can see.

Changed references. A couple of functions needed names update and
after
that
everything loaded.

At this stage it compiles, runs to the point that I get number of
devices,
get and set volume and do other useful functions (essentailly toy
activity
to
make sure it is working) but no sound since the crucial object
(MessageSoundWindow instance is null).

I feel I will crack it open tomorrow or in the next couple of days
provided
I have a window of about two hours and a clear head.

One of the reasons I am posting this is to get a feel if you will be
willing
to answer a couple of questions should I have any tomorrow. Although
our
first encounter was rather dismissive later I was favorably impressed
by
your
thorough and helpful item by item explanations why the approach I was
trying
to take could not work.

Anyhow, I understand you are busy people, you have your jub
description to
worry about and should you decided to say "No," I won't mind at all.

Thanks for what you've done. It was helpful.




--
AlexB


"<ctacke/>" wrote:

Yes, I did go to my MessageWindow replacement. And I may
eventually do
what
you are suggesting: trying to analyze painstakingly what the code
is
doing
but now I want to try to run it with true coredll.dll

You can't. It's impossible for several reasons, some of which are:

1. It's not a "standard " DLL that can be pulled from a device -
it's in
ROM. Only the OEM would have access to the actual DLL on the device
thorugh
the build process.
2. It's built for Windows CE, so the desktop cannot use it. It
targets
the
wrong OS.
3. It's highly likely it's compiled for a totally different
processor
(like
if's a WM/Pocket PC device).

It is my way of learning. How can I get hold of this dll?

See above.

coredll.lib of course did not work as a substitute for coredll.dll

Of course. It's only a LIB meant for linking. Again, see above.

I want to try the next step. Where can I get this dll, please?

The "next step" is to quit trying this insanity. You don't need
coredll.dll. THe functions you need are implemented in kernel32.dll
and/or
user32.dll on the desktop, plus many have managed wrtappers already
in
the
framework. Use those.

I promise to report on my progress no matter how painful it is. I
am
not
sure you will be delighted with the prospect but it is my way
also.

Report away - it's good for the archives (and the entertainment of
everyone
else reading this that knows how Windows CE works).

-Chris








.

Relevant Pages

  • Re: Memory Reference???
    ... have nothing to do with sound devices as far as I can see. ... At this stage it compiles, runs to the point that I get number of devices, ... One of the reasons I am posting this is to get a feel if you will be ... It's built for Windows CE, so the desktop cannot use it. ...
    (microsoft.public.windowsce.embedded)
  • Re: Memory Reference???
    ... have nothing to do with sound devices as far as I can see. ... At this stage it compiles, runs to the point that I get number of devices, ... One of the reasons I am posting this is to get a feel if you will be ... It's built for Windows CE, so the desktop cannot use it. ...
    (microsoft.public.windowsce.embedded)
  • Re: Memory Reference???
    ... A stage report: ... At this stage it compiles, runs to the point that I get number of devices, ... One of the reasons I am posting this is to get a feel if you will be willing ... It's built for Windows CE, so the desktop cannot use it. ...
    (microsoft.public.windowsce.embedded)
  • Re: Memory Reference???
    ... I like asking questions since it sometimes helps to solve the problem even ... At this stage it compiles, runs to the point that I get number of devices, ... One of the reasons I am posting this is to get a feel if you will be ... It's built for Windows CE, so the desktop cannot use it. ...
    (microsoft.public.windowsce.embedded)
  • Re: [SLE] RANT: Advantages of Dual Core
    ... Most of the time I avoid doing too much to my system, there are a few reasons why. ... I've always find Linux somewhat a Rock and a Hard place, because the updates to the core are far too often. ... you don't get yourself a toolbox ... ... Using Windows as "MyToolbox" it's the same as doing it without a toolbox at all! ...
    (SuSE)