Prevx - Problem with latest build

hey prevx users/staff,

i used to use prevx 1.0.2 build 123 with ZERO problems, however.......

after updating to 1.0.2 build 127, prevx fails to load and i just get the flashing envelope,

any ideas?

btw: this is the vista beta version.

 

nevermind, the repair feature seems to have fixed it.

however, maybe the staff should look into their auto updating, it doesnt look 100% to me.

 

We'll look into this

Thanks for your report

 

The manual built in update does nothing for me... no update to 127...

 

You have to download this version manually
http://info.prevx.com/downloadprevx2.asp

Gerard

 

Merci!

 

Ooops... Problem with the install...
Multiple attempts... all with same result.
windows XP Pro

 

IS this a new build ( ie build 127) ??
I have had no auto update since 112
I recall that the 123 build did not need to be installed due to minor changes however the 127 release seems to have some more significant changes

So do we wait for autoupdate or have to go and get this ?

 

I would wait... a few of us (Me included) had failure for results..

 

i experienced the network error upon uninstalling build 123. i had to use Prevx uninstaller before it would go away. yep, i real nicely matured app indeed.


Mike

 

Hi, prevx users:

The build in question was listed here http://www.majorgeeks.com/Prevx_d5293.html more than TWO WEEKS ago.

Different time zone (universe vs earth ?)

The product is matured and its update is ever greened.

I have ditched Prevx from my laptops after almost one year solid loyal following (not any more). Good luck guys.

 

same problem i got.

however, all is well now after a repair.

glad to know they will look into it.

 

You haven't got the update just because you're using Windows XP. We've already released the update only for Windows Vista users.

Installer is online since a lot, for the people who want to manually install it instead of waiting the update.

 

im a vista user, and got the same error as hermes.

i re-downloaded the package from the website, and used the 'repair' feature and it fixed it all.

but still, it shouldnt have to be done.