🚀 go-pugleaf

  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