Hoorah! and a nice unified installer, great stuff 😀

Sweet 😀

Why are there some options disabled by default in the installer? A full binary install is only 1.9 Mo...

Yiipee.

Btw, is this the latest SAPUCDEX version? I've got 1.0.0.5 already installed and running, but I can't figure out the revision number of the new one included in the package.

It's an uberl33t secret version that SaPu sent only to me. But I think it's 1.0.0.5. 😉

wow after years of waitning a new version....
Thanks!

Oh blah, it hasn't been years...
*looks at the VDMSound page*

Okay, years then! 😉

yep, years and still no new official version 😀

The Run With VDMS option (without musical note) has just disappeared. Is this normal?

Yes. That behaviour is intended.

I don't get it. It was quite useful when you have something already configured. Maybe for newbies is better, though. Less confusing.

very strange and I can't really say it happened after the installation of vdms. But %systemroot% was suddenly not pointing at anything and I had to enter a variable for it...

Dominus wrote:

very strange and I can't really say it happened after the installation of vdms. But %systemroot% was suddenly not pointing at anything and I had to enter a variable for it...

I have the same problem!!!!

Regedit Before VDMS Install:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Wert 11
Name: Path
Typ: REG_EXPAND_SZ
Daten: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;

SET before Install:
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;

Regedit after Inastall:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Wert 11
Name: Path
Typ: REG_SZ
Daten: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;;C:\Programme\VDMSound

Set after Install:
Path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;;C:\Programme\VDMSound

My "laming" Workaround!
Problem REG_SZ versus REG_EXPAND_SZ
Started regedit
I made a new REG_EXPAND_SZ in directory
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
NAME "Path"
content: "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%VDMSPath%"

Exit regedit
Log off or boot your computer

READY

Here is the complete "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" and "SET" before/after Installing VDMSound!

I have WinXP Pro SP1!

so it was caused by vdms after all? By the installer at least...

Another minor thing I noriced: in the installer when you can choose what to install you get some help on hovering over each "thing" you can install. You don't get that when hovering above the help files.

@Dominus
YES!
But it is a minor bug and easy to fix:D

Snover wrote:

KNOWN ISSUES […]
Show full quote

KNOWN ISSUES

• PATH environment variable does not update correctly until Windows is restarted.
• PATH environment variable gets broken somehow in the install (paths are still in the variable but they are not checked when typing a command).

Originally posted by Snover KNOWN ISSUES

• PATH environment variable does not update correctly until Windows is restarted.

Doesn't the install specifically say to reboot?

[*]DiskWriter module causes an error in thread 0 ((null)).

Make sure you don't make the same goof I did when I first tried it: keep in mind you have to specify a *directory*, not file name. A new .wav file is generated whenever the game changes sound parameters (i.e. sample rate, mono/stereo, etc.) since you can only have one frequency/aurality /etc. per single .wav file.

Note that, in my tests, it was the AdLib module of DiskWriter that had the problems. It seems to happen almost sporadically for me. It would happen several times in a row, then it wouldn't. As soon as I'm ready to declare one AdLib choice as "safe", it would turn around and crash.

Here's basically what I found:
Auto-Detect -> Crashed most frequently
OPL3 --> Almost as frequent as Autodetect
Dual OPL2 --> Almost as frequent as OPL3
OPL2 ----> Almost never crashed

The most unusual thing I noticed was that these errors happened frequently under "XP Home", but almost never under "XP Pro" (Pro had exactly 1 crash after a LOT of testing).

[*]OPL3 emulation will occasionally cause VDMSound to crash.

I never had any crashes that I could link to use of OPL3 (not counting DiskWriter). My results were either silence or dreadful music. Fortunately, Vlad's new options for OPL emulation really help. With VDMSound 2.04, if your program used a single sound/music option; you always had to choose "SB Pro". Choosing "SB 16" would cause it to use OPL3 emulation. With version 2.10, you choose "SB 16", then go to the AdLib tab (under "Advanced") and manually choose OPL2 or Dual-OPL2. That should give you 16-bit audio while still giving you FM music.

[*]Old installations may not be correctly detected and removed.[/list]

Out of habit, I always remove an original program before installing an update (unless the original is required). It's a good habit to have.

One oddity I came across:
Was testing a reinstall of TombRaider and found that both the SETUP and game programs were locking up on me (oddly, SETUP only locks just as it's quitting). Removing the PopF fix enabled proper operation

Trivial thing, but if the "skins" of XP (Visual Themes, whatever...) are used it creates a graphic glitch on windows.

FIXED:

• PATH environment variable gets broken somehow in the install (paths are still in the variable but they are not checked when typing a command).
• No tooltip when mousing over "Optional Modules" or "Help Files".

thanks for the fixes. it is always good to have betas 😀

DiskWriter crash may or may not be related to certain antivirus software running according to Thierry D.

V.