nativeEx_Win7 goes Turbo
#1
Posted 23 December 2009 - 02:03 PM
What it does, you can see in the GUI
And here the log of a minimum build (w/o additional apps / drivers etc.)
Peter
#2
Posted 23 December 2009 - 02:27 PM
i got a download error
an error has ocurred and file bla bla bla was not downloaded
#3
Posted 23 December 2009 - 02:33 PM
Sorry!Hello
i got a download error
an error has ocurred and file bla bla bla was not downloaded
Fixed.
Peter
#4
Posted 23 December 2009 - 03:08 PM
What did i do wrong??
#5
Posted 23 December 2009 - 03:24 PM
#6
Posted 23 December 2009 - 03:53 PM
I wish you and everybody here a MERRY X-MAS!!!
#7
Posted 23 December 2009 - 04:58 PM
Your log lets me assume that you use as source CD Win7 RC1 32 bit En.
What did i do wrong??
I tried with tis one and got no errors. The files in question are on the source and copied.
IMHO something on your source CD is corrupted. Mayby you try to rebuild the cache, like Virtual-R suggested.
BTW: You already know that there are troubles to delete the cache directory using explorer.
I use a cmd window
- cd to the cache directory
e.g. cd "V:\wb\wb debug\Workbench\nativeEx_Win7\Cache" - make the candidate to delete visible and non-system by
e.g. attrib -r -s -h Install_5_en-US_0_6.1.7100.0.0 /S /D (for install it takes around one minute, boot some seconds) - delete the directory
e.g. rd Install_5_en-US_0_6.1.7100.0.0 /s /q
Peter
#8
Posted 23 December 2009 - 06:10 PM
I think this is why
#9
Posted 23 December 2009 - 06:15 PM
No, if you work in nativeEx_Win7 only, no mount is made. And then you do not need wimserv.exe and wimmount.sys, only wimgapi.dll.I do not have wimmount.sys registered right?
I think this is why
For other projects maybe you need (also for Win7RescuePE). And maybe then there occurr some issues.
BTW: To use Win7RescuePE (linked) apps, also these two files are not necessary (I hope ...)
Peter
#10
Posted 25 December 2009 - 09:04 PM
1. When using this, the registry-hack to make desktop.ini dissapear doesn't work, the regkey is gone, but desktop.ini is there again.
When building without this turbo-script, the desktop.ini stays away with the reg-modification.
I do not know WHY at the moment, I will investigate it on monday, but just wanted to let you know that this script works great, exept for this little thing. (anyway this is the case for me)
I will post again in monday. Have a great holiday!
#11
Posted 25 December 2009 - 09:09 PM
Until now I did not do anything on "Desktop.ini".Peter, you should work in a rocket-lab, this really speeded up the build process even more! This is great, only one thing bothered me, but I need to do more testing before i am 100% sure.
1. When using this, the registry-hack to make desktop.ini dissapear doesn't work, the regkey is gone, but desktop.ini is there again.
When building without this turbo-script, the desktop.ini stays away with the reg-modification.
I do not know WHY at the moment, I will investigate it on monday, but just wanted to let you know that this script works great, exept for this little thing. (anyway this is the case for me)
I will post again in monday. Have a great holiday!
Please forget it for now.
I'm sure to solve it soon. But just several hours before I extended my 32 hours day to 36 hours. And, excuse me, I refuse to expand to 40 hours!
Peter
#12
Posted 25 December 2009 - 09:18 PM
Have a beer, have a kit-kat, dance to a song sleep in a cosy bed. Sing a song with the birds (ok, do not do the last thing) but Well, you
know what I mean!
#13
Posted 25 December 2009 - 09:23 PM
Thanks Google, Or should I learn Swedish?
Peter
#14
Posted 25 December 2009 - 09:27 PM
Vi ses imorgon, alternativt på Måndag!
#15
Posted 28 December 2009 - 05:08 AM
Again, good work!
#16
Posted 28 December 2009 - 05:34 AM
As I mentioned in the other thread on the NativeEX_Win7 project, I think this is GREAT, but we should have a way to make at least the simple configuration changes that apply to the PELoader's configuration file. Looks like all of them are stored into the main project file, and really should be updated into the actual Win7PE.cfg after all the other things in the "build" area are done...
So I added a bit of "cut/paste" code to your script...feel free to take it or ignore me on this...
[Do-Restore] If,%pCheckbox2%,EQUAL,True,Set,%Sh%,Open Else,Set,%Sh%,Hide If,EXISTDIR,%TargetDir%,DirDelete,%TargetDir%,FAST DirMake,%TargetDir% ShellExecute,%Sh%,%Tools%\7z.exe,"x -y #$q%CacheFile%#$q -o#$q%TargetDir%#$q" If,ExistFile,"%PECfg%",Run,%ScriptFile%,UpdatePECfg,"%PECfg%" // <---------- If,ExistFile,"%PECfgCD%",Run,%ScriptFile%,UpdatePECfg,"%PECfgCD%" // added two lines and routine below [UpdatePECfg] IniRead,%ProjectInfo%,"ProjectInfo","wpeinit","%wpeinit%" //not sure why this one isn't in the ini file IniRead,%ProjectInfo%,"ProjectInfo","screen","%ScreenResolution%" IniRead,%ProjectInfo%,"ProjectInfo","mountprogram","%mountprogram%" //not sure why this one isn't in the ini file IniRead,%ProjectInfo%,"ProjectInfo","HideLoader","%HideLoader%" IniRead,%ProjectInfo%,"ProjectInfo","CopyPreLogonFiles","%CopyPreLogonFiles%" IniRead,%ProjectInfo%,"ProjectInfo","DetectHardwareFull","%DetectHardwareFull%" IniRead,%ProjectInfo%,"ProjectInfo","RemoveShortcutArrows","%RemoveShortcutArrows%" IniWrite,#1,"main","screen","%ScreenResolution%" IniWrite,#1,"main","wpeinit","%wpeinit%" IniWrite,#1,"main","mountprogram","%mountprogram%" IniWrite,#1,"main","HideLoader","%HideLoader%" IniWrite,#1,"main","DetectHardwareFull","%DetectHardwareFull%" IniWrite,#1,"main","RemoveShortcutArrows","%RemoveShortcutArrows%" //not sure why we don't use the stored value here??? IniWrite,#1,"main","defaultshell","" //
I put in a few comments since I'm not sure what a couple of the variables are used for (or if they are just left over "cobwebs" as these scripts get modified and re-used in different projects.
BUT, I think you have the start of something "cool" here...Now, if we can just make the ManageWims script a bit smarter so that if we are actually executing on an X64 machine, but building an X86 image, I could point at the X64 DVD instead of extracting the wimgapi.dll file by hand (not that it's that hard to do...)
Again, good work, and let me know if (or how) I can help!
Scott
#17
Posted 28 December 2009 - 03:59 PM
Many thanks for your tests and suggestions.
When I do not react now, it is not that I ignore you.
I currently have to do a lot of other things.
Peter
#18
Posted 28 December 2009 - 08:16 PM
No problem - we all have (at times) way too much to get done and hobbies (like this) aren't supposed to be our full time job !When I do not react now, it is not that I ignore you.
In thinking about the whole turbo thing, it might be better to "hide" the configuration script (as opposed to duplicating it's settings)...Either way, it's confusing to have it show up, but not take effect...
Oh, and I really REALLY like the "link" options. It's a bit confusing in the display, since the directory name may get repeated due to different level settings of the scripts, but it makes it very easy to have my own set of stuff, and just "link" it into the project (just like you linked in the Win7Rescue)...then if I need to blow things away and start over, it's SIMPLE...
Great idea!
#19
Posted 28 December 2009 - 08:31 PM
Thanks for your help.No problem - we all have (at times) way too much to get done and hobbies (like this) aren't supposed to be our full time job !
In thinking about the whole turbo thing, it might be better to "hide" the configuration script (as opposed to duplicating it's settings)...Either way, it's confusing to have it show up, but not take effect...
Oh, and I really REALLY like the "link" options. It's a bit confusing in the display, since the directory name may get repeated due to different level settings of the scripts, but it makes it very easy to have my own set of stuff, and just "link" it into the project (just like you linked in the Win7Rescue)...then if I need to blow things away and start over, it's SIMPLE...
Great idea!
Just a secret: The "other thinks" are mainly concerning nativeEX_win7.
It is about the issue to combine x86 and x64 host and x86 and x64 source and not to have that "Copy from" textbox.
Right now it looks very well.
About "Configuration", I also work on a solution (include it in ManageWimsEx or have a separate Tweak script).
Concerning my my last reply, please understand it as as "I read every of yours and other member's post, but I currently need some time to organize my own ideas, before discussing suggestions"
I'm sure that we together will have succes in a final good usable solution.
Peter
#20
Posted 28 December 2009 - 08:44 PM
If you have an improvement suggestion about that, please write it into the "Bugs Tracker" sectionOh, and I really REALLY like the "link" options. It's a bit confusing in the display, since the directory name may get repeated due to different level settings of the scripts, but it makes it very easy to have my own set of stuff, and just "link" it into the project (just like you linked in the Win7Rescue)...then if I need to blow things away and start over, it's SIMPLE...
Then it will not be forgotten and the responsible developer (Unfortunatelly currentle me ) will take care of that.
Peter
#21
Posted 28 December 2009 - 09:36 PM
@sbaeder:If you have an improvement suggestion about that, please write it into the "Bugs Tracker" section
Then it will not be forgotten and the responsible developer (Unfortunatelly currentle me ) will take care of that.
maybe "Level" writing on .link files
Currently 14-iso.Link is
but level seems to me have no effect[main]
Title=Create ISO
Selected=True
Level=1
link=Projects\Win7RescuePE\Finalize\4-iso.script
To avoid such things, We try to match levels of different projects . Example: All apps scripts are at level 5 and all finish scripts are at level 8since the directory name may get repeated due to different level settings of the scripts,
But there are "mismatches" between projects especially when level number is below 5
example:
vistapecapi:
level4 used for tweaks and drivers
level3 for Addons
win7rescue:
level4 used for tweaks
level3 used for net (there are net drivers and penetwork) + Addons
level2 used for shell
and with the scripts used in these levels....
@Peter
I guess "Components" of LiveXP and nativeex_barabone maybe level=3 since it is mostly* the equilavent of "Addons".
#22
Posted 28 December 2009 - 09:44 PM
BUT, I think you have the start of something "cool" here...Now, if we can just make the ManageWims script a bit smarter so that if we are actually executing on an X64 machine, but building an X86 image, I could point at the X64 DVD instead of extracting the wimgapi.dll file by hand (not that it's that hard to do...)
But does not work well.It is about the issue to combine x86 and x64 host and x86 and x64 source and not to have that "Copy from" textbox.
Right now it looks very well.
0-ManageWims.script suggestion at post 115 is a general solution for hostosarchitecture-sourcearchitecture mismatch situations. Further 0-ManageWims.script can still take files automagically when hostosarchitecture-sourcearchitecture matches..... Well further decision about the "method" is up to psc. With current solution I use my "old" style of copying files .
#23
Posted 28 December 2009 - 10:36 PM
Please try to be a bit patient and wait.
is new for me, but I'll see what happens ...I guess "Components" of LiveXP and nativeex_barabone maybe level=3 since it is mostly* the equilavent of "Addons".
Peter
#24
Posted 28 December 2009 - 10:41 PM
replying to edited post:
new for me too, for now it is only an ideais new for me, but I'll see what happens ...
#25
Posted 03 January 2010 - 04:32 AM
Does this make sense, or do you need a more detailed "log"...Probably not something that most would run into, but probably worth fixing...
THANKS
Scott
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users