Installation of Creative Labs audiopci card

[Volker Halle]

Paul,

you might also want to check the creation date or image identication information of the drivers in SYS$LOADABLE_IMAGES:

[SYS$LDR]MMOV$ENSDRIVER.EXE
[SYS$LDR]MMOV$ESSDRIVER.EXE
[SYS$LDR]MMOV$MSBDRIVER.EXE
[SYS$LDR]MMOV$VIDRIVER.EXE

They should show dates in 2005 (the kit has been created in APR-2005 according to SPL). V8.2 has been built in NOV-2004, so the drivers should NOT preceed that date if they are supposed to work with V8.2.

Volker.

[Paul Beaudoin]

VOlker, Steven

It appears that is at least part of the problem. I have been picking up:
DEC-AXPVMS-MMOV-V0202--1.PCSI-DCX AXPEXE

From the HP site and interpreting the version as 2.2-1 from the title.... it apparently isn't. I can't find the later version - does anyone have a link. Also, I noticed you have installed the dev version rather that just the RT. Is this important?

Thanks
Paul

[Steven Schweda]

Note that my SYS$LOADABLE_IMAGES:MMOV$*
files all have date "31-MAR-2005", and there
are explicit references to "V82", as, for
example:

ALP $ dire /date /size SYS$LOADABLE_IMAGES:MMOV$ENS*

Directory SYS$COMMON:[SYS$LDR]

MMOV$ENSDRIVER.EXE;1
67 31-MAR-2005 18:04:47.92
MMOV$ENSDRIVER_V732.EXE;1
67 31-MAR-2005 18:04:47.92
MMOV$ENSDRIVER_V82.EXE;1
71 31-MAR-2005 18:04:47.96

Total of 3 files, 205 blocks.

Where:

ALP $ diff SYS$LOADABLE_IMAGES:MMOV$ENSDRIVER.EXE MMOV$ENSDRIVER_V732.EXE
Number of difference sections found: 0
Number of difference records found: 0

DIFFERENCES /IGNORE=()/MERGED=1-
SYS$COMMON:[SYS$LDR]MMOV$ENSDRIVER.EXE;1-
SYS$COMMON:[SYS$LDR]MMOV$ENSDRIVER_V732.EXE;1


The new ("-1") kit seems to be:

DEC-AXPVMS-MMOV-V0202-1-1.PCSI

I've lost track of where I got mine, but if
you get desperate, send me some e-mail
(sms@antinode-org, more or less).

[Volker Halle]

Paul,


Also, I noticed you have installed the dev version rather that just the RT


The PROD SHO HIST output from Steven shows:

DEC AXPVMS MMOV V2.2-1 Full LP Installed

This is a 'Full Layered Product', there is no separate development or runtime kit. The functionality is controlled by the license PAK (MMOV-RT for runtime license, MMOV-DV for development kit).

Volker.

[Steven Schweda]

As for development v. run-time, I usually
install the biggest thing I can find, just
in case I might need the extras some day.

In this case, my source thought that he had
two different kits, but they were actually
the same. The Hobbyist LP license kit
includes both PAks, of course.

[Paul Beaudoin]

Gents,

Bummer. I really expected that my error with the MMOV version was THE error. Not so - Removed the old one, installed the new one (and checked to be sure), adjusted sys$user_config.dat to take out the embeded card (documented problems if you have multiple cards) and rebooted - During config stage an error came up referring to this card as 'not supported on primary PCI bus' (!?). The console I am using is not wonderful and may have actualy said 'only supported ...' In either case this is a PSW500au and as fas as I can tell there is only one PCI bus... Isn't there? I then commented out the new card and reinstated the embedded card. After reboot - no au device. VMS still does not recognise the embedded device. Stuck again. I'll re-check all last night's work for accuracy but I am starting to head for the plan c solution - Run a mixed version cluster and use the other machine at 7.3-2 for audio only. Not great but should work.
Many thanks for all the help.

Regards

Paul

[Paul Beaudoin]

Gents,

Some real progress. Re-installing MMOV adds 2 new entries to sys$user_config.dat - one for the PCI card and one for 'Microsoft Sound Card'. I assumed the 2nd one was the embedded card - but that does not seem to be the case. Taking a hint from Steven's post of driver versions, I changed the original hand-crafted entry (following the earlier release notes)and changed the driver to xxxx_V82. The embedded card now works. The same fix does not work for the PCI card but I am now where I originaly wanted to be. In conclusion, there were 2.5 errors. 1-MMOV install does not detect the embeded audio device correctly and 2- it does not detect the VMS version and supply the right driver. The .5 in mine - I might have leaped earlier to the idea that the original entry needed modification as per original install 3-4 years ago.

BTW - I finally located a version of the manual for the AudioPCI card on the net. If anyone wants a copy, please mail me.

Many thanks for your help and patience

Regards

Paul

[Steven Schweda]

> I changed the original hand-crafted entry
> (following the earlier release notes)and
> changed the driver to xxxx_V82. [...]

Why? On your system, the "xxxx" file should
be a copy of the "xxxx_V82" file (as mine, on
a VMS V7.3-2 system, was a copy of the
"xxxx_V732" file).

(At first glance I was expecting "xxxx" to be
the result of SET FILE /ENTER, but a closer
look revealed it to be a copy. Well, they're
small.)

[Paul Beaudoin]

Steven,

Agreed - it should have and that was the complaint. It was from your earlier post that showed the specific 'V82' files that triggered the investigation. MMOV 2.2-1 install creates 2 new entries neither of which pointed to the V82 drivers. Worse - I was assuming the 'Microsoft Sound Card' referred to the embedded one (it may have but didn't work). Back when I first installed MMOV there were instructions to add an entry into sys$user_config.dat which I did and it worked happily therafter. The change here was then twofold: Ignore (actualy comment out)the automatic entry and change the original manual entry to the V82 version of the driver. This then made the embedded card work. (Yeah!). Unfortunately the same 'fix' did not help the PCI card - it still doesn't even show as a device. I plan to fool around with this over the weekend but as it stands, I can live with the result.

Thanks again for the pointer


Paul

[Paul Beaudoin]

Steven,

I should have read your reply a bit better. Now that I have, The 'fix' then should have been simply to ignore the new entry and continue on with the manual one, however, that is how it should have been after the initial install which didn't work. Best guess at this stage is that the new entry, being later in the file, replaced the manual entry and all I neeeded to do was comment it out. Sometimes ya just gotta do it the hard way...

Paul