johnhc

Digitalfox, I am curious about this. Did you mean unlimited GB downloaded not unlimited bandwidth (speed)? If you really meant speed, how is this accomplished? Is the delivery via cable, fiber or what? What kinds of speeds do you actually see? Enjoy, John.Interestingly, this thread has taken some strange turns.

Glad to help. Enjoy, John.

ghines, I suspect your c: and e: are reversed. See this MS TechNet article. Please let us know what you learn. Enjoy, John. EDIT: BCDboot not bootBCD. In a command prompt enter 'BDCboot /?' (no quotes) and get instructions.

fadedmaximus, do you realize you are creating about 81 x 10 to the 30th power addresses? Did you mean to do this or 4,194,304 addresses (128-22=106 for the mask)? In your first post, the IP address changed to has only seven 16 bit values. One must be missing. I was curious how it was being changed. Where are you observing the assigned address, HW or VM? Are you stepping on some reserved addresses (a crazy guess/question). Enjoy, John

Try getting KB2647753 from Windows Update Catalog which has v4 - should stop Windows Update from complaining. Enjoy, John.

kinshan, if you search this forum (Windows PE) for UEFI you will get several useful hits. Here is a good one for WinPE 4.0 that applies just fine to 3.0 Enjoy, John.

I copied the files from the above into the appropriate folders and tried it. I see no difference. I can change to several resolutions but to only a few selected ones. I used the OUTPUT switch on SetResolution-x64 to get a list and will post it if anyone is interested. There are no 16:9 ratios which is what my monitor is, only 5:4 and 4:3. With none of these changes on a 32 bit WinPE, the same list of resolutions is available. I also see no difference between running the booted driver and the Catalyst driver. So I still cannot convince myself that the Catalyst driver is actually controlling my video card. Enjoy, John.

Thanks, wimb. I assume I am to copy these files from my W7 x64 system and place them in the WinPE image. My W7 does not have a shacct.dll.mui file. Thanks and enjoy, John.

I ran setresolution-x64 on my WinPE 3.0 x64 and was able to set 1024:768 only. Any other resolution I tried, except for 800:600, did nothing. I wrote an AutoIt script to show the current display settings and it works fine except the refresh always shows 1. The scrip is one line: MsgBox (1,"Resolution",@DesktopWidth&":"&@DesktopHeight&":"&@DesktopDepth&":"&@DesktopRefresh)During searching I found qres and ran it on my VM. It looked neat, so I tried it on WinPE 3.0 32 bit and it works fine. I tried 'qres /L' to see what valid resolutions were available but it showed nothing. Changing the unattend.xml file to reflect a resolution of 1024:768 worked also. I searched for a 64 bit version of qres with no luck, but the link (above) has the source. Maybe some enterprising programmer can compile qrez for x64. There is a readme-build.txt file with instructions. I am not a programmer. The real purpose of all this was to test the Catalyst driver. I have been unable to convince myself that after installing the Catalyst driver that it is actually controlling the video card. Using devcon stack "PCI\VEN_1002&DEV_6738" I see the card and a line that shows the controlling service as amdkmdap. This is the same as on W7. I can also see the driver files in 'devcon driverfiles' and 'devcon drivernodes'. I expected to be able to set my display resolution to 1920:1080 (actual screen size) but could only set 800:600 and 1024:768. Perhaps this is a WinPE 3.0 restriction. Can anyone tell me how to determine for sure that the Catalyst driver is controlling the video card? Thanks and enjoy, John. EDIT: I just learned that the source pointed to above is not for the QRes by Anders Kjersem and does not seem to work at all.

Thanks, cluberti. Compatibility mode seems to have corrected my problems but as you said there is some hesitations here and there. Thanks and enjoy, John.

Kelsenellenelvian, thanks again. I had tried the 'Mark all as read', but the problem is that only one notification is shown - only one can be marked and deleted at a time. I have Chrome installed so I tried it: Drop down flash problem is gone. Inserting link in post problem is gone. Of course there is no message "An Add-on for this website failed to run". Only one notification continues to be shown. That is, most of the problems are cured by not using IE9. So, a forum that is dedicated to MS products does not work properly on the latest MS browser? Enjoy, John.

Kelsenellenelvian, thanks, but nothing can be done about it? I just noticed that I have a bunch of notifications but am shown only one at a time. How do I see them all so I can delete them? Thanks and enjoy, john.

I have several problems with the forums. I often get a message at the bottom of the screen: "An Add-on for this website failed to run". There are no options, so I do not know how to correct that issue. When I insert a link into a post, it always goes to the front of the message even though I have selected a word or phrase before I click the link icon. When I click on "Signed in as johnhc" at the top of the page, the drop menu shows briefly, then my Settings page opens. I can't seem to figure out how to send a message other than click on a user name in a post. I am running IE9 under W7 x64 Ultimate. Any help greatly appreciated. Thanks and enjoy, John.

Tripredacus, thanks. The DL link in the site pointed to by your link is broken. I DLed setresolution.script from the guy's site. I tried it on a VM but Wscript will not run it. Perhaps it needs to be compiled into an .exe - don't know how. I tried to find setresolution-x64.exe with no luck. Any ideas. Thanks and enjoy, John.

OK, I have successfully installed the Catalyst driver using drvload after updating the Registry (WinPECacheThreshold to x200 and DXGKrnl service set) in the mounted image. I can see the AMD driver in DriverView and devcon driverfiles and drivernodes. Next I will try to inject the driver. Enjoy, John. EDIT: Injecting the driver did not result in seeing the driver in use when I booted WinPE. I can see the driver in the System32\FileRepository folder. I use drvload to load the driver and again can see it in DriverView and DevCon but the screen is still in low resolution so I am not sure if the Catalyst driver is really being used. No reboot was requested. But I see a Videoprt.sys (Video Port) in DriverView. I took a quick shot at installing the Catalyst Control Center, but the installer is a 32 bit PE. Is there a way to try to change the resolution? I am using an Unattend.xml file with the resolution set to 1920:1080.

Thanks, JFX. Only have one machine with 16 GB memory. I'm not using a driver package, just injecting SDD and RAID drivers now and would like to try Catalyst. Thanks and enjoy, John.

submix8c, thanks for your reply. I had not planned on adding CCC, just the driver. I am really only interested in testing the driver (hope I can inject it) and learning something. I do use CCC on my W7 system but I don't plan on using WinPE for more than testing and starting W7 flat install. I guess the first three (post #12) is all that is needed to get the driver going but I use the CCC also. I simply run the DLed .exe suite, and then capture the files I need from the "%SystemDisk%\AMD\Support\12-8_vista_win7_win8_64_dd_ccc_whql" directory. This time I wanted to install the package on my system but usually I just Cancel the installer at this point. Thanks and enjoy, John.

Thanks, JFX. I was thinking off-line Registry changes were needed - the PE3-SYSTEM key was the hint. It looks like the WinPECacheThreshold defaults to 32 MB, which is way too small for the Catalyst driver (folder is 129 MB). Is there any reason not to set it to x200 (512MB)? Will I be able to inject the Catalyst driver to the image with these changes? Thanks and enjoy, John.

wimb, I gave it a try with no luck. First the Registry update failed with "Error accessing the Registry". I did not see a PE3-SYSTEM key in LOCAL_MACHINE, so I changed it to SYSTEM. I was then able to load the key. When I try to run drvload against the Catalyst .inf file I get "Unable to load driver x80070070". Searching seems to indicate that this means out of space but I am not sure this applies to drvload. Where can I find the error codes that go with drvload? Was I correct in changing PE3-SYSTEM to SYSTEM? Do I need more than the 8 files and Registry update? I am not inclined to go all the way to the build talked about in the referenced thread. Thanks and enjoy, John. EDIT: In my Registry the key in the link (HKEY_LOCAL_MACHINE\PE3-SYSTEM\ControlSet001\services\DXGKrnl), without the PE3-, has a sub key, Enum: [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\DXGKrnl\Enum] "0"="Root\\LEGACY_DXGKRNL\\0000" "Count"=dword:00000001 "NextInstance"=dword:00000001 Do I need this?

jaclaz, I agree this is really strange. I do not understand why a vendor would release SW that uses some 'different' compression technique that the average user (even enthusiast) cannot extract. It looks like AMD has quit but not nVidia. They may have a name list or their own internal extractor SW. The latter is my suspicion. Thanks for all the work, adding to my knowledge base. Enjoy, John.

Tripredacus, thanks. I should have said my real intent is to test my new video driver (preferably injected) on HW without doing a W7 install. wimb, thanks also. As I infer, I should run the Registry file on WinPE after placing the listed files into the System32 folder, then use drvload to install the video driver. Is this correct? I noticed that the author stated that the nVidia drivers required a Restart. Probably Catalyst also? I would like to use the injected driver but it sounds like this is not possible. Thanks to both and enjoy, John.

jaclaz, attached are all three versions of two files from tomasz86's nVidia driver. The xx_ is the original, the xx file is the "Expand -r" and the last is the 7-zip extracted. One 7-zip extracted with no extension (nvuninst). Enjoy, John. EDIT: tomasz86, have you tried to inject this nVidia driver into an image - results? What.7z

I am trying to add Catalyst video drivers to WinPE3.0 x64. I injected the driver with no problems and can see the folder/files in the Windows\System32\DriverStore\FileRepository directory. But when I boot WinPE and use DriverView (also have DevCon available), the injected driver is not being used. I found some old threads here saying I needed to install PnP, but this was in XP days. Is this true and if so how do I do that? What I would like to know is how to get the injected video driver to be the running one. Thanks and enjoy, John.

Sorry, jaclaz, did not know what you were looking for. I DLed a couple of old Catalyst drivers and cannot find a .xx_ file that does not yield the correct name when 'expand -r' is used. What I do not know is if the older drivers will inject. If it is really important to you, I'll see if I can find the AMD forum thread to determine the exact driver version I had a problem with. I cannot say with absolute conviction that it was the name problem that kept the driver from injecting. I can only say when I used 7-Zip (v9.20) to extract the files, I could inject them. Enjoy, John.

I have none of the older Catalyst files and the 12.8 has no .in_ files in it. Attached is a driver (7-Zipped). Using expand with the -r switch extracts and restores the original file name. I infer that the file was compressed with the -r switch. Enjoy, John.atikmpag.7z