Jump to content


Photo
- - - - -

New Release of ProIV


3 replies to this topic

#1 Rob Donovan

Rob Donovan

    rob@proivrc.com

  • Admin
  • 1,640 posts
  • Gender:Male
  • Location:Spain

Posted 03 June 2003 - 05:32 PM

A New kernel & client release is out.

Kernel 5.5 r302
Client 500

Edited (12/06/2003): This release has been removed due to problems.

#2 Rob Donovan

Rob Donovan

    rob@proivrc.com

  • Admin
  • 1,640 posts
  • Gender:Male
  • Location:Spain

Posted 05 June 2003 - 02:24 PM

This release seems to have been removed from the web site.

I guess there was a problem with it

Rob D.

#3 Guest_Guest_Neil Mellis_*

Guest_Guest_Neil Mellis_*
  • Guests

Posted 05 June 2003 - 08:33 PM

The 302 release has been removed due to an issue that has surfaced on AIX but indicates a potential problem on
on other platforms where large functions that exceed work space through too many open files (deep global call nests)
may not report failure or potentially hang. The release has been withdrawn pending further testing and will be re-released
A.S.A.P (probably as 303).

Although the probability of failure should be low we thought it warranted further investigation and would advise those that have downloaded
302 to wait for 303

We have also fixed the import block by VIP which was due to a bad setting in our build process

#4 Ross Bevin

Ross Bevin

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 226 posts
  • Gender:Male
  • Location:Manzanillo, Colima, Mexico

Posted 10 June 2003 - 06:17 PM

I have noticed that 5.5 r220 for Windows 2000 has been pulled from the pro-IV web site, together with r302. r221 is now on the list. Last week we went back to r216 from r217 because of too many thread exception errors. We were told the thread exception errors were being caused by a memory leak and were fixed in r220. We tried to migrate to r220 but encounted a bug when genning functions that used global logics that called global functions. The gen process was telling us that a particular parametre was not defined. I logged this bug two weeks ago and it was confirmed to be a bug in r220. Can anyone at Pro-IV tell me whether this parametre problem is fixed in r221? If not, when can we expect it to be fixed? We are now in a situation where we can't go forwards or backwards with any releases and have to contend with r216 that crashes our kernel several times a day.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users