From: jknepley@isis.cs.du.edu (Ranseus (Jim Knepley))
Subject: Re: DR-DOS Installation HORRORS!  HELP....
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Keywords: dr-dos, hell, ...
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Sat, 11 Apr 92 00:39:11 GMT

In article <1992Apr10.204208.2193@galileo.cc.rochester.edu> scls_ss@uhura.cc.rochester.edu (Eric Scoles) writes:
>I need help and it doesn't look like I'm going to get it from DRI.
>
>I got my brand new DR-DOS disks in the mail day before yesterday, and they
>were the wrong media.  My A: drive is 3.5", not 5.25", and they sent me 5.25
>(even though I had explicitly ordered 3.5 -- a salesperson at the Novell
>orders & resolutions place in Buffalo said "they [meaning special coupon
>shipments] were all shipped that way".

First, don't panic.  If DRI sent you the wrong disk size, for god sake,
complain.  Get the correct disk size from DRI.

>By various means, I managed to get the diskettes copied onto 3.5" floppies
>in a bootable form.  HOWEVER, every time I tried to run the Install routine,
>it would get to a certain point and go into a loop that seemed to indicate
>that it didn;t recognize the disk it was running off of.

This is a resonable first step.  It doesn't seem like it worked -- go to
step 2.

>That was only the first of several awful behaviors, but I persisted.  I
>installed everything _manually_, and started trying to get everything
>configured in a useable fashion.  And lo!  DR-DOS would not load High!

Manual installation is a reasonable second step, but I doubt that you
got all of the little toys tweaked correctly.  If you're sure you did,
I don't know what to say.

>Yes, I did everything by the book, but THE GODDAMNED M*^^&^*&^%^&(^ WON'T
>LOAD HIGH!

Technically, my copy won't load high either (this is intentional, BTW).
The DOS kernel will, but I run out of High Memory before COMMAND.COM gets
loaded.  I won't load anything into segment FFFF: since I use DesqView
and everyone (Quarterdeck, DRI, etc.) suggests leaving that upper memory
segment free for DesqView's use.

>And to top it all off, DRI says they'll "try to get back to me within the
>next several business days."  I never thought I'd say this, but this makes
>DOS 5 (or DOS 4.01, fo rthat matter) seem like nirvana.

I wouldn't give up on DRI yet.  I've never had any trouble...

For reference, I've included my DCONFIG, CONFIG and AUTOEXEC files.  These
work for me (I do have a 386), and may shed some insight into what you're
doing wrong.  I get 635k free with this configuration.

Hope I can help,
  Jim

----- DCONFIG.SYS -----
DEVICE=C:\QEMM386.SYS RAM ROM NW3 ST:F
DEVICE=loadhi.sys C:\SSTORDRV.SYS /hidma
DEVICE=C:\DEVSWAP.COM
CHAIN=C:\CONFIG.SYS

----- CONFIG.SYS -----
HIDOS=ON
DEVICE=\drdos\hidos.sys /b=auto
SHELL=C:\COMMAND.COM C:\ /P /E:512 /mu
BREAK=ON
FCBS=4,4
FASTOPEN=0
LASTDRIVE=E
HISTORY=ON, 256, OFF, OFF, OFF
COUNTRY=001,,C:\DRDOS\COUNTRY.SYS
device = \qemm\loadhi.sys mouse.sys

----- AUTOEXEC.BAT -----
@echo off
PATH C:\BATCH;C:\DRDOS\SSTOR;C:\DRDOS;C:\QEMM;C:\UTIL...
VERIFY OFF
loadhi files=40 >NUL
loadhi buffers=5 >NUL
PROMPT $P$G
SET TEMP=C:\DRDOS\TMP
SET PKTEMP=F:\
SET EDITOR=VDE
SUBST E: C:\ZIP\TEMP
IF NOT "%TEMP%"=="" MD %TEMP% >NUL
SUPERPCK  /A+ /S:930 /L:900
FDREAD >NUL
LOADHI C:\DV\DVSIXDI >NUL
CLS

*** END ***
Newsgroups: comp.os.msdos.apps