SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 9 Feb 2005 15:00:29 PST8
From:	Colin Campbell <cmcampb@adelphia.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: That's better! eCS 1.2 Install on Dell PC

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

I'll try to do the audio driver update the right way, and see what happens.

I did download the 21-day trial version of the commercial SNAP Graphics
3.0, and it has made significant improvements to the monitor's
performance. And, for those who might be interested, it installed very
easily. The download is a .EXE; I ran it, and I was in business with
just one reboot. A so called "Special Edition" is licensed for eCS 1.2,
and it didn't recognize my monitor / video card. The full version sees
everything perfectly. It costs $36.95.

I tried using one of my USB memory devices, and a (new?) utility called
the USB Device Manager sees it as a Lexar, but opening Drives and
clicking on Refresh Removeable Media doesn't bring it into the Drives
list. On my older eCS 1.1 system, I applied USB updates, and things
work nicely. If I have Drives open and plug in my Jump Drive, I get a
warning that Drive H: was attached; it appears in the Drives list, and I
can open the drive and see a bunch of Jpegs. (I would have expected eCS
1.2 to be pretty clean in this regard.)

What should I do to get USB devices working?
Colin

Steven Levine wrote:

>In <42095693.9010601@adelphia.net>, on 02/08/05
> at 04:17 PM, Colin Campbell said:
>
>
>>I simply replaced the two UNIAUDxx.SYS files where I found them on the
>>system - the MMOS2 directory, and a subdirectory thereunder. I also
>>replaced UNIMIX.EXE where I found it, and added UNIAUD.DLL to OS2\DLL,
>>since I think I read that the DLL was new.
>>
>>
>You might be able to get away with this. However, given your continued
>lack of audio, maybe not. One of the most important things a driver
>install does is setup mmpm2.ini. This establishes the logical connections
>between all the multimedia components. Almost anything wrong with this
>file results in no audio, or worse.
>
>In your case, even though the drivers have the same name, there's no
>assurance that the connections and the various flags should have the same
>settings.
>
>The correct way to replace a multimedia driver is to uninstall the old
>driver with minstall and install the new driver with minstall. This has
>been the case since the days of Warp3 or before.
>
>
>Steven
>
>

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 09 | February | 2005 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.