Unable to complete DOS backup: Program can't locate "VDM IPX/SPX"

I'm running Win2K Pro. An older program of mine was unable to complete a DOS backup which is built into the program because it couldn't locate VDM IPX/SPX. It had been working OK for years, until recently. I'm suspicious that it might have something to do with my "messing around" with my Services files -- like maybe I disabled a Service that it needs -- but, which one? Your ideas or suggestions would be appreciated.

Jim

 

Hmmmm.

VDM - virtual DOS machine which is a thingy your OS builds in a protected section of memory to look like a complete DOS PC to programs that need to see one of those.

IPX/SPX - older Novell network protocol and if your backup program uses BTrieve, it will want to see that.

Locate your autoexec.nt file (should be in \system32) and copy the contents then paste it here.

 

@echo off

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
REM different startup file is specified in an application's PIF.

REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

REM Install DPMI support
lh %SystemRoot%\system32\dosx
REM Install network redirector
lh %SystemRoot%\system32\nw16
lh %SystemRoot%\system32\vwipxspx

I see it there but don't know what it means or what to do with it. Look forward to your suggestion. Jim

 

Lets see if things will run without those trying to load. If no help (or worse than now) it's easy enough to undo.

You have
REM Install network redirector
lh %SystemRoot%\system32\nw16
lh %SystemRoot%\system32\vwipxspx

You want
REM Install network redirector
REM lh %SystemRoot%\system32\nw16
REM lh %SystemRoot%\system32\vwipxspx

which will stop the novell pieces from trying to load. If the backup app is BTrieve based, it will bomb even worse and you may have to search around for those files since I'm guessing they are no longer located in \system32 or else some other piece needed to load first and isn't.

Anyway, for now try REMing out the two additional lines.

 

It worked!

Thanks for the suggestion. I rem'd out the lines you suggested, rebooted and the program didn't complain about not finding the VDM. I appreciate your help.

Jim