Anyone?

still with the issue

psaez wrote on 2024-11-10, 12:52:

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz. […]
Show full quote

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz.

Under windows 95 it works perfectly. But under windows 98 SE, I got this problem:

Sound was not working, so I openned device manager and I saw an error on my audio device called "creative sound blaster pci128 legacy mode". When openning it I got this message of the problem it had:

This device cannot find free Direct Memory Access (DMA) resources to use (Code 12.)

The only way I found to make sound work was to disable a device. In this case I disabled "Creative gameport joystick". Then, the sound started working and the error dissapeared.

But something is still broken because sometimes I got blue screens and game frozens, and this doesnt happens with windows 95. Also dont happen on my othe retro computer with windows 98, but thar computer haves a tualatin and a different motherboard.

Any ideas?

Turn of automatic resource management for Creative legacy audio and set up resources manually.

Babasha wrote on 2024-12-08, 14:14:

psaez wrote on 2024-11-10, 12:52:

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz. […]
Show full quote

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz.

Under windows 95 it works perfectly. But under windows 98 SE, I got this problem:

Sound was not working, so I openned device manager and I saw an error on my audio device called "creative sound blaster pci128 legacy mode". When openning it I got this message of the problem it had:

This device cannot find free Direct Memory Access (DMA) resources to use (Code 12.)

The only way I found to make sound work was to disable a device. In this case I disabled "Creative gameport joystick". Then, the sound started working and the error dissapeared.

But something is still broken because sometimes I got blue screens and game frozens, and this doesnt happens with windows 95. Also dont happen on my othe retro computer with windows 98, but thar computer haves a tualatin and a different motherboard.

Any ideas?

Turn of automatic resource management for Creative legacy audio and set up resources manually.

Can you give me a little help with doing that?

psaez wrote on 2024-12-08, 15:28:

Babasha wrote on 2024-12-08, 14:14:

psaez wrote on 2024-11-10, 12:52:

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz. […]
Show full quote

Hi, i hace a multi boot systen with appen ax34 and pentium 3 1ghz.

Under windows 95 it works perfectly. But under windows 98 SE, I got this problem:

Sound was not working, so I openned device manager and I saw an error on my audio device called "creative sound blaster pci128 legacy mode". When openning it I got this message of the problem it had:

This device cannot find free Direct Memory Access (DMA) resources to use (Code 12.)

The only way I found to make sound work was to disable a device. In this case I disabled "Creative gameport joystick". Then, the sound started working and the error dissapeared.

But something is still broken because sometimes I got blue screens and game frozens, and this doesnt happens with windows 95. Also dont happen on my othe retro computer with windows 98, but thar computer haves a tualatin and a different motherboard.

Any ideas?

Turn of automatic resource management for Creative legacy audio and set up resources manually.

Can you give me a little help with doing that?

With screenshots from you.

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

I see that bios is from 2001 and there is a 2004 version of the bios, you mean that if I update it, the problem will be solved?

Will be necessary to reinstall W98 ?

Seeing that you are using a VIA Apollo Pro 133A motherboard, did you install the VIA Service Pack 4.43 prior to installing the sound card drivers?

psaez wrote on 2024-12-08, 19:32:

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

I see that bios is from 2001 and there is a 2004 version of the bios, you mean that if I update it, the problem will be solved?

Will be necessary to reinstall W98 ?

No you should not have to reinstall W98.

Dmetsys wrote on 2024-12-08, 20:17:

Seeing that you are using a VIA Apollo Pro 133A motherboard, did you install the VIA Service Pack 4.43 prior to installing the sound card drivers?

I installed this: via-4in1-443v-63160adabfe43125550176

from here: https://theretroweb.com/motherboards/s/aopen-ax34#driver

is that the service pack you are talking of?

Horun wrote on 2024-12-08, 21:16:

psaez wrote on 2024-12-08, 19:32:

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

I see that bios is from 2001 and there is a 2004 version of the bios, you mean that if I update it, the problem will be solved?

Will be necessary to reinstall W98 ?

No you should not have to reinstall W98.

I'll try when I go to that place. Will it be necessary to uninstall and reinstall drivers? or everything should start working fine without doing nothing?

psaez wrote on 2024-12-08, 21:42:

Horun wrote on 2024-12-08, 21:16:

psaez wrote on 2024-12-08, 19:32:

I see that bios is from 2001 and there is a 2004 version of the bios, you mean that if I update it, the problem will be solved?

Will be necessary to reinstall W98 ?

No you should not have to reinstall W98.

I'll try when I go to that place. Will it be necessary to uninstall and reinstall drivers? or everything should start working fine without doing nothing?

No you should not have to reinstall drivers but W98 may do a few "found new hardware" thingy's...

psaez wrote on 2024-12-08, 21:41:

I installed this: via-4in1-443v-63160adabfe43125550176 […]
Show full quote

Dmetsys wrote on 2024-12-08, 20:17:

Seeing that you are using a VIA Apollo Pro 133A motherboard, did you install the VIA Service Pack 4.43 prior to installing the sound card drivers?

I installed this: via-4in1-443v-63160adabfe43125550176

from here: https://theretroweb.com/motherboards/s/aopen-ax34#driver

is that the service pack you are talking of?

Yes. That should be installed first prior to installing drivers for graphics cards and sound cards.

Dmetsys wrote on 2024-12-08, 23:18:

psaez wrote on 2024-12-08, 21:41:

I installed this: via-4in1-443v-63160adabfe43125550176 […]
Show full quote

Dmetsys wrote on 2024-12-08, 20:17:

Seeing that you are using a VIA Apollo Pro 133A motherboard, did you install the VIA Service Pack 4.43 prior to installing the sound card drivers?

I installed this: via-4in1-443v-63160adabfe43125550176

from here: https://theretroweb.com/motherboards/s/aopen-ax34#driver

is that the service pack you are talking of?

Yes. That should be installed first prior to installing drivers for graphics cards and sound cards.

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled windows 98 SE with the last bios, and the problem persisted.

Any idea how to solve this?

psaez wrote on 2025-02-02, 21:36:

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled window […]
Show full quote

Dmetsys wrote on 2024-12-08, 23:18:

psaez wrote on 2024-12-08, 21:41:

I installed this: via-4in1-443v-63160adabfe43125550176

from here: https://theretroweb.com/motherboards/s/aopen-ax34#driver

is that the service pack you are talking of?

Yes. That should be installed first prior to installing drivers for graphics cards and sound cards.

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled windows 98 SE with the last bios, and the problem persisted.

Any idea how to solve this?

Do you have Plug and Play on or off in the BIOS?

OVERK|LL wrote on 2025-02-02, 21:41:

psaez wrote on 2025-02-02, 21:36:

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled window […]
Show full quote

Dmetsys wrote on 2024-12-08, 23:18:

Yes. That should be installed first prior to installing drivers for graphics cards and sound cards.

rasz_pl wrote on 2024-12-08, 16:12:

This is most likely caused by broken bios ACPI tables, those are responsible for resources. Win95 probably ignores those 😀
You can try updating bios, but it might be unsolvable without manually fixing resource allocation and editing bios - hardcore.

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled windows 98 SE with the last bios, and the problem persisted.

Any idea how to solve this?

Do you have Plug and Play on or off in the BIOS?

I'm not there now, I go to that place once each 2 weeks. If I can remember correctly, yes, it was ON in the BIOS. How can that affect? what should I try when I go there?

psaez wrote on 2025-02-03, 10:11:

OVERK|LL wrote on 2025-02-02, 21:41:

psaez wrote on 2025-02-02, 21:36:

Hey guys, I finally updated BIOs to last version, 2004 version, and the issue persisted. I even formatted and reinstalled windows 98 SE with the last bios, and the problem persisted.

Any idea how to solve this?

Do you have Plug and Play on or off in the BIOS?

I'm not there now, I go to that place once each 2 weeks. If I can remember correctly, yes, it was ON in the BIOS. How can that affect? what should I try when I go there?

When it's on, Windows is expected to manage resources and sometimes it doesn't do a very good job. Turning it off has the BIOS manage it, which can often fix errors such as the one you are experiencing.

OVERK|LL wrote on 2025-02-03, 13:22:

psaez wrote on 2025-02-03, 10:11:

OVERK|LL wrote on 2025-02-02, 21:41:

Do you have Plug and Play on or off in the BIOS?

I'm not there now, I go to that place once each 2 weeks. If I can remember correctly, yes, it was ON in the BIOS. How can that affect? what should I try when I go there?

When it's on, Windows is expected to manage resources and sometimes it doesn't do a very good job. Turning it off has the BIOS manage it, which can often fix errors such as the one you are experiencing.

that machine has a multiboot with win3.11, win95, win98se and winxp

disabling it seems to be a bad idea

psaez wrote on 2025-02-04, 15:06:

OVERK|LL wrote on 2025-02-03, 13:22:

psaez wrote on 2025-02-03, 10:11:

I'm not there now, I go to that place once each 2 weeks. If I can remember correctly, yes, it was ON in the BIOS. How can that affect? what should I try when I go there?

When it's on, Windows is expected to manage resources and sometimes it doesn't do a very good job. Turning it off has the BIOS manage it, which can often fix errors such as the one you are experiencing.

that machine has a multiboot with win3.11, win95, win98se and winxp

disabling it seems to be a bad idea

Given that list of OS's, it sounds like it's probably a good idea to turn it off. You can always turn it back on, but 3.11 doesn't support it.