VCOND(03) error when in DOS

I'm constently getting the following blue-scree error when I'm trying to
launch a particular Win32 program in a DOS window:

"File Name: VCOND(03) + 00002409 Error: 0E : 0028 : C02C737D"

I am not sure what I did to precipitate this problem. I can open an MSDOS
window and do other "DOS" things and run other programs just fine. But one
particular program seems to keep causing the error. I have since replaced
the original program with a newer verion and tried running another copy;
same problem.

Any ideas?

Ogg:

Sounds like a Windows 95 fatal exception error and probably is related to a
missing VXD file in your mentioned program.
The fix can be tricky and is not guaranteed.
I will leave it for someone more experienced, to come up with the proper
solution, if he would be so kind.

Harry.


"Ogg" wrote in message
...
I'm constently getting the following blue-scree error when I'm trying to
launch a particular Win32 program in a DOS window:

"File Name: VCOND(03) + 00002409 Error: 0E : 0028 : C02C737D"

I am not sure what I did to precipitate this problem. I can open an MSDOS
window and do other "DOS" things and run other programs just fine. But one
particular program seems to keep causing the error. I have since replaced
the original program with a newer verion and tried running another copy;
same problem.

Any ideas?

The VCOND.VXD is described as a "Virtual Device Driver" which could be
associated with almost anything g but probably hardware. The file *may* be
damaged/corrupted but unlikely - however a fresh copy can be extracted from
the WIN_20.CAB and confirmed or replaced if necessary. NB confirm that it is
the correct WinMe version (25,759 bytes 08 Jun 2000 @ 17:00:00)

But the OP has already tried that! - I only put it in for completeness g

Ogg doesn't say what the DOS program actually does (requires) - Sound,
Graphics, Modem, etc. - even USB devices - which could give a clue.

VCOND.VXD would normally get 'absorbed' into VMM32.VXD during setup (or
hardware detection - plug and play) even checking for stuff in the BIOS
(Legacy devices?)

However, it might be worth looking in Device Manager - first in Normal
Mode - for any conflicts (Yellow question/exclamation marks). Then check
DevMan in Safe Mode for duplicated devices as well as above. The (03) in
VCOND(03) makes me suspicious. 'Remove' (delete) any/all duplicated devices
or yellow 'bangs' etc. and reboot to let WinMe re-detect hardware and
drivers. Any improvement?

If it turns out that this program will just not run thru' a DOS window in
WinMe (too old?), try it in Real Mode DOS using the WinMe Startup floppy
disk - but hardware drivers *may* be required - and that then *may* point
you in the direction of the problem.

Good luck

Mart


"webster72n" wrote in message
...

Ogg:

Sounds like a Windows 95 fatal exception error and probably is related to
a
missing VXD file in your mentioned program.
The fix can be tricky and is not guaranteed.
I will leave it for someone more experienced, to come up with the proper
solution, if he would be so kind.

Harry.


"Ogg" wrote in message
...
I'm constently getting the following blue-scree error when I'm trying to
launch a particular Win32 program in a DOS window:

"File Name: VCOND(03) + 00002409 Error: 0E : 0028 : C02C737D"

I am not sure what I did to precipitate this problem. I can open an
MSDOS
window and do other "DOS" things and run other programs just fine. But
one
particular program seems to keep causing the error. I have since
replaced
the original program with a newer verion and tried running another copy;
same problem.

Any ideas?

Hello, Mart!
You wrote on Mon, 11 Sep 2006 09:50:47 +0100:

M Ogg doesn't say what the DOS program actually does (requires) - Sound,
M Graphics, Modem, etc. - even USB devices - which could give a clue.

The program uses the internet to move some files back and forth. I've used
the program for years without a problem -but now suddenly the VCOND error
shows up.


M However, it might be worth looking in Device Manager - first in Normal
M Mode - for any conflicts (Yellow question/exclamation marks). Then check
M DevMan in Safe Mode for duplicated devices as well as above. The (03) in
M VCOND(03) makes me suspicious. 'Remove' (delete) any/all duplicated
M devices or yellow 'bangs' etc. and reboot to let WinMe re-detect
M hardware and drivers. Any improvement?

DevMan looks fine. No conflics, no warnings.


M If it turns out that this program will just not run thru' a DOS window
M in WinMe (too old?), try it in Real Mode DOS using the WinMe Startup
M floppy disk - but hardware drivers *may* be required - and that then
M *may* point you in the direction of the problem.

Hmmm... I won't be able to test the program in Real Mode DOS following a
WinMe startup via floppy. The program I need to use requires an internet
connection.

As a work-around, I'm running the program on a networked XP computer. Then
I am transferring the "results" to my WinME pc. Bleah.

Hello, webster72n!
You wrote on Sun, 10 Sep 2006 22:34:09 -0400:

w Sounds like a Windows 95 fatal exception error and probably is
w related to a missing VXD file in your mentioned program.
w The fix can be tricky and is not guaranteed.
w I will leave it for someone more experienced, to come up with the
w proper solution, if he would be so kind.

I know how to successfully rebuild the VMM32.VXD file; well.. I've only done
it on a Win98se pc.

Maybe it's time to retire WinME afterall.

Ogg, you say that your DOS program uses the internet - perhaps a
'Remove/Delete' of your modem and re-install may be worth a try.

OTOH - If no improvement, maybe a selective start-up, omitting one h/w
device at a time to see if you can pin-down the offender. Does your Modem
software package include a DOS driver? - just a thought.

Also, if the BSOD subsequently causes a scandisk on re-boot, a look in the
scandisk.log file might give a further clue. (Ignore FSInfoSector
errors/reports - they are caused by the 'incorrect' shutdown)

Mart



"Ogg" wrote in message
...
Hello, Mart!
You wrote on Mon, 11 Sep 2006 09:50:47 +0100:

M Ogg doesn't say what the DOS program actually does (requires) - Sound,
M Graphics, Modem, etc. - even USB devices - which could give a clue.

The program uses the internet to move some files back and forth. I've
used
the program for years without a problem -but now suddenly the VCOND error
shows up.


M However, it might be worth looking in Device Manager - first in Normal
M Mode - for any conflicts (Yellow question/exclamation marks). Then
check
M DevMan in Safe Mode for duplicated devices as well as above. The (03)
in
M VCOND(03) makes me suspicious. 'Remove' (delete) any/all duplicated
M devices or yellow 'bangs' etc. and reboot to let WinMe re-detect
M hardware and drivers. Any improvement?

DevMan looks fine. No conflics, no warnings.


M If it turns out that this program will just not run thru' a DOS window
M in WinMe (too old?), try it in Real Mode DOS using the WinMe Startup
M floppy disk - but hardware drivers *may* be required - and that then
M *may* point you in the direction of the problem.

Hmmm... I won't be able to test the program in Real Mode DOS following a
WinMe startup via floppy. The program I need to use requires an internet
connection.

As a work-around, I'm running the program on a networked XP computer.
Then
I am transferring the "results" to my WinME pc. Bleah.

"Ogg" wrote in message
...
Hello, webster72n!
You wrote on Sun, 10 Sep 2006 22:34:09 -0400:

w Sounds like a Windows 95 fatal exception error and probably is
w related to a missing VXD file in your mentioned program.
w The fix can be tricky and is not guaranteed.
w I will leave it for someone more experienced, to come up with the
w proper solution, if he would be so kind.

I know how to successfully rebuild the VMM32.VXD file; well.. I've only
done
it on a Win98se pc.

Maybe it's time to retire WinME afterall.

No need to be so quick with the trigger, Ogg.
Mart just might get you there.
'See what happens.

Harry.

Ogg, from your initial post, I've ASS-U-ME-d that you'd already gone through
the System Restore/Scanreg /restore processes but as you'd stated that you'd
also re-installed a later version etc., I didn't bother suggesting that
route as it was likely to have been a waste of time. Too much water under
the bridge.

However, some further thoughts. I tried the MS KB and even Googling without
any useful leads, but Win98ResKit (there's no WinMe RK of course!) has some
further possible pointers. See :-
http://www.microsoft.com/technet/arc....mspx?mfr=true
and scroll down to the section called "Windows 98 Startup Process",
particularly where it refers to VMM32. Consequently system.ini might be
worth scrutinising.

You might still have an old system.ini (system.zzz) file floating around
(timed when your DOS program was working OK) which you may be able to
compare - maybe in an old RBxxx.CAB file perhaps.

Mart


"Mart" wrote in message
...
Ogg, you say that your DOS program uses the internet - perhaps a
'Remove/Delete' of your modem and re-install may be worth a try.

OTOH - If no improvement, maybe a selective start-up, omitting one h/w
device at a time to see if you can pin-down the offender. Does your Modem
software package include a DOS driver? - just a thought.

Also, if the BSOD subsequently causes a scandisk on re-boot, a look in the
scandisk.log file might give a further clue. (Ignore FSInfoSector
errors/reports - they are caused by the 'incorrect' shutdown)

Mart



"Ogg" wrote in message
...
Hello, Mart!
You wrote on Mon, 11 Sep 2006 09:50:47 +0100:

M Ogg doesn't say what the DOS program actually does (requires) - Sound,
M Graphics, Modem, etc. - even USB devices - which could give a clue.

The program uses the internet to move some files back and forth. I've
used
the program for years without a problem -but now suddenly the VCOND error
shows up.


M However, it might be worth looking in Device Manager - first in Normal
M Mode - for any conflicts (Yellow question/exclamation marks). Then
check
M DevMan in Safe Mode for duplicated devices as well as above. The (03)
in
M VCOND(03) makes me suspicious. 'Remove' (delete) any/all duplicated
M devices or yellow 'bangs' etc. and reboot to let WinMe re-detect
M hardware and drivers. Any improvement?

DevMan looks fine. No conflics, no warnings.


M If it turns out that this program will just not run thru' a DOS window
M in WinMe (too old?), try it in Real Mode DOS using the WinMe Startup
M floppy disk - but hardware drivers *may* be required - and that then
M *may* point you in the direction of the problem.

Hmmm... I won't be able to test the program in Real Mode DOS following a
WinMe startup via floppy. The program I need to use requires an internet
connection.

As a work-around, I'm running the program on a networked XP computer.
Then
I am transferring the "results" to my WinME pc. Bleah.