Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.pick > #701
| From | Kevin Powick <nospam@spamless.com> |
|---|---|
| Newsgroups | comp.databases.pick |
| Subject | Re: d3/nt problems if c: not the boot drive? |
| Date | 2011-07-08 12:01 -0400 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <iv79li$mp5$1@speranza.aioe.org> (permalink) |
| References | <H8edneU1eKdxmorTnZ2dnUVZ_uCdnZ2d@posted.internetamerica> |
On 2011-07-08 10:35:03 -0400, "Frank Winans" <fwinans@sbcglobal.net> said: > Anybody care to comment on problems using the, say, > E: drive for d3 on older releasese? 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
Back to comp.databases.pick | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
d3/nt problems if c: not the boot drive? "Frank Winans" <fwinans@sbcglobal.net> - 2011-07-08 08:35 -0600
Re: d3/nt problems if c: not the boot drive? Kevin Powick <nospam@spamless.com> - 2011-07-08 12:01 -0400
Re: d3/nt problems if c: not the boot drive? Excalibur21 <pgmcmurray@gmail.com> - 2011-07-10 16:07 -0700
Re: d3/nt problems if c: not the boot drive? DrewConboy <dconboy@drexelmgt.com> - 2011-07-11 14:29 -0700
csiph-web