Hi Tom,
> On Aug 16, 2024, at 10:33 AM, tom ehlert via Freedos-devel
> <freedos-devel@lists.sourceforge.net> wrote:
>
> Hallo Herr Jerome Shidel via Freedos-devel,
>
> am Freitag, 16. August 2024 um 12:19 schrieben Sie:
>
>> Hi Eric,
>
>> I was having similar issues. So, switched to VSBHDA. Afterwards, I was still
>> experiencing lots of problems and submitted a bug report. But as it turned
>> out, it was user error. I just needed to change the configuration settings
>> and that fixed me right up.
>
> Now it would be cool if you shared the working configuration and the reason
> the configuration before filed.
>
> "I managed to find a solution" mails without presenting the solution is
> bragging and wasting everybody's time.
>
> Tom
VSBHDA comes with a couple example startup batch files.
I only use the one called START.BAT. Originally, it contained the following
lines:
@echo off
rem run vsbhda
jload -q qpiemu.dll
jload -q jhdpmi.dll
lh hdpmi32i -x2
rem set blaster=A220 I7 D1 T3
rem set blaster=A220 I7 D1 T4
set blaster=A220 I7 D1 H5 T6
vsbhda
After Japheth told me what I should try, I simply changed that file to the
following:
@echo off
rem run vsbhda
jload -q qpiemu.dll
jload -q jhdpmi.dll
lh hdpmi32i -x2
rem set blaster=A220 I7 D1 T3
rem set blaster=A220 I7 D1 T4
rem set blaster=A220 I7 D1 H5 T6
set blaster=A220 I2 D1 H5 T6
vsbhda /VOL9
And for me at least, it fixed the crashing on both the Acer Aspireone D250-1924
and the Toshiba Satellite P25-S5092.
Even though I was getting JEMM exceptions, my problem was most likely caused by
an IRQ conflict.
Jerome
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
