From:	jdashiel AT eagle1 DOT eaglenet DOT com
Date:	Tue, 25 Feb 1997 05:34:00 -0500 (EST)
To:	opendos AT mail DOT tacoma DOT net
Cc:	chuckh AT taconic DOT net
Subject:	[opendos] provox hard drives and opendos great news!
Message-Id:	<Pine.NXT.3.95.970225051700.10418A-100000@eagle1>
Mime-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

Hi Chuck,

I have provox running under opendos on my hard drive where the boot
process
mostly happened with opendos.  I say mostly for the reason that
it was necessary to create a dconfig.sys file and
put the lines:
device=c:\dos\himem.sys
device=c:\dos\emm386.exe noems
dos=high,umb
device=c:\dos\ramdrive.sys 1024 /e

into it and have them separated out from config.sys.
Evidently the problem really is himem.sys;
emm386.exe and likely ramdrive.sys since these
three must go together and won't mix and match with
other systems.
Those files were the msdos versions for now until caldera and developers
debugs the mess borland and microsoft left behind.
Now in autoexec.bat, I don't know why this is but opendos won't
have any part of provox in config.sys so I put it
all into autoexec.bat where I wanted it to start talking.
c:\provox
c:\provox\pv restore
got that job done.
I ran setup and got the system set up but may end up disabling
diskmap resource.  Have to study that one.
If anyone wants to run edit and have bios writing
edit filename.txt /d
will get that done too.  That order is required if a user
types a file name.
Finally, tinytalk also works with opendos as well.
I succeeded with tinytalk and figured provox ought to
have a shot at it too and scored.  This computer is running
under opendos and off its hard disk as I write this e-mail too.
This solution works for ami bios machines of a 386 flavor
pre-flexbios.  Others mileage is likely to vary.  If any of the membership
could use a copy of my relevant files, please write and let me know
and I'll get them out as soon as this e-mail backlog is cleared.
hth.



jude <jdashiel AT eagle1 DOT eaglenet DOT com>

- Raw text -