Alaska,
1. In the recent release (575), the new libeay32.dll no longer compatible 
with xb2net and fatally shut-down when loading SSLEAY32.DLL with OS code 
182.
2. I’ve placed a few 3rd-party dlls in rentime folder (see32, xb2net and 
related dlls), but installing the new release, delete them.  Can you please 
change the install to replace only Alaska dlls and keep others?
3. If I don’t like the new release, can I roll back to the previous one? 
How?
4. I have a Professional edition, but the documentation shows Foundation. 
Does Professional version come with different docs than the Foundation?
5. Where can I read [again] the changes made with each release?

Many thanks,
-Itai

Itai Ben-Artzi wrote:

> 3. If I donʼt like the new release, can I roll back to the previous one? 
> How?

Just go into the update manager in the workbench, there should be an option
to re-install the older versions.

> 5. Where can I read [again] the changes made with each release?

In the update manager, tehre should be version information for each
release.

Thomas

Thomas wrote:

>Just go into the update manager in the workbench, there should be an option
>to re-install the older versions.

In theory, that might be true, but if the Alaska Update/Activation Server 
is down, as it has been for at least the last three or four days, then you 
can't even get to the Update Manager. If you have no Internet access, the 
same issue arises.

Of course, you can manually install any of the "updates" that you have 
downloaded. All those MSI files are stored in the following directory:

"My Documents"\Application Data\Alaska-Software\xpp20\update-cache\

All those MSIs are complete installation packages, and don't need anything 
further. So just uninstall Xbase++ 2.0 and then execute one of those MSI 
files to install whichever build you like.

So, here is another plea to Alaska:

Please fix the Workbench, so that one can access the "Update Manager", even 
if the "asget.exe" program can't connect -- for whatever reason -- to the 
Alaska Update/Activation Server.

Also, please get the Update/Activation Server (193.159.219.61) online again.

And finally, please post information about new releases in the Announcement 
News Group here.

Thanks,

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas.GP@Charter.net
web:   http://www.Aerospace-History.net

Itai,

>1. In the recent release (575), the new libeay32.dll no longer compatible 
>with xb2net and fatally shut-down when loading SSLEAY32.DLL with OS code 
>182.

The Alaska-supplied "libeay32.dll and "ssleay32.dll" files have always been 
the same ones, Version 0.9.8e (or 0.9.8.5), even though Alaska changes their 
file date/time stamps with every new Xbase++ build/release.

Xb2Net uses (and recommends) a much later version of those files, Version 
1.0.1j (or 1.0.1.10), even though some older 1.0.1 versions should also work 
with Xb2Net. You should replace the Alaska-supplied DLLs every time you do 
an Xbase++ update, and use the newer ones (from Xb2Net or OpenSSL). Xbase++ 
will work fine with the newer version dlls, but you shouldn't mix files 
with different versions. The "ssleay32.dll" file is also sometimes named 
"libssl32.dll". The two files are identical and just have a different file 
name. You might want to have both in your runtime directory, just in case.

>2. Iʼve placed a few 3rd-party dlls in rentime folder (see32, xb2net and 
>related dlls), but installing the new release, delete them. Can you please 
>change the install to replace only Alaska dlls and keep others?

Good luck with that request. I asked for this a long time ago, but Alaska 
doesn't seem to want us to put anything in their directories, or even let us 
decide were to install those files. Every update -- and rollback -- will be 
a complete uninstall of the existing Xbase++ version, followed by a complete 
install of the new (or older) Xbase++ version. All files that were changed 
in the Source directories are also deleted by those "updates".

>3. If I donʼt like the new release, can I roll back to the previous one? 
>How?

If you have Internet access -- and the Alaska Update/Activation Server is 
up and running and you can connect to it -- you can open the Update Manager, 
which will list all the versions (builds) that you have downloaded. Without 
Internet access and a connection to the Alaska Update/Activation Server, you 
can always manually uninstall and install the different Xbase++ builds, as I 
described in my other post in this thread.

>4. I have a Professional edition, but the documentation shows Foundation. 
>Does Professional version come with different docs than the Foundation?

The header in the documentation shows either "Foundation" or "Professional", 
depending on the topic. Most items show "Foundation", but several of the 
DBEs, like the ADSDBE, the ODBCDBE, and the PGDBE show "Professional", as do 
some other subjects, like most of the items under "Internet Library". 

Because of a "design flaw" in the (implementation of Alaska's) HTML help, 
many of the Topic Headers don't display any text and the "Foundation" or 
"Professional" header only changes when there is some actual text to 
display, so you can't relay on the header to be always updated correctly, 
unless the detail pane of the help is updated.

>5. Where can I read [again] the changes made with each release?

In the online help, under: "Release Information", "Xbase++", "Changelog per 
build", you get a (very broad) summary of the changes made in each build. 
The same summary is listed in the "Update Manager" -- if you can get it to 
come up -- and that information comes from the "*.update" XML files in the 
"My Documents"\Application Data\Alaska-Software\xpp20\update-cache\ folder.

But because all "updates" are complete new installations, with (virtually) 
all files having a new (release) date/time file stamp, there is no way to 
tell which files have actually been changed. In this release, all source 
code files, including all header files, were "updated" with a new copyright 
year, but if you want to know if anything of substance was changed, you need 
to manually compare all files between each release.

Hope that helps,

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas.GP@Charter.net
web:   http://www.Aerospace-History.net

I wrote:

>Because of a "design flaw" in the (implementation of Alaska's) HTML help, 
>many of the Topic Headers don't display any text and the "Foundation" or 
>"Professional" header only changes when there is some actual text to 
>display, so you can't relay on the header to be always updated correctly, 
>unless the detail pane of the help is updated.

That should of course read: 

[...], so you can't rely on the header to be always updated correctly, 

Sorry for the confusion,

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas.GP@Charter.net
web:   http://www.Aerospace-History.net