Message-Id: <3.0.32.19970119202302.00692934@mail.wa.net>
Date: Sun, 19 Jan 1997 20:23:05 -0800
To: mharris AT sympatico DOT ca
From: Gene Buckle <geneb AT deltasoft DOT com>
Subject: [opendos] Re: OpenDOS to be released next week! (fwd)
Cc: opendos AT mail DOT tacoma DOT net
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

>> Right now there is no more detailed information other than is already on
>> their homepage.  I imagine next week more info will be posted. (the
>
>If you know of more URL's please post them.

There are none right now.  I've set up http://www.deltasoft.com to be the
"semi-official" OpenDOS support/info site.  There should be something there
this week.

>
>> package is going to be distributed in two forms.  A multi-disk install set
>> that can make bootable install disks, and a large archive contained in one
>
>How many megs will it be?

Probably close to 7.  The install archive is (probably) a special version
of diskcopy that can write images, and 6 image files.

The sources on the other hand may be huge.  There are over 2900 files to
the full tree.
>
>> file)  I'm hoping to be able to get more technical documentation from the
>> EDC and get it out among you folks in a short period of time.  
>
>What is the EDC?
>

European Development Center.  That's where all the OpenDOS work is being
done. (England)

>> Since OpenDOS uses a 6.22 compatible FAT system, there should be no
>> problems at all doing a multi-boot system.  What's really neat is that the
>
>Well I assumed the filesystem would be the same, but what I was concerned
>about was the kernel and AUTOEXEC.BAT & CONFIG.SYS files, and if it uses
>the DOS Multiconfig, or if it has a better one.
>

There is no multi-config that I know of.  Then again, I've not gone looking
for it. ;)
No changes need to be made to either .BAT files or CONFIG.SYS.

>Problem 1:  The boot sector loads the kernel so to boot from the opendos
>kernel, it would have to be called something else instead of MSDOS.SYS and
>IO.SYS.  I assume it will be DRDOS.SYS and DRIO.SYS or OPENDOS.SYS,
>OPENIO.SYS.  However this still leaves the problem of the bootsector
>loading the kernel.  Looks like we're going to be installing LILO or some
>other boot manager.

The kernel files are IBMIO.SYS and IBMDOS.SYS.

There should be no problems with normal boot managers.

One thing that DOES need to be kept in mind is that OpenDOS goes nuts over
Win95 long file names.  CHKDSK thinks they're lost clusters.  Don't use
CHKDSK /F, the disk optimizer or the backup software if you're dual booting
win95.  It won't ruin the disk, but it sure will screw up the long file
name tables. ;)

>> 
>> You can multi-task multiple applications via the TaskMgr interface.  If
>> you want more info on that particular bit, check out Rolf Brown's
>> Interrupt list.  Search for TaskMAX and TaskMGR.  (the api given is enough
>> to develop a new task manager from scratch)
>
>Is it similar to DESQview?  I've used Ralf's DV code to impliment a few DV
>programs before.
>
 
I don't know.  I've never done any DesqVIEW programming.  

>Here's the kicker...
>
>Will it run Windows... ...  ...  and stop Windows from GPFing?  :o)
>Ok, sorry, I'm pushing my luck now.
>
Mike, GOD can't even keep Windows from GPF'ing. ;)

I've had it running Windows For Work(less) Groups 3.11 w/network support
without any problems.

g.