🚀 go-pugleaf

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