VDMSound Problems, and ke386 \ VOGONS

VDMSound Problems, and ke386

Topic actions

First post, by Cidrick

Posted on 2003-06-30, 19:15

Cidrick Offline

Rank Newbie

Rank: Newbie
Posts: 5
Joined: 2003-06-19, 20:32

I'm trying to get Discworld up and running on my system but I'm running into some problems, but I'm fairly certain they're related to VDMSound. VDMSound is being weird on me - it used to work brilliantly but I guess something's wrong with it. I downloaded the Ms. Pac-Em "test" game and installed it. It runs decently without VDMSound, using just Windows XP sound emulation, but it freezes up when I try running it with VDMSound.

Doing a lot of research on VOGONS has led me to believe I have some culprit .sys file with the dreaded "ke386" in it. I got the handy Files Search Assistant and did some digging, and this was its output:

http://www.msu.edu/~renfrowm/report.htm

So I have a number of files containing our friend ke386, but I'll be damned if I know which one is actually causing my problem. The files are

mbmiodrvr.sys (in my system32 directory)
videoprt.sys (In numerous directories)
entech.sys (system32\drivers)
ntiowp.sys (system32\drivers)
dlportio.sys (In my GBA Flash Linker Directory)

Any ideas? System specs:

ABIT KT7A Motherboard w/1.2ghz T-Bird
512mb PC133 RAM
Sound Blaster Audigy MP3+
Windows XP
Geforce 4 Ti4400 (Using 44.03 Detonators)

Reply 1 of 5, by MajorGrubert

Posted on 2003-06-30, 20:26

MajorGrubert Offline

Rank Member

Rank: Member
Posts: 208
Joined: 2002-11-18, 14:23
Location: Brazil

Cidrick wrote:
mbmiodrvr.sys (in my system32 directory) videoprt.sys (In numerous directories) entech.sys (system32\drivers) ntiowp.sys (system […]
Show full quote

mbmiodrvr.sys (in my system32 directory)
videoprt.sys (In numerous directories)
entech.sys (system32\drivers)
ntiowp.sys (system32\drivers)
dlportio.sys (In my GBA Flash Linker Directory)

We can safely confirm that videoprt.sys is the standard Windows XP video port driver, used by all display drivers and it dos not interfere with VDMSound. He's one of the good guys, so leave it untouched.

Given the output you provided and the file names, I believe that two files are the prime suspects:

mbmiodrvr.sys looks like a low-level driver for some sort of motherboard/CPU monitor. Do you have any kind of hardware monitor, temperature monitor or hardware diagnostic software installed?
ntiowp.sys is also used by some diagnostic software (I had this one some time ago but cannot name the exact program that installed it).

To make sure that these two are not loaded, you should stop all hardware monitoring and/or diagnostic utilities you have running as the first step. If it doesn't work, rename these two files and reboot, then see if you can get VDMSound to work and let us know the results.

Finally, the last two ones:

entech.sys looks like a video driver (it has some reference to videoprt.sys), although it should not call any kernel function. Let's leave it at the end of the list.
dlportio.sys assuming GBA Flash Linker is somehow related to a specific hardware, I believe it's safe to believe this driver os only loaded when you run its software. Let's keep it quiet for now.

Regards,

Major Grubert

Athlon 64 3200+/Asus K8V-X/1GB DDR400/GeForce FX 5700/SB Live! 5.1

Reply 2 of 5, by Cidrick

Posted on 2003-06-30, 22:22

Cidrick Offline

Rank Newbie

Rank: Newbie
Posts: 5
Joined: 2003-06-19, 20:32

MajorGrubert wrote:

mbmiodrvr.sys looks like a low-level driver for some sort of motherboard/CPU monitor. Do you have any kind of hardware monitor, temperature monitor or hardware diagnostic software installed?

ntiowp.sys is also used by some diagnostic software (I had this one some time ago but cannot name the exact program that installed it).

I forgot to mention, that first one says mbm - I use Motherboard Monitor to monitor my CPU temps, so that's probably what that is. But I'll give it a shot and let you guys know whats up.

Reply 3 of 5, by Cidrick

Posted on 2003-07-01, 02:01

Cidrick Offline

Rank Newbie

Rank: Newbie
Posts: 5
Joined: 2003-06-19, 20:32

Okay, VDMSound works again. I renamed both the mbmiodrvr.sys and ntiowp.sys to something else and rebooted. Lo and behold, VDMSound likes me again. Thanks for your help.

Reply 4 of 5, by vladr

Posted on 2003-07-01, 04:38

vladr Offline

Rank Oldbie

Rank: Oldbie
Posts: 894
Joined: 2002-06-30, 20:09
Location: Montréal, QC, CAN

How old is your version of MBM? The people at MBM made it VDMSound-friendly quite a while ago (at least one year), so I'm surprised...

Reply 5 of 5, by Cidrick

Posted on 2003-07-01, 15:45

Cidrick Offline

Rank Newbie

Rank: Newbie
Posts: 5
Joined: 2003-06-19, 20:32

I was using MBM 5.1.9.1, which looks like it's from June of last year. Silly me. Time to upgrade.

Go to top of page Go to top of page

Back to VDMSound General