This is a minor maintenance release. No new functionality has been added beyond fixing the issue described below.

Recent changes to the There webapps servers have resulted in more frequent XML errors when accessing the Auction site pages, and these errors usually cause jX to freeze. While I have been aware of these effects for quite some time, the XML errors did not happen often enough for me to actually be able to devise a solution for them, as I could never replicate them for test purposes. But, odd as this may sound, the increased frequency of the XML errors these last few days gave me the ideal environment, so I was able to get the errors to occur pretty regularly when I was coding. So what I was able to come up with was a version of jX designed to be more resilient to XML errors, and to be able to survive and recover from them. While I fully expect the cause of the XML errors to be found and dealt with by the There Engineering team, the changes made to the jX code should help keep it chugging along even after these frequent errors are long gone.

Note that, as in previous builds, I only tested jX on Windows 2000 and Windows XP, both with Internet Explorer 6 installed. I have not done any testing of the application on on older or newer versions of Windows or the IE browser.

This is a *very* minor maintenance release. No new functionality has been added beyond fixing the issue described below.

Recent changes to the way the There webapps servers work caused some very odd behavior with jX; when listing an item in the auctions, the app would successfully list the item but would return a false error and attempt to list it up to two more times before giving up. While the effects were mostly just annoying, a few tests I ran resulted in a single item being listed three times in the auctions, which certainly was not a good thing. This release addresses this issue.

• Due to recent changes in the There website, particularly the Auction site, the previous version of jinXplorer would "hang" after it listed one item. There were a few other incompatibilities, but this one was the most obvious. This update addresses these compatibility problems.

• The HTTPGet function in jX has been completely replaced. The older function, which I originally found in 1998 and have reworked and/or adapted over the years, had a nasty memory leak that I could not get rid off. The new function, which I had to license, has a rock-solid thread safe foundation, and it has proven to be much more reliable than the previous function. Unfortunately, it was not a direct drop-in replacement, so it required a *lot* of work to remove all instances of the old routine and adapt the existing jX code to work with the newer function. For most of you there will be no noticeable difference, but for the few who have encountered the symptoms of the memory leak this should be a welcome change.

• DocD found a bug that started in jX v1.08; those of you who have auctioned large numbers of items from your inventory (not your Developer catalog) at Fixed Price Sales may find that the Sync process jX does at the very beginning of every sessions could be taking longer. The reason is that the "skip list" that jX was maintaining with this data was not getting written correctly. This update corrects that problem. After installing this versio it will recreate the skip list (so it may take a little longer), but once it has the newly created skip list the Sync should be faster in subsequent sessions.

Minor maintenance release. The following changes were made:

• As the base auction listing fee was raised from 30T to 100T, the code was modified to account for this in its calculations.

• The first time you run this version of jX it will search your catalog and auction history files for any items that are based on the Shop Builder5, Hoverboat Builder Config2 or Animated Hoverboat Builder Config 2 product types, and it will adjust their wholesale prices accordingly.

• Due to changes in the There website, older versions of jinXplorer could nolonger login correctly and had difficulty recognizing the data it was seeing on some of the auction pages. This build addresses these issues.

• As there are possibly more changes coming in the future, this version has a simple "semi-automatic update" mechanism built into it. Just before you login to jinXplorer, it will download a tiny file (less than 100 bytes) to verify that you are running the most recent version of jX, and will give you the option to download and install the latest version if one is available.

• Jinx_tv, Dreamweaver and tablatronix reported some unusual behavior with the previous jinXplorer release. In particular, it was not consistently updating the Auction data for listed items (ie. it could not detect the number of items sold or which items where actually listed). It took a while to track down, but the problem was caused by the change in Auction IDs from six to seven digits; the subtle change in the format threw jinXplorer's internal indexing out of whack. This has been fixed, but it did require some slight alterations to the .jxf file format; the Auction IDs are now zero padded to maintain a consistent width.

• Jinx_tv, Kittenkat, Mercuria and Dreamweaver all reported encountering "out of memory" errors when listing their items. Again, this took a *LONG* time to track down, and it might not be entirely fixed yet, but I did find a very nasty memory leak in the code which was occuring at approximately the same points that they indicated. While the fix should be virtually invisible to everyone, it required replacing the section of code that was responsible for downloading auction related webdata, so this also took a lot of work.

• This may be of interest to tablatronix: the date formats in the .jxf files has changed slightly. Previous versions of jinXplorer saved dates using the standard Julian Day system, which has a starting day of January 1, 4713 BCE. Beginning with this release, dates in .jxf files will use a modified Julian Day system that starts on April 16, 1998 CE. This change was made, among other reasons, to compensate for the increase in the Auction ID width.

• When logging in through jinXplorer, if you select the "Thorough" Sync Data option your auction history data will be pruned (compressed) a bit; that is, the application will clear out the Extra Descriptions and Logo URLs from older auctions. This not only decreases the size of the file significantly, but it helps make the data much easier to process and work with.

• A few bugs (including another Banshee Bug) have been fixed.

• Majandi pointed out that if you opt to remove an Item Group name in the "Modify Item Groups" and then click [No] when prompted to remove it the dialog would appear to "freeze." It was not actually frozen, but none of the controls in the dialog were enabled, so it looked like it was frozen. This behavior has been fixed.

• tablatronix discovered that if you specify a URL with an embedded port value in the "Logo URL" field that the [Preview Logo Image] button could not download and display the image file. It also returned the wrong error message, saying that the specified image was an unsupported file format. This bug was caused by a last minute replacement of the HTTPGet function, and was easily fixed by creating a hybrid of the old and new functions.