Paradox V8.0 on Windows 10 after Creators Update.

Does not start any more (PDXWIN32.exe). Only see a fast Flash of Paradox Initial Screen. Uninstalled and Instaled again, but still does not start. Other apps from the Corel WordPerfect Package. start Ok
On another PC with Paradox 10 it works ok after the Creators Update.
Has anybody this problem?

sorry, what is the "creators update" ?

are you starting clean? net file and locks files gone, no command line, new config in BDE, etc? what is different between the two machines, if anything?

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

"Creators Update" is the last Windows 10 (big) Update in April.
Pardox 8 started Ok before the update, not after. then I un-installed and Installed WordPerfect 8 Pro again, and same problem. Pdx 10 on a windows 10 after creators works ok as before.

ok.. why do you need an 8 and a 10? can you just go with 10? as the paradox market gets smaller and smaller, there is less information on the "odd" versions.. everything from 7 thru 11 should work, but it's hard to know every quirk that could get in the way.. most of the knowledge and experience is for 9, 10, and 11, and they all work.. so far

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Steven
Different Customers/Environments; and, the Pdx 8 Customers are ending the use of Pdx not so far away (and are not on windows 10, yet), so I don't want to invest with a migration. Probably my own stuuf I'll have to migrate. If come up with any solution or this problem I'll appreciate it very much.
Leonardo.

just an FYI.. I've seen other folks report that they have issues with P7 and P8 with the Win10 Creators Update

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

To solve this in a hurry I Installed Pdx 10 and had a lot of problems until I found and deleted a lot of (old) .lck and IDAPI32.cfg files (as far as remember) ALL OVER THE DISK and made a clean new Installation. But did not make yet, a reinstallation of Pdx 8.

Just in case: I may also have found and deleted: "Pdoxusrs.NET"
before a new and clean Corel WordPeferct Professional (Paradox 8 or 10) instalation

Be patient (it took a lot ot time) when searching (all over the disk) the files i.e. *.lck or others.

to monitor/delete all the lock and nets files, use my old Remlok32 utility.. it takes a while to list them all, cuz drives get way bigger, all the time..

http://www.oasistradingpost.com/cartpages/paradox.htm#Remlok32

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

I also have this issue with P8.  I am currently researching but also hoping someone finds a solution soon

everyone.. no solutions yet, but I'm seeing it more and more.. p7, p8, and the old database desktop for delphi.. can I get the BDE version each is using?.. maybe, just maybe, that's the common item

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Quote:

Originally Posted by leochaim

Just in case: I may also have found and deleted: "Pdoxusrs.NET" before a new and clean Corel WordPeferct Professional (Paradox 8 or 10) instalation Be patient (it took a lot ot time) when searching (all over the disk) the files i.e. *.lck or others.

As I told before I Used the BDE that was in the installation package (WordPerfect Office 2002). Now I'm using (and working) Pdx10 with BDEAdmin Version .2.0.2.

I do not remember how Pdx 8  "Borland Share" SubDirectory was installed, but I think (in other not windows 10) it was not installed in "Program Files (x86)"; but in another SubDirectory, I think this may be the "Update" or "Installation" problem.
 

Sorry I'm now using Pdx 10 and BDEAdmin 5.2.0.2 (and working)

thanks.. just trying to get info from all the folks who've had this problem.. as I mentioned above, the default BDE from that time frame might be the common denominator.. 5.2 came from p10, not p8..

but.. did you already have p10 on the machines that used p8, before you installed p8? it would have used the 5.2 BDE that was already there, so that would eliminate my theory..

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Quote:

Originally Posted by Steven.G

thanks.. just trying to get info from all the folks who've had this problem.. as I mentioned above, the default BDE from that time frame might be the common denominator.. 5.2 came from p10, not p8.. but.. did you already have p10 on the machines that used p8, before you installed p8? it would have used the 5.2 BDE that was already there, so that would eliminate my theory..

Hi,

we are using P8 Borland, with BDE 4.0.0.36. At the moment we solved with an immediate rollback after the Creator Update.

thanks.. there is no p8 borland, only p8 corel, but that's not the point.. only question I have is, if possible, have you tried a default p8 install with a later BDE version?

sure would be nice if we knew the full scope of the problem (how many other programs besides paradox have a problem), and if it's fixable by MS?

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

You're right , is Corel P8.

I only have this BDE Version, so i can't try other type of installation.

if a later version of paradox is already running on the machine, a p8 install will keep the later BDE that installed with it

if you only have p8, and you want to roll out the Creators Update again, there are later version BDE installs available that you can load

and, there are other people with these problems, who might be able to test one of the above, more easily.. I've been looking, to see if I still have a good copy of p8 here

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

No, On the machine I had Pdx 8 (with windows 10) and working. Then Creators Update came and it didn't work any more.

Tried to reinstal Pdx 8 and it didn't work (also Pdx 10).

I deleted/cleaned everything (I could) and installed Pdx 10 (never Pdx 8 again) and it worked.

I think it may be the insatallation process of Pdx 8 where something does not get installed in the "Program Files (x86)" subdirectory; like the C:\Program Files (x86)\Common Files\Borland Shared\ or C:\Program Files (x86)\Corel\WordPerfect Office 2002\

thanks.. yes, a UAC conflict is also very possible

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

That is possible the problem. Some body with Pdx 8 and Windos 10 (after creators update) should look in it.

https://docs.microsoft.com/en-us/windows/access-protection/user-account-control/user-account-control-overview

I have a P8 App which (before W10 Creators)
I had successfully deployed in over 250 locations on on Win 7, Win 8, Win 8.1 & Win 10,  Depending on the OS of the client and OS of the file Server where that database was located, we used one of the following BDE's P8 default; 5.1 BDE; 5.2 BDE.  

After the Win10 creators, The APP will no longer run. I have spent countless hours on repeated clean installs using different scenarios. none worked.

At some point I started decided to take PARADOX 8 out of the equation and attempt to test the BDE.  I found a tool called BDE Information Utility (http://cc.embarcadero.com/Item/17173).  I am not sure who to give credit to for this utility,  but thank you.

For My test,  I reset My Win 10 environment and got my app up and running (Using BDE 5.2)

I ran the BDE Info utility to get the baseline settings and info, I took a before screen shot of the configuration and then ran the TEST BDE Option.  The BDE tested successfully. (I am not sure what it is actually testing other than creating and deleting a table, but my app was also functional).

I then installed Creators Update, after which my app was dead, P8 was also dead.
When I ran the BDE Info Utility, the configuration was unchanged from the Baseline test and the "Test BDE" continued to test successfully.

At this point I installed P9, and My app began to work again.  The BDE Info utility to reported the same information as the baseline data.

My conclusion is that the BDE is working fine,  But something in Paradox 8 is no longer calling it properly.

My final solution is this: I purchased Word Perfect Office X8,  which contains the Paradox 11 and the most recent service packs.   I recompiled my application objects and have begun testing my APP using the Paradox runtime.  This is a big step for me,  but since P11 is based on the .Net 2 framework,  it buys me some time to finish my software rewrite.

I know this may not be a solution for you, but I am ditching P8.

thanks for the details, and for the effort you put into this.. so bottom line, it's not the BDE, it's P8, cuz you're using a later BDE version..

but that means it is something about P7, P8, and the DataBase Desktop, that is NOT directly related to the BDE.. exact cause, still unknown, but this definitely narrows the focus

beyond that, p9, p10, and p11 are fine.. for now, hopefully going forward, too..

just an FYI about your "p11 is based on" comment.. p8 was a transitional effort.. p9 was the one and only clean and total rewrite when it passed from borland to corel.. p10 was a work-in-progress that was stopped, mid-stream.. p11 is just p10 with the service packs applied.. all work ceased in 2002

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Steven,   based on your comment

"p8 was a transitional effort.. p9 was the one and only clean and total rewrite when it passed from borland to corel.. p10 was a work-in-progress that was stopped, mid-stream.. p11 is just p10 withthe service packs applied.. all work ceased in 2002"

Since I have to extend the life of my program for another 6-9 months,   can you suggest the version (P9-11) that is the most stable to use...?

they all work.. if you go for 9 or 10, make sure you do the SPs, too

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Do you know where to get the 9 or 10 Service packs?

I've just joined up to chime in on this subject. I am not the creator of our Paradox database (done in Paradox 7), but I am picking it up as I go along as I will need to be able to repair and modify the database. I do look after most of the IT issues at our small company. Everything works "fine" on our Windows 7 machines. Our one Windows 10 machine was working with P7 until this big update (although the update didn't install until just over a month ago). When launched regularly, there are no messages whatsoever. When launched as an administrator, there is a security prompt, and then nothing. Reinstalling it did not change anything. Although, strangely, I didn't have to point my temp environment variable to a small USB drive in order to complete the installation as I usually do on newer machines.

If I find anything helpful I will post it. Has anyone tried to dig into exactly what the creator's update included that might cause our problem?

no suggestions as to what was changed, or how widespread the impact might be, beyond our small Paradox universe.. my guess, a dll got altered or removed

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Hi,  Has anyone discoverd a way to get PDOX8 working again after the creators update?

Jeff

not that I'm aware of

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

 Just had an MS 10 update and pardox 8 won't work now. Is the solution to just upgrade to paradox 11?

9, 10, or 11.. yes

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

any suggestions on where to get paradox 11?

ebay, other online sites, or brand new from Corel.. 11 comes with every WordPerfect Suite Professional since 11.. they're up to 18 now.. Paradox is all the same, in all of them

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

these links to the Corel FTP on my web site, should still be valid, AFAIK

http://www.oasistradingpost.com/cartpages/morelinks.htm

I have copies of the SP files, too

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

I am having a hard time finding the software.

I don't see anything on ebay at the moment, either, and it's usually the most likely place to find anything.. you can buy it new, direct from Corel, of course, but it'll cost you

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

hi, Patrick

Paradox 7, Paradox 8, and the old Delphi Database Desktop will not run on Windows 10 after last year's Windows 10 Creators Update.. Paradox 9, 10, and 11 are fine, so far

the links on my URL Links page point to the original Service Packs for Paradox, by version.. they have not changed

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

People are still using Paradox! This is great!

I designed the database our company runs on in the original version of Paradox and it was still going strong until recently. At some point we had upgraded to Paradox 8 and BDE 4.0 which ran fine through Windows 7. Now we can't avoid Windows 10 on a couple of machines and have finally gotten around to installing our app on them.

Based on this thread and others on this site, I purchased a copy of Paradox 11 and installed it fine on a Windows 10 machine. When I tried to open the app the scripts started ok and reset the working directory, but the first form did not open due to incompatible version errors.

All tables seem to open fine, but delivered forms say they were compiled in an earlier version and ask to be recompiled. Some .fsl files open while others complain of PAL syntax errors and open in Design Mode.

Is there any easy way through this? Will I have to either upgrade all the Windows 7 machines to Paradox 11 and troubleshoot the syntax errors, or abandon hope of ever running on Windows 10? There isn't any compatibility mode or virtual machine workaround is there?

Any advice would be greatly appreciated!

Thanks!

Steve

every app is unique, every environment is unique.. simplest thing is to upgrade all the machines to win 10, recompile, and go on your merry way..

your mileage may vary, of course

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Hi Steven,

Thanks for the quick reply!  That is the most robust and future-proof way to proceed.  My only concern is that I was a terrible debugger 25 years ago when I wrote the code as an ameture, and I haven't done any programming since...

Are there any common changes of syntax between Paradox 8 and Paradox 11 that could be causing the errors; or is there a list of syntax changes anywhere that might help me debug?

Thanks again for the help!

Steve

no.. 99% of it will just be recompiling, but here's the standard bug list reference we all contributed to, over the years

http://hem.bredband.net/bertilisberg/

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Hi Steven,

Thanks for the advice and resource link!  I sure wish I had had that 25 years ago when I was deep in it!

Steve

SteveM,

Steven.G's course of action is dead on. I went through the same issue this past year(2018) with over 200 users on a deployed system.   The most painful part of the process was making the decision to undertake the process. It actually wasn't that hard once I decided to stop second-guessing what I was doing.

As far as the compile errors, if you want to send me a private message, I would be happy to take a look at a few them.

Jeff

Hi Jeff,

Thanks for the reply!  It was actually your post that headed me in this direction in the first place.  I will gladly take you up on your offer to see if you can help me with a little of the low hanging fruit.  I truly don't know where to start any more.  Hopefully you will be able to find a couple of things, then I can fix them in all the forms that suffer the same problem.  I am so far removed from my coding days that I have lost my debugging muscle memory.  I remember something about a version number hard-coded into a routine somewhere, but I can't even remember if that was Paradox or AutoCAD!

Anyhow, I had tried to respond a couple of times earlier but realize that my files are such a mess that I can't even turn them over yet, and it will take some time to sort it out and make it easier for you to help me.  I will be working on it, but it is likely to take me a week or longer before I respond again.  Thanks so much for your offere though!  It is very much appreciated!

Steve