🚀 go-pugleaf

In article <30e6dbc9.6499201@distort.demon.co.uk>
           Nigel@falken.demon.co.uk "Nigel Belbin" writes:

>
>I have the PC Mag editors collection cdrom which has NT 3.51 server on it in a
>directory called NT351. This directory contains a lot of .s files which
>presumably identify the disk numbers. The drivers are all in a subdir named
>i386... For some reason when I tried to install drivers from the CD for a Dat
>drive the setup program requested that I insert disk 23 or the server cd rom...
>I tried both d:\nt351 and d:\nt351\i386 as the3 path but neither worked - I had
>to give up and install the driver manually :(
>
>Can anyone tell me whats wrong & how to fix it??
>
The install/add drivers routine expects to see a directory off the root
for each given platform - thus here it's looking for <drive>\i386

The original install from the PCMAG-UK disk worked because a text file
was altered to expect <drive>\nt351\i386, but this only works for the
first install as the setup info does not persist.

An easy fix is to share \nt351\i386 on your cdrom as i386, then mount it
from the SAME MACHINE as the next drive letter.

Thus if g: is your cdrom, share g:\nt351\i386 as i386,
use file manager browser to mount this share as drive h: -
and it becomes h:\i386, and as such accessible to the setup program.

Have fun,
Neville
-- 
  Internet:  jnw@phaedrus.demon.co.uk    CompuServe: 100042,3501
             j.n.wilford@ncl.ac.uk       PGP 2.x public key available