Tripredacus

LOL thanks for reminding me about how I was a Cyrix VAR. When they went under, I got grandfathered into being a National Semiconductor VAR, but I had stopped needing that ability, plus i didn't know anyone that was interested in buying ICs...

You can find instructions on building a CD from IcemanND's guide stickied in this forum. As far as licensing goes, you can use it all you want, but you can't sell it. You can use it in a commercial product, such as via WinRE and you can charge extra for providing a backup or recovery service, but not for the winPE itself.

I'm sure if the WAIK has it, but the OPK tools (vista servicing 1.1) comes with an SDK. If you do have the SDK, check out the Component Platform Interface (CPI) Reference and Windows Imaging Interface Reference CHMs.

OK you mean you moved the Recycle Bin and did not actually delete it? try make new shortcut. Put path to be the following: explorer.exe ::{645FF040-5081-101B-9F08-00AA002F954E} Test putting that line in your run box first to make sure it opens the recycle bin.

Administrator Tools\Active Directory Users and Computers

If you are in the corporate or hobbyist environment, get the WAIK (Microsoft Windows Automated Install Kit) or if you are in the OEM channel you can use the Microsoft OPK (Vista SP1 servicing edition). It will walk you through creating the boot media in which you can use PXE or a CD-ROM to boot the clients with. You can do everything manually or get a program to install into the Win PE (your boot media) that makes it easier on you. As for setting up a PXE server, see my sig. IcemanND has a good WinPE/ImageX guide in the WinPE forum. I use Geezery's GiMagex COM object HTA program in my WinPE. I recommend you learn how to use the command prompt in the PE before trying out someone's program, because sometimes you have to do it manually if something isn't working right.

The things that are loaded can be seen in MSCONFIG both under startup and services tab. Also items in the registry, such as the RUN key. Usually failures will get logged in Event Viewer, or you can create an Audit Policy to report failures to the Security log as well.

Battery removal is almost instant. You don't need to wait 30 minutes. Also some motherboards have a BIOS backup built-in that you can make it reload using a different jumper than the reset one.

The computer used to be the master browser but rebooted. Then one of the other computers gets to be the master browser. I don't know how to check for sure which one it is. Maybe you could post your error here from the event viewer?

I voted Intel. I used to work for Sony so I kinda like them but only half of their products are good to me.

Any time it comes to me wanting a new PC, I'll look and see what I can get. So maybe there is a computer I can buy that has exactly what I want, but usually this isn't the case. So I have to build it instead.

I do not know when dual booting first came about, but I know you could do a dual with Windows 95 and Linux. I am also not sure if Netware 4.1 and earlier counts. Netware is an OS but it required DOS in order to launch. This might open up the whole OS vs Shell debate so I'm not sure if Netware counts. Also, not sure is concurrent DOS counts as being more than one OS or not... Virtualization is a lot better because it allows you to use more than one OS install at once. Obviously Dual Boot you can only use one at a time.

I've been told that I am pretty fast but I never got measured before.

Try enforcing power settings through Local Computer Policy. You will find it under Administrator Templates\System\Power Management. It has options for both plugged in and on battery.

Is your shell so large it can't run off the ramdisk?

You should be able to do it the same way as in XP or Vista. When you go to Personalize, there is a link on the left that says 'Change Desktop Icons'. Then you can check the box like in XP. Here is a picture of these menus here: http://www.howtogeek.com/howto/windows-vis...-windows-vista/

Reassign Admin B to a lower user group, such as Backup Operators, and remove from that domain administrator group.

Reading through this document, I am beginning to think of how Windows goes about sharing DLLs (or other files) in the first place. If anyone has ever run filemon, you notice that programs spend a large amount of time trying to find the files they need. They first look in the app dir, then they look in c: and then they look in c:\windows. Typically, most of the shared (or system) files programs try to use are sitting in c:\windows but they will constantly search other places first. And programs don't seem to learn where these files are, so next time you open that program, it goes through its searching all over again. When I worked as a desktop applications programmer, is when I first found this behaviour. After checking with our other programmers and the source code, it was determined that this behaviour either comes from the compiler's instructions or Windows itself. In the idea of speeding up application calls, don't you think that this could be something that could be also fixed? I know this borders on a System bug or inadequacy and not so much related to DLL Hell, but I figured I'd post it.

msizap.exe would not identify any orphan MSI/MSP file ; it's meant to cleanup the registry and not the harddisk... quite the opposite of your objective ? You asked for DOS commands ? hmm ? Here is a tested and working batch that will cleanup orphaned MSI/MSP files (i've just made it, and it found 6 MSP to delete on my disk -- thank you for the idea). Additionaly it will delete any TMP files, so be sure to run the batch after a clean reboot, or when you have no installation/uninstallation pending. Important : no backup is made. but you may replace the del/f/a/q command by a move one... @REM ***** copy/paste this in a file named "CleanMSIP.cmd" then run it ***** @echo off REM go to the mess cd/d %systemroot%\Installer REM get all available info from registry reg export HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData UD.reg REM convert Unicode to ASCII and keep only lines containing .ms? type UD.reg | findstr/ri "\.ms." >> UD.txt REM for each file in the folder, check if it's in the list, and delete (only) if not for %%i in (*.msi *.msp) do ( findstr/i %%i UD.txt 1>nul || del/f/a/q %%i ) REM delete some temporary and no more needed files del/f/a UD.reg UD.txt *.tmp Note you need full read/write access to the Installer folder... The abstract is to get the list of the registered (thus valid) MSI/MSP files from the registry, then to identify which files from the disk are not in the list. As a consequence, this batch will only clean the Installer folder, leaving any subfolder untouched. You may modify it to compare the subfolders names with the contents of UD.reg to find orphaned folders. PS: about Office : i don't know the exact process of updates, service packs and hotfixes that may be applied to your son's computer ; but, if it was mine, i would : 1/ uninstall Office 2/ reboot 3/ run the above batch 4/ use a dice to decide between the two solutions below : 5a/ go to www.openoffice.org 5b/ reinstall MSOffice, go to office update site, install first the latest service pack, then any other fix Anyway, running the step n°3 may be enough pain... good luck I'd say using a coin would let you reach a decision faster in step 4.

Do you know which motherboard it is? You might be lucky and have a BIOS reset jumper.

I've only used Godaddy, although only on a renewal, prior registrars were Tucows, OpenSRS and AccountSupport (i think) and Hypermart and Xoom, those last two are long gone however.

That is cool. I still use CDex with CDDB to get all my tags filled when I rip from CD. The only real problems is getting stuff on straight DL that are tagged or named wrong. Those are so few in number that it really isn't worth it to me to have such a system.

Fight Club

Transformers!

Updated config info in first post.