

PDFs can be read and processed on just about any system, so it should be a standard practice to save PDF to and from other file types. First run Regedit.exe from a CMD prompt (I raised its security level to Administrator, just in case) then search the Registry (by clicking on Edit/Find. The PDF format was created to fulfill the dream of a paperless workspace. Free to use online, no installation required. Page File: 2730MB used, 15905MB availableĭevice Key: Enum\PCI\VEN_10DE&DEV_0FC6&SUBSYS_84311043&REV_A1Ĭurrent Mode: 1680 x 1050 (32 bit) (59Hz)ĭriver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2umįeature Levels: 11.0,10.1,10.0,9.3,9.2,9. Create PDF files from various file formats, such as images, PPT, Excel, and Word. But so long as PDFCreator does actually create the pdf file I can live with the problem. Go to the Windows Start menu (then Run on WinXP). This problem did not happen before and I'm puzzled why it should have started now. In the simplest terms possible, this registry hive contains the necessary information for Windows to know what. Yes, I can now confirm that the pdf file has in fact been created and it seems that the problem solely relates to PDFCreator trying to use PDF Architect 7 to display the file. Processor: Intel(R) Core(TM) i5-3350P CPU 3.10GHz (4 CPUs), ~3.1GHz HKEYCLASSESROOT, often shortened as HKCR, is a registry hive in the Windows Registry and contains file extension association information, as well as a programmatic identifier (ProgID), Class ID (CLSID), and Interface ID (IID) data. Get the message 'Cant get CLSID for PDF Creator Pilot' Was printing until Monday afternoon just fine. System Manufacturer: ASUSTeK COMPUTER INC. Language: English (Regional Setting: English)
