[stsaerox]

jinkazama, on 09 October 2012 - 04:09 PM, said:

WPI 8.6.3

What is this? Beta? I can only download 8.6.2 on the site...

How do I update from 8.6.2? Just copying over this time?

Also network paths will ever be supported?

This post has been edited by stsaerox: 15 October 2012 - 12:46 PM

[myselfidem]

It's the link to the new WPI 8.6.3 release!

From your WPI 8.6.2 you can use the update button to download the new release.
Select: About WPI and check for update.

Enjoy!

[Kelsenellenelvian]

stsaerox, on 15 October 2012 - 12:36 PM, said:

jinkazama, on 09 October 2012 - 04:09 PM, said:

WPI 8.6.3

What is this? Beta? I can only download 8.6.2 on the site...

How do I update from 8.6.2? Just copying over this time?

Also network paths will ever be supported?

Few notes on your post:

• Things go this way now. New releases are ONLY posted here and in the "Update" feature in WPI. After a few days I then updtae the site to reflect this. (Prevents minor release for quick fixes)
  
• Network paths are FULLY supported. It all relies on HOW you start WPI. (If by script you MUST use the start /wait wpi.exe format...
  
• How do I update? RTM, RTM, RTM....

[Kelsenellenelvian]

ALSO DID YOU read the contents of the first post of this thread???

Sheesh...

[stsaerox]

Yes but I got error when I was try to update. I could not even get update info instead I get an error screen about the script not responding. After a computer restart It was ok that's why I asked. First I think was to check if it really an update or something else because your site was not updated, only this post.

Updating from 8.1.0 failed. At first I run the batch and then tried manually with instructions from the read-me I think. I always got a script not responding error and a blank wpi. I had to enter commands from the beginning to the newer version... I thought that again I'm missing something

I thought also that was the forum for... to ask questions to get straight something... I always get that type of answer from you. We are not in your head because maybe we are not your team. If you don't like to answer there are other member that can answer. I'M NOT DEMANDING anything from you.

Also some people are trying to learn as you did, I suppose, before you built wpi.

For me and for most people is more boring to write than searching or reading. We are not doing anything on purpose. Maybe we entered wrong search criteria...

[Kelsenellenelvian]

There is no " team " it's mainly just me. Yes there are a couple of members that have been posting mods.

So all of the info I write here is useless? I am just supposed to answer everyone who cannot be bothered to read even the first couple of sentences of the first post in a release thread?

My crystal ball has been broken for quite some time. Your post mentioned nothing of the issues you were having in details that would actually show you were doing more than just complaining.

I guess I can now delete the manual to? Hey that's all just useless, wasted effort then, right?

[Kelsenellenelvian]

Also you SPECIFICALLY mention upgrading from 8.6.2 NOT 8.1.

That is a special case I COULD have helped you with.

[myselfidem]

stsaerox, on 16 October 2012 - 05:15 AM, said:

Updating from 8.1.0 failed.

Tested and I have no errors!

Launch WPI 8.1.0 and select: About WPI and click on Check for update and download the new WPI 8.6.3.

This post has been edited by myselfidem: 16 October 2012 - 06:30 AM

[Kelsenellenelvian]

Network paths are also mentioned in the changelog. (There is a ton of stuff buried in there)

*** If WPI is started from a network share (\\share\folder) it will look
for the mapped drive letter (if has one) and use it.

[stsaerox]

Kelsenellenelvian, on 16 October 2012 - 05:46 AM, said:

There is no " team " it's mainly just me. Yes there are a couple of members that have been posting mods.So all of the info I write here is useless? I am just supposed to answer everyone who cannot be bothered to read even the first couple of sentences of the first post in a release thread?My crystal ball has been broken for quite some time. Your post mentioned nothing of the issues you were having in details that would actually show you were doing more than just complaining.I guess I can now delete the manual to? Hey that's all just useless, wasted effort then, right?

No but people think different I know english I have a degree but never truly used them. I cannot understand always, like I do with my mother language but that's my problem.. I know. I've read your info that's why I can use wpi about 2 years now for XP. I need some help that's all because I have to use it for win 7 and xp also now.

Wpi is ok as it is no complaints...

I've checked that fixed network related components or something is fixed. I'm using a network between xp and 7 and I've been in running generally in troubles not only with wpi... I'd just like to know if there is known bugs in wpi that I cannot handle and have to wait.

If you fixed this many network administrators may be happy. A proper wpi always releases our hands.

myselfidem, on 16 October 2012 - 06:29 AM, said:

stsaerox, on 16 October 2012 - 05:15 AM, said:

Updating from 8.1.0 failed.

Tested and I have no errors!Launch WPI 8.1.0 and select: About WPI and click on Check for update and download the new WPI 8.6.3.

The first think I noticed was that I have to move the script files to other directory that's what I found first and did in a new version's thread ... I thought until now that normal update won't work from 8.1.0. Note also that I had some commands in the older version that are not working with the newer...

[Kelsenellenelvian]

There are some features that were rendered useless by updates or found redundant.

These have\had been removed and are mentioned in the changelog.

*** Fixed getArch6432 and getmshtaBits don't work.
-- They were removed as they did not work properly

*** Removed Tool tip position: Float

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
People still have a mix of x86 and x64 software and are running into
issues with installing the proper architecture version. Now in Config
Wizard -> menu -> Other there is a new Architecture item.

Instead of creating two entries for each program with conditions to hide
it depending on x86 or x64, do it this way as a shortcut:

When adding items in the Config Wizard, if needed, double the entries
for the install program:

{x86} D:\MyProgram_x86.exe /s
{x64} D:\MyProgram_x64.exe /s

When start the installer and it comes to these entries, WPI will check
the architecture bits (32 or 64) and either skip the entry or install
it like normal.

It will say Skipped when not on the right architecture.

This is only needed if the install package doesn't have both versions in
it and checks itself for which to use.

This method will reduce the number of entries and not require any
condition statements.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This post has been edited by Kelsenellenelvian: 16 October 2012 - 07:42 AM

[Kelsenellenelvian]

Also from reading your posts remember WPI is not free for business uses.