VOGONS

computer resets (driver conflict?) need service names

Topic actions

First post, by ab

Posted on 
User metadata

😲 I downloaded vdmsound awhile ago and after restarting to try it out i found that my computer could not get past the windows splash screens any further than the blue background for the login screen (login box does not appear before the computer resets itself).

i am using windows 2000 and luckily i had a free partition and i installed a fresh version of win2k there and can still use my computer though i want to save my old installation (reinstalling all the software i had would be a huge chore). I have tried to repair the installation using the windows disk to no avail. The installation refuses to boot in any mode (can you do a step by step in win2k, how?) even safe mode so i cannot uninstall vdmsound.

vdmsound was the only thing i installed and seeing as my other partition on the same drive boots fine and accesses info on the old partition and windows repairs and gives no errors i feel sure that vdmsound is the problem, i believe it is a driver conflict (it always resets at teh time as well). I have heard that emulating old joysticks can sometimes cause trouble. I have gone in with the repair disk and the emergency console to try and disable the culprit services, but have had to resort to guessing as i cant do step by step boot (i think) nor do any service descriptions mention vdmsound.

my question is what services vdmsound and the bundled software run under? particularly the joystick emulation.

has anyone else had this problem? anyone know a solution?

thanks in advance!

Reply 1 of 2, by MiniMax

Posted on 
User metadata
Rank Moderator
Rank
Moderator

I think you got caught by this NT-incompability (which seems to appky to 2K too??):

VDMSound 2.1.0 PUBLIC BETA KNOWN ISSUES […]
Show full quote

VDMSound 2.1.0 PUBLIC BETA
KNOWN ISSUES

  • PATH environment variable does not update correctly until Windows is restarted.
  • DiskWriter module causes an error in thread 0 ((null)).
  • OPL3 emulation may generate incorrect sound.
  • Old installations may not be correctly detected and removed.
  • XP themes cause graphical anomalies in the Launchpad.
  • Overwrites NT4 files with incompatible XP versions, causing NT4 to bluescreen on every subsequent reboot.

Sorry - I don't know which files, or how to restore them...

Edit: well, well, here they are: atl.dll and msvcrt.dll. From the same thread:

SaPu wrote:

DO NOT RUN the installer on NT 4.0, or you'll find than your system becomed unbootable.
The installer copies two files (atl.dll and msvcrt.dll) into the \winnt\system32 directories, but they are not compatible with the O.S., and the system crashes (blue screen of death) at every following reboot.
The copy is done immediately after the language selection: after this step, also if you cancel the installation, it's already too late !!!

But then we have this:

Nicht Sehr Gut wrote:

Originally posted by Unregistered is this safe to install on win2k pro?

Yes. NT4 is the only one that has a compatibility issue at the moment.



And this:

Thuderbird wrote:

I installed this on Win2K Pro SP4, rebooted, and now cannot log into the system (the login process keeps crashing, which takes the entire system down). I can't get into Safe Mode to undo this either. However, I can access the disk from another OS. Is there any way to undo what has happened to my system?

vladr wrote:
This is soooo foobar. :dead: The only possible explanation would be the MSVCRT & Co. DLL's. Snover has a list of all the DLLs […]
Show full quote

This is soooo foobar. 😵 The only possible explanation would be the MSVCRT & Co. DLL's. Snover has a list of all the DLLs that the 2.1.0 installer comes with, you can try replacing those with the Win2k SP4 DLL's.

Cheers,
V.

Thuderbird wrote:

I did a system repair with the Win2K CD and got the system back up and running. I think this set me back quite a bit in some spots though 😜. Better than reinstalling the entire OS at least.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 2 of 2, by Snover

Posted on 
User metadata
Rank l33t++
Rank
l33t++

The Windows 2000 and Windows XP drivers should be compatible with each-other. Maybe I just need to bloat up the installer some more, check for the correct OS and install different drivers if..
I don't know. People have tested this on Windows 2000 without a problem, though.

Yes, it’s my fault.

Go to top of page Go to top of page
Back to VDMSound General
Close window
Close window