10 Installation: Paradox 11

VERSIONS: Paradox 11 build 233 and build 302
SUBJECT: Perfect Expert does not run
BY: BERTIL ISBERG

After having installed Paradox 11 build 233 (from WP Office 11) or build 302 (from WP Office 12), Perfect Expert does not run.

Registry value shown below should be modified or added
[HKEY_LOCAL_MACHINE\SOFTWARE\COREL\User Assistant\11\Applications\EN]
"Help Path"="C:\Program\Corel\V12\Paradox\Shared\Help"

[HKEY_LOCAL_MACHINE\SOFTWARE\COREL\User Assistant\11\Applications\EN\Paradox]
@="C:\Program\Corel\V12\Paradox\Template\UAPA11en.AST"

Note:
  1. If you don't have the \EN key, look for one with your language selection
  2. C:\Program\Corel\V12\ should be changed to the folder you specified when installing.


VERSIONS: Paradox 11 build 233 and build 302
SUBJECT: Page Setup reporting paper size in inch instead of mm
BY: BERTIL ISBERG

After having installed Paradox 11 build 233 (from WP Office 11) or build 302 (from WP Office 12), Page Setup reports paper size in inch instead of mm.

In Registry the value below should be changed

[HKEY_LOCAL_MACHINE\SOFTWARE\COREL\WordPerfect Suite\11]
"PreferredLanguage"="EN"

Replace EN with your language selection


VERSIONS: Paradox 11 build 302
SUBJECT: Installing Paradox after WPWin12 prevents access to the Address Book.
BY: MICHAEL LUECK
Date: 29 July 2004

Corel has a critical DLL conflict between the WPO12 Pro MSI and the Paradox MSI files.

D:\Program Files\WordPerfect Office 12\Programs\WPIntegration.dll
The CRC32 of the specified file is: A7E109EC
The FileVersion of the specified file is: 12.0.0.238

D:\Program Files\Paradox\Programs\WPIntegration.dll
The CRC32 of the specified file is: 4E35FF2B
The FileVersion of the specified file is: 1, 0, 0, 1

If you install Paradox after WPO12 (which kind of makes sense to do it that way) this back level DLL is registered and causes at least the Address Book not to open. Run RegSvr32 to reregister the correct version after installing Paradox. I have tested that solution and it works.



VERSIONS: Paradox 11, WPO 11 SP2
SUBJECT: Losing personal settings
BY: ELLIO MARTINA
Date: 28 October 2004

I recently applied the latest WPOffice11 update which as far as I know did not contain any Paradox items. My version of PDox is 11.0.0.300

To my surprise I lost all my personal settings such as the preferences and my custom colors. Fortunately I have made a regkey backup to restore, since I also lost these when I did a repair of the installation. Before the use of the MSI installer I did not expirience these problems



VERSIONS: Paradox 11 from WP Office 12 Suite
SUBJECT: Paradox won't install from WPO12 CD - claims "interrupted"
BY: "Whitefuzz" < peterschuman AT comcast.net >
Date: 29 March 2005

I cannot install Paradox from the WPO12 disks. The installer starts to set itself up, then quits, saying it has been interrupted and can't continue. Paradox Runtime did install. I have even tried using "End It All" to close all possible programs before starting the Paradox installer. Same error message.

I have Win98SE, a 400 MHz Pentium II, 224 MB of RAM and a bit under 18GB free on the hard drive. I also have a small LAN with a D-Link 4-port router. I have several printer drivers installed for printing to files in addition to the driver corresponding to my physical printer. WPO12 says it has SP1 included. WP12, QP12, Word97, Excel97 all seem happy enough with this arrangement, but Paradox's installer won't fly.

Well, after four months of trying a variety of things to cater to the installer, I tried once more WITHOUT killing other processes (but without having PowerDesk or NoteTab Pro running), and it installed as though it hadn't been misbehaving for months. Apparently, it only took defaming the installer in the Group.
the installer in the Group.



VERSIONS: Paradox 11 from WP Office 12 Suite, Service pack 2
SUBJECT: WP Office 12 Service Pack 2 and separate Paradox patch
BY: "Michael Lueck" < NmlueckO AT SlueckPdataAsystemsM.com >
Date: 26 July 2005

Corel is up to something with the BDE configuration when you install SP2. They drop an EXE on the drive which looks to be written to the BDE API, and the locks directory is adjusted / a new directory created. Just a heads up as others try SP2, keep an eye on your Net directory and other settings... in fact, back up your BDE config file prior to SP2 would be my suggestion.

This is where BDE is configured to look for its Cfg file...
[HKEY_LOCAL_MACHINE\SOFTWARE\Borland\Database Engine]
"CONFIGFILE01"="D:\\Program Files\\Common Files\\Borland Shared\\BDE\\IDAPI32.CFG"

SP0 and SP1 of WPO and Pdx MSI files have it in THIS location.

SP2 MSP for WPO flips THIS REGISTRY to a new location and the CFG file in that new location points at the new NetDir. The original / unedited CFG file is still in this location.

Then I found the Pdx SP2 MSP and ran it with the computer in the above state. It flips the registry back to the original location for the CFG file (that file was still there on disk this entire time...) and does not change the contents of the CFG... binary still matches the CFG file I saved of after the install of PDX MSI and WPO MSI installed in that order.


Release notes for the separate Paradox service pack says:
Paradox SP2 updates
Paradox launches correctly for new users without having to update the user permissions on PDOXURS.net and idapi32.cfg files.


Oy! Adding "usage" to BDE makes the behavior of the MSP's change, here's a run down of what to expect from the two MSP's for SP2.

I installed the WPO12 SP2 MSP first, then Pdx SP2 MSP. I am NOT doing this test again the other way round...

WPO12 SP2 MSP:
Copies the existing BDE Cfg and changes the NetDir even though I had the NetDir pointed at P:\Locks Existing aliases are maintained

Pdx SP2 MSP:
Creates a brand new BDE Cfg back in the BDE program dir this time, no aliases, and the NetDir stays pointed the way WPO SP2 MSP configured it... totally different behavior than running this MSP on a box where the apps have never been started or settings configured!

I'll dig through what the Paradox Registry Cleanup EXE does as I decide if I will allow it to run at each logon in my environment.

The file:
D:\Program Files\Paradox\Programs\PdxRegCl.ini
basically tells what this wiz-bang cleanup should do. They drop (deltree) all of:
HKEY_CURRENT_USER\Software\Corel\Paradox\11
HKEY_CURRENT_USER\Software\Corel\Paradox\11.0

There must be corruption thing they are taking this extreme whack against. I sure have not seen it, and don't care to have all of those preferences wiped out... thus I don't plan on letting this program stay in the RUN key.


VERSIONS: Paradox 11 from WP Office 12 Suite. Service pack 2
SUBJECT: Preferences not saved
BY: "Michael Lueck" < NmlueckO AT SlueckPdataAsystemsM.com >
Date: 18 Augusti 2005

After having installed, WP Office 12 SP2 and the separate SP2 for Paradox, the preferences changed under Tools | Settings | Developer Preferences and Preferences, are not restored after a reboot of the PC.

This is due to their new in SP2 "delete the Paradox HKCU stuff at logon" exe they tossed in the Run key. Open RegEdit, locate the run key, delete the entry for PdxRegCl.exe

Run key only is processed when Explorer.exe starts, so if Paradox puked its HKCU, was exited, and restarted, their magic program would fail to save the day since it is not run. I am only too glad Corel left it external and did not modify Paradox itself to no longer keep preferences! This way the cleanup can be disabled.

Solution verified by: "Miguel" < miguel AT system.ecology.su.se >


VERSIONS: Paradox 11 Runtime from WP Offcie 12
SUBJECT: Installing RT11 from WP Office 12 resets Language driver
BY: "Anders Jonsson" < gt3TakeThisAway AT bredband.net >
Date: 18 November 2005

I had a PC with Win XP SP2 and P10 RT 658. The BDE was the original but I had changed some of the BDE settings like date formats, language drivers, block size, buffers etc.

I installed RT 11 from WPOffice 12 and got P11 RT 233

The BDE got updated to 5.2 and most of my BDE settings were kept including the NET-file location (which points to a network drive), block size etc.

However the language drivers were changed from my original setting of "Paradox 'Swedfin'" to "Pdox ANSI Swedfin", not a big deal for most of you but I guess international users should look out for this.

To index