Eagle710

I cannot find how to change the ownership.....will keep looking.

I will try and find time to post a zip file of all the regedits and system file I required to get Wireless to work in WinPE 2.1 but have been very busy as of late. Please proceed with testing and I will update you all when I get the chance. I may be able to take a screenshot of connection to a wireless accesspoint if you would like a quick Proof of Concept. Let me know!

It appears that it is used for most wireless 802.11 access points and is based on the Extensible Authentication Protocol (EAP). Therefore wouldn't this be adding wireless functionality?

How do you manage to change the registry to not allow the value to change?

I am trying to use CrossLoop portable launching the Share session on the WinPE system and the Access section on my regular system. This uses WinVNC which requires a password. I have found that if you set the Registry setting: HKLM\Software\ORL\WinVNC3 AuthRequired to 0 it should avoid this issue however everytime I try to connect using CrossLoop it resets that registry setting causing the WinVNC warning message to appear. Any ideas?

Then, being the title of this thread "New support for wifi", and seeing what Eagle710 posted, does it means that BOTH gosh and Eagle710 are lieing? @Eagle710 Care to post some details on the topic and your success? jaclaz So this is not wireless functionality? Are you sure it seems like they are talking about wireless. I will but let me put my information together.

Just wanted to bring an old thread back to life and if anyone has found something meeting this criteria?

This would only work if the systems were on the same network? And it doesnt appear to have a built-in function for creating some kind of help file similar to Remote Assistance.

It appears that Remote Assistance depends heavily on the Windoes Desktop Sharing API. Does anyone know how to apply an API to a WinPE image or how to check which are currently applied?

So I ran MSRA.exe on a regular (vista) image and than ran ProcMon and filtered by the process MSRA.exe for regedits . So how do I know that there is to be something in a value or not using ProcMON? Would i just launch MSRA and look through all the regedits in the procmon log comparing them to the current registry.

Now that Wireless works how did we connect to wireless networks. What Interface is recommended?

Tripredacus, When using Process Monitor to look at the registry it appears that some entries dont appear but yet ProMon picks them up. Is this something I should create manually if I can notice them? If you look at the picture below. It indicates that the RegOpenKey, RegQueryValue and RegCloseKey.... does that mean it opens that registry. It looks for the value and if not there it adds it then closes the key?

I assume you mean Dependency Walker?

I was going to take one last swing at this. I know for a fact that you need the following two files but am not sure if anyone can assist me an further with a tool that can help determine what is needed files or regedits. msra.exe msra.exe.mui

That is pretty funny considering I got it working just 3 weeks before they released this Hotfix.

Does anyone know what files/services are needed for Remote Assistance? Or what utility can help me with determining this.

Do you think that updating the BIOS will make a difference? Perhaps chaning something?

Has anyone used TeamViewer Portable? This seems to be free and works great through different networks.

Has anyone gotten MSRA(Remote Assistance) or a similar application that will create a file that can help with the initialization of the connection working in WinPE?

There is nothing in the registry.

On the server side this is the command I use: Winvnc4.exe portnumber=5888 password=01230123 I got it work but when I try to connect from a different system(Vista) using the VNC Viewer I can see the incoming connections but it states the password is incorrect. On the server side it states "SConnection: AuthFailureException: No Password configured for VNCAuth." Any advice?

But the same exact WIM file will boot on another system that has only 2GB of RAM as well.

So i moved all the files in the Sys32 folder and that did not make a difference. When I simply run winvnc4.exe it shows Starting User-Mode VNC and pauses. However when I enter the following: winvnc4.exe portnumber=5800 password=Test123 The command line parameters show me all the options. ANy other ideas? Please note I am using RealVNC 4(Free Edition)

I have tried USB.... CD i havent tried yet but can if need be. With a clean version "nothing added" it boots fine.

Tripredacus, It gives me the "Windows is loading files" bar which fills in all the way. But then it stops and doesnt load. I leave it fow 10 minutes and it nevers loads up. There is 2GB of RAM with a scratchspace set to 512. The model is HP 6930p. Thanks, Brian