Tripredacus

While coming to MSFN may help your typing English, it probably will not help with the spoken language. Then again, it might not help with the typing either... have you seen how some of these guys spell?!

Indeed!

Unfortunately, Verizon isn't here in Eastern Europe... Well Verizon isn't the only one doing it. I think from all fiber based TV providers are doing it for competition reasons. When I worked for Verizon (4 years ago) they had the tech but it was still in testing, I think it still is. However a client of mine was having a conversation a couple weeks ago, he said they have that where he lives. I forget the name of the company, it isn't Verizon, but he lives in Canada. How lucky he is! But I've seen recently at stores some high-end HDTV routers but they don't seem to be good sellers yet.

I'd like to do a little research here and see if anyone else is having this problem. So far I have encountered 4 Intel motherboards that run memory at the wrong speed. I am limited in what boards and memory I can use. Also on our non-Intel boards we cannot see what speed the memory is running at. It is possible that some of you guys may have this problem too and not even know it! Symptoms 1. DDR2 800MHz memory is read properly (SPD) in the BIOS but the actual running speed is 667MHz and the timings are wrong. 2. Windows 7 Recovery environment and/or Windows PE 2.x - 3.0 runs very slow. At first we did not notice that this was happening until WinPE ran slow on a couple machines. Normal boot time (PXE) for my custom WinPE 3.0 x64 is 3-4 minutes. On machines running the memory at the wrong speed it would take over an hour. Oddities Let's take a machine with 2x2GB sticks of DDR2 800, total 4GB. Of course this runs at 667MHz. 90% of the time, Win PE does not work properly. Then take out one stick and then Win PE works normal speed. Also works fine with 2x1GB sticks. It is determined that the memory is not the problem, but the board OR in some cases the BIOS version. We can take the memory and put it in another board and it runs at the normal speed and timing. We have since realised that Win PE does not always act slow when the memory is at the wrong speed, so we now check the speeds on everything, and we are finding too many with this problem. Now, if we decide to "overclock" the memory to the correct speed the system will run fine with 4GB. However this is not a viable option, as if you were to load defaults in the BIOS, it could cause big problems! And who knows what the end users do with these things once deployed into the field! It occurs to me that this may not necessarily be an Intel only problem but it may also be related (in some complex way that i could not explain) to other boards that have had the 4GB memory issue. Platforms that do not run properly 1. Windows PE v2.1 x86 from CD-ROM 2. Windows PE v2.1 x86 from PXE 3. Windows PE v3.0 x86 from PXE 4. Windows PE v3.0 x64 from PXE 5. Windows 7 Recovery Environment The last part, #5 was only tested because I did a full system check early on. So we start with a machine with 2x2GB. WinPE runs very slow. Shut down the machine, take a stick out, Win PE runs normally. Then put a Windows 7 image on the hard drive. Shut down the machine. Put the stick back in. Boot into Windows 7. At this point, Windows 7 runs fine. Then I sysprep the machine, reboot and set up the user. Everything runs fine unless I do a "repair" via WinRE. Affected boards - Intel DG45ID with stock BIOS: updating to current runs memory at 800. - Intel DG41TY all versions - Intel DG43NB all versions - Intel DQ45CB with stock BIOS: updating to current runs memory at 800. Boards not affected - Intel DG31PR all versions I would like to post the memory used but I don't have specific part numbers. If any of you find your memory is running at the wrong speed, please post what memory you have, perhaps this will help. We have had this problem with Crucial and Micron (Avant) memory so far. We do not stock any other kind to test. OK that's enough typing! Let me know your ideas, thoughts, or other useful information. Also if you have seen this issue too, please post the board, BIOS version and kind of memory used, even if it isn't an Intel board.

What is in your setupact.log file? There may be more information there. Also, did you remove that DLL either physically or in the registry at all? Also, what programs are you installing before running sysprep? Would one happen to be anti-virus?

Well some things never die I guess. It looks better than the original, but only for the hardcore fan or those still stuck in HL2 land.

I bet you're going to love it when Verizon releases the WiFi HD TV equipment to the public! Just think, TV signal from the FiOS router wireless to any TV!

Are you asking how much it would cost to write a program similar to that one? Or looking for similar programs and their costs? I only know Total Video Converter, which handles audio files even if the name nor website says it does. The Audacity project on SourceForge also can do audio conversion and has plugins to get other features.

Crosspost: http://www.msfn.org/board/index.php?showto...mp;#entry906517 Verbal warning about crosspost, read the forum rules please.

Did you get it on the first try?

Welcome to the MSFN!

Try this: http://support.microsoft.com/kb/310426 WinPE has a regedit built in, but you probably need to load the hive and edit the PE's registry from another machine.

Hey, I am having the same problem. Can someone show me step by step how to use drvload.exe "location of driver.inf" and wpeutil initalizenetwork. The drivers are realtek RLT8102 by the way, I am not sure i inserting the message correctly. I am tired. Well those ARE the commands. drvload e:\folder\driver.inf wpeutil initializenetwork You type that in the CMD in Windows PE.

You could use AppLocker to block the ability to run Netsh.exe from any user or group on the computer. http://technet.microsoft.com/en-us/library...28WS.10%29.aspx

This isn't a "default" path. When you choose to change the icon for anything, Windows will load the current library from which the current icon is from. So the reason why SHELL32.dll is always there for a folder is because the default folder icon is stored in SHELL32.dll. You would need to change the default folder icon (OS wide) to something that is in IMAGERES.DLL to get that library to show up when you go to change a folder's icon.

Well I feel the same way about certain topics, but its just that many of us here can be specialized in a certain area. The other thing is that there are many of these specialties on this forum so it can be overwhelming sometimes. I find its best just not to go into forums that I have no idea what is going on.

Pat Benatar - Hit Me With Your Best Shot

Dreamweaver has its good parts. Now after using CS4 a little bit, I still find that it can crash when directly editing CSS files, which was a bug that goes back to Dreamweaver 2. But for me, the only things useful about it are the code coloring and the Site panel/link changer.

WinPE registry is similar to regular windows. You can try to change ownership of that registry key to say, a service rather than the main account. That way, the key can be read but not changed. I can't remember how to change that atm. Just an idea!

I agree, reposts from other blogs or forums should have their source URL included with the post. This not only will alleviate the problem Jaclaz had in thinking it was something you (gosh) was working on, but it also will stop the original authors from thinking someone is stealing their work. This has come up on other forums in the past, and it is best to cite your sources, although you don't have to go TOW crazy.

I don't know of a tool like this, especially not one with sounds. Moving to network forum, best place for this kinda thread!

The Chasm - The Eclipse: Monument to the Empire

There are two steps you can try, one is a test and the other is the fallback in case the test does not work. The first, which is your fallback, is in case you have to reload Vista and want to keep things like your settings, emails, etc. And that is to use the User State Migration Tool. It is designed to take your settings from one OS to another. Instructions are all here: http://technet.microsoft.com/en-us/library...28WS.10%29.aspx Once you get your settings backed up, you can TRY to migration your OS in one of 2 ways, both involve using Sysprep. It is located in C:\Windows\System32\Sysprep. Here are your 2 different methods: 1. Sysprep /oobe /shutdown 2. Sysprep /oobe /generalize /shutdown You choose the first option IF the hardware in the destination computer is very similar, such as having the same chipset but most importantly SAME Mass Storage Controller. For example, if your current motherboard uses an Intel ICH9 and your new one does also, then this may work. While the other motherboard components may not end up being installed, if you stay on the same Mass Storage Controller, you will at least be able to boot into the OS. Otherwise, if you are moving to a different Mass Storage Controller, when you boot up, you'll get a STOP 0x7b. Option 2 if for moving to different hardware altogether. However there is a caveat to be aware of. If your Vista install does not already have support for your new Mass Storage Controller you will have to inject the drivers into the OS. This would require capturing the drive with ImageX and injecting the drivers with the WAIK. NOTE: you can only use the WAIK version for your version of Vista. You can't use the current one for Windows 7 as DISM will give you an error. This would also mean you need WinPE media and another drive (external hard drive, network share) to put your image on. There may be other options that I do not specialize in however. I don't know everything! In addition, if you generalize, Sysprep will remove any PnP drivers from your OS and you'll have to create a new User account in Welcome. Of course you can always delete this account and log in with your original one if you want. You should get that choice on the reboot. After either of these options, you can transfer the hard drive to the new PC. Now, what to do if it won't boot into Vista and you get an error? Well there are a couple options left. If this is a hard drive from an OEM computer, it may have a recovery partition. You get to it (usually) by pressing F8 and there should be a Repair option in the menu. It may be another key. If you don't have this kind of drive then you can also fix the problem with a Vista install DVD. In either case, you would want to do a repair install, or it may say "repair windows" or something to that effect. So, whether you can migrate the drive with just sysprep, or you do a repair install, after you are all back up, you use USMT to restore your original settings. However, repair install is usually good enough at keeping your old settings, but some shortcuts might not work among other things. If this seems too much, then just start clean. I can make no promises that any of these options will work out perfectly, except for the USMT which will work in either case. Hopefully everything works out for you.

Welcome back! If you do not remember your old username, and want to see if we can find it, send me a PM.

That's how I started here I think... I actually can't remember.