WimPack + Wimboot
#1
Posted 23 June 2010 - 03:03 AM
1. Fastest Boot time from disc insertion to PE Desktop
2. Snappy and Smooth Performance once inside of PE
3. Compatibility on all/most Computers -(aside from drivers)
I am using Wimpack.script and Wimboot.script to attempt to accomplish these three things.
Below are a couple of screenshots of my configurations.
WimPack Script Configuration
WimBoot Script Configuration
im needing a Professionals opinion on this one *COUGH*lancelot*COUGH*
#2
Posted 23 June 2010 - 03:47 AM
Thanks for calling me professional, reminded me an old Tv Series The Professionals of my youth.
First let me start with thanking to the Real Good Professionals (not me) for wimpack script to Galapo and wimboot script to Nikzzzz
I guess you already found out that you need to alter script setting of ProgramFilesPE to have both wimpack and wimboot enabled.
and one more question, is your hostos xp/2k3 or vista/win7 ?
Further:
Assuming you are booting from cd,
As far as i know above settings will give you fastest boot time + snappy and smooth performance in a very good balance
For Compatibility, better to use BootsectorPE option of "set bootsect.bin......" (which is default but in case you alter better to remind you at this point)
Rest are all about the things you added to your core build (mmc etc.)
As far as i know* maanu and Amalux have lots of build experience with wimboot, maybe they as well as others who have experience come by to comment on settings.
Tip: check King Amalux's LiveXP package to see wimboot settings there.
Also for other things (great number of things to write, all there), especially portable package of Amalux.
Happy building.
#3
Posted 23 June 2010 - 03:54 AM
on that webpage - it says "Dave Matthews Presents..."
Dave Matthews?
lol
anyways, to answer the questions you have about my build...
Yes, I just enabled that script without modifying any settingsI guess you already found out that you need to alter script setting of ProgramFilesPE to have both wimpack and wimboot enabled.
you are correct, sir.Assuming you are booting from cd,
i am using a fully updated Windows XP Professional SP3 inside of A virtual Machine (VMWare Workstation 7) without any antivirus or anything "Extra" installed.and one more question, is your hostos xp/2k3 or vista/win7 ?
and after i post this, i will read up on amalux's livexp package settings =)
thanks for the info - hopefully we can get amalux, galapo, or nikzzz to post
#4
Posted 23 June 2010 - 04:14 AM
they are very old now, all i remember the theme music and some short photos in my memory .Dave Matthews?
you will need to There was a topic.... well follow the warning in your build tests. (probably it will be "WimPack needs SettingsDrive set on ProgramFilesPE Script") .Yes, I just enabled that script without modifying any settings
i am using a fully updated Windows XP Professional SP3 inside of A virtual Machine (VMWare Workstation 7) without any antivirus or anything "Extra" installed.
you are correct, sir.
and after i post this, i will read up on amalux's livexp package settings =)
#5
Posted 23 June 2010 - 10:57 AM
1. in programfiles PE , make sure the settings looks like the pic below ,
2. in WIMBOOT script , click on " No gui boot " .
3. use zPNP by Nikzzzz , to be able to install Network drivers automatically at boot time , see my tutorial here,
http://www.boot-land...?showtopic=9994
@ Lancelot
nice to see you being active again.
#6
Posted 23 June 2010 - 03:39 PM
few points :
1. in programfiles PE , make sure the settings looks like the pic below ,
2. in WIMBOOT script , click on " No gui boot " .
3. use zPNP by Nikzzzz , to be able to install Network drivers automatically at boot time , see my tutorial here,
http://www.boot-land...?showtopic=9994
nice to see you being active again.
alrighty, i have performed all the things you suggested. i am currently building my livexp now.
quick question about Driver Import PE - do i need it? and if so, am i correct in saying that to obtain the drvimpe.exe - i have to pay $25 to the kare website?
i also see the option to use amalux's version of driver import pe, should i use that instead?
#7
Posted 23 June 2010 - 04:12 PM
#8
Posted 23 June 2010 - 04:18 PM
this is version 2 of my livexp build.
about a year ago, i created a nice livexp that booted in around 1min 30sec. and then on some computers - it would take 6 minutes to boot.
so i would like to try to get a boot of around 1-2minutes
#9
Posted 23 June 2010 - 04:51 PM
Boot time of less than 2 minutes should be possible without finetuning, imo, especialy if you already once had a build like that.
#10
Posted 24 June 2010 - 01:09 AM
ive succesfully booted to my livexp's desktop in 1min 55sec!
=)
you guys have been SUPER HELPFUL ^)^
#11
Posted 24 June 2010 - 02:43 AM
It makes sure that the VMDK image isn't loaded into RAM, but you have to make sure that you put the output at the root of a drive (ie generally the folder named 'WIMs').
Regards,
Galapo.
#12
Posted 24 June 2010 - 10:19 AM
anyways , tell me , did you also use zPNP feature ?
@ Galapo
i was wondering if " pack system 32 " feature of WIMPACK is working with WIMBOOT ?
#13
Posted 24 June 2010 - 12:36 PM
shortly the best on internet , but do you need it ! how can i knowquick question about Driver Import PE - do i need it?
script contains last free version, option on script only for people who pay for next version.and if so, am i correct in saying that to obtain the drvimpe.exe - i have to pay $25 to the kare website?
check amalux's topic and instructions, also check maanu's above zPnp feature -->both serves same goals with different ways. (+also check script's topic page to see if you need or not )i also see the option to use amalux's version of driver import pe, should i use that instead?
principle of Galapo's livexp is "always success", as a result simply The Best PE1success!
ive succesfully booted to my livexp's desktop in 1min 55sec!
Hi maanu,
@ Lancelot
nice to see you being active again.
it was there since i come boot-land , your idea = contribution is one below (Copy VMDK image to .....)if i recall correctly it was implemented on my request (correct me guys if im wrong)
+ i was wondering how maanu missed to test this . (honestly i do not know the answer now since i do not use that option (i've never look inside how it works) hence it never came to my mind to check ...... ) Well i have my time excuse, lets wait what Galapo will say.i was wondering if " pack system 32 " feature of WIMPACK is working with WIMBOOT ?
#14
Posted 24 June 2010 - 01:17 PM
the zPNP.script worked like a champ! love love LOVE zPNP. =)anyways , tell me , did you also use zPNP feature ?
and the tutorial is very straight forward.
i am now working on the PPAPPSGEN thing. fun fun!
#15
Posted 24 June 2010 - 04:34 PM
Hi dsolomon
shortly the best on internet , but do you need it ! how can i know
script contains last free version, option on script only for people who pay for next version.
check amalux's topic and instructions, also check maanu's above zPnp feature -->both serves same goals with different ways. (+also check script's topic page to see if you need or not )
principle of Galapo's livexp is "always success", as a result simply The Best PE1
Hi maanu,
it was there since i come boot-land , your idea = contribution is one below (Copy VMDK image to .....)
+ i was wondering how maanu missed to test this . (honestly i do not know the answer now since i do not use that option (i've never look inside how it works) hence it never came to my mind to check ...... ) Well i have my time excuse, lets wait what Galapo will say.
yes , actually i meant about VMDK image suggestion not wimpack of course . and i guess Galapo fixed this option.
i have just tried that system32 function with wimboot , it seems WIMPACK or WIMBOOT does not bother at all . the size is same of both images no matter i build project with packed system32 or else .
@ dsolomon
i personally use zPNP and Driverimport pe together . zPNP for automate the network drivers stuff , driver importPE is for those rare systems where zPNP miss to find any driver , so i use driverimport pe to IMPORT the driver from host OS . also for multi media , i will have the option to IMPORT all the drivers from the host OS.
#16
Posted 24 June 2010 - 10:53 PM
No, it won't work with WimBoot because the %systemdrive% filesystem isn't NTFS so won't accept junctioning. Two future possibilities:@ Galapo
i was wondering if " pack system 32 " feature of WIMPACK is working with WIMBOOT ?
1) The driver in development here: http://www.boot-land...showtopic=11340
2) Nikzzzz modify the his wimpack.exe to allow for having the relocated system files to be on a ramdrive.
Regards,
Galapo.
#17
Posted 25 June 2010 - 07:37 AM
No, it won't work with WimBoot because the %systemdrive% filesystem isn't NTFS so won't accept junctioning. Two future possibilities:
1) The driver in development here: http://www.boot-land...?showtopic=1134
2) Nikzzzz modify the his wimpack.exe to allow for having the relocated system files to be on a ramdrive.
Regards,
Galapo.
what is the name of driver ? clicking on the link , brought me
Sorry, the link that brought you to this page seems to be out of date or broken.
i will point Nikzzzz over this post of your's to comment.
#18
Posted 25 June 2010 - 09:27 AM
Regards,
Galapo.
#19
Posted 01 January 2011 - 06:14 AM
Happy new Year,
I don't know if this is the right place to ask this question.so forgive me if any!!
just wanted to know more about the difference in using imagex version(6.1.7600.16385) instead of (6.0.6001.18000) with LiveXP
<when:using Wimpack+WimBoot scripts.>?
well if imagex v.6.1.7600 is used, what change should be added/(modified) to wimmount.cmd in order to (mount) Program Files wim/s ? or if there should be more/another services installed on live PE?
thanx
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users