Hello. Can anyone tell me how to backtrack a files origin? I've got this .txt file called CPUInfo.txt and I'd like to know what program or service is creating it. If I delete the file it returns on the next startup.

Im going to guess its the program CPUinfo.

nope no program or process by that name on my computer...

what programs and service are on your computer?.
and look through all of your programs and service it is just about finding out what is not causing the files.

Well there's heaps of different programs that can create a cpuinfo.txt file.

To name just 3 of them:
CPUZ
RMClock
CPUinfo as already stated above by AMDPhenomX4 which you not too politely disregarded.

It really could be any number of programs creating this file - please post back with the exact path of the file and we may be able to help you better.

Where abouts is the .txt file being created? On your desktop?

CPUInfo

cpuinfo consists in an API/library used by programs to get information about the underlying CPU. Such information include CPU vendor, model name, cache hierarchy, and supported features (e.g. CMP, SMT, SIMD). cpuinfo is also a standalone program to demonstrate the use of this API.

Loads of examples:

Projects

• [2007/07/15] cpuinfo
  cpuinfo is a simple library and program used to retrieve some information about the underlying CPU. e.g. model name, caches hierarchy, processor features. It currently supports x86, ia64, ppc and mips architectures.

• [2007/08/26] nspluginwrapper
  nspluginwrapper consists in a proxy plugin and a viewer for Netscape 4 (NPAPI) compatible plugins. It makes it possible to use 32-bit x86 plugins like Flash Player or Real Player on Linux/x86_64, NetBSD and FreeBSD platforms.

Macintosh Emulation

• [2006/05/01] Basilisk II JIT
  Basilisk II is an Open Source 68k Macintosh emulator. It supports Apple operating systems up to MacOS 8.1. The Basilisk II JIT project aims at improving the emulation performance with dynamic translation technology, also known as just-in-time (JIT) compilation.

• [2006/05/15] SheepShaver
  SheepShaver is the first PowerMac G4 emulator for non-PowerPC platforms capable to run MacOS 7.5.2 up to 9.0.4. It provides a basic JIT implementation but still performs decently. On PowerPC platforms, no CPU emulation is performed to reach near native speeds.

• [2005/03/16] Benchmarks
  The benchmarks section tries to evaluate the performance of various MacOS emulators. So far, only Basilisk II, SheepShaver and PearPC are compared against a real PowerMac system.

CPU Emulator Testers

• [2007/07/08] M68K Emulator Testsuite
  Large testsuite (118 million tests) supporting several CPU emulation engines including QEMU and UAE-based cores. It was helpful to hunt remaining emulation bugs in Basilisk II. This might be useful to other M68K Emulator authors too.

• [2006/07/04] PowerPC Emulator Testsuite
  Small testsuite I wrote while developing the SheepShaver PowerPC Emulator. It was helpful to me for reducing development and testing time. This might be useful to other PowerPC Emulator authors too.

Virtualization

• [2006/03/17] QEMU
  QEMU is a generic and Open Source processor emulator from Fabrice Bellard. This page contains some patches I wrote for QEMU. e.g. the initial port to MacOS X for Intel platforms.

• [2007/06/06] VirtualBox OSE packages for Mandriva Linux
  VirtualBox is a general-purpose full virtualizer for x86 hardware. This page only hosts x86-64 packages for older Mandriva Linux distributions. Additional patches are available in the source RPM.

CPUInfo 1.0-Prerelease [Web > Gwenole Beauchesne]

CPUInfo updates [Web > Gwenole Beauchesne]

This should answer a few questions for you.

However there are many things that can be similar to this CPUInfo.txt file.Would you like us to list the hunders that are out there?

AMDPhenom I belive is proberly right in what he said.