is there an internal crash log that poser uses for users to report errors for help?

[IMG]http://i41.tinypic.com/a10fwi.jpg[/IMG]

here's the debugger call stack

    00000000()    
     MEngineUIReleaseWin32.dll!02a0cd40()     
     [Frames below may be incorrect and/or missing, no symbols loaded for MEngineUIReleaseWin32.dll]    
     MEngineUIReleaseWin32.dll!029ff23e()     
     MEngineUIReleaseWin32.dll!02a2204b()     
     MEngineUIReleaseWin32.dll!029feead()     
     PoserPro.exe!00402d7a()     
     msvcr90.dll!78586774()     
     gdi32.dll!77f176ab()     
     wxmsw291u_core_vc_custom.dll!019f468e()     
     user32.dll!7e418734()     
     user32.dll!7e418816()     
     user32.dll!7e42a013()     
     user32.dll!7e42a039()     
     opengl32.dll!5ed2699b()     
     user32.dll!7e418734()     
     user32.dll!7e418816()     
     user32.dll!7e428ea0()     
     user32.dll!7e428eec()     
     ntdll.dll!7c90e473()     
     user32.dll!7e42aef1()     
     user32.dll!7e42aedc()     
     wxmsw291u_core_vc_custom.dll!019f59c2()     
     PoserPro.exe!00786ded()     
     user32.dll!7e429950()     
     wxmsw291u_core_vc_custom.dll!019f023b()     
     PoserPro.exe!006f60a4()     
     msvcr90.dll!78583db8()     
     msvcr90.dll!78583eb8()     
     wxbase291u_vc_custom.dll!01da679b()     
     wxbase291u_vc_custom.dll!01da6dfc()     
     user32.dll!7e418c3a()     
     wxbase291u_vc_custom.dll!01dcdd7f()     
     msvcr90.dll!78583c1b()     
     wxbase291u_vc_custom.dll!01dcda81()     
     PoserPro.exe!006ee0d1()     
     user32.dll!7e418734()     
     user32.dll!7e418bd9()     
     user32.dll!7e41885a()     
     user32.dll!7e41882a()     
     ntdll.dll!7c916e08()     
     ntdll.dll!7c9161a5()     
     ntdll.dll!7c91554d()     
     ntdll.dll!7c912416()     
     ntdll.dll!7c911028()     
     ntdll.dll!7c911028()     
     ntdll.dll!7c9101db()     
     ntdll.dll!7c910222()     
     ntdll.dll!7c9101db()     
     ntdll.dll!7c910323()     
     ntdll.dll!7c910323()     
     kernel32.dll!7c812cfb()     
     kernel32.dll!7c812de0()     
     kernel32.dll!7c812e35()     
     PoserPro.exe!00a7966c()     
     msvcp90.dll!78484d14()     
     msvcr90.dll!78586293()     
     ntdll.dll!7c90d80a()     
     ntdll.dll!7c9132f0()     
     msvcr90.dll!785435eb()     
     msvcr90.dll!7858cd95()     
     msvcr90.dll!78542e2b()     
     msvcr90.dll!785421e7()     
     msvcr90.dll!7858ce95()     
     PoserPro.exe!00a4c861()     
     PoserPro.exe!00a4c8e7()     
     PoserPro.exe!00af944a()     
     msvcr90.dll!785436c5()     
     msvcr90.dll!785438b3()     
     msvcr90.dll!785438c5()     
     msvcr90.dll!7855c40c()     
     msvcr90.dll!7856028d()     
     PoserPro.exe!006f0043()     
     PoserPro.exe!006c0075()     
     PoserPro.exe!0074006e()     
     PoserPro.exe!0077002d()     
     PoserPro.exe!0077002d()     
     PoserPro.exe!0077002d()     
     PoserPro.exe!0077002d()     
     PoserPro.exe!0077002d()     

Maybe (probably) Poser didn't install correctly. Not an uncommon problem. I would reinstall.

I uninstalled everything, even removed the registry data to reset everything, but same error occured.

if my computer doesn't meet system requirement or driver error, shouldn't there be a proper dialog telling me something went wrong?

I also checked event viewer to see if there's any thing that poser might report there, but nothing either.

What happens when you click 'no' when it asks you if you want to run the debugger?

everything closes and nothing else happens. no poser for me...

Damn, all I could suggest is to open at ticket at SM.

".....if my computer doesn't meet system requirement or driver error, shouldn't there be a proper dialog telling me something went wrong?"

What are your system specs? I assume you're on a 32bit OS as that's what you seem to be installing to - all those 32 errors.

it's intel D945GCLF2 desktop board, it's pretty much a netbook for desktop.

now I know it's crap and I shouldn't try to run poser on this, but I still don't expect the software to just crash instead of giving me a proper dialog box about my low system spec.

I think you just answered your own question.

I have a Toshiba 255 netbook - it will run P7. As in: it will load it. Yay. Render? A pein. IOW, not really. I had installed it so that I could compile matmatic scripts into material shaders on the road. Well, I did. Now, with PP2012, it's not an option anymore.

I'll probably convert it to an Ubuntu thingo and have it run at least normally: Windows Starter is a bit of a gee-golly-whiz OS. And forget running graphics/memory hungry stuff like Poser.

@Robyn?

I run both Poser9 and PP2012 on a little Asus Windows XP Starter on a 10" netbook
AND!
I run both Poser9 and PP2012 on a little Dell Windows 7 Starter on another 10" netbook

Both run flawless, but are pretty slow at rendering anything.

But both interfaces run without a problem.

But???
I keep all my systems super clean....And => Stick to the standard.
Both of these are Super important to run Poser on low spec machines.

• Keep your systems clean.
• Stick to the standard.

They are my 'to go' workhorses.
Not that I do a lot on them, but I test a lot on them, and both run Poser almost every day.

I notice OpenGL in the middle of the call stack. So perhaps it crashed doing something about setting up the preview.

Switch to SreeD and see if you can get it to work.

And, no, software cannot examine your video drivers and tell you that you have a buggy driver that is about to crash. It just crashes.

If you're curious, the "Halting Problem" is one of the oldest and most venerated insights in computer science.

http://en.wikipedia.org/wiki/Halting_problem

Basically it says this: For certain very simple programs, it is possible to decide if it stops or runs forever by analyzing it, but in general it is not possible.

Decades later, a branch of computer science has evolved to define a set of rules and if you stay inside those specific rules, it is possible to solve the halting problem. This branch of computer science is called "formal methods" and it's one of my favorite things in the world.

However, people who write video device drivers and 3-D graphic programs can't even tell you what formal methods are, let alone follow them.

http://en.wikipedia.org/wiki/Formal_methods

Quote - Handwritten proofs of correctness need significant time (and thus money) to produce, with limited utility other than assuring correctness. This makes formal methods more likely to be used in fields where it is possible to perform automated proofs using software, or in cases where the cost of a fault is high. Example: in railway engineering and aerospace engineering, undetected errors may cause death, so formal methods are more popular in this field than in other application areas.

It is the generally few deaths associated with CG that make the economics favor buggy software.

Quote - Switch to SreeD and see if you can get it to work.

can you switch to SreeD in some setting files or can you only do this inside poser? as you can see, I can't use poser right now...

Somehow I knew I was going to end up researching that for you. But I don't have time - have to go to work.

I do know it is somewhere in the main poser preference file. I don't remember the file name or parameter name, but you should be able to find it.

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?message_id=3496836&ebot_calc_page#message_3496836

I used notepad++ to search "sreed" in all files in the program files folder, and although I did get some results, it's hard to determine which one sets the setting.

google doesn't help... it can't even accept sreed as a word

Search on your system for a file called : Poser.ini

Open it with a word editor.

Search for :  USE_OPENGL_1

Switch it to : USE_OPENGL_0

You're now using SreeD.

Quote - You can edit the Poser.ini. See link.

SWEET!!!! I can do stuff now! but lol it is pretty damn slow, but at least it's running so I know the problem is in opengl.

btw, something I don't understand about this opengl distribution rights.

I thought opengl is only available for freewares not commercial wares.

so how can smith micro write libraries based on opengl and sell the software?

now, I know sreed is an old render tool for poser, what some limitations for it compare to the current default opengl?

I hope?
You did try to upgrade your video card drivers to the latest versions????

Quote - I hope?
You did try to upgrade your video card drivers to the latest versions????

intel already stopped supporting my old ass netbook grade desktop board becase this thing is dated back in 2008.

I updated the drivers to as new as possible, but poser 2012 is just too new for this so I have to use sreed

Joe, thanks, I learned something today too.   Jan

Quote - I notice OpenGL in the middle of the call stack. So perhaps it crashed doing something about setting up the preview.

Switch to SreeD and see if you can get it to work.

And, no, software cannot examine your video drivers and tell you that you have a buggy driver that is about to crash. It just crashes.

If you're curious, the "Halting Problem" is one of the oldest and most venerated insights in computer science.

http://en.wikipedia.org/wiki/Halting_problem

Basically it says this: For certain very simple programs, it is possible to decide if it stops or runs forever by analyzing it, but in general it is not possible.

Decades later, a branch of computer science has evolved to define a set of rules and if you stay inside those specific rules, it is possible to solve the halting problem. This branch of computer science is called "formal methods" and it's one of my favorite things in the world.

However, people who write video device drivers and 3-D graphic programs can't even tell you what formal methods are, let alone follow them.

http://en.wikipedia.org/wiki/Formal_methods

Quote - Handwritten proofs of correctness need significant time (and thus money) to produce, with limited utility other than assuring correctness. This makes formal methods more likely to be used in fields where it is possible to perform automated proofs using software, or in cases where the cost of a fault is high. Example: in railway engineering and aerospace engineering, undetected errors may cause death, so formal methods are more popular in this field than in other application areas.

It is the generally few deaths associated with CG that make the economics favor buggy software.

Read this and looked for the like button or thanks button. I enjoyed this and found it useful. Thanks, BB.

Quote - Joe, thanks, I learned something today too.   Jan

As did I. Thank you, Joe.