Thread View: comp.os.os2.bugs
3 messages
3 total messages
Started by Victor Bien
Mon, 05 Jan 1998 00:00
ESS1868 problem with Warp4 solved.
Author: Victor Bien
Date: Mon, 05 Jan 1998 00:00
Date: Mon, 05 Jan 1998 00:00
33 lines
2234 bytes
2234 bytes
This finding may be of interest to ESS1868 users who: with an ESS1868 the 1st time Win-OS2 is started it reports that there is an incorrect setting for the audio device and then gives sound but that after shutting it down and restarting no error message is given but neither is there sound. The problem was fixed by making the assignment in config.sys for /W: to 3 rather than the default installation value of 0 in the line that reads:- DEVICE=D:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:300,1 /W:3 /N:ES18681$ Also the setting in auddrive.drv section of \OS2\MDOS\WINOS2\SYSTEM.INI of course has to be:- DMAChannelWave2=3 and PortMPU401=300 to match. Ensure the lines:- D:\OS2\MDOS\WINOS2\ESSCFG.EXE /A:220 /I:5 /D:1 /E:0 /B:300 /J:E D:\OS2\MDOS\WINOS2\ESSVOL.EXE /V:8 /L:8 /W:8 /M:0 /C:8 /S:8 /A:8 are in your OS/2 autoexec.bat (or whatever initialising bat files you might select). Use version 5.1 ESSCFG.SYS rather than version 4.9 found with the 1868 distribution file from ESS - http://www.esstech.com. The 1869 distribution has version 5.1. (The 1869 while only 1 digit different does not work with 1868 driver, you have to use the 1869 driver. The 1869 has the 3D sound upgrade). I don't think the above problem occurs with the 1869. It was noteworthy that with the default W:0 in config.sys MS Win-OS2 did not exhibit this problem. There is a version 2.01 1868 distribution. The current distribution from ESS is 1.04 and the distribution from the IBM site is 1.06 but is incomplete, possibly broken. If you can't get a copy from elsewhere e-mail me. I acknowledge Jerry McBride sent me my copy. Regards Victor Bien Trying network selling as a means to promote OS/2.
Re: ESS1868 problem with Warp4 solved.
Author: Ivan Adzhubei
Date: Tue, 06 Jan 1998 00:00
Date: Tue, 06 Jan 1998 00:00
29 lines
1896 bytes
1896 bytes
In <34b16649.0@news2.ibm.net>, on 01/05/98 at 11:01 PM, vbien@ibm.net (Victor Bien) said: >DEVICE=D:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:300,1 /W:3 >/N:ES18681$ Are you sure this is necessary at all? ESS1868 is a PnP card, you don't need to specify any of the params at the driver command line. At least, there is none in my CONFIG.SYS and it works perfectly well both in OS/2 and WinOS2. I just followed the instructions in Warp Desktop Guide to enable sound in WinOS2, but did not modify anything in CONFIG.SYS. > There is a version 2.01 1868 distribution. The current distribution >from ESS is 1.04 and the distribution from the IBM site is 1.06 but is The one included in Warp 4 GA is reporting version 1.0.4. Is 1.0.6 better? In what way it is broken? The only problem I'm having is that although full-duplex mode works fine from WinOS2, none of the native OS/2 applications seems to recognize the card/driver as full-duplex capable. However, I don't know whether this is a driver problem, or just poorly written apps... Cheers, -- ----------------------------------------------------------- "Ivan Adzhubei" <ivan@protein.bio.msu.su> -----------------------------------------------------------
Re: ESS1868 problem with Warp4 solved.
Author: Victor Bien
Date: Wed, 14 Jan 1998 00:00
Date: Wed, 14 Jan 1998 00:00
58 lines
3421 bytes
3421 bytes
In <34b1e96d$1$vina$mr2ice@news.radio-msu.net>, "Ivan Adzhubei" <ivan@protein.bio.msu.su> writes:
>In <34b16649.0@news2.ibm.net>, on 01/05/98
> at 11:01 PM, vbien@ibm.net (Victor Bien) said:
>
>>DEVICE=D:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:300,1 /W:3
>>/N:ES18681$
>
>Are you sure this is necessary at all? ESS1868 is a PnP card, you don't
>need to specify any of the params at the driver command line. At least,
>there is none in my CONFIG.SYS and it works perfectly well both in OS/2
>and WinOS2. I just followed the instructions in Warp Desktop Guide to
>enable sound in WinOS2, but did not modify anything in CONFIG.SYS.
>
No, not absolutely sure - there is a limit of time as to how much R&D
I can manage. Certainly I could get OS/2 to work the card without all
those parameters provided PnP was enabled in the CMOS as I mentioned in
another posting, but Win-OS2 had the problem I mentioned, so did a colleague
and I understand other people. One of the critical finding was that W:3
assignment since W:0 was the default. Presumably, without the parameters
the card would default to W:0 and that was the source of the trouble.
Since OS/2 uses hardware so intensively it may be attributable to the
mainboard we've selected. What mainboard are you using?
With my networking idea (in the non technical sense) you may like to
investigate this situation even more deeply and report back so the
prospective network gains even more intelligence about this, that and the
other thing about using OS/2.
>
>The one included in Warp 4 GA is reporting version 1.0.4. Is 1.0.6
>better? In what way it is broken? The only problem I'm having is that
The files present in the package did not fully match the files list and a
specific file which was a feature of the package was not present, namely:-
ES938.EXE which is a 3D enhancer perhaps not essential.
The package did not appear to be any advance on 1.04. I got the distinct
feeling, perhaps prejudiced by the off-handed way IBM has been treating
OS/2, that the package was thrown together carelessly. E-mail me for
version 2.01. Wherever Jerry McBride got it from, it at least is an
integrated package. I haven't had time to study every little detail whether
2.01 is significantly better than 1.04.
>although full-duplex mode works fine from WinOS2, none of the native
>OS/2 applications seems to recognize the card/driver as full-duplex
>capable. However, I don't know whether this is a driver problem, or just
>poorly written apps...
>
>Cheers,
>--
>-----------------------------------------------------------
>"Ivan Adzhubei" <ivan@protein.bio.msu.su>
>-----------------------------------------------------------
Victor Bien
VCB Computing (R)
Using Network distribution concepts to promote OS/2
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads