Kelsenellenelvian
Dec 29 2008, 05:20 PM
Steps to update your WPI folder:
- Download and unRAR to a different location.
- From your old WPI folder, copy config.js, useroptions.js, and windowoptions.js from WPIScripts to the new WPIScripts folder.
- Copy your Audio folder from old to new.
- Copy your Install folder from old to new.
- Copy Themes folder from old to new.
- Rename or move your old folder in case something goes wrong.
- Move the new WPI folder to where you want it.
- Test it!
Stoner81
Dec 30 2008, 12:15 AM
Thanks for the info kel much appreciated buddy!
Stoner81.
Maeggor
Jan 17 2009, 04:34 AM
I have a 6.4 version and i want to upgrade it to new 7.2.2 but i dont know how because i extract the new files into the old folder and it doesnt start
Any suggests? Thanks!
Kelsenellenelvian
Jan 17 2009, 05:12 AM
Thats DEFINATLY not how the first post describes updating WPI. I suggest you read it a bit more...
deadbug
Jan 18 2009, 02:46 PM
I upgraded from 6.something to 7.2.2 using the instructions here and it worked like a charm.
It did mangle two things, but (given that I maintain config.js manually) that's pretty good.
1. It stripped all comments out
2. I define variables at the start and then use those rather than 'yes'/'no' so I can easily build a disk to install just new programs when I'm updating my disk.
It would be neat if a future upgrade could preserve comments. It would be frighteningly good if it preserved all lines it didn't understand - in the right place :-)
It took me two minutes to restore my manually maintained stuff, so anything that takes more than 10 mins to code isn't worth the hassle !
Once again, excellent job!
mritter
Jan 19 2009, 06:10 PM
I don't like it when people manually edit the config.js. It only leads to problems down the road. Changes like global replacements of text are fine. There will be no support for user entered comments.
deadbug
Jan 21 2009, 06:58 PM
QUOTE (mritter @ Jan 20 2009, 12:10 AM)

I don't like it when people manually edit the config.js. It only leads to problems down the road. Changes like global replacements of text are fine. There will be no support for user entered comments.
That's fine - I was thanking not complaining ... honest
frasuperbike
Feb 28 2009, 02:31 AM
I have a problem. I want upgrade my wpi 720 to 730.
I have saved the 3 files in wpiscript (Config.js, useroptions.js and windowoptions.js). I have delete all old file of my older wpi without install folder and music. I have replace all file with new version (730). In wpiscript i have replace the old 3 file with my option. I run wpi and i receive message that say :
your config.js and ask if i want to update it. If i say No wpi wont't start. If i say YES wpi start but with one problem. In config.js each program lost a command line...
New situation:
pn=1;
prog[pn]=['.Net Framework 1.1'];
uid[pn]=['NETFRAMEWORK11'];
desc[pn]=['Microsoft .NET Framework utiliti per rendering grafico avanzato di windows'];
ordr[pn]=[1];
dflt[pn]=['no'];
bit64[pn]=['no'];
forc[pn]=['no'];
cat[pn]=['Sistema'];
configs[pn]=['free,mondo,mondomerda,sistema'];
cmds[pn]=[''];
deps[pn]=['DELETENETUSERACCOUNT'];
picf[pn]=['netframeworks.jpg'];
picw[pn]=['128'];
pich[pn]=['128'];
textl[pn]=['Bottom'];
pn++;
Old situation
pn=1;
prog[pn]=['.Net Framework 1.1'];
uid[pn]=['NETFRAMEWORK11'];
desc[pn]=['Microsoft .NET Framework utiliti per rendering grafico avanzato di windows'];
ordr[pn]=[1];
dflt[pn]=['no'];
forc[pn]=['no'];
bit64[pn]=['no'];
cat[pn]=['Sistema'];
configs[pn]=['free,mondo,mondomerda,sistema'];
cmds[pn]=['%WPIPATH%\\Install\\DOTNET\\dotnetfx1.exe /q:a /c:"install /l /q"','"%WPIPATH%\\Install\\deluser\\deluser.exe"'];
deps[pn]=['DELETENETUSERACCOUNT'];
picf[pn]=['netframeworks.jpg'];
picw[pn]=['128'];
pich[pn]=['128'];
textl[pn]=['Bottom'];
pn++;
Help me please
What i can do???
Kelsenellenelvian
Feb 28 2009, 03:27 AM
Please attach you config.js
mritter
Jun 10 2009, 10:01 AM
Steps to update your WPI folder:
- Download and unRAR to a different location.
- From your old WPI folder, copy config.js, useroptions.js, and windowoptions.js from WPIScripts to the new WPIScripts folder.
- Copy your Audio folder from old to new.
- Copy your Install folder from old to new.
- Copy Themes folder from old to new.
- Rename or move your old folder in case something goes wrong.
- Move the new WPI folder to where you want it.
- Test it!
I have thought about using an actual install package creator, but steps 3-5 would still need to be done manually.
Francesco
Jul 6 2009, 02:22 PM
QUOTE (mritter @ Jun 10 2009, 05:01 PM)

Steps to update your WPI folder:
I have thought about using an actual install package creator, but steps 3-5 would still need to be done manually.
Many installers can be programmed to copy/move/delete folders and do most of the stuff you can do with a custom application without touching a single line of code but if you could create folders for user-inserted themes and audio files (and add two options inside WPI to hide default themes and sounds in the list) then even a simple RAR SFX would be enough to update WPI.
freeAppz
Jul 7 2009, 07:03 AM
I think a simple MSI could be nice or even Executable with features or propertys that install a fresh or upgrades WPI.
I can take a look at it someday.
echo-soft
Nov 7 2009, 02:45 PM
Thanks for the info kel much appreciated!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.