VOGONS


First post, by RogueTrip2012

User metadata
Rank Oldbie
Rank
Oldbie

Using a SBLive! with 3.0 driver and supplement patch from vogons. I recently installed the Dos driver again so it can be used under dos and now Win98SE.

I was building the config and autoexec files to my liking but also created a batch file which allows me to enable/disable the config,autoexec by renaming to *.fff or back to original. Got that working but when disabling the files I noticed a new autoexec is written with SBLive! settings during bootup.

Reading further I seen renaming the ctsyn16.drv would stop the autoexec from being built on every boot. This does work but breaks windows dos gaming.

Example is carmageddon 1/splat pack. I usually play it in windows under dos and works for a race or two then crashes. Now disabling the ctsyn16.drv will cause carmageddon to not even start in windows.

The only reason I installed the dos drivers was to try to play carmageddon under pure dos but also have issues doing that as under dos it won't start and just has a black screen.

So is there another way to disable the autoexec from being built each boot? If not I'll probably just uninstall the dos drivers and deal with the eventual crashing of carmageddon under windows dos.

Under Pure dos I think its a voodoo 3 thing even using the patches. Carma.exe runs. Voodo2s.exe/Voodo2c.exe/Carmav.exe will always fail though. Using a dos4gw of 2.01a doesn't help either.

TIA!!

> W98SE . P3 1.4S . 512MB . Q.FX3K . SB Live! . 64GB SSD
>WXP/W8.1 . AMD 960T . 8GB . GTX285 . SB X-Fi . 128GB SSD
> Win XI . i7 12700k . 32GB . GTX1070TI . 512GB NVME

Reply 1 of 5, by Gemini000

User metadata
Rank l33t
Rank
l33t

I ran into this problem too back in 2000 on a P3 machine. If I recall, my solution was to turn the autoexec into a goto label nightmare so that the SB drivers could put their extra lines in the spot they wanted to, and I would then just jump around them as necessary.

This was after my first thought, just make the autoexec file read-only. Surprisingly, the SB drivers DO NOT honour read-only file attributes. o_O

I think that technically makes them evil. >_>;

--- Kris Asick (Gemini)
--- Pixelmusement Website: www.pixelships.com
--- Ancient DOS Games Webshow: www.pixelships.com/adg

Reply 2 of 5, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

I think they would call it userfriendly 😉

Water flows down the stream
How to ask questions the smart way!

Reply 3 of 5, by 7cjbill2

User metadata
Rank Member
Rank
Member

I got so frustrated with my SB!Live card that it got removed and exiled it to the island of misfit cards. Now I know why I jumped straight from my SB16ASP to my TB Montego back in the mid/late-90's.

Will pay $$$ for:

caching ISA I/O-IDE controller

PM me for my list of trade-ables...

Reply 4 of 5, by leileilol

User metadata
Rank l33t++
Rank
l33t++

This problem is even more aggravating in Windows ME that it eats your autoexec.bat every boot as well! DOS game compatibility, SB Live with Windows ME is just a terrible combination. Back in 2000 I was genuinely p-i-s-s-e-d about this problem. It even made me question why I had gotten a SBLive...

apsosig.png
long live PCem

Reply 5 of 5, by TheMAN

User metadata
Rank Oldbie
Rank
Oldbie

maybe someone can hack the dll to make it go away... or at least change it so that it updates some unoffending file 😉