DOS errors while running 95 in VirtualBox

[kleefarr]

I have set up VirtualBox with a Windows 95 guest OS in.
When starting I get the following 'Can't find files' errors..

nwredir.vxd
nscl.vxd
vredir.vxd
ndis.vxd
ndis2sup.vxd
vnetbios.vxd

Although I can bypass these and stop them from occurring again just by
saving the machine state when closing, is there a way to correct the problem?

My DOS problem is, when running a DOS program called VMS I get the following
errors and it won't load..

ERROR DBFNTX/1001 O_PEN ERROR VUTI71.DBF (DOS ERROR 5)

Does anyone have any ideas on a fix for this please?

TIA , Kevin

[Tim Meddick]

kleefarr,

I can't really help on the second problem.

However, concerning your virtual Win95 installation : you must have installed win95
from "somewhere" - can you not run the command :

extract /a WIN95_02.CAB nwredir.vxd /l c:\windows\system

...from where the Win95 cabinet [.cab] files are? Plus, here I have made the
example for [nwredir.vxd] but you would need to repeat it for all the missing files.

This should stop the error messages on bootup by replacing the missing files into the
[system] directory, by extracting them from the Win95 cabinet setup files.

==

Cheers, Tim Meddick, Peckham, London. :-)

"kleefarr" <klee...@discussions.microsoft.com> wrote in message
news:7D0A79F9-7A95-42CE...@microsoft.com...

[kleefarr]

Tim,

Thanks for the reply. Shame you don't have a fix for the second problem as
that is the more important of the two.

There was a slight typo for it in the first post.. no _ between O and P.

ERROR DBFNTX/1001 OPEN ERROR VUTI71.DBF (DOS ERROR 5)

Don't know if that changes anything. I'm going to try an other install of
DOS.5 and see if there is ay change.

I'll check out the EXTRACT command as well.

Cheers.

"Tim Meddick" wrote:

> kleefarr,
>
> I can't really help on the second problem.
>
> However, concerning your virtual Win95 installation : you must have installed win95
> from "somewhere" - can you not run the command :
>
> extract /a WIN95_02.CAB nwredir.vxd /l c:\windows\system
>

> ....from where the Win95 cabinet [.cab] files are? Plus, here I have made the

> example for [nwredir.vxd] but you would need to repeat it for all the missing files.
>
> This should stop the error messages on bootup by replacing the missing files into the
> [system] directory, by extracting them from the Win95 cabinet setup files.
>
> ==
>
> Cheers, Tim Meddick, Peckham, London. :-)
>
>
>
>
> "kleefarr" <klee...@discussions.microsoft.com> wrote in message
> news:7D0A79F9-7A95-42CE...@microsoft.com...
> >I have set up VirtualBox with a Windows 95 guest OS in.
> > When starting I get the following 'Can't find files' errors..
> >
> > nwredir.vxd
> > nscl.vxd
> > vredir.vxd
> > ndis.vxd
> > ndis2sup.vxd
> > vnetbios.vxd
> >
> > Although I can bypass these and stop them from occurring again just by
> > saving the machine state when closing, is there a way to correct the problem?
> >
> > My DOS problem is, when running a DOS program called VMS I get the following
> > errors and it won't load..
> >
> > ERROR DBFNTX/1001 O_PEN ERROR VUTI71.DBF (DOS ERROR 5)
> >
> > Does anyone have any ideas on a fix for this please?
> >
> > TIA , Kevin
>

> .
>

[Tim Meddick]

About that 2nd problem : I am assuming that the error message - ERROR DBFNTX/1001
OPEN ERROR VUTI71.DBF (DOS ERROR 5) was a Windows (Win95) error message you got on
trying to run your VMS program.

I don't know (have no idea) what your "VMS" program does or is about but suppose that
you were running it in a dos-box under your virtual Win95 installation.

I think you will find that the "DOS ERROR 5" part of it refers to a specific error
code and not to a DOS Version number.

In case you didn't realise Win95 CANNOT run on top of anything but DOS 7 (including
7.1) - installing DOS 5 into the root of a Win95 installation will make Windows
unusable.

However, if you want to try your program under different DOS versions you can do this
on a Virtual PC.

Download the relevant bootdisk creator (.exe) files from the list below :

For DOS 5.0 http://www.shrum.net/files/boot500.exe

For DOS 6.0 http://www.shrum.net/files/boot600.exe

For DOS 6.21 http://1gighost.com/ed/jamiephiladelphia/boot621.exe

For DOS 6.22 http://www.ulink.net/crossroads/computers/sli/boot622.exe

==

Cheers, Tim Meddick, Peckham, London. :-)

"kleefarr" <klee...@discussions.microsoft.com> wrote in message

news:08D3150F-3AD5-4562...@microsoft.com...

[kleefarr]

I'm giving up on running the DOS program in a Windows 95 Virtual Machine.
Will now look for options of just running DOS on Windows 7 64bit.

[Tim Meddick]

You cannot "Run" DOS on Windows 7 64bit - the most you can do is either;

1). start a Command Prompt (cmd.exe) DOS EMULATION under protected mode Windows 7.
This is not REAL DOS by any means but an emulated DOS environment and LOADS of older
DOS programs will NOT run properly under it.

2). start Real-Mode DOS in a virtual PC under Windows 7
This IS real-mode DOS but as you know - running in a virtual environment.

==

Cheers, Tim Meddick, Peckham, London. :-)

"kleefarr" <klee...@discussions.microsoft.com> wrote in message

news:0791C53F-1362-4E59...@microsoft.com...

[kleefarr]

Gentlemen (and ladies)

Progress has been made.
I reverted to Virtualbox, as this is what was giving the most promising
results for everything tired so far.

I discovered that the error DBFNTX/1001 related to the files that were
trying to accessed were marked as READ ONLY. The subsequent error of course
related to the file that was trying to be opened. So, after unchecking the
READ ONLY box for that file resulted in a new file being displayed as an
error. Eventually the VMS program has started, but there are lots of other
files that will need to be accessed that are marked as READ ONLY. So, I
slowly going through the files, highlighting about 50 at a time and
unchecking the READ ONLY box. However, there are thousands of these files.
Is there a quicker way to uncheck the READ ONLY box?

My only other problem is the display size of Virtualbox. Would I be correct
in assuming that in order to increase the size of the VB display, I will have
to find drivers for the Win 95 display adapter and monitor?

Happier so far.

Kevin

[Tim Meddick]

In virtually all DOS environments (after dos 5.0) you can use the command :

attrib /s -r *.*

The [/s] "switch", before the [-r] instruction to remove the read-only bit, makes
this command perform on ALL files in the current directory *and* ALL sub-directories,
starting from the current one.

I even use it in XP (from a Command Prompt, of course) because it's a hell of a sight
quicker when you've got a lot of files in a lot of folders that you want attributes
changing on.

Type the command :

attrib /?

...for help (on usage) for the ATTRIB command.

You can also use the "wildcards" (* and ?) with the ATTRIB command to only process,
say, files with a given extension, or that start with a certain letter...

==

Cheers, Tim Meddick, Peckham, London. :-)

"kleefarr" <klee...@discussions.microsoft.com> wrote in message

news:9F69B997-C234-4095...@microsoft.com...

[kleefarr]

Files sorted. All Read Only unchecked. Was simply a case of highlighting them
all and then unchecking the Read Only box and waiting for the system to run
through them all.

Anyone know what the following means?

"Error: TERM\0 Print error" which comes up when the program starts.