Thnx
The Official Windows Post Install Wizard Thread
#82
Posted 04 August 2004 - 06:21 AM
#83
Posted 04 August 2004 - 06:25 AM
#84
Posted 05 August 2004 - 01:27 AM
I'm getting the help/comment boxes when i move my mouse over the "Begin Install", "Select Defaults", "Select All", "Help", "Exit Installer" buttons. But i don't get them when i move my mouse over my programs.
Anyone knows how to fix this?
I found a bug in 2.0b in the default settings option.
E.G.
When you select prgram 1 to 7 everything goes fine, when you select only option 8, -> option 8 AND 10 will be selected.
OR: When program 13 is selected as default, program 15 is selected in wpi.hta
#85
Posted 05 August 2004 - 07:14 AM
#86
Posted 05 August 2004 - 01:36 PM
My posted Version is only a alpha...please work with the original Version from author...
I will put this weekend another version online, that contains following features:
up to 4 rows a 10 entries possible (then the space is off
tip will be shown on programs also!!!!<=Im working now on it
a new options will be available: "make pre-boot"
(This is my way to develope the software. I want to make possible use the programm to start a windows setup from an existing windows or from a multiboot cd with windows pe! Using the "make pre-boot" i will create BEFORE the Setup all the necesary files like winnt.sif (unnatend.txt); %OEM% Folder (only necessary apps/drivers/files/hotfixes will be in there; reg settings; Ident-Settings; maybe Licence-Input)).
I also want to integrate viruscan routine and backup routine...i want so much....i want more time.....
#87
Posted 05 August 2004 - 01:42 PM
in default.js "prog[001]" and "dflt[001]"
and in config.js "prog[1]" and "dflt[1]"
you must fix it and the button work fine
#88
Posted 06 August 2004 - 02:55 AM
Kampfwurscht, on Aug 5 2004, 01:42 PM, said:
in default.js "prog[001]" and "dflt[001]"
and in config.js "prog[1]" and "dflt[1]"
you must fix it and the button work fine
i changed in config.js: "prog[1]" to "prog[001]" and "dflt[1]" to "dflt[001]"
But the problem is still there.
#89
Posted 06 August 2004 - 04:44 AM
prog[001] --> prog[1], dflt[001] --> dflt[1]
prog[002] --> prog[2], dflt[002] --> dflt[2]
and so on
i have add the fixed defaults.js as attachment
Attached File(s)
-
defaults.js (3.01K)
Number of downloads: 158
#90
Posted 06 August 2004 - 07:31 AM
Ideally, I want to have 2.0 "finalized" in time for Service Pack 2. I'm also investigating the idea of making a new "Large Version" available, which would be pre-configured for most users.
Thanks for your support, everyone
#91
Posted 06 August 2004 - 07:56 AM
#92
Posted 06 August 2004 - 08:37 AM
-RunOnceEx
-you can install programs from cd or systemdrive(see config.js)
-if you add a desciption it will display a tooltip
-deselect button
-3 commandlines
-fixed default-button
-1 boxes file for all resolutions
it is a preversion but i hope the are not big bugs
Attached File(s)
-
WPI.rar (94.8K)
Number of downloads: 274
#93
Posted 06 August 2004 - 02:51 PM
#94
Posted 06 August 2004 - 03:35 PM
have you copy the wpi folder to "$OEM$\$1\install\" on your WinXP-CD?
have you add OemPreinstall=Yes in the [Unattended] category from the file winnt.sif?
try my wpi version
i have add a new version(1.3) from my wpi as attachment
Attached File(s)
-
WPI_2.0b_Kampfwurscht_1.3.rar (94.81K)
Number of downloads: 386
#95
Posted 07 August 2004 - 07:03 AM
Attached File(s)
-
winnt.sif (2.13K)
Number of downloads: 163
This post has been edited by jgut: 07 August 2004 - 07:10 AM
#96
Posted 07 August 2004 - 07:26 AM
[GuiRunOnce]
%systemdrive%\install\wpi\wpi.cmd
%systemdrive%\install\wpi\install.cmd
is the wpi.cmd really on right place?:
winxpcd\$oem$\$1\install\wpi\wpi.hta
winxpcd\$oem$\$1\install\wpi\wpi.cmd
the install.cmd will be generate "on the fly" if you click on the continue button
This post has been edited by Kampfwurscht: 07 August 2004 - 07:45 AM
#97
Posted 07 August 2004 - 10:57 AM
#98
Posted 07 August 2004 - 03:01 PM
jgut, on Aug 7 2004, 11:57 AM, said:
Once setup gets to the GUI mode, the files for WPI will have been copied to drive c:. That that point...
You should have \install on your system drive.
In the \install folder, you should have the WPI Folder and WPI.cmd. The WPI.CMD File should contain something like start %systemroot%\install\wpi\wpi.hta .
c:\install\install.cmd will probably not exist yet. WPI Creates this file "on the fly". Ideally, you will have created a "default" install.cmd in advance, (by running WPI, and completing it like you would normally. It will create the c:\install\ folder by itself) which will be called when you hit exit (Or else, you will get an error).
I'll try to get 2.5 out in the next few days, which would ideally have a new, perhaps more elegant method of installing stuff, and may also have the new code for the popup "tool tips".
EDIT: Also, while hacking WPI is more than welcome, I'd like it if you would specify what version you are hacking int he file name. For example, something like "WPI 2.0b - Whimsy 1.7.rar" might refer to a hack for WPI 2.0b, but being my own personal "1.7" version. This would greatly simplify things, since many users are still using the 1.x series, and this would simplify support between the two available versions.
#99
Posted 09 August 2004 - 06:58 PM
I've edited the api.js file because I didn't liked having the window at position (0,0) so I've modified the sizer() function:
if ((screen.width == 640) && (screen.height == 480)) {
self.resizeTo(640,480);
self.moveTo((screen.width / 2) - (640 / 2), (screen.height / 2) - (480 / 2));
}
else if ((screen.width == 800) && (screen.height == 600)){
self.resizeTo(800,600);
self.moveTo((screen.width / 2) - (800 / 2), (screen.height / 2) - (600 / 2));
}
else if ((screen.width == 1024) && (screen.height == 768)){
self.resizeTo(1024,768);
self.moveTo((screen.width / 2) - (1024 / 2), (screen.height / 2) - (768 / 2));
}
else if ((screen.width == 1920) && (screen.height == 1200)){
self.resizeTo(1024,768);
self.moveTo((screen.width / 2) - (1024 / 2), (screen.height / 2) - (768 / 2));
}
so it will popup on the midle of the screen. I also added a section for my 1920x1200 display
I think I'll translate it in french for my own usage, anyone interested?
Edit:
Do you think you could include a special environment variable? %SourceDrive% like in XPlode?
- The file C:\windows\system32\$winnt$.inf
In the section [Data] there should be a:
dospath=G:\
G:\ was the drive letter I installed XP from. - The reg key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\\SourcePath] should point to the same thing.
#100
Posted 10 August 2004 - 02:40 PM
big_gie, on Aug 9 2004, 07:58 PM, said:
I've edited the api.js file because I didn't liked having the window at position (0,0) so I've modified the sizer() function:
if ((screen.width == 640) && (screen.height == 480)) {
self.resizeTo(640,480);
self.moveTo((screen.width / 2) - (640 / 2), (screen.height / 2) - (480 / 2));
}
else if ((screen.width == 800) && (screen.height == 600)){
self.resizeTo(800,600);
self.moveTo((screen.width / 2) - (800 / 2), (screen.height / 2) - (600 / 2));
}
else if ((screen.width == 1024) && (screen.height == 768)){
self.resizeTo(1024,768);
self.moveTo((screen.width / 2) - (1024 / 2), (screen.height / 2) - (768 / 2));
}
else if ((screen.width == 1920) && (screen.height == 1200)){
self.resizeTo(1024,768);
self.moveTo((screen.width / 2) - (1024 / 2), (screen.height / 2) - (768 / 2));
}
so it will popup on the midle of the screen. I also added a section for my 1920x1200 display :)
I think I'll translate it in french for my own usage, anyone interested?
Edit:
Do you think you could include a special environment variable? %SourceDrive% like in XPlode? :) There is two way to extract this from windows:
- The file C:\windows\system32\$winnt$.inf
In the section [Data] there should be a:
dospath=G:\
G:\ was the drive letter I installed XP from.
- The reg key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\\SourcePath] should point to the same thing.
If it can be done with WSH and JS scripts, it can be done with an HTA file. I use HTA files because, to me, they are a very logical extention to windows scripting :)
I'm considering a feature to make everything into a string that can be manipulated so that you could dynamically select languages while the application runs. While this woulden't be until much later (think 2.9 or later), I figured I should mention it.
Boring crap ahead
For now, I'm kinda torn between three features. On one hand, I am making a handy installer app that will nearly eliminate the need for install.cmd being called, while making it a bit more elegant. There would be no code changes required. Matter of fact, I could implement that functionality that you requested (%sourcedrive), while not stepping far from my goal.
The other item is the removal of the popup balloons. I didn't like the previous implementation, mainly because it was barrowed from a website, and while I am using it within their license requirements (I.E. Pasting their copyright in their source files), I'd like to "reinvent" it so that it's a lot smaller (I don't need 4000 different menu transitions), and so that it fades in. I have an idea how to implement exactly what I would like, but once again, it's a code barrier.
The third is not so much a feature, as it is another project. A while ago, I built a series of scripts called QCDI-Suite. I have a version I've not quite finished yet, which allows for some new features, and I was thinking of adding some more profile features, including a new directory structure, while maintaining compatiblity with the old structure. Does anyone know of an opensource equal to cdimage which accepts most of the same syntax? Cause I'd love to bundle them together :).



Help

Back to top









