🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: demon.tech.pc
Article #71792

PROMISE DC-200 and WINDOWS 3.11

#71792
From: David Longley
Date: Sun, 12 Nov 1995 00:00
54 lines
2423 bytes
As part of the Ambra Hurdla upgrade, I have installed a PROMISE DC-200
IDE Cache controller, and tried setting it to TURBO mode. The manual &
help file on installation say that there's no need to do anything for
windos UNLESS you are trying TURBO (deferred write) mode. You then have
to copy a couple of .386 files to the \windows\system directory and make
some changes to SYSTEM.INI.

This is what they say:

(ignore steps 1-3)

     4. Locate the SYSTEM.ini file found in your Windows directory.
        Check if the following line exist in the [386Enh] section of
        your SYSTEM.ini file:

        [386Enh]
        32BitDiskAccess=ON

        If the statement does not exist, add it into the [386Enh] section.
        If the statement exists, but 32BitDiskAccess is set to "OFF", you
        need to change it to "ON".

     5. Delete the "device=*wdctrl" and "device=*int13" device setting.

        Delete the command lines "device=*wdctrl" and "device=*int13"
        from the [386Enh] section of your SYSTEM.INI file, if they exist.

     6. Install the virtual devices "PTICTRL.386" and "PTI13.386".

        Add the following command lines in the [386Enh] section of the
        SYSTEM.INI file:

              device=[drive:][\path\]PTICTRL.386
              device=[drive:][\path\]PTI13.386

        The [drive:] and [\path\] point to the directory that contains
        PTICTRL.386 file and PTI13.386. Note that the setting must specify
        the full path of the device drivers.

     Start Windows to activate the drivers and TURBO MODE.

Now, if I do this, when it goes into windows, the I get the windows logo
and then the machine reboots. Putting SYSTEM.BAK to SYSTEM.INI corrects
this.

I am runnig DOS 6.20 and DBLSPACE, but drive C: is not doublespaced.

IS there a PROMISE site where I can get new drivers for WIN 3.11 for
workgroups???

Anyone know what the problem is?

-- 
David Longley
Technical Details
Message-ID: <816180530snz@longley.demon.co.uk>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1036bc,a61f829cbb7d73f9,start
X-Google-Attributes: gid1036bc,public
From: David Longley <David@longley.demon.co.uk>
Subject: PROMISE DC-200 and WINDOWS 3.11
Date: 1995/11/12
Message-ID: <816180530snz@longley.demon.co.uk>
X-Deja-AN: 119211906
x-nntp-posting-host: longley.demon.co.uk
organization: Relational Technology
reply-to: David@longley.demon.co.uk
newsgroups: demon.tech.pc