I too, have a question regarding MCI32.OCX.
I wrote an ASP app to allow web users to record and play wav files from
my website using MCI.OCX.
It worked great under Windows 2000, sp3, with VS6 and VS.NET
2003/Framework 1.1
I've upgraded to Windows XP Professional, and have VS6 and VS2005
installed.
MCI32.OCX is in the Windows\System32 directory, and is properly
registered.
VB.Net applications using the interop MCI functions work fine.
However, the ASP pages do not. They display the MMControl, however it
is no longer usable. It is inactive.
I've changed all my IE security settings on the off chance I was
blocking ActiveX in some form or another, but no matter what I do, I
can't get the displayed control to actually open a file or activate any
of the control's buttons (play, record, RW,FF, Rec, etc).
Here's a sample of my code:
<PRE>
<OBJECT CLASSID="clsid:C1A8AF25-1257-101B-8FB0-0020AF039CA3"
HEIGHT=25 WIDTH=200 ID=MMControl1></OBJECT>
</PRE>
<script language = VbScript>
MMControl1.DeviceType = "WaveAudio"
MMControl1.filename = "<% =fname%>"
MMControl1.Command = "Open"
</script>
<script language="vbscript">
Sub btnSave_OnClick
MMControl1.DeviceType = "WaveAudio"
MMControl1.filename = "<% =fname%>"
MMControl1.Command = "Back"
MMControl1.Command = "Save"
ffname="<% =ffname2%>"
ddesc="<% =desc%>"
End Sub
</SCRIPT>
Of course there are some missing parts to the code above but you can
get the gist. The object is created.
There are functions for saving the current file.
There are functions for opening a file.
On "open" the MMControl buttons should become active
and usable but they are not.
I get no errors on this page, and I haven't changed a thing since the
upgrade. This was working beautifully
under 2000/Net 1.1.
Any ideas?
Thanks
Phillip.
