🚀 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

In article <ELE9zM.Fu0@world.std.com>,
jeffb@world.std.com (Jeffrey T Berntsen) wrote:

>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.
>

I'll backup that claim. I am currently running Warp 3.0 with FP#31 and a
ESS1868 sound card, no problems what-so-ever. Even managed sound in WinOs2.
However moving to FP#32 causes traps with the ESS driver. Any version of ESS1868
driver fails.

Having passed a few EMails with an IBM employee, I was told that the ESS
problem will be address in the next round of public FixPak... whatever the
number will be.

So, unless you need Y2K fixes for Warp 3.0 right now, just wait a bit and it'll
get fixed pretty soon... <G>
--

/-------------------------------------\
| Jerry McBride  (mcbrides@erols.com) |
\-------------------------------------/

  Thanks mainly to Jerry McBride whose comments and experiences helped me to get 
the ESS1868 card working fully with FP26!  I'm not sure how crucial it is to use 
the Version 2.01 of the ES1868DD.SYS driver which he forwarded, but here are my 
findings.
  Well, I did try varying the settings in the CMOS but this made no difference 
that mattered.  When PnP was switched on you could leave the various switches out 
e.g. I/O, IRQ etc.  The problem was that TIMER0.SYS would not load.  Its 
successful loading was crucial for playing MIDI files despite what Erik
Huelsmann said.  Without it the MIDI player just crashes as soon as a MIDI
file is loaded.  The same happens with FP17 unless BASEDEV=TIMER0.SYS
is unremmed.  I tried the HD on another mainboard, also Gigabyte, but a
different model (I use a HD drawer caddy to make swapping HDs easy but on 
this other machine I had to temporarily swap out the ESS1869 card for the 1868 
which is a bit of a pain).  I tried both the versions of TIMER0.SYS that I had.  
The one in the version 1.04 and 2.01 drivers from ESS was dated 27.9.95 and
is 3030 bytes.  The one from a Warp4 box is 3026 bytes dated 9.8.96. 
However, what was important was to overwrite the FP26 versions of
\OS2\BOOT\CLOCK01.SYS and CLOCK02.SYS with the ESS versions (which 
are older and slightly larger files).  When this was done TIMER0.SYS loads! 
and the MIDI player comes to life!
  I agree with Jerry McBride's experience - the 1868 won't work with FP32 
(I haven't bothered with the "non-public" release FPs such as FP31.  There 
you have no hope since the ES1868DD.SYS drivers throws such an exception the 
operating system just stops with a Trap 000D error.
  Well I've advanced from FP17 to FP26 with the ESS1868!  I still think 
it's a great card despite the difficulties because it can take 
concurrent access from Win-OS/2 sessions unlike the Sound Blaster which 
just gives an error message when this happens.

Regards
Victor Bien
VCB Computing(R)
Trying out network distribution to promote OS/2

In article <34a8e926.0@news2.ibm.net>, vbien@ibm.net   (Victor Bien) wrote:
>  Thanks mainly to Jerry McBride whose comments and experiences helped me to get
>the ESS1868 card working fully with FP26!

Glad to help. After all, this is what the newsgroups are for... helping where
possible.

Cheers, Victor. Talk to you next year. :-)


--

/-------------------------------------\
| Jerry McBride  (mcbrides@erols.com) |
\-------------------------------------/

I had to go back to the original ESS driver after FP32 under Warp
Connect on my ThinkPad 365xd.

Mark

Victor Bien wrote:
> 
>   Thanks mainly to Jerry McBride whose comments and experiences helped me to get
> the ESS1868 card working fully with FP26!  I'm not sure how crucial it is to use
> the Version 2.01 of the ES1868DD.SYS driver which he forwarded, but here are my
> findings.
>   Well, I did try varying the settings in the CMOS but this made no difference
> that mattered.  When PnP was switched on you could leave the various switches out
> e.g. I/O, IRQ etc.  The problem was that TIMER0.SYS would not load.  Its
> successful loading was crucial for playing MIDI files despite what Erik
> Huelsmann said.  Without it the MIDI player just crashes as soon as a MIDI
> file is loaded.  The same happens with FP17 unless BASEDEV=TIMER0.SYS
> is unremmed.  I tried the HD on another mainboard, also Gigabyte, but a
> different model (I use a HD drawer caddy to make swapping HDs easy but on
> this other machine I had to temporarily swap out the ESS1869 card for the 1868
> which is a bit of a pain).  I tried both the versions of TIMER0.SYS that I had.
> The one in the version 1.04 and 2.01 drivers from ESS was dated 27.9.95 and
> is 3030 bytes.  The one from a Warp4 box is 3026 bytes dated 9.8.96.
> However, what was important was to overwrite the FP26 versions of
> \OS2\BOOT\CLOCK01.SYS and CLOCK02.SYS with the ESS versions (which
> are older and slightly larger files).  When this was done TIMER0.SYS loads!
> and the MIDI player comes to life!
>   I agree with Jerry McBride's experience - the 1868 won't work with FP32
> (I haven't bothered with the "non-public" release FPs such as FP31.  There
> you have no hope since the ES1868DD.SYS drivers throws such an exception the
> operating system just stops with a Trap 000D error.
>   Well I've advanced from FP17 to FP26 with the ESS1868!  I still think
> it's a great card despite the difficulties because it can take
> concurrent access from Win-OS/2 sessions unlike the Sound Blaster which
> just gives an error message when this happens.
> 
> Regards
> Victor Bien
> VCB Computing(R)
> Trying out network distribution to promote OS/2

-- 
mbruffey@voicenet.com
http://www.voicenet.com/~mbruffey