Hi,
I want one of my .exe programs to run with vdms when I double click it--- NOT when I right click and select --run with vdms -- I really need to do this because another program targets the .exe file and I cant enable sound otherwise -- PLEASE HELP
Instead of selecting "Run with VDMSound" I need to be able to launch an executable program with VDMSound enabled from a Shortcut.
I want to run an executable file with VDMSound enabled but I want to launch the program from a shortcut I have created and placed on My Desktop. Problem is that clicking the shortcut launches the executable but doesnt enable VDMSound because I didnt right click the executable and select "Run with VDMS". I am thinking I should be able to edit the command line on my shortcut to launch the executable with VDMSound. Or Change the Command line on the executable file itself so that it always launches with VDMSound. PLEASE HELP
Use the LaunchPad and create a LaunchPad shortcut for the program. The LaunchPad is linked in the posting guidelines stuck to the top of each forum.
Another option is to create a batch file containing both a reference to the program you want to run and the VDMS dosdrv program and then creating a shortcut to it. This methods clunkier than the first but it gets the job done.
Launchpad is the ideal solution.
With the batch file solution, remember that DOSDRV must be loaded first. 😀
"I see a little silhouette-o of a man, Scaramouche, Scaramouche, will you
do the Fandango!" - Queen
Stiletto
wrote:With the batch file solution, remember that DOSDRV must be loaded first. 😀
Actually, I discovered through experimentation that in some cases (particularly with NOLFB) that dosdrv is best loaded last. Don't ask me why but I noticed that I got exactly the same hanging up business (and by that I mean the symptoms, the cause may be entirely different. I hardly see nolfb interfering with VDMS's CLI/POPF emulation) I mentioned in the my thread about the LaunchPad when I loaded dosdrv before nolfb. It disappeared if nolfb was ran before dosdrv. Another thing I noticed, and again I'm not entirely sure why, was that, if nolfb is loaded as part of the Autoexec section of the Launchpad performance was slower than loading it through a batch file (adding it to the regular autoexec.vdms files, presumably for execution as part of the regular 'Run with VDMS' option, didn't work but I'm still investigating this).
wrote:Actually, I discovered through experimentation that in some cases (particularly with NOLFB) that dosdrv is best loaded last. Don't ask me why but I noticed that I got exactly the same hanging up business (and by that I mean the symptoms, the cause may be entirely different. I hardly see nolfb interfering with VDMS's CLI/POPF emulation) I mentioned in the my thread about the LaunchPad when I loaded dosdrv before nolfb. It disappeared if nolfb was ran before dosdrv. Another thing I noticed, and again I'm not entirely sure why, was that, if nolfb is loaded as part of the Autoexec section of the Launchpad performance was slower than loading it through a batch file (adding it to the regular autoexec.vdms files, presumably for execution as part of the regular 'Run with VDMS' option, didn't work but I'm still investigating this).
Hm... continue talking to Vlad about it in the other thread about this you started. In any case, you meant load it last BEFORE the application, right? Like:
nolfb
dosdrv
duke3d
Versus
dosdrv
nolfb
duke3d.
(And definitely not:
nolfb
duke3d
dosdrv
or anything stupid like that!)
That's kinda weird. Continue testing. But this guy wasn't asking about NOLFB. And I still recommend LaunchPad.
You might be able to regedit your way to automatically using VDMSound on double-click for a legacy program, but I won't tell you how and I won't be responsible if you totally screw up your .EXE associations.
Yes, it’s my fault.
Assuming same poster:
YES YES YES ---- That did it :) So Happy Thank you :) […]
YES YES YES ---- That did it 😀 So Happy
Thank you 😀----- Original Message -----
From: "Vlad ROMASCANU"
To: "Brian Bothwell"
Sent: Wednesday, November 13, 2002 8:22 PM
Subject: Re: Always launch VDMSound on Executable> If nrp_all.exe has no idea bout VDMSound then your solution may be simple:
> edit C:\WINNT\SYSTEM32\AUTOEXEC.NT (C:\WINNT may be C:\WINDOWS for you)
and
> add DOSDRV.EXE at the end of the file. This will load VDMSound for any
DOS
> exe that is run by double-clicking on it.
> V.
...and closing.
V.
