[ludo]

Hello Vvurat

And about the server functions ?

[Kullenen_Ask]

server functions works on mmc snapins, from my previous experiences snapins doesn't work without related winsxs folders (normaly windows functions works without winsxs folders). It boots with all services (i don't say all working) like vhd,hypervisor,dhcpserver services. At the time of writing (now) none of hyper-v related services works. I have only 1GB RAM so adding more files and work on it is difficult for me (in virtual machine). Also my mother board usb boots very slow. I decided to stop on server based winpe until i decide to continue. Want start from basic windows 7 x64.

This post has been edited by Kullenen_Ask: 25 November 2010 - 04:03 PM

[ludo]

dhcpserver services work ?

[Kullenen_Ask]

if you need i can work on it. probably you can integrate to windows 7 too.

[ludo]

You work really fast, what is secret ?
How find you registry and files settings, with procmon... ?
I am interested by DHCP Server and also Windows Deployment Services
Thanks Vvurat,

PS: Have you find a solution for multilanguage support ?

[Kullenen_Ask]

Hehe. I made that in two days. Previous i was also made a x64 build i have experience from there, but in that build i couldn't get x86 programs to work. Because of that i couldn't get procmon to work and couldn't develop more also i didn't have x64 capable pc to work on. I extracted files from JFX script and see that i forgot to put all x86 commoncontrol winsxs entries. When i integrate that i saw x86 programs work. It get procmon to work and i have x64 capable pc now. After months of work i found to convert full hives to winpe capable hives. It takes me a few hours to convert them so i don't work on registry much now. Also i have default services.hiv for both x86 and x64. I made 3 months. In every project i use them and it never blue screen. If there is extra services like in this server project i copy and add them. Also have experince from previous work and i can understand from file names what it is for. I made lots of optimizations with dism and had lots of optimized file lists. It is a plus too. In x64 builds procmon not works as i expected. It is my opinion. Also optimizations with dism gives x86 optimization file txt but it doesn't clean x86 files when applied to wim. Maybe bug. Maybe it needs servicing x86 programs and x86 servicing stack under x64 environment. Also using dart tools under winpe environment and as loader is a plus. It's winpe log files gives missing files for services and everything about under windows\inf\setupapp.log, setupdev.log

PS: Have you find a solution for multilanguage support ?
I made as it should be. Don't know why doesn't work. I didn't test in real environment because so much work for me

This post has been edited by Kullenen_Ask: 25 November 2010 - 05:09 PM

[ludo]

And your services.hive integrate What registry hive ?
HKEY_LOCAL_MACHINE SOFTWARE ?
HKEY_LOCAL_MACHINE SYSTEM ?
HKEY_USERS ?
...

[Kullenen_Ask]

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services

There nothing language specific stuff in it. Can use every language. I need to make anew hives editing for my turkish x64 windows 7. If you want i can give a teamviewer sesstion lesson for editing of everything. You can see every change on all hives that i do. If you know about teamviewer.

This post has been edited by Kullenen_Ask: 25 November 2010 - 05:20 PM

[ludo]

Kullenen_Ask, on 25 November 2010 - 05:17 PM, said:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services

There nothing language specific stuff in it. Can use every language.

You are right, i confirm. I have create this script for a other software forum
But HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services does not interact with HKEY_LOCAL_MACHINE\SOFTWARE ?

[Kullenen_Ask]

No. Doesn't interact. Will not crash if you have all inf and drivers for services start 0,1,2. I didn't see you use that.

I nearly finished x64 winpe. Flash player x64 and media player x64 working. Used K-Lite_Codec_Pack_64bit_400.exe and it adds 10MB codecs to wim Can not get media player to work without it. Works better then mine x86. There is no interruption at sound and video when playing with media player. (sometimes i get little interrupts at x86). I used windows 7 imageres.dll and it is 20mb standalone, maybe i need to change with winpe one. So it get over 400mb I don't see theme background and can not join to homegroup (it says no license for it.) Other everything works. For x86 have fundamental support and for specific x86 programs need to add extra dll files that programs need to work.



I think to work on Media Center Winpe. That will start with Media Center shell default. After will return to work on Server winpe. I don't know why i spend all my time with this winpe sh*t

Working Media Center Winpe. It is only 400mb wim with .NET 2.0 and ehome. Now it has explorer shell. My aim was to boot ehome shell after boot but there is problems for that. First need to install sound and video drivers for to lauch ehome. It can be possible using batch files and inf loading at boot. If i can use profiling and optimize it can be better. It plays my divx files without problem. I didn't check every function. Screensaver and games works.



And this is another full winpe7 i made from zero again. I installed Windows Embedded Standart 7 with my desired features. Used it's file list and boot all windows. No media center and size 600mb. Updates finds but i couldn't installed webcam driver from updates. The reason of i want updates to work is user will not need to carry or add drivers to build. He will just use updates and install (if doesn't need restart of course)



I want to explain the difference of my builds from a real ram booting windows.

*I always keep it as winpe. My builds uses wpeutil and winpe boot process. In real windows it is user session login without wpeutil.
*Winpe registry values always kept for it to work and boot.
*I always keep SAM and SECURITY hives unchanged. It wasn't boot when they kept. (did not try again in near past) This gives some function loose to my builds. Forexample "User Control Panel" and "Reboot/Shutdown" icons never works. I believe the reason is that.

I have seen a real ram booting windows 7 in 450mb size at a russian friend. If i compare his and mine builds.

In real ram booting 7
*User control panel and shutdown buttons works.
*It works slow when compared to mine builds.
*After boot windows 7 driver loading works and it takes lots of time to install drivers.

In my builds.
*User control panel and shutdown buttons not works.
*It works faster then ram booting.
*Driver install is very quick.

I believe they can convert to each other very easly with little registry and file changes. I did not test.

This post has been edited by Kullenen_Ask: 13 December 2010 - 12:26 PM

[ludo]

 It took months and brain crash.

Courage 

[narcotic]

I tried looking at the whole topic but couldn't get a clear picture on how to configure RDP Server on the WinPE like you...

Could you please provide instructions for this feature only?

Thanks in advance!

[Kullenen_Ask]

It is so complicated that better to use teamviewer to remote connect. I don't put to my builds anymore or work on it at least 6 months. You will need so many rdp services, rdp files, terminal services, secondary/user logon (i think my minimal winpe can connect remote at first page was 360mb) Also after boot need to start all services it could to connect. If i start to explain need to rewrite all 7 pages and winpe building instructions. If you ask more simpler questions i can try to help better.

[narcotic]

Kullenen_Ask, on 13 December 2010 - 01:56 PM, said:

It is so complicated that better to use teamviewer to remote connect. I don't put to my builds anymore or work on it at least 6 months. You will need so many rdp services, rdp files, terminal services, secondary/user logon (i think my minimal winpe can connect remote at first page was 360mb) Also after boot need to start all services it could to connect. If i start to explain need to rewrite all 7 pages and winpe building instructions. If you ask more simpler questions i can try to help better.

I thought that was a pretty simple question. Have been trying to get DameWare MiniRemote Control to work without success... Hangs on initializing.

I thought RDP shouldn't be too hard if you just provide the filenames needed from the full win7 media. Also if you provide some info for the n00b how to modify those registery settings and what settings are needed for RDP. I'm not even trying to make
a full Win7 bootable media, just PE that I can connect remotely.

This post has been edited by narcotic: 13 December 2010 - 02:05 PM

[Kullenen_Ask]

Investigate this Procmon log file. I made remote desktop from inside winpe to same winpe. You will have idea some of registry and all needed files. It will probably not help DameWare MiniRemote Control. It is another software that will probably not need all microsoft remote desktop registry and files. Different things.

http://www.megaupload.com/?d=F72JQJJ0

Procmon.exe /OpenLog Logfile.PML

Download procmon from here

I thought RDP shouldn't be too hard if you just provide the filenames needed from the full win7 media

-False. Have you seen anybody or any other topic or something that anybody get remote desktop to work under winpe? (I talk about server. Not client.)

Also if you provide some info for the n00b how to modify those registery settings and what settings are needed for RDP.

-Do you know how many services that start with RDP* under system\controlset\services?

Theese files need for most of remote connection programs to work

IPHLPAPI.DLL, winnsi.dll, bcryptprimitives.dll, ncrypt.dll,bcrypt.dll,msasn1.dll,oleaccrc.dll,oleacc.dll

This post has been edited by Kullenen_Ask: 13 December 2010 - 03:01 PM

[ludo]

Hello Vvurat
Have you find a solution with your network error ?
What is your solution for play video without iefix & wmvfix ?
Thanks,

Ps i Will test your creation this night...

[Kullenen_Ask]

Yes i solved but i don't know how. Now i have a 321mb base iso. It has all the files from 120mb base boot.wim plus all the files for wireless,networking,explorer shell etc... I didn't delete anything from boot.wim because i want it stay optimizable. Now this 321mb base wim is optimizable. It means i can add as much as want, boot, run the desired feature, take the profilling list and have the minimal file list for that function. From this 321mb wim i added .net2.0 +intel,nvdia,ati drivers, directx/opengl (game functionality) and nearly all mmc stuff and it is 380mb now.

i didn't do anything for iefix & wmvfix. just it was working. When you boot you will see my network error. Maybe you can solve and find the reason

This post has been edited by Kullenen_Ask: 13 December 2010 - 05:40 PM

[Tripredacus]

I see by your screenshot that you can access the internet (and use flash) in x64 WinPE. I'm not too concerned with IE, but can yours have the ability to view SVG files in IE? I've tried working on this (presumably if SVG can work in IE, then it can work in MSHTA) however the DLL that is used is 32bit and cannot be registered. Or is there perhaps another source besides Adobe to be able to view SVG in IE?

FWIW, IE needs a plug-in for SVG files that are interactive. As far as I know, other browsers like Firefox (haven't tested Chrome) do not fully support interactive SVGs, although that may change once more adoption of HTML5 and IE9 hits RTM.

[Kullenen_Ask]

I arrenged everything to work x64bit only. Also x64 bit of mediaplayer works and default player. Program Files x86 complately empty. For flash support i installed flashplayer_square_p2_64bit_activex_092710.exe. I don't know what you mean with SVG? What is it's long name or meaning?

It was very difficult way for me to build everything x64. Because when you investigate registry deeply also you see that Microsoft doesn't support x64 environment much. It is designed to use iex86 and mpx86 mostly. I think it is a middle operating sytem between x86 to x64 transpassing until everybody decide to use x64 environments and x64 software supoort gets enough level. If i decided to build on x86 programs it would be much easy. I am not used to use x64 operating systems.

Before i decide i thought "If i build x64 why not everything be x64?" Maybe it could get me rid of lots of x86 files and smaller size. Because when i use iex86 and mpx86 i will need to put all mediafoundation, image system, codecs of x86 inside it too. Also now forexample media player uses some files from x86 folder but i think enough less amount. But understand that when somebody wants to use mostly x86 programs in a x64 winpe he should better prefer to use x86 winpe.

I think only aim of the people that desire to use x64 winpe is they want to get rid of more then 4gb ram limitation. For such people better thing is to use core x64 files and design winpe to work on x86 files mostly. But if somebody needs only specific x64 programs to run under winpe it is better to have full x64 support one.

In this winpe forexample i can not see eula screens. First i thouht i have got some missing x86 msthml.dll, mshta.dll, vbscript, jscript, ... files but i get bored to work only for it.

There is twice of everything in x64 environment. As well as files also there is a complate mirror of registry for x86 bit. Probably also 2 regsvr files should exist. One of it should be under system32 folder and other one should be under syswow64 folder. If you write regsvr32 probably it will use x64 one default and it will not let you register a x86 file. Did you try to write regsvr command with path spesific? Foreample "X:\windows\syswow64\regsvr32.exe file.ocx" But you should know that also x86 Flash.ocx can not be registered under x86 environment. Flash.ocx do not accept to be registered manually. Because of that i use installer always.

Maybe you can use a way i use sometimes. Install or register what you want on your own machine, track registry difference and add your winpe manually.

This post has been edited by Kullenen_Ask: 16 December 2010 - 05:37 PM

[Tripredacus]

I haven't had a problem with Flash so far but, now that I think of it, I never used it in x64. Flash for me in WinPE was in x86 and using Projector. Not sure if I have ever tried to make an x64 Projector or if it is possible. Currently, I do not have the resources to do WinPE testing like I used to, since my dev environment has changed radically. My only testing option is WinPE x64. The only reason why I am concentrating on x64 is becuase it can handle everything concerning deployments, with very few exceptions (such as creating recovery partitions with MBR.exe) so naturally I want to be able to do everything in x64.

SVG is Scalable Vector Graphics. It was something I worked on back in 2003 or so, building regular graphics and also interactive graphics. I had found in the IE9 platform previews that SVG is making a comeback. The reason why this is cool (and a good competitor for Flash) is that it is written as XML files. Originally, you could only use SVG files in IE using the Adobe SVG Viewer Plug-in/ActiveX control. In recent years, SVG has been viewable without a plugin in newer IE (I think 8, not sure about 7) and Firefox and Chrome. The problem is that you still need the plugin in IE to use interactive SVGs but in FF they will remain mostly static! I had originally written a website that was all XML and had no pictures except for SVG. I ended up killing that site because it only worked in IE with the plugin, so it wasn't a viable option. Even with today's browsers it doesn't display properly or at all in anything but IE.

The answer to this may lie in the IE9 beta for x64 but I don't have a system to try that on.

I have uploaded an example of an SVG I made earlier this year for fun (also to show off to a guy at work who was trying to out dev me lol)
http://tripredacus.n...st/svgtest.html

You can see the differences in this between IE and Firefox, so even using Firefox files to render SVGs is not an option, and there is no x64 SVG Viewer plugin from Adobe.

Wikipedia uses SVG a lot as well, especially for any articles with maps for countries, cities, etc. Their page is here:
http://en.wikipedia.org/wiki/Svg