🚀 go-pugleaf

Well, I'm not sure about FP32 or 1869 cards, but I'm running Warp 3 with FP31
and an 1868 card and it seems to work fine.  One thing you need to make sure
of is that you're running clock01.sys and/or closck02.sys drivers that support
timer0.sys.  You'll need to use the drivers that came with the ESS driver, 
the drivers that came with the Netscape Plug-in Pack for multimedia support,
or any Warp 4 driver (Warp 4's timer0.sys should be all right to use as well).
You'll need to make sure that those copies of clock01.sys, clock02.sys, and
timer0.sys are the only ones available in the system.  I had endless problems
until I discovered that there were more than one copy of the clockxx.sys 
drivers in different directories in the path.  You should make sure that the
current versions of those drivers are located in  \OS2\BOOT and not anywhere
else.

I have heard that FP32 causes problems for sound cards, especially ESS, but
can't tell you for certain.  I can tell you that my system seems to work well
with FP31.

Jeff Berntsen
jeffb@world.std.com

vbien@ibm.net   (Victor Bien) writes:

>  Neither the ESS1868 nor the ESS1869 cards will work with Warp3 
>beyond FP17.  What a pain!  Someone at Sydney Australia's OS/2 UG 
>said that IBM has failed to honour certain deep level APIs? in 
>their fix packs so that they are not quite "service level" fixes.
>Consequently the integrity of code written by third parties 
>breaks down across advancing fix packs!  What a freaking out
>conclusion!
>  I've tried moving to FP26 and had to back out.  Today I tried 
>FP32 - just the base operating system and then with the multimedia
>update.  In each case during boot up you get a trap 000d error 
>unless the lines:-
>Rem BASEDEV=TIMER0.SYS
>Rem DEVICE=D:\MMOS2\ES1869DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:330,1 
>/W:0 /N:ES18691$
>Rem DEVICE=D:\MMOS2\VAUDDRV.SYS ES18691$
>are remmed out.  Of course you then get no sound.
>  I am interested because I have some Warp 3 licenses I bought 
>cheap as a means to induce customers to try out OS/2 at low cost.  
>They work great under Warp 4 (so far not having applied any fix 
>packs under that!).  A colleague has had trouble but we're not
>sure of the status of the trouble at this point.
>  So does that mean I can't benefit from code improvements beyond 
>FP17 if I stick with the ESS cards?  I've come to quite like these 
>cards.
>  What are the options?  Use some other brand of sound card?  
>If so which one?  I have an ESS688 but am reluctant to give up the 
>improvements in the advancing ESS card models.  So is staying at 
>FP17 the best compromise?
>  I would be interested in hearing your opinions.
>TIA
>Victor Bien
>VCB Computing(R)
>Trying out network distribution to promote OS/2