Tripredacus

On some notebooks, those special or Fn keys are controlled by a program on the OS. For example, the keys on MSI notebooks will only work if you have the SCM installed. Even a whitebook (barebone) notebook is made by someone. See if you can track down who that is and see if you can find this software.

I don't know if the Recovery DVD will put the recovery partition back on. From looking at my Vista WinRE info, it appears there may only be 2 reasons why it does not give the option anymore: 1. The drive ID number has been changed. 2. The volume GUID has been changed. Unfortunately I can only give these reasons and not be able to assist you in fixing it.

I removed your attachment because you had your product key in it. That path is a protected folder. You normally shouldn't have access to it. It is for system level use. What kind of changes did you make to your base image? Did you move the profiles to another location besides the default?

Well be at ease that your admin decided to go the right way. A lot of times people in companies don't care about their products or service enough to follow rules in license agreements and policies. I guess it all comes down to how much you could possibly lose if you got caught. Anyways, there is always another way to do things. I've learned a lot here myself.

You'd have to test this. i do not know if this works. I adapted your code into an existing AutoIT script I made to pull different info. #include <file.au3> Global $sWMIService, $objWMIService, $colItems, $sName, $oItem $sWMIService = "winmgmts:\\" & @ComputerName & "\root\CIMV2" $objWMIService = ObjGet($sWMIService) IF IsObj($objWMIService) Then $colItems = $objWMIService.ExecQuery("SELECT * FROM Win32_BIOS") If IsObj($colItems) Then For $oItem In $colItems $sName = $oItem.Manufacturer Next EndIf This is an incomplete function. This code doesn't do anything but get the Manufacturer and store it as a variable $sName. I also just declared everything a global. Probably don't need everything but $sName needs to be a global in order for the rest of the script to access it. So now that you have your result stored in $sName, you could verify it with this: MsgBox(64, "Win32_BIOS Item", "manufacturer = " & $sModel) So then now you have this as a global variable, you can do other things with it besides show it in a messagebox. While you can do the multiple IF/Then statements, you should probably use a Switch statement instead.

After install, it wants you to enable auto updates, yes this is true. But if you change your setting to "download and ask" instead of "install automatically" MSE won't complain. That is how I use it.

You can reprogram every key with their software.

I am not familiar with this method. I have written scripts to read from the DMI via WMI but using VBScript and AutoIT and not a cmd file. Moving to scripting forum.

Welcome to the MSFN! As a next step, you should read the license agreement for nLite. You'll find posts all over the nLite forum regarding this, here is an example:

Oh yeah, I forgot about training... or getting docs from Microsoft. Once when I had nothing to do I read the 200 page Office 2010 training book.

This keyboard promises to be the most customizable keyboard ever, but it is also out of mostly everyone's price range: http://www.artlebedev.com/everything/optimus/

I use Heavy Load and Treesize: http://www.jam-software.com/freeware/index.shtml

Some of them are able to be used if you use the ASCII code. There was one code that did get updated when XP came out, and that was the Delete code is now "ignored" by Windows. In Windows 98, if you put the Delete code in a file or folder name, you couldn't open or delete the file from Explorer, only could do things in the command prompt. I am guessing the reason why they still don't let you use those reserved characters is because Windows is still based on the command interpreter, which isn't smart enough to know anything about fonts.

I basically handle my work schedule with projects. If all current projects are completed and I am in relative limbo, I have the following on my list: - testing new recovery partition solutions - develop a thin client that supports video acceleration for burn in - organize files on the file server - rewrite the loader on our USB Boot Keys - test server backup solutions - rewrite websites/test security Otherwise i just throw the football around the office.

In my HTA, yes the value does not update but it actually does in the background. I think this is why the GImagex HTA has a reload button on it... Anyways, what WinPE are you using? In WinPE 3, diskpart commands are recognized instantly by the system, while in WinPE 2, you needed to do rescans or refreshes. I ran into this problem when I was converting my recovery partition to WinPE 3 and didn't know that diskpart updates instantly. I've asked these questions to Microsoft as well (concerning drive letters) when I was having problems fixing drive letters of multiple partitions and custom recovery. Unfortunately, there isn't much you can do about how WinPE assigns letters. Basically you should design your system around how WinPE operates. You could use trickery to re-assign letters to existing partitions (using hidden files) but then you get into trying to fool proof the system. Like what if a user has a USB key plugged in? Well you can't account for every situation!

I don't know if it is important infos, but what are the operating systems on these Domain Contollers?

You will probably get a faster response in the Application Installs section. I shall move this topic there.

I just thought of a new use for this tool... Since I've used PE Explorer before, I know that you can view string values that are registry keys that are written or read from. Can these types of values be changed in your program?

I believe the best practice is always change where the end of the volume is, never where it starts. If this all sounds too scary, maybe just add another drive. if it is a notebook, look at USB storage.

You can try doing this in the registry: http://support.microsoft.com/kb/314054 Time Server info and list links: http://support.microsoft.com/kb/262680

I remember using a registry key in Windows NT 4 that would allow NT to shut down in about 5 seconds. This key held the timeout that Windows allows programs and processes to end themself when given the shutdown command. I believe the default is 30 seconds, but I had changed that key to another value and it shut down a lot faster. I was never really concerned with the shutdown or startup speeds of systems since XP came out, because they are reliable enough to just leave on. Does that registry key still exist?

The period is actually 30 days, but it will only ever show you 3 days at the most on the Properties page. If it ever says 0 days (say on day 4) and you reboot your system, it will say 3 days again.

maybe? http://www.msfn.org/board/forum/42-logonui-boot-screens/

I've had problems in the past with card readers in notebooks that like to take the C drive letter. I got around it by modifying my diskpart script to do something at the beginning: sel vol c assign letter=y