We've often found promising raid controllers that are not
natively supported by the target windows platform; the
drivers must be installed in a custom copy of the windows
install media for you to boot off that array. Or, you can
plug in a 'loaner' ide drive, load that up, then install fresh
copy of windows on the raid array, then remove ide drive.

But this leaves you with a windows box that doesn't have
c: as the boot drive letter. In the past we've always put
d3/nt on the default partition and directory path during install.
Anybody care to comment on problems using the, say,
E: drive for d3 on older releasese? 'Cause when your
winbox dies, you really don't want to go buy the latest d3
version to go on the shiny new replacement box, if the
old box was fine for all these years with that old d3/nt release...

On 2011-07-08 10:35:03 -0400, "Frank Winans" <fwinans (AT) sbcglobal (DOT) net> said:

I don't know what you mean by "older" releases of D3/NT, but I can
confirm that I have at least one client with D3/NT 7.x installed on
their "E:" drive, thought their boot drive is still "C:". Windows
Server 2003.

If Windows itself can be installed and boot from a drive other than
"C:", I don't see why D3 would have any problems. It's just a Windows
compliant application, like many others. It would have been crazy for
TL to hard code some type of drive letter specification into the
product. AFAICT, it's just like any other application, using registry
entries to determine configuration, data paths, etc.

I usually set up NT systems with D3 on the boot (C drive, but have
application data (accounts) on a different drive (D, E, etc).

--
Kevin Powick

On Jul 9, 2:01*am, Kevin Powick <nos... (AT) spamless (DOT) com> wrote:
Hi
I have always setup a D: drive for data and left the C: drive for
Windows system stuff when setting up a client. So my standard D3
install is to D Drive. The only time I had any trouble was when I
named the D: drive D3 and did not immediately realise that D3 was
expanding this to the full path for the database. At the time I was
giving instructions over the phone and the user had not noticed the
change.
Peter McMurray

On Jul 8, 10:35*am, "Frank Winans" <fwin... (AT) sbcglobal (DOT) net> wrote:
we have setup over 100 + d3nt machines...... we NEVER put the d3
database in the c drive (unless there is no "d" or "e" drive)