|Subject:||Re: Paradox crashing on terminal server leaves application unrunable
|Date:||Fri, 9 Dec 2016 06:29:28 +1000
|From:||Royce Lithgo <email@example.com>
According to this:
change user /install:
Disables .ini file mapping to the home directory. All .ini files are
read and written to the system directory. You must disable .ini file
mapping when installing applications on an RD Session Host server.
I fail to see how this would make any difference to a Paradox
installation and in fact the majority of modern applications which are
registry based. Who still uses .ini files?
I don't think PDOXWORK.ini counts, as it resides in folders and not
On 6/12/2016 2:37 PM, Tom Krieg wrote:
> That could, however, be your problem. When you run Paradox on a Terminal
> Server, you are sharing all the exe and dll files between all the TS
> users and the change user/install does the installation with that in
> mind. A normal install doesn't do the "shared" thing. This has nothing
> to do with the NET file or Paraodx shared files. It's a Terminal Server
> On 6/12/2016 2:58 PM, Royce Lithgo wrote:
>> Yup paradox 7.
>> If you mean did i switch the server to install mode prior to running the
>> installer, i'm pretty sure I didn't. At that time i was pretty new to
>> RDSH and still finding my way.
>> There is an installer that was built by my predecessor which installs
>> Oracle, Paradox and Crystal runtime all in one hit. I just ran that. I
>> guess i should have done 'change user /install' prior to running it.
>> I am a little reluctant to experiment with it now though.