RegCreateKeyEx failed;code 5

[Xeander]

when I attempt to install  I Get

Error Creating Registry Key
HKEY_CLASSES_ROOT\.tvp

RegCreateKeyEx failed;code 5

any ideas?

[darqSHADOW]

What OS are you on?  That's the system trying to register the file types, not sure why that would fail.  Did the install complete or fail because of that?

John

[Xeander]

I am using Win Xp Pro purchased from Microsoft online 2 year ago

ver 6.3 installed with no problem
yes I was aware it was trying to register a file type
the file type is .tvp Nview profile file
used by my video driver files to store desktop profile rules

from NVIDIA

I ran an online search for .tvp

http://filext.com/file-extension/TVP

found this data clearly showing that NVidia has
registered this file type for use with GeForce driver files
as a  profile info save file type

so why is it used in this version? 6.5?

what are the odds that the target computer may be using
a Nvidia driver file?

[RuntimeError101]

TVP is a particle system file.  Try installing only the sdk (not the full installer).

[SylvainTV]

Ah weird didn't know that TVP was already used by another program. It could cause issues indeed. I guess we will add a dialog to the setup to ask about file associations.

[FiziK]

I dont know when the last time you updated your drivers but u could try that. Also are u running any firewall?

[darqSHADOW]

As I said in reply to your PM, this does not replace the association, it only adds to it.  When you right click the ParticleEditor it should be an Open With option if you already had something associated to TVP.

I also use Nvidia's tools and the installer works w/o issue, this was fully tested on the QA boxes.

John

[Xeander]

I reinstalled the 6.5 demo package

I get JIT failed to run error
0x888 cordbg.exe 02(2)

my registry has a DWord of 000000001 for JIT enabled

this ran on my machine a few month ago

any ideas?

[Xeander]

Ok I manually attached my debugger and this is what i get


*** wait with pending attach
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 11000000 11026000   C:\Program Files\TV3D SDK 6.5\tv3demo\TV3Demo.exe
ModLoad: 7c900000 7c9af000   C:\WINDOWS\system32\ntdll.dll
ModLoad: 79000000 79046000   C:\WINDOWS\system32\mscoree.dll
ModLoad: 7c800000 7c8f6000   C:\WINDOWS\system32\KERNEL32.dll
ModLoad: 77dd0000 77e6b000   C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f02000   C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000   C:\WINDOWS\system32\Secur32.dll
ModLoad: 77f60000 77fd6000   C:\WINDOWS\system32\SHLWAPI.dll
ModLoad: 77f10000 77f59000   C:\WINDOWS\system32\GDI32.dll
ModLoad: 7e410000 7e4a1000   C:\WINDOWS\system32\USER32.dll
ModLoad: 77c10000 77c68000   C:\WINDOWS\system32\msvcrt.dll
ModLoad: 76390000 763ad000   C:\WINDOWS\system32\IMM32.DLL
ModLoad: 629c0000 629c9000   C:\WINDOWS\system32\LPK.DLL
ModLoad: 74d90000 74dfb000   C:\WINDOWS\system32\USP10.dll
ModLoad: 791b0000 79419000   c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll
ModLoad: 7c340000 7c396000   c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\MSVCR71.dll
ModLoad: 008c0000 00905000   c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\fusion.dll
ModLoad: 774e0000 7761d000   C:\WINDOWS\system32\ole32.dll
ModLoad: 7c9c0000 7d1d7000   C:\WINDOWS\system32\SHELL32.dll
ModLoad: 773d0000 774d3000   C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
ModLoad: 5d090000 5d12a000   C:\WINDOWS\system32\comctl32.dll
ModLoad: 79780000 7998e000   c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll
ModLoad: 79990000 79cce000   c:\windows\assembly\nativeimages1_v1.1.4322\mscorlib\1.0.5000.0__b77a5c561934e089_361cafa0\mscorlib.dll
ModLoad: 79510000 79523000   c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorsn.dll
ModLoad: 5ad70000 5ada8000   C:\WINDOWS\system32\uxtheme.dll
ModLoad: 74720000 7476c000   C:\WINDOWS\system32\MSCTF.dll
ModLoad: 65b70000 65b8b000   C:\Program Files\Qwest\QuickCare\bin\sprthook.dll
ModLoad: 74c80000 74cac000   C:\WINDOWS\system32\OLEACC.dll
ModLoad: 76080000 760e5000   C:\WINDOWS\system32\MSVCP60.dll
ModLoad: 77120000 771ab000   C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 7b610000 7b808000   c:\windows\assembly\gac\system.windows.forms\1.0.5000.0__b77a5c561934e089\system.windows.forms.dll
ModLoad: 7b810000 7baf2000   c:\windows\assembly\nativeimages1_v1.1.4322\system.windows.forms\1.0.5000.0__b77a5c561934e089_359b1471\system.windows.forms.dll
ModLoad: 7b0a0000 7b1d0000   c:\windows\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll
ModLoad: 7b1d0000 7b3b4000   c:\windows\assembly\nativeimages1_v1.1.4322\system\1.0.5000.0__b77a5c561934e089_493ae865\system.dll
ModLoad: 00e00000 010c5000   C:\WINDOWS\system32\xpsp2res.dll
(a58.138): Break instruction exception - code 80000003 (first chance)
eax=7ffd9000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005
eip=7c90120e esp=010dffcc ebp=010dfff4 iopl=0         nv up ei pl zr na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\ntdll.dll -
ntdll!DbgBreakPoint:
7c90120e cc              int     3


Is this an error in install of TV3d or is an error in my system setup?
and if so why now after I installed this in January and it ran?

could this because Microsoft just updated me to SP3??
there is a ver of xpsp2res.dll as xpsp3res.dll present in win/sys32 dir

Found this on the BREAK ERROR
a debugger message that indicates a single deferred procedure call (DPC) was executing for longer than one second. This serves as a good illustration of the type of checks implemented in the checked build. This breakpoint means that a driver has spent an unusually long time in a DPC routine, which could be a symptom of a serious driver problem. On the other hand, this breakpoint can also occur if the driver generates a large amount of debug output in its DPC routine, thereby extending the length of time required for the DPC to execute. Examining what the DPC routine is doing, and continuing past the breakpoint once or twice, will usually result in discovering the underlying cause of the problem.


Well it is definetly a result of a Microsoft update

Windows XP SP3 updated on 4/13/2008 at about 5 PM my time
and NTTDLL was last modified at 5:11 PM on 4/13/2008

Let me guess there may be issues with TV3D and XP SP3 ?

the NTTDLL file is causing the break point in load

[TecnoBacon]

One Thought,

When I installed 6.5 it did not remove  the last version from the registry and install group. Try going to your installed program group in control panel and remove both and re-install if both are there. Worked for me.

[Xeander]

not my problem
I completely reformatted my PC
reinstalled OS and programs
just got to re install of TV3D

but this install follows a patch to SP3 under XP Pro

most of the roles I had assigned to this PC are now in use on my
local server a dual proc Win 2003 Server

somewhere something I had installed over came this problem
the NTdll used by windows XP was ver 2 in the system32 directory
it was modified during the patch up to SP3 and may be the cause of program failure to execute

the Break point is always at ntdll

other errors like JIT not found even when running on PC are TV3D errors
and the loss of Symbols path is DEBUGGER config error on my end I have to reseed
the path each time i use it (i prefer it that way)

but simply put the only variation I see this time is a modified ntdll from Microsoft update
of SP3 for WIn XP Pro  and a crash of TV3D at ntdll due to excess response times exceeding
1 actual second of time meaning my PC cant establish a full read and break from ntdll
in 2.3 million machine cycles of CPU execution time. This is most likely HARDWARE
based error may indicate a HD cabling problem in the works
or could be one of my DUAL DAC's is going bad
or could be something associated with NETWORK setup

I am researching it .. however I have about 6 3D engines under review
and delays in viewing current status of this one may cause me to just
move along.. But my team likes the blogs on this particular project's
expected progress and final solution.

The original error I had was minor the .tvp asscociation problem came from
DUAL view of Nvideo profiles
switching PC to SIngle monitor and thus using default profile management
corrected the duplicate file extentions association.

However the .tvp file association is publicly avail as used by NVidia
years prior to the use by TV3D and my comment was isn't it just simpler
to change the file name extention from .tvp to something else

rather than expect NVidia to change thiers?
or limit users of TV3D to single monitor non profiled desktops?
or manually associate extension usage with each use?

It was a simple question made 5 months ago and apparently
instead of not putting red thread on the green monster
we are.

[Waterman]

Sounds like a tricky problem...
---
Your style of writing and breaking the lines, case usage and punctuation very much reminds me of a former tv3d user called... hm was it Netframeworker? Would that be you?

[Xeander]

No but he must had a very long background in assembler as well

we tend to think and write like code rather than english