![]() ![]() I don't know how much use tit will be to you, but here is how the autoexec.bat, config.sys, and dosstart.bat files look on my PII 400 computer, which has Windows 98 and an SBLive.Ĭ:\PROGRA~1\CREATIVE\SBLIVE\DOSDRV\SBEINIT.COM Windows 98 doesn't normally even have a C:\DOS folder unless you create it manually yourself. You probably need different paths in the autoexec.bat and config.sys then. I've only used the DOS emulation on a computer with Windows 98, which is a LOT easier to configure. I'm afraid I don't have any first hand experience using SBLive DOS drivers under DOS 6.22. Check with the respective motherboard supplier for NMI compatibility. Until the motherboard fully supports NMI then the software emulation simply cannot operate. If you have a ALI/ASUS chipset/motherboard an updated BIOS is now available which supports NMI, check out for this patch. Some manufacturers of motherboards state that they do support NMI but when tested and used (like with the SB128/Live) they don't work. You will need to check with the motherboard manufacturer and ask them does their motherboard fully support NMI (Non Maskable Interrupts) and if it does how to enable them. One limitation other than the settings can also be your motherboardĬonfiguration and compatibility. ![]() Don't be scared of experimenting with different values under DOS, you're unlikely to be using other devices that would normal conflict under Windows. Changing the IRQ to 10 did wonders for me, I have no idea why because there's nothing on the default of 5 that should be conflicting with it. In your autoexec.bat, reboot into "pure" DOS and give it a go. Now all you need to do is make sure you have the line Sbeset should also automatically set your blaster environment variable. That's an *upper case* letter "I" followed by a one and zero to set the IRQ to ten, then a lower case "w" followed by a zero to tell it to ignore your Windows configuration. You'll need the sbeset command that should come with the dos drivers, I'm assuming it's in your c:\sblive\dosdrv directory. ![]() An alternative scenario was worked out by Shifty for those who are still having difficulties even with the previous procedure: Īn alternative scenario was worked out by Shifty for those who are still having difficulties even with the previous procedure: SBESET.EXE, or modify your BIOS settings following the instructionsĪnd toward the end of the "sblive in dos" file in the "howto" folder there is "An alternative scenario was worked out by Shifty for those who are still having difficulties" with a suggestion for sbeset. If you experience any problems such as no sound, interrupt conflicts or else, try to modify the settings for your driver using ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |