LLXX

Google 'BartPE'.

You're lucky you didn't burn your CPU. It's called Thermal Compound. It's mandatory for the new CPUs, as they produce so much heat they'll overheat without the compound to transfer the heat.

According to http://msdn.microsoft.com/vstudio/express/visualc/ the Express version does support "native" (i.e. non-.NET) application production. Since Express is just a reduced version of the full Visual Studio, I believe it can do the same as well. Edit: For some reason, the newer compilers tend to produce more bloated code. If you want smaller programs, use an older version of the native C++ compiler.

Are the speakers and the computer plugged into the same outlet (or preferably, through the same surge suppressor)? This buzzing may be caused by something known as a "ground loop", i.e. the voltage levels between outlets vary slightly that there is a constant current through the speaker cable at rest.

Athlon... check to ensure it's not overheating. I recently serviced a system that was displaying the same symptoms. The CPU was idling at 52°C. After cleaning out the fan and heatsink, the temperatures decreased to low 30s and the system was stable again.

I may consider it. It seems that the driver file is not locked and can be replaced while Windows is running

...I'm still working on it though @glaurung: I believe M$ is using a private tool to generate these INFs. I guess I'll just use the relational DDF method... or maybe a script to replace the CAB numbers in the original layout INFs with the correct ones.

It's a small and fast image editor, I use it for simple editing. If I need anything more complicated, I use Photoshop (still using 7.0).

This looks like a hardware problem, specfically the mobo. Error 05 is "disk controller reset failed".

You will definitely see better performance, on any OS, since the hardware is faster. If I remember correctly, benchmarking tests showed that the Conroe's 32-bit performance is better than its 64-bit.

If you have two ethernet adapters in your machine, Windows can use both of them.

Idling: low 30s. Full load: not exceeding 60°

Trojans are usually self-contained and don't spread to other files, whereas virii will infect other files (they're parasitic). It seems you have the latter, in which case a reinstall is highly recommended.

http://www.robvanderwoude.com/regedit.html Section "Removing registry entries"

I doubt he's using 64-bit XP, as there is a separate Forum for that (http://www.msfn.org/board/index.php?showforum=104)

I've inspected the layout INF files in more detail, and it seems that there is no pattern to how the files are listed, although they are in numerical order; for example, the following files are listed as free-floating in file 1: dossetup.bin=0,,85050 suback.bin=0,,229680 w98setup.bin=0,,168096 chl99.cab=0,,14451 mini.cab=0,,686042 deltemp.com=0,,496 save32.com=0,,920 scanprog.exe=0,,4438 setup.exe=0,,5712 smartdrv.exe=0,,45379 sucatreg.exe=0,,77824 wb16off.exe=0,,537 xmsmmgr.exe=0,,14144 scandisk.pif=0,,995 setup0.wav=0,,439824 setup1.wav=0,,14924 setup2.wav=0,,14992In the second file, only one file is listed as free-floating. scandisk.exe=0,,143818The third, which does not list any files from CAB 1: setup.txt=0,,52294 What was M$'s intention in doing it this way? If I just split the output INF into three equal parts sequentially, the setup doesn't work.

No. You mean you don't even know what version of Windows you're using? If you know enough to know about this problem, you should know which driver to install.

Set language for non-unicode programs to Japanese. In Language control panel applet.

Take a look through the Unattended forum. There should be information there regarding OEM-specific installs.

Just disable automatic updates and do it manually...

Delphi is even more bloated, all the apps I've seen are at least 100Kb. At least it's a little faster... Agree to that.Would you like to code a Delphi version of this simple program, and then a Visual C version?

I doubt it is possible to obtain the serial number of the battery through software, you have to remove it and physically look at it.

Probably the hard drive, when it's warmed up it reads/writes fine but on a cold start makes various errors.

ALL hard drives are sensitive to vibration, but as it is impossible to maintain 100% lateral alignment of the head with the platters via the magnetic actuator, and in a design with higher densities the head does not have as much tolerance of movement before it reads the wrong track or sector. The timing requirements are also much tighter at high densities, and a small lateral movement of the head can result in read/write timing varying a tiny amount, but enough to cause an error.

http://www.google.ca/search?hl=en&ie=I...of%22&meta= Finds http://ftp.saix.net/pub/simtelnet/winnt/secsys/ The company itself seems to have gone under. I doubt it's commercial software anymore.