Win95: VSGLX16.386 Initialization Error

wiz...@maui.net

unread,

Mar 17, 1997, 3:00:00 AM3/17/97

to

After someone else attempted to load Soundblaster drivers in Win95,
I removed all the references I could find to those drivers and loaded
Win95's sound drivers for the Blaster card.

All is working fine with the card and sound, but as Win95 starts I
get the message, "VSGLX16.386 Initialization Error. VSGLX16.386 was
unable to locate the audio board hardware."

Where do I look for the call which is causing this message so I may
remove it?

Thanks in advance,

Ken
Wiz...@maui.net

David Elliott

unread,

Mar 17, 1997, 3:00:00 AM3/17/97

to

I have pretty much the same problem. I get a message about VSGLX16.386 being
unable to load after trying to get an Aztech soundcard to work. Uninstalling
the card (physically and/or through software) doesn't fix it. I got the same
message 3 times in a row, then able to login normally. After deleting a
reference in the Registry to the file, I get the same message only twice.

I grepped the hard-disk for the text "vsglx16" and found it contained in
mm16.drv (I think) but since this driver wasn't explictly loaded anywhere I
still can't fix the problem.

Removing all sound drivers didn't fix it. Reinstalling random soundcard
drivers didn't fix it. Replacing vsglx16.386 with a 0 byte file didn't fix it,
replacing it with another (random) *.386 file didn't fix it. In fact all of
these ended up giving the same errors as before.

I'd quite like to fix this *and* get the soundcard to work too.

(If you get any email replies, please forward.)

David....@shu.ac.uk
Computer Services, Sheffield Hallam University, Sheffield, UK, S10 2BP
(+44) 114 253 2532

Paul Coddington

unread,

Mar 17, 1997, 3:00:00 AM3/17/97

to

David Elliott <David....@shu.ac.uk> wrote in article
<5gja5a$1...@redwood.shu.ac.uk>...

| I have pretty much the same problem. I get a message about VSGLX16.386
being
| unable to load after trying to get an Aztech soundcard to work.
Uninstalling
| the card (physically and/or through software) doesn't fix it. I got the
same
| message 3 times in a row, then able to login normally. After deleting a
| reference in the Registry to the file, I get the same message only twice.

*.386 files are often installed by applications to the \Windows\System
folder and a reference is made to them in SYSTEM.INI. Windows attempts to
load these files each time it starts and produces an error message when it
can not find them. If the file is referenced in SYSTEM.INI and does not
exist, try removing the line which contains the reference.

--
PAUL CODDINGTON
pa...@mail.act.apana.org.au
http://www.geocities.com/athens/2488

PEC Pink Axolotl is a non-sensical disorganisation...

Ian Pollard

unread,

Mar 18, 1997, 3:00:00 AM3/18/97

to

On Mon, 17 Mar 1997 04:35:17 GMT, wiz...@maui.net wrote:

<snip>

> Where do I look for the call which is causing this message so I may
>remove it?
>
> Thanks in advance,
>
> Ken
> Wiz...@maui.net

I had a similar problem and traced it to the system.ini file. I
checked on the original soundcard floppy for an install file and
traced the names of the drivers it installed. I then commented out all
of the lines in system.ini [drivers] section which referred to these
drivers and, Hey Presto!! the vsglx16.386 message disappeared. It is
evident that vsglx16.386 is called from another one of those 16 bit
drivers. If you are still having problems, copy me the [drivers]
section from your system.ini and I will attempt to identify the
relevant lines if I can remember them.

Regards

Ian
--
***************************************************
Ian Pollard - Bellshill - Northumberland - UK
<->< e-mail: pol...@bigfoot.com
Despite the Bigfoot, It's a U-Net Address!!
***************************************************