• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Kelsenellenelvian

WPI v8.6.3 Release Thread!

38 posts in this topic

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?

0

Share this post


Link to post
Share on other sites

Also you SPECIFICALLY mention upgrading from 8.6.2 NOT 8.1.

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

0

Share this post


Link to post
Share on other sites

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.

Edited by myselfidem
0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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.

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...

0

Share this post


Link to post
Share on other sites

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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Edited by Kelsenellenelvian
0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

Hey im new to useing this so im sorry if these questions seem stupid. First I need to know if this will work on a Windows 7/8/8.1 install disk? Also where do I put the files on the install disk (or does the program do it for me?)

0

Share this post


Link to post
Share on other sites

Yes it does work on 7&8 I dun know about 8.1 yet.

Please remember though WPI is not free for business uses.

0

Share this post


Link to post
Share on other sites

Never planned it to be. I have bought my own copy of each version (even tho my company I work for has lic. for them all). I just want to have all my norm used programs I install ready to install when I reformat my PC every 6 months (Firefox, Skype, VLC, Trillian chat, etc). So this prog. seemed like the best one out there :). Thanks for all your help and information :)

Yes it does work on 7&8 I dun know about 8.1 yet.

Please remember though WPI is not free for business uses.

0

Share this post


Link to post
Share on other sites

In the manual that is included there's instructions on how to do that

0

Share this post


Link to post
Share on other sites

Where exactly do I place the WPI folder... Do I place it in the root , in the sources or in the "$oem$\$$\setup\scripts" folder... I am asking as I put it in the sources folder and when it is supposed to be running, nothing happens and the windows install is stuck in the same place (no WPI.exe running at all). So was wondering if I need to put it in another folder...

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.