mritter

I had another moment of "greatness" Maybe........... I was sitting here at my desk and glanced over and saw my notes on sub-items. Still trying to come up with a viable plan of attack. Then it dawned on me: I don't need to assign every item Install Order values, or change UIDs to match parent, when I convert config.js to JSON; I will just put them directly "under" the parent as a child array. This really should make things easier, yet a little harder in some places. But as a whole, I think this just might work. Stay tuned..................................

Al: Wouldn't it just be easier to make a Cleanup category (and others) and check/uncheck what you want? And make it a Configuration so can select them automatically. TwoJ: That would be very hard to change. I see your point and like the idea, but, not going to happen any time soon.

JSON is really just embedded arrays. Yes, it is very easy to add/remove items, but you still have to know what you're doing. Adding items in the Config Wizard will still be the same, just how I use it internally will be different. The loading code for config.js will drop to like 3 lines instead of the ~100 lines now. Saving won't be any different/easier code wise. The good part is that it will be super easy to update the config wizard code to handle it. I am already using JSON for the new Network Wizard. Works great. I'm glad I tried it out. I will also be using JSON in the installer, as well.

{EXTRACT} "%root%\\Downloads\\WPI.rar" "W:\\Work\\WPI Test\\" Put quotes around both paths, spaces or not. It's very finicky. When you use the file requester it does the quotes for you for the source.

Well, after getting home from trip, and next day my main computer crashed (drive in raid 0 fubar), I am on an old computer and back up to 80% speed. Here is the fix: core.js line 104 // Removable, ie, USB Key cddrv=""; Delete the cddrv=""; line. Kel, get that updated in the main archive.

Ummmmmm.....................you may want to wait on making a script to convert down. The config.js file will be getting a make over for next version. I am going to start using JSON. Someone had asked way back if the cmds could be listed on seperate lines for easier reading/editing, they will be in JSON. And no, it will not be easy to down grade and you will lose a ton of functions/commands; all {JSCRIPT} for example. I don't support WPIC, I just do small stuff for Kel once in a while for it.

Kels is right about the themes: only what is in your Themes folder is what is listed. If you have downloaded 7.7, you need to download the latest version from the web site and put it in the Themes folder. That is why it is saying Vista is not found. Only Accordion, CorporateIT, and Windows are in the archive. For the lang issue, I would guess you have some old reg keys lingering around. When you are testing/building entries on desktop, how are you exiting WPI? If you hit the X close button on the top right of window, that is your problem. YOU MUST USE THE EXIT BUTTON INSIDE WPI THEME OR HIT ESCAPE TO QUIT WPI. If you don't reg keys will be left and re-used next run "confusing" the new instance of WPI. HKCU/Software/WPI delete the entire WPI folder from registry and run again to see if cures problems.

If you are not using English, manually edit the useroptions.js file to 'en'. If you are using English, what string does it say it can't find? Several language codes were wrong and have been changed to correct ones.

I am out of town so I will look at it Monday when I get all settled. Probably something simple I changed a while back that something else is affecting. Should be an easy fix.

I saw it. Looking in to it..............

Al, You are going to have to email me some examples. That post is way too vague to get what you mean.

Is this during an install when maybe no user accounts have been set up yet? Or is this on your desktop? Did you do the command prompt test?

The ChangeLog.txt will ALWAYS be current. The manual has fallen behind; Kels can't keep up with me. Read that every new release. If you have ANY ideas/requests/complaints, now is the time to post them. v8.0.0 is going to be a MAJOR release. So big I am jumping 2 versions.

Has always worked fine for me. Type it in to a command prompt. It should say 'Mark' is not recognized as an ....... but your name instead, of course.

Don't delete the entries completely, just set up multiple configurations: Full, Limited. Assign each item to either, or both. When copy to DVD just copy the files you need. When run from DVD select Limited config and only the in it will be selected. Or do FileExists() conditions to hide the item when on DVD, but show on share.

{JSCRIPT}=CreateShortcut() was released back in 7.6.0. Read the manual and changelog. Look at the Commands menu. It's all there.

Are you launching with WPI.exe or WPI.hta? Use the .exe. Is there a reboot somewhere before Office gets installed?

Thanks, chaoticyeshua! Since no one has an opinion, I went ahead with my idea. Working out beautifully! One theme done, copy and paste to the others. Going to be nice to only have to update the theme code 4 times instead of 44 times. The nice thing is that you will never know the difference. Everything, well, 98%, will look and work exactly the same.

I have been updating the themes yet again for 8.0.0. I have made them cleaner for the end user to update/modify, easier for me to update/modify, just all around better. Then it dawned on me after I updated the first 5 themes: these themes are redundant and a pain in my butt!!!!! There are only 4 "kinds" of theme styles: Windows, and my 3 styles: euDock, CorporateIT, and Accordion. Of the 44 themes there are: 1 Accordion, 1 Corporate, 6 euDock, and the rest Winows's style. So why am I busting my butt updating 44 themes over and over and over......?????? Talk about getting old QUICK! Here is my proposal: With the new upgrade for the DHX modules, they have merged all the skins into one file using a new Style Editor (coming soon to a WPI near you). This makes perfect sense to me: pick a color (skin), say SkyBlue, and all the components will then be SkyBlue. Can eliminate 7 of the combo boxes on the Style tab. 7 items will still be customizable. Pretty much every one does all black, all blue, all the same anyway since it matches main theme bg color. Why not do that with the themes? Make 4 "universal" theme files in a common location, look at the actual theme folder for the images and style sheet, and voila! Instant themes. This will make my life SOOOOOO much easier for updating. AND make your life easier since you will never have to update your themes manually. All themes will look "alike". Now don't whine just yet. 95% all of skinnable programs just allow basic image/color replacement anyway. The image locations will all be the same, but still unique images/colors to every theme. And if someone comes up with a new theme style, it can be added lickity-split. Want to make a new theme? Pick a style, make new folder, throw in images, edit style sheet (basic colors), and you're done! So..........I want opinions, ideas, complaints, whatever. For me, this is the way to go.

Above. If you just want to change the bg for ALL themes by using a custom one, the image must be in the Graphics folder, and specify it in Style tab.

That's what I needed clarification on: Was is even possible to make a user account on the client machine and join a domain from the client machine and have the server recognize it. Sounds like no. So really, all I even need to have there is a box for Workgroup name. Not even offer anything for domain, right? Since it is all done through the server. The whole idea behind the new Network Wizard is you make a list of users with their appropriate machine IP info, computer name, user account, etc. ahead of time. So say you have a business with 25 computers on a Workgroup, you make an entry for every person/computer. Then your winnt.sif could still have the basic info (key, unattended, display, etc), but no user/machine specific info. WPI's new Network Wizard will open a new window when install process is started and you pick the user you want to install for (or none). Or specify from command line args so no window opens. For people on a domain, you can still use this to set IP info, computer name, create Window's accounts, etc. So what I will do is get rid of all domain stuff, no radio button for Workgroup, just a text box. If something is entered then it will assume Workgroup and join it. If left blank, nothing will be done.

I've pretty much figured everything out through trial and error. Just have one last thing I believe I have over-built: When picking either Workgroup or Domain for the client machine, if pick a Domain, do you enter anything or leave it up to Admin on the AD server? Is the below section for Domain needed? Is just the Domain name text box needed, or the user stuff, also? I have all of it working, but I would imagine the user would really need to be created on the Admin server through AD.

Never got any reports about the language problem you have. Set it to the first choice, system default, and see if it works. It could also be because the original translators had the wrong country codes for some languages. I have them all fixed. What version are you using? As far as the graphics being faster, if you are still using IE6, then yes, it will be slow.

This is along the lines of the main Feature Requests thread, but I am going to narrow it down a bit. What would you like to see automated by WPI that you always do after installing Windows? I have already added for v8.0.0: CreateWindowsUser() SetFirewall() SetFilePrintrSharing() SetPageFileSize() MapNetworkDrive() ShareFolder() JoinWorkgroup() Anything else you would like to have WPI do so you can truly come back to a fully installed, ready to go, system?

Ah yes, the lovely ol' tool tips............... The problem is that each theme has it's own default style "sheet" for tips. That way the tips will match the theme colors,etc. Makes sense. Until you go to upgrade and the supplied default settings over-writes your settings. The settings file can't be left out since it has all the theme-specific settings. When someone makes a theme, that file has to be there when someone downloads it from the web site. So if you are using one of the themes in the archive, it will always overwrite anything you changed. I will make a note and think some more on it. I totally understand the issue. It sucks.